Instructions on restoring the old drivers can be found here. Though, honestly, with all the other problems I might just recommend simply reverting to 10.5.2 with archive and install and the combo updater, followed by Leopard Graphics Update 1.0. As for Wifi, I didn't really see any problem in 10.5.2, and at least I was connecting and not crashing. As for Mac OS before OS X, everyone knew how horrid THAT was, and that's why I never even considered touching Macs until Tiger.
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.5.4
- Thread starter nanotlj
- Start date
- Sort by reaction score
Instructions on restoring the old drivers can be found here. Though, honestly, with all the other problems I might just recommend simply reverting to 10.5.2 with archive and install and the combo updater, followed by Leopard Graphics Update 1.0. As for Wifi, I didn't really see any problem in 10.5.2, and at least I was connecting and not crashing. As for Mac OS before OS X, everyone knew how horrid THAT was, and that's why I never even considered touching Macs until Tiger.
This command in the Terminal will get rid of most tearing:
Code:
sudo defaults write com.apple.windowserver Compositor -dict deferredUpdates 2Honestly, I just wish Apple would fix their most basic bread and butter apps: quicktime and DVD player. I'm really sick of seeing border artefacts in both players. Video quality was supposed to be Apple's ace up their sleeve, and they've dropped the ball on this one.
That changes the preference value in the window server on how Quartz Compositor (the window server) handles beam sync. A value of 0 completely turns it off, meaning the computer makes no effort to prevent tearing, ever. The upside is that means everything is instant and the computer wastes no resources trying to "nice things up," so to speak. A value of 1 turns it on in the "automatic" mode, making Compositor do a slight delay to sync all beams of pixels as it needs based on what it detects. A value of 2 forces beam sync on at all times, meaning the window server is always enforcing beam sync, even in scenarios where spending the resources/time might not be necessary (overall still windows, etc.). I haven't played with it myself, but since you're changing a preference in the window server, you probably have to restart the computer after changing the value to see it actually go into effect.
I have to use Force Beam Sync because ever since getting the 8800 GT, Safari pages tear while scrolling and it was bothering me. This was the only way to get rid of it. Pretty sad. I never got tearing in Safari with the 7300.
I'm willing to revise my ranking of Leopard .4 from "negative" to "neutral." For whatever reason, .4 was incredibly slow for a day or two immediately after install. Now that it's "settled in", the speed decrease has all but disappeared and apps are opening ALMOST as quickly as before. And the constant beachballs have more or less disappeared. But, my hard drive is getting pretty darn full, and I think that is affecting overall speed. I'll be more conservative in the future with these upgrades, for sure.
Recent discussions stated that .4 activates code that was included in the .3 update, where .3 was substantially larger. It is possible that Apple planned these sets of code to be sent separately to deliver dormant code that can be activated as a defense against jailbreak and activation mods. They may have been sent separately to help camouflage its discovery.
Sounds like a description of a trojan to me.
Well, if Apple is going the Sony way, I may just have to reconsider which company I buy my next notebook from, just like I reconsidered whether to ever buy another Sony product again when they pulled their rootkit shenanigans. Good going, Apple.