Originally posted by lkrupp
Let's see now. 10.3.7 is nice and stable. NO, it's not stable. 10.2.8 was a nightmare. No it wasn't. 10.3.5 was the "worst update ever" (from an Apple Discussions thread). 10.3.6 was a "disaster" (from MacFixit).
When will it finally sink in to people that problems with updates are mostly due to individual system quirks, corruption, etc., than the update itself?
Not always. Sometimes there are problems with the updaters from Apple even if you have no third party hardware or software.
I upgraded a stock Tangerine iBook by formatting the drive and installing MacOS X 10.3.0 Panther from the original CDs. Let me repeat, this was a pure, clean machine. I restarted and the machine ran fine. I installed no other software or hardware. I ran no applications. I changed no settings.
I then immediately ran Apple's Software Update and let it install what was suggested which included the Combo update to MacOS X 10.3.7. At the end of the update the machine rebooted and the hard drive was no longer functional, mountable or even visible using the Disk Utilities. I can hear the hard drive spinning and it sounds normal. But there is no access happening and it is not available. Disk Utilities does not recognize the hard drive's existance. I have reset PRAM, NVRAM (Open Firmware), PMU, etc, etc. Still no hard drive. There is no individual system quirk here and I started with a working machine.
The Combo 10.3.7 update destroyed my previously working clean stock Apple computer.
Fortunately I have a backup of the data and have moved that to a new machine. The iBook awaits my futher administrations when I have the time to waste on it. It has already occupied more than a day and a half of my time. Taking apart these particular computers is a trip. I will try that drive in another machine and see if I can revive it. I'll also try another drive in that machine.
Sometime Apple screws up. 10.2.8 was an excellent example. My one experience with 10.3.7 seems to be another example. This is why I wait to try new updaters and when I do I do it on one machine that is backedup.
I've been working with and programming Mac's since the original 128 and with Apple's computers before that to the original Apple I. I know what I'm doing, apparently the updater didn't.
I'll wait and see what 10.3.8 is like and not upgrade any other machines to 10.3.7. On the other hand, 10.3.5 is running fine for me. 10.3.7 works for some people. Stick with what ever works for you. But be paranoid - when in doubt, backup carefully... I'm always in doubt.