Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Has larger effect than obvious ...

Worked fine on my wife's 2006 white MacBook too.

Although it is only 275 MB in size, my first Time Machine backup after the install was a whopping 1.55 GB, so it must spread some changes around.
 
Wirelessly posted (Mozilla/5.0 (iPod; U; CPU iPhone OS 4_3_3 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8J2 Safari/6533.18.5)

Apple wins. Again.
 
Seems like they changed how digital out audio is handled. It isn't sending a continuing signal anymore

Same here - kinda annoying watching a flick where audio has hiccup. And also Time Machin is not working... Crap!


iMac 21.5 3.6 IC i5 8 GB
 
Installed without a hitch here on my early '08 MacBook. So nice having a system that runs as good as it did on day one, even after all the OS and point releases along the way.
 
Another failed SW update for Alu imac 2007

It's pretty-much been the pattern since Snow leopard upgrade,
software update -
download,
shutdown to install,
install hangs for 1-2 hours, or until I'm bored/pissed off at it, again.
forced power-off
download stand-alone installer
works perfectly.
WTF?

Is the late '07 alu imac now so legacy, or is clean-install needed?
Repair permissions does sweet FA btw, so before you ask!

I remember this kind of problem was why I never bought anything MS since win98 and went Linux, and then later Mac because I was bored of DIY everything.

*wanders off grumbling*
 
Has anyone noticed their screen turning black for a second or two and then fading to blue instead of just going from grey boot screen to blue after the portion of the boot process where the Apple logo with the spinning wheel completes? I'm seeing this on a 2010 MBP 15".
 
Has anyone noticed their screen turning black for a second or two and then fading to blue instead of just going from grey boot screen to blue after the portion of the boot process where the Apple logo with the spinning wheel completes? I'm seeing this on a 2010 MBP 15".

A fickle observation to say the least.
 
It's pretty-much been the pattern since Snow leopard upgrade,
software update -
download,
shutdown to install,
install hangs for 1-2 hours, or until I'm bored/pissed off at it, again.
forced power-off
download stand-alone installer
works perfectly.
WTF?

Is the late '07 alu imac now so legacy, or is clean-install needed?
Repair permissions does sweet FA btw, so before you ask!

I remember this kind of problem was why I never bought anything MS since win98 and went Linux, and then later Mac because I was bored of DIY everything.

*wanders off grumbling*

Did you install Mac OS X Snow Leopard clean from day one? do you have third party extensions etc. installed? I've got Snow Leopard running on 5 machines raging from an early 2008 iMac through to a cutting edge 2011 iMac - none of them showing a single sign of problem.

One thing I do say, always use a combo updater - never had a problem using it.

I can assure you it's a problem. Here are just a couple of the many threads documenting the problem:

https://discussions.apple.com/thread/2792691

https://discussions.apple.com/thread/3126177

The issue must be specific to the magic mouse because right now I'm using the bluetooth 'Magic Pad' and the battery level shows up in the bluetooth drop down menu at in the 'System Preferences' pane. All I can suggest is to delete everything in your Library directory, reboot and allow Mac OS X to re-create all the *plists again.
 
One thing I do say, always use a combo updater - never had a problem using it.

People with 2010 MBAs who followed that piece of advice suffered greatly reduced OpenGL performance in games for 10.6.7. The Combo updater broke something on those machines. Not that the Combo or incremental update should be different, but somehow it did (maybe something to do with patch order in the bundle).

The solution was of course to reinstall, update to 10.6.6 and then apply 10.6.7 from software update instead of the Combo update.

Personally, I've never used the combo updater, never installed OS X from scratch (upgraded my old MB UB from 10.5 to 10.6 by running the installer in place) and never had any issues (I skipped 10.6.7 after reading the woes of others).

One thing I do say : Don't upgrade on day 1. Wait for day 2 after all the other people have been burned.
 
People with 2010 MBAs who followed that piece of advice suffered greatly reduced OpenGL performance in games for 10.6.7. The Combo updater broke something on those machines. Not that the Combo or incremental update should be different, but somehow it did (maybe something to do with patch order in the bundle).

The solution was of course to reinstall, update to 10.6.6 and then apply 10.6.7 from software update instead of the Combo update.

Personally, I've never used the combo updater, never installed OS X from scratch (upgraded my old MB UB from 10.5 to 10.6 by running the installer in place) and never had any issues (I skipped 10.6.7 after reading the woes of others).

One thing I do say : Don't upgrade on day 1. Wait for day 2 after all the other people have been burned.

1) What 10.6.7 issues did you experience (besides the font issue which was resolved quickly by Apple)?

