4850, but that's not the point now is it? The fact is: the card can handle it (as shown in Windows 7 through Bootcamp). OpenGL can handle it (as shown in OSX with the 5000 series). So why can't the 4850 in OSX handle it?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases Mac OS X 10.6.5
- Thread starter MacRumors
- Start date
- Sort by reaction score
4850, but that's not the point now is it? The fact is: the card can handle it (as shown in Windows 7 through Bootcamp). OpenGL can handle it (as shown in OSX with the 5000 series). So why can't the 4850 in OSX handle it?
Airprint have been working all the time with iOS 4.2 GM and Mac OS X 10.6.5 10H574. If you don't believe me, check this video I have made now to prove it. Or may all the papers that I printed with these two versions are just a composite effect or just magic... I guess if those who have problems to make it work have upgraded to 10.6.6 and then tried to downgrade to 10.6.5. I don't know, but with the current iOS 4.2 GM and the last MOX 10.6.5 version it works perfectly.
http://www.filesonic.com/file/31174419/Airprint iPad.mov
http://www.filesonic.com/file/31174419/Airprint iPad.mov
I'm now running 10.6.5 on an iMac all seems to work great.
Also, I have a Canon printer connected via USB to an old Airport Express with the printer being shared by the iMac and my iPhone 4 can print to it. I've been able to do this for ages, in fact I could even do it on my old Edge iPhone too!
Now, I don't have iOS 4.2 GM or anything like that - but I do have a great little app called Air Sharing, which [in the full version] has the option to print to shared printers.
So my point is... if these 3rd party guys can do it - why not Apple too? I guess I'll wait till 4.2 hits my iPhone to see if Apples Air Printing is there or not... and if it isn't, then I'll still be able to print from my iPhone, so no bother.
What Canon printer model are you using, I have been wanting to do this for some time. However the canon app does not work with a MP980.
Before insulting someone, try it out for yourself. In the time you spent in this forum you could have answered your own question. But in case that is too difficult for you, see all the other responses that agree with me.
It would help if you said what the bug was, but I ran some iTunes actions and they worked just fine...
Yes. Simply put, file permissions can't change on their own accord, something needs to do it maliciously, or you've got a serious hardware problem. They simply can't change on their own accord.
You may see permission errors when doing a repair, but they're most likely all benign, such as a file being 664 when it was originally 644 or vice-versa. These are usually due to transient files being re-created after installation, when the running application has a different UMASK set to the one that initially created it. Certainly every error I've seen when running these repairs could be safely ignored as it was of this nature.
The repair permissions facility can only check permissions from software installed by PKG files (including anything installed via Software Update), as it simply extracts file details from the relevant BOM files, and changes permissions back to how they were when the relevant software was initially installed. It can't do anything with applications installed via other means, or with any of your own data files. So running to resolve issues with your own data files is obviously pointless.
Repairing permissions was necessary in the early days of Mac OS X when you could still boot up into Mac OS 9, as the latter OS didn't honour them properly. In particular some software installers than ran under Classic could be really problematic and mangle core operating system files. Since Mac OS 9 and Classic are no longer an issue, these problems can no longer occur.
So unless someone has been doing silly things in terminal with chmod, chown and chgrp, or there's a really badly behaved application, there's no point doing to unless you want to waste time.
I'd say my point is proven however all these arm chair techies will start crying how those logs are inaccurate.
Yes, Apple told you to do so...is that enough?
No. They did not.
Please post a link, if you believe that they did.
Haven't had any performance issues here with MTP, but I'm now able to turn off Bluetooth......Yeah.....My battery loves this update......
Have you ever got another (earlier) build of 10.6.5 installed?
If so, it could be the remains of that build. If not, great!
That's not too bad. The biggest issues I see are still when enabling the "Shading" setting. Something about Blizzard's shading code with the Mac drivers doesn't seem to mesh well.
I just got my first Mac on Monday, so it's fun to get to update so fast. But... I downloaded the update and let it restart. It got almost to the end and then failed. I should have written down exactly what it said, but basically "the update failed. please try to use software updater again once you restart"
Any idea why this would happen on essentially a brand new MBP? I'm downloading again right now and hoping for the best. Maybe I need the combo? I have no idea, being so new to all of this.
Any idea why this would happen on essentially a brand new MBP? I'm downloading again right now and hoping for the best. Maybe I need the combo? I have no idea, being so new to all of this.
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_1 like Mac OS X; en-us) AppleWebKit/532.9 (KHTML, like Gecko) Version/4.0.5 Mobile/8B117 Safari/6531.22.7)
I think it is becuase I am at Valencia Community College and they have the Internet limited to a max of 60 Kbps. It always slow.
I think it is becuase I am at Valencia Community College and they have the Internet limited to a max of 60 Kbps. It always slow.
I never upgraded to 10.6.6, doesn't work here. Did you install previous 10.6.5 betas? Someone else on this thread said that perhaps the Airprint files from that beta remained. Seems like a plausible explanation.
I'm surprised by all the repairs being made. I repaired permissions as part of a maintenance routine last week, so the repairs must be down to 10.6.5.
Doesn't hurt to do the repair. 10 minutes is nothing.
But archiving one Combo update file is far more efficient both in storage space terms and usage than going through multiple x.x.1 updaters. Some of us plan for contingencies as well as having to look after multiple Macs.