Jump to content
15 posts in this topic

Recommended Posts

An apple support article refers to users experiencing a "Blue Screen for an extended period of time after doing an upgrade install of Leopard." Turns out this is caused by an application called "Application Enhancer"

It had to happen sooner or later! The Blue Screen of Death meets Mac OS X! Note the avoidance of the word "Death" in the article, even though it prevents you from starting your computer.

 

The article: http://support.apple.com/kb/TS1545

Sorry, I saw this on Apple's feed of RECENT Mac OS X support articles, and seeing no date on the article, assumed it was recent. I did not think apple would create a whole support article on a bug in one of the earlier versions of leopard.

Are you from the Mars? It was a bug in last year after Leo official release.

It's actually a problem with Application Enhancer, not really with OS X. "APE" is not made by Apple - it's made by Unsanity to change parts of the OS that Apple didn't intend to be changed. It can potentially cause problems with other applications, and when the OS is updated, and APE no longer works right, things happen like not being able to boot. Unsanity should make it so APE is disabled when the OS version does not match what it was made for.

Must not of read the article fully. Ooops. Maybe this should be moved to laughs now? I posted it for the fact that it was a blue screen, extremely similar to Windows' infamous "Blue Screen of Death."

Only similar in that they're both blue. :rolleyes: The Mac "version" of the blue screen is just that - a blue screen. The background color, before the background picture loads, is plain blue, which is where it was hanging.

It's actually a problem with Application Enhancer, not really with OS X. "APE" is not made by Apple - it's made by Unsanity to change parts of the OS that Apple didn't intend to be changed. It can potentially cause problems with other applications, and when the OS is updated, and APE no longer works right, things happen like not being able to boot. Unsanity should make it so APE is disabled when the OS version does not match what it was made for.

 

The Blue Screen of Death in Windows is really not a problem with Windows, either. It is a problem with a bad program installed, a virus, a hardware failure or error, or some other mishap that is usually the responsibility of the actual user. The operating system does not intentionally invoke a blue screen randomly just to screw with the user.

 

So in this respect, the blue screen on the Mac would be somewhat comparable to the Blue Screen of Death in Windows. Of course, with the only difference is that Microsoft actually planned to help the user if one ran into problems. Whereas, Apple decided to just let the computer freeze, or pop up with a black box that says "Restart Your Computer".

 

If I had to choose between the two, Windows Blue Screen or Mac Restart Dialog, I would choose the Windows Blue Screen of Death. I could at least take the information from the Blue Screen to troubleshoot my problem, instead of doing an endless reboot...

If you use something to modify the system, it should be disabled before upgrading the OS OR check with the people who made the haxie about it. Why doesn't anyone seem to understand this?

 

SDRacer--There is a way to report kernel panics to Apple that will give some wonderfully detailed information (should you choose to utilize it). Reboot and you'll get the pretty crash dialog box. For APE, all you have to do is never ever ever ever ever ever ever ever ever ever adopt an OS on the first day (Windows, Linux, or Mac). Let someone else work out the kinks.

Cool, Microsoft is not alone then. Lol. =p Just kidding...

SDRacer--There is a way to report kernel panics to Apple that will give some wonderfully detailed information (should you choose to utilize it). Reboot and you'll get the pretty crash dialog box.

 

Yes, I am aware of that, but the average user isn't. Whereas, the average user can easily see 0x00000fa on the top line, type that into Google, and get a good idea what the problem may be, or more importantly in most cases, what it may not be...

 

Just my PERSONAL opinion though...

I also had a blue screen of death after installing Hackintosh!

 

I installed it, and was transferring my files from another HD in the Setup Assistant, and then I got the BSOD, so i turned off the comp, and it wouldn't load, it just gave me the BSOD every time. Turns out that my comp fell asleep during the assistant and went unresponsive, just booted with "-x" went through the utility again without transferring, and all my files were transferred after all.

Yes, I am aware of that, but the average user isn't. Whereas, the average user can easily see 0x00000fa on the top line, type that into Google, and get a good idea what the problem may be, or more importantly in most cases, what it may not be...

Funny :D The average user sees hexadecimal code. The average user probably doesn't even know what hexadecimal is, let alone what the text on a BSOD means. When greeted with a BSOD, the average user gets a mild heart attack, resets, prays to whatever god they swore allegiance to and hopes that their computer will boot normally.

They don't write the stuff down to search Google for it :D

That's probably why Apple handles it this way, because they full well know that the average user gets weak in the knees when greeted with whatever they are not familiar with :)

The Blue Screen of Death in Windows is really not a problem with Windows, either. It is a problem with a bad program installed, a virus, a hardware failure or error, or some other mishap that is usually the responsibility of the actual user. The operating system does not intentionally invoke a blue screen randomly just to screw with the user.

I think that's false. I'm pretty sure ME was made solely to show off the BSOD every 20 minutes or so.

×
×
  • Create New...