Leopard bites some early adopters
As expected, thousands and thousands of eager Mac users rushed out to buy and install the new version of Mac OS X, Leopard, over the weekend. And for some it did not go well.
The most common Leopard install problem, in all its cruel irony, is a Windows-like Blue Screen of Death as the Mac nears the end of the install process. Affected users report a system hang with a blank blue screen. Ugh.
The finger of blame has pointed mainly to third-party software from Unsanity, specifically its Application Enhancer system hack that enables several of the company’s utilities to alter parts of the Mac operating system (they’re actually called “haxies”). As a long-time fan of Unsanity’s FruitMenu, which creates a fully customizable Apple Menu, I have had APE installed on my Macs for years. It’s unfortunate, if not surprising, that such software would create problems with a new version of the Mac OS.
Unsanity says the problem could be caused by incarnations of APE earlier than version 2.0 that users still may be running on PowerPC-based Macs. Previous versions of APE won’t run on Intel-based Macs, so these newer Macs appear to be immune to the problem.
Some affected Mac users who found a way to delete the APE components were able to install Leopard successfully. An easier option for less technically adventurous users afflicted with the dreaded blue screen is to reboot the Mac with the Leopard DVD and re-install using the “Archive and Install” option (instead of the default “Upgrade” option). This should remove the offending components and allow Leopard to install properly.
To make matters worse, some users have reported unusually long install times apart from the APE issue. Apparently the installer does a full hardware check before rebooting the system. Some who called Apple’s support line said they were told this process could take up to three hours. Because the APE issue causes a permanent hang at the same point in the installation, many users can’t be sure how long to wait before giving up and attempting a re-install.
My advice: Use “Archive and Install” and be patient, no matter how much the wait kills you.



Comments
APE can also cause system problems in OS versions earlier than 10.5, like preventing your Apple menu bar from displaying. See Unsanity's uninstall document:
http://unsanity.com/support.php?vf=15
Posted by: Peter | October 29, 2007 2:48 PM
Blue screen of death? In Macland, isn't it aqua? :)
Posted by: Neil Anderson | October 29, 2007 3:48 PM
Everyone knows that "hack" is only one letter away from "ack!" Why should it surprise anyone that a user-hacked OS can't sustain a complex upgrade? And why would that user blame Apple?
Posted by: GSJohnson | October 29, 2007 4:57 PM
Ya..what's with this 'Leopard bites adopters', when the issue is with a third party system HACK??
How 'bout you refraise that to 'Third party system hack bites Leopard'??
Geez...
Posted by: Nodrog | October 29, 2007 6:35 PM
I just upgraded 2 systems (mac pro and a mac book pro).
The mac book pro rebooted just fine and I played with it for a bit. I rebooted the unit again and it forever stayed with the spinning wheel. I booted using the option-v key combo to see the kernel messages....it seemed to of gotten stuck in an infinite loop over some "mDNSDaemonInitialize failed" failing to initialize. Quick look on the internet yielded nothing for a failure. Looking for mDNS... I found only the source on opensource.apple.com (I think I will leave the kernel debugging for the guys in cupertino) I am currently re-installing the os by forcing a boot from the dvd. Not sure if this is going to be a real "install" or a "refresh". My system was running 10.4.9 x86.
Posted by: Chris Collins | October 30, 2007 12:47 AM
See this Daring Fireball article.
Unsanity really has no business installing its software in the /System/Library/ folder, which Apple explicitly prohibits.
They should really own up, and either make a public apology or take the rap.
Posted by: JC | October 30, 2007 1:03 AM
Apple has posted a page in their online support area regarding this issue:
http://docs.info.apple.com/article.html?artnum=306857
Posted by: Dave Zeiler | October 30, 2007 2:01 AM