Most Windows users are at least aware of the existence of the dreaded “Blue Screen of Death” (BSoD) that can occur when a particularly bad error surfaces. Rarely do Mac OS X users encounter the same sort of thing, but apparently that isn’t the case for some people upgrading to the newly released OS X 10.5 Leopard. According to most reports, the BSoD is caused by old versions of Unsanity’s Application Enhancer (APE) being present on the system.
Everything I’ve read about APE makes it sound pretty shady and it definitely isn’t something I’d install myself, so I figured that I’d be pretty safe once I get around to upgrading my own system. Well, Daring Fireball reveals that APE actually gets installed behind the scenes when the Logitech Control Center (LCC) is installed. Want to guess what I have installed? Yup, you got it.
So, before I even think about upgrading to Leopard, I’m going to have to figure out how to uninstall (and never reinstall; curse you, Logitech!) the LCC as well as make sure all remnants of APE are gone. So much fun.
Posted Tuesday October 30, 2007 in Computers & Software by Chris Curtis
that’s pretty crazy..never knew Mac had the dreaded blue screen of death haha…I’m a gamer and the first comp I had was a Mac and I would play Warcraft on it with no problems…sucks that they don’t really make games anymore..at least mainstream ones.
By Gargamel on February 13, 2008 at 05:52pm link
But it was incredibly annoying and impossible to diagnose myself, especially after my upgrade on my Macbook went so well.
By derya baykal on June 28, 2008 at 04:22am link
Copyright 2001-2010 Some rights reserved. ‡ Contact. ‡ Subscribe to Feeds.
XHTML, CSS. Powered by ExpressionEngine. Hosted on EngineHosting.
In addition to having that problem myself on my G5, I had a further problem that caused an immediate beachball when booting Leopard. Did the normal upgrade path and then Archive and Install, but no dice. After many many hours, I found on the Apple forums that DivX was to blame. So before upgrading, also go to /Library/Application Support/ and look for a folder named “DivXNetworks”. Either delete it or rename it (I just added ‘.prev’ to it), and the problem goes away. But it was incredibly annoying and impossible to diagnose myself, especially after my upgrade on my Macbook went so well.
By Derek Jones on October 30, 2007 at 08:59am link