prostuff1
Sep 22, 06:29 PM
It was originally 250 and it was one that was up for the 100 dollar rebate. When i ordered it the website said that it was on back order adn that it would probably take 6 weeks to get here, which did not bother me seeing as i did not need it right away.
I just called them and they said it was discontinued and that they no longer carried it. Meaning that i ordered a printer 5 weeks ago that in the end would never get here. I am peeved because when i ordered the printer it was not discontinued. And while there are some other printers availible they are not the ones that i want!! I want the one i ordered 5 weeks ago.
Apple should at least honor the orders that were mad for that printer before it was discontinued!!
I just called them and they said it was discontinued and that they no longer carried it. Meaning that i ordered a printer 5 weeks ago that in the end would never get here. I am peeved because when i ordered the printer it was not discontinued. And while there are some other printers availible they are not the ones that i want!! I want the one i ordered 5 weeks ago.
Apple should at least honor the orders that were mad for that printer before it was discontinued!!
TheMacBookPro
Apr 24, 09:35 PM
Since the 11" and 13" are almost identical, I suppose that the technician guide mentioned here applies to both.
There is a specific service manual for each Mac, including the 11-inch Air.
I've uploaded it to Mediafire: http://www.mediafire.com/?745cwqotg5zjiq5 (mba_11_late2010.pdf)
Hopefully this helps someone.
Cheers
There is a specific service manual for each Mac, including the 11-inch Air.
I've uploaded it to Mediafire: http://www.mediafire.com/?745cwqotg5zjiq5 (mba_11_late2010.pdf)
Hopefully this helps someone.
Cheers
peapody
Jun 20, 10:00 PM
Tried to send you a pm, but your box is full.
Put me in line, if not first in line pending pics. I would like a machine of these specs. Consider me a serious buyer if there is no serious damage.
Put me in line, if not first in line pending pics. I would like a machine of these specs. Consider me a serious buyer if there is no serious damage.
yellow
Mar 7, 11:48 AM
By using a 3rd party application. Here are 2 choices.
http://www.versiontracker.com/dyn/moreinfo/macosx/15490
http://www.versiontracker.com/dyn/moreinfo/macosx/17924
You might also consider creating a password protected disk image (don't store the password in your keychain :rolleyes: ). And then mount it, copy your.. umm.. sensitive material into it... and then unmount it. Next time you mount it, you will be prompted for the password.
http://www.versiontracker.com/dyn/moreinfo/macosx/15490
http://www.versiontracker.com/dyn/moreinfo/macosx/17924
You might also consider creating a password protected disk image (don't store the password in your keychain :rolleyes: ). And then mount it, copy your.. umm.. sensitive material into it... and then unmount it. Next time you mount it, you will be prompted for the password.
more...
s2dio
Apr 23, 01:31 PM
ifixit.com.
'Nuff said.
sorry, I should have mentioned that I've checked ifixit.com, and they have no specific directions on that. All they say is "Remove the following ten screws: Two 9 mm Torx Plus screws, Eight 2.6 mm 5-point Pentalobe screws. To reassemble your device, follow these instructions in reverse order."
'Nuff said.
sorry, I should have mentioned that I've checked ifixit.com, and they have no specific directions on that. All they say is "Remove the following ten screws: Two 9 mm Torx Plus screws, Eight 2.6 mm 5-point Pentalobe screws. To reassemble your device, follow these instructions in reverse order."
robbieduncan
Apr 24, 07:54 AM
Actually there is a malloc, it's embedded in the memcpy.
My mistake. But the underlying problem is the same: the address of returnElement is on the stack. The address of the memory the at malloced in the call to memcpy is "lost" as it is never saved into a variable. So that malloced memory is leaked.
But, if I understand you correctly, the act of copying from the heap to the stack has the same effect of free()?
No. Absolutely 100% not. You have allocated space on the heap with the malloc. The malloc returned the address for you to free later. You did not save this address so cannot call free but that is OK as memcpy also returns the destination address (so as you can put the memcpy and malloc in one line like you have). But you fail to save the address their, instead dereferencing the pointer and saving that value in a variable. So at this point the malloced space on the heap is leaked. This is a problem. The space you allocated on the stack for the double is fine: it will get cleaned up for you.
The solution is to split this into two lines. You need to have a void * pointer variable that you store the return from memcpy in. You can then dereference and cast the that into returnElement. And finally free the void * pointer returned from memcpy.
My mistake. But the underlying problem is the same: the address of returnElement is on the stack. The address of the memory the at malloced in the call to memcpy is "lost" as it is never saved into a variable. So that malloced memory is leaked.
But, if I understand you correctly, the act of copying from the heap to the stack has the same effect of free()?
No. Absolutely 100% not. You have allocated space on the heap with the malloc. The malloc returned the address for you to free later. You did not save this address so cannot call free but that is OK as memcpy also returns the destination address (so as you can put the memcpy and malloc in one line like you have). But you fail to save the address their, instead dereferencing the pointer and saving that value in a variable. So at this point the malloced space on the heap is leaked. This is a problem. The space you allocated on the stack for the double is fine: it will get cleaned up for you.
The solution is to split this into two lines. You need to have a void * pointer variable that you store the return from memcpy in. You can then dereference and cast the that into returnElement. And finally free the void * pointer returned from memcpy.
more...
alansmallen
Jun 3, 04:27 PM
Wanted to clarify that it comes with all accesories except for headphones.
CaoCao
Apr 24, 12:09 PM
A grease monkey can change almost anything about a Mac Pro whereas MBPs are PITAs to upgrade
more...
zedsdead
Mar 19, 08:09 AM
The next Mac Mini should be fine for that. If as hoped it gets a Sandy Bridge processor it'll make the MacBook Air look terribly slow in comparison for CPU intensive tasks, especially if you put a SSD in the Mini.
As for EyeTV, the current Mini isn't as powerful as many of us would like, but I find it to be adequate. Hopefully the refresh will correct this and allow smooth playing of live sport in HDTV using progressive scan.
I think part of the issue was the 2.13 core2duo processor in the Macbook Air, but I agree that the next Mac Mini should be much more powerful. The Graphics Card will be a downgrade, but shouldn't be that much of a difference.
As for EyeTV, the current Mini isn't as powerful as many of us would like, but I find it to be adequate. Hopefully the refresh will correct this and allow smooth playing of live sport in HDTV using progressive scan.
I think part of the issue was the 2.13 core2duo processor in the Macbook Air, but I agree that the next Mac Mini should be much more powerful. The Graphics Card will be a downgrade, but shouldn't be that much of a difference.
b-rad g
Mar 5, 04:31 PM
Been in the process of ripping and encoding my DVD collection to the Mini for about a month now. Have been using Handbrake only to do the entire process so far, and usually can only get about 3 a day after work.
Today decided to try Rip It to pre-rip a bunch and the queue them up in Handbrake so I can leave it running. The Rip It part has gone really well as I ripped 15 DVD's in a row in a matter of hours.
But now have started the encoding part, and Handbrake is crawling!:(
When I was using Handbrake for the entire process I was averaging around 30 fps. But now I have all rips queued up and the first is doing around 10 fps! What's the deal? I figured it would be faster encoding from HD instead of DVD.
Also tried to encode Hunt for Red October and it says "Suspected RCE Region 1". Is there any way to remove the region from ripped file?
Hopefully someone has been through this before and can help me out.
Today decided to try Rip It to pre-rip a bunch and the queue them up in Handbrake so I can leave it running. The Rip It part has gone really well as I ripped 15 DVD's in a row in a matter of hours.
But now have started the encoding part, and Handbrake is crawling!:(
When I was using Handbrake for the entire process I was averaging around 30 fps. But now I have all rips queued up and the first is doing around 10 fps! What's the deal? I figured it would be faster encoding from HD instead of DVD.
Also tried to encode Hunt for Red October and it says "Suspected RCE Region 1". Is there any way to remove the region from ripped file?
Hopefully someone has been through this before and can help me out.
more...
Jameschillman
Jun 22, 05:36 AM
Yup i'll be heading down but haven't decided on a time to be honest. Wasn't really expecting there to be many people going there!
Id imagine i'd be along sometime after 7, I wonder roughly what kind of stock they'll get!
Id imagine i'd be along sometime after 7, I wonder roughly what kind of stock they'll get!
treehorn
Apr 23, 09:34 PM
So H.264 is a very compressed format. That sets off a flag right there. Ideally you wouldn't be provided footage in such a lossy format.
Taking the H.264 footage and converting it to DV NTSC is essentially compressing it again (albeit a lesser compression), but it is still increasing the generation count. Instead, I would try throwing it into compressor and transcoding to apple prores 422. That should hopefully alleviate any loss of quality.
But sadly we don't live in an ideal world :) And this is footage given out for television usage, believe it or not...(do CBS Sunday Morning and the Today Show really like getting footage in compressed h.264?)
I'll try prores 422. My thought was that as the the other footage is DVPro NTSC converting it to DV NTSC would be transcoding to a closely matching format. But it didn't seem to help any...
Taking the H.264 footage and converting it to DV NTSC is essentially compressing it again (albeit a lesser compression), but it is still increasing the generation count. Instead, I would try throwing it into compressor and transcoding to apple prores 422. That should hopefully alleviate any loss of quality.
But sadly we don't live in an ideal world :) And this is footage given out for television usage, believe it or not...(do CBS Sunday Morning and the Today Show really like getting footage in compressed h.264?)
I'll try prores 422. My thought was that as the the other footage is DVPro NTSC converting it to DV NTSC would be transcoding to a closely matching format. But it didn't seem to help any...
more...
charlestrippy
Oct 27, 01:40 AM
heh, i'll just wait for USF to get it next week for $69 :D
alphaod
Apr 20, 07:02 PM
YouTube: video (http://youtube.com/watch?v=CD2LRROpph0)
That's just sadistic! :eek:
That's just sadistic! :eek:
more...
kntgsp
Sep 2, 07:15 PM
Wow, thought this thread was deleted already.
Anyway, yea hard to ship something when UPS store is closed for labor day weekend haha. I was at a wedding in Salt Lake until Friday, I made that clear to those interested in buying it. It's being shipped two day air on Tuesday everyone, so stop wigging out, I've sold many things on here and never cheated anyone. And thank you w8ing.
:rolleyes::rolleyes:
Anyway, yea hard to ship something when UPS store is closed for labor day weekend haha. I was at a wedding in Salt Lake until Friday, I made that clear to those interested in buying it. It's being shipped two day air on Tuesday everyone, so stop wigging out, I've sold many things on here and never cheated anyone. And thank you w8ing.
:rolleyes::rolleyes:
zelmo
Mar 31, 08:10 AM
A-ha! So one version is good enough for a dabbler, as suspected.
Excellent, Smithers [/Mr. Burns];)
Excellent, Smithers [/Mr. Burns];)
more...
JoeG4
May 6, 04:22 PM
http://img12.imageshack.us/img12/7/ateaseuserfolder6923567.png (http://imageshack.us/photo/my-images/12/ateaseuserfolder6923567.png/)
Uploaded with ImageShack.us (http://imageshack.us)
http://www.technewsdaily.com/images/stories/mac-osx-lion-launch%20pad_101020-02.jpg
How far we've come.
Uploaded with ImageShack.us (http://imageshack.us)
http://www.technewsdaily.com/images/stories/mac-osx-lion-launch%20pad_101020-02.jpg
How far we've come.
the future
Oct 26, 03:02 PM
I haven't used this keyboard myself, but i've heard it comes pretty close to what you're looking for: http://www.macally.com/spec/usb/input_device/icekey.html
job
Oct 20, 04:01 PM
Originally posted by Rower_CPU
'Lemon is on page 4.
hah. not in post count. i was wondering about his physical location. haven't seen him on these boards in ages.
;)
'Lemon is on page 4.
hah. not in post count. i was wondering about his physical location. haven't seen him on these boards in ages.
;)
germanjulian
Jun 15, 05:32 AM
Hi,
anyone coming down? Who wants to meet up at 7am (or earlier?).
I shall bring cookies for everyone, mcdonalds for myself and some water (trying not to drink to much :D)
anyone coming down? Who wants to meet up at 7am (or earlier?).
I shall bring cookies for everyone, mcdonalds for myself and some water (trying not to drink to much :D)
spoonyfreshh
Feb 20, 06:38 PM
donated.
iSaint
Dec 16, 07:52 AM
Well, it can survive a hard fall of about 4 feet, I know that for sure. I own a G3 iBook without wireless (I'm broke) so I always have a 100 foot ethernet cord trailing behind me. Somehow, as I was walking from one room to another, I got tangled up in it, did a funny little twirly-dance, practically threw the iBook out of my way (if I would have landed on it there would surely be no chance of survival) and fell to the ground face first (ouch). The iBook landed hard on its left side. It was powered on, as a matter of fact I was browsing this forum. The sound it made on contact was horrible to say the least. But I'll be damned...so far not a thing wrong with it! When I say it took a hard hit I mean it REALLY took a hard hit. When I picked it up off the floor I wasn't breathing...it felt like my heart had stopped. The screen was black, all was quiet...for about 3 seconds. All of a sudden the screen lit up and it was right where I left it. I just had to reconnect to the internet and I was rolling again. Just wanted to share that with everyone, for I am blown away that the thing isn't dead. If a moose like me can't kill this iBook it is one hardy machine;)
Maybe it's time to get that wireless card (http://forums.macrumors.com/showthread.php?t=167333)!
Maybe it's time to get that wireless card (http://forums.macrumors.com/showthread.php?t=167333)!
Legion93
Apr 23, 09:43 PM
He used a Mac.
Image (http://boskolives.files.wordpress.com/2009/11/powerbook_5300_screen.jpg?w=400&h=263)
Looks like Mac OS X Cheetah or Puma :d
Image (http://boskolives.files.wordpress.com/2009/11/powerbook_5300_screen.jpg?w=400&h=263)
Looks like Mac OS X Cheetah or Puma :d
shenfrey
May 6, 04:31 PM
Just run it at its native resolution, if the something you find is to small to read/see you can always zoom in or of course change the font : )
0 comments:
Post a Comment