2) When they suffered 'greatly reduced OpenGL performance in games' - how did they benchmark it? please point me to the exact posts of such issues if possible.

3) 10.6.8 has been problem free on day one - installed a 2011 MacBook Pro and iMac without any problems; nor did I have problems with my older hardware - either I'm the luckiest man on earth or I'm doing something right whilst those who are experience problems are doing something wrong.
 
The issue must be specific to the magic mouse because right now I'm using the bluetooth 'Magic Pad' and the battery level shows up in the bluetooth drop down menu at in the 'System Preferences' pane. All I can suggest is to delete everything in your Library directory, reboot and allow Mac OS X to re-create all the *plists again.
Yeah, it's a Magic Mouse problem although there are some threads reporting the same issue on the wireless keyboard too.

I deleted the com.apple.bluetooth.plist file but that didn't change anything. Just have to wait until 10.7 Lion. It's not a big deal as long as iStat Pro tells me the correct %.
 
Did you install Mac OS X Snow Leopard clean from day one? do you have third party extensions etc. installed? I've got Snow Leopard running on 5 machines raging from an early 2008 iMac through to a cutting edge 2011 iMac - none of them showing a single sign of problem.

One thing I do say, always use a combo updater - never had a problem using it.



The issue must be specific to the magic mouse because right now I'm using the bluetooth 'Magic Pad' and the battery level shows up in the bluetooth drop down menu at in the 'System Preferences' pane. All I can suggest is to delete everything in your Library directory, reboot and allow Mac OS X to re-create all the *plists again.

It was an update and install each time since the machine was delivered with Tiger.

I know the combo updates work, but the whole point of software update is to keep it simple. Won't somebody think of the Grand-parents?

;)
 
1) What 10.6.7 issues did you experience (besides the font issue which was resolved quickly by Apple)?

I didn't experience any issues, I never upgraded. But to answer your question :

Read my post again though, I stated the issue. People who used the combo updater for 10.6.7 to upgrade 10.6.6 suffered greatly reduced OpenGL performance in games on the 2010 MBA.

2) When they suffered 'greatly reduced OpenGL performance in games' - how did they benchmark it? please point me to the exact posts of such issues if possible.

The problem was that vector processing amounted to slow triangle output in the near matrix transformation subroutines... :rolleyes:

How do you think they benchmarked it ? Frame Rate Per Second. Lower FPS (by quite a margin) after using the combo update. Here's the main thread about it :

https://forums.macrumors.com/threads/1124748/

I'm not digging up more, have fun on the MacBook Air forum if you really want to see.

Oh, and while you're at it, look for 10.6.7 iTunes. iTunes was an unusable mess after the 10.6.7 update for people on the 2010 MBA :

https://forums.macrumors.com/threads/1125335/

BTW, this required an iTunes patch to fix, so it's not like it's all in people's head.

3) 10.6.8 has been problem free on day one - installed a 2011 MacBook Pro and iMac without any problems; nor did I have problems with my older hardware - either I'm the luckiest man on earth or I'm doing something right whilst those who are experience problems are doing something wrong.

And still, not upgrading on day 1 is sound advice, words I live by. You never know what might creep up. Just wait for others to either get burned or not and then proceed or wait for the vendor to issue fixes.

This advice has served me well with every software patch and vendor out there, not just Apple.
 
Last edited:
I didn't experience any issues, I never upgraded. But to answer your question :

Read my post again though, I stated the issue. People who used the combo updater for 10.6.7 to upgrade 10.6.6 suffered greatly reduced OpenGL performance in games on the 2010 MBA.

But is it due to the driver itself or has Apple deliberately made the GPU clock scale towards the lower end to address possible heat concerns? I'm not excusing what has happened, I am just trying to work my head around the fact that you have the problem appear in MacBook Air but the MacBook Pro with the exact same chip doesn't appear to demonstrate the same sort of decrease in OpenGL performance

The problem was that vector processing amounted to slow triangle output in the near matrix transformation subroutines... :rolleyes:

How do you think they benchmarked it ? Frame Rate Per Second. Lower FPS (by quite a margin) after using the combo update. Here's the main thread about it :

https://forums.macrumors.com/threads/1124748/

I'm not digging up more, have fun on the MacBook Air forum if you really want to see.

There is no need to be an abnoxious prick about the situation - all I asked is how they benchmarked it, did they use in game statistics, Geekbench, GLView's own benchmark - all of which have their own quirks and could be software related (third party) or a setting in the operating system. I know it is 'cool' to get hysterical about things but how about standing back, taking a deep breath and calm down.

Oh, and while you're at it, look for 10.6.7 iTunes. iTunes was an unusable mess after the 10.6.7 update for people on the 2010 MBA :

https://forums.macrumors.com/threads/1125335/

BTW, this required an iTunes patch to fix, so it's not like it's all in people's head.

So it took 4 days to address the problem - again, does it justify your hysteria?

And still, not upgrading on day 1 is sound advice, words I live by. You never know what might creep up. Just wait for others to either get burned or not and then proceed or wait for the vendor to issue fixes.

This advice has served me well with every software patch and vendor out there, not just Apple.

I never said that you should upgrade on day one but I would take many of the problems with a grain of salt given the number of times that the problem is the user and what they've done to the machine.

It was an update and install each time since the machine was delivered with Tiger.

I know the combo updates work, but the whole point of software update is to keep it simple. Won't somebody think of the Grand-parents?

;)

Yeah I know what you mean - in theory delta updates should be a lofty cloud of scented loviness but in reality my experience in multiple platforms is that it never quite works out as perfect in practice hence I have no problems going around to my sisters house to install the latest update for her. Steve might want to believe that the world can be solved so easily with a bit of code magic but the reality is that computers are complex multi-functional devices and no amount of pixie dust can change that reality.

Yeah, it's a Magic Mouse problem although there are some threads reporting the same issue on the wireless keyboard too.

I deleted the com.apple.bluetooth.plist file but that didn't change anything. Just have to wait until 10.7 Lion. It's not a big deal as long as iStat Pro tells me the correct %.

Interesting, I opted for the wired keyboard so I wonder if something related to two wireless devices being hooked up.
 
It's pretty-much been the pattern since Snow leopard upgrade,
software update -
download,
shutdown to install,
install hangs for 1-2 hours, or until I'm bored/pissed off at it, again.
forced power-off
download stand-alone installer
works perfectly.
WTF?

Is the late '07 alu imac now so legacy, or is clean-install needed?
Repair permissions does sweet FA btw, so before you ask!

I remember this kind of problem was why I never bought anything MS since win98 and went Linux, and then later Mac because I was bored of DIY everything.

*wanders off grumbling*

Why not always just use the combo updater from Apple's site instead of Software Update?
 
Why not always just use the combo updater from Apple's site instead of Software Update?

Actually I probably will in future. In fact, the incremental installer from the Apple site always works and I haven't had to resort to the combo update, it is only the software update that fails. That's why it bugs me so much. It's not as if my level of third party programs is real - hack it yourself stuff.
 
But is it due to the driver itself or has Apple deliberately made the GPU clock scale towards the lower end to address possible heat concerns? I'm not excusing what has happened, I am just trying to work my head around the fact that you have the problem appear in MacBook Air but the MacBook Pro with the exact same chip doesn't appear to demonstrate the same sort of decrease in OpenGL performance

It was an issue with the combo updater on the 2010 MBA. I already said so.

There is no need to be an abnoxious prick about the situation

I don't like having to repeat things I already said. The question you asked was answered in the post you quoted. Next time, read and no one will be a prick about it (and insults are against forum rules).

I know it is 'cool' to get hysterical about things but how about standing back, taking a deep breath and calm down.

So it took 4 days to address the problem - again, does it justify your hysteria?

What hysteria ? You pretended updates never caused real problems because you've never had any, I dug up proof they did.

You keep using that word, yet there's no hysteria anywhere here. Simply me pointing out facts to you, and you having apparently a hard time reading my posts (twice now you've had me repeat stuff that is in the posts you quote).

I never said that you should upgrade on day one but I would take many of the problems with a grain of salt given the number of times that the problem is the user and what they've done to the machine.

Except as I've pointed out, there are real issues from these updates. To dismiss them as you are doing in a vain attempt at proving god knows what point is ludicrous. I never take reports of issues with a grain of salt, I wait patiently for confirmation and try to dig up the facts to know if I will upgrade or not.

That's not hysteria, that's simple logic. Let others break their stuff if it's going to break and then decide whether the update is worth it. For me, 10.6.7 wasn't, no matter how fine it worked once iTunes was upgraded and if I used Software Update instead of the combo.
 
... The solution was of course to reinstall, update to 10.6.6 and then apply 10.6.7 from software update instead of the Combo update.

Personally, I've never used the combo updater ... (I skipped 10.6.7 after reading the woes of others).

One thing I do say : Don't upgrade on day 1. Wait for day 2 after all the other people have been burned.

Hey Knight, did you upgrade to 10.6.8? (I'm on '10 MBA as well)
Do you think it's safe to use 10.6.8 combo (I'm still on 10.6.6 :rolleyes:)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.