Slashdot Mirror
Blue Screen of Death for Mac OS X
An anonymous reader writes "Possibly nothing in the OS world has as much of a bad rap as the infamous BSOD (blue screen of death) in Microsoft Windows. On the other hand Apple hides the ugly kernel panics behind a nice looking GUI which only tells you its time to restart your dead system. Interestingly Mac OS X kernel has a secret API which lets you decide what your kernel panics are going to look like! In this Mac OS X Internals article Amit Singh explains how to use this API. Apparently you can upload custom panic images into the kernel and there's even a way to test these images by causing a fake panic. The article also shows the ultimate joke is to upload an actual BSOD image for authentic Windows looking panics right inside of OS X."
It's not like Microsoft invented it, either. I remember these quite unfondly. Before that I had a frozen screen on a C64. And before that I had stopped lights on the PDP-11 display. And before that we had random characters all over the screen of Ohio Scientific (OSI) computers.
But Microsoft is widely credited with perfecting the BSoD and giving it fame.
A system crash with a tasteful little box can be as easily dispised as all the the preceding. I suppose, like everything Apple is doing these days, they've given it a certain panache and now everybody will want one.
A feeling of having made the same mistake before: Deja Foobar
I, for one, welcome our new department-wide goatse.cx kernel panic message.
Any of you guys hiring?
Eloi are stupid, throw morlocks at them!
The Win32 BSOD does give you better information so you can try to diagnose the problem.
Which is kinda lacking in the OSX Panic screen.
Your hair look like poop, Bob! - Wanker.
That's not NEARLY as cool as the car crash sound Macs used to make when they really, really, REALLY blew up fierce. Get a good pair of speakers, and that sound would scare the tar out of everybody in the area!
I think it only happened to me once, on a junky old LCIII, while I was just working. There was a key combo to induce it on boot, though, and I got a lot of mileage out of that...
Why yes, I AM a rocket scientist!
"The article also shows the ultimate joke is to upload an actual BSOD image for authentic Windows looking panics right inside of OS X."
Ya! and then we could like, (snicker, snicker) we could like, bring up pictures of toilet paper on the monitor (snicker, snicker) and they would think (hehe, snicker) they would think they got T.P.'ed! HAHAHAHA!!!!!111!!!
Did anyone else just develop a twitch in their left eye?
THis includes GUIs etc. That's why a simple text-based BSOD or oops handler is a better idea than something that tries to do a whole bunch of cute graphics etc (which relies on a whole lot more hardware & software to be working properly).
You are so not a Mac owner based on these statements.
$30 Off All Plans: Use code TRIPLESAWBUCK
You young punks and blue-screens-of-panic blah, blah blah!
...In my day, we didn't even HAVE screens, just a blinking light and if that light ever stopped blinking, you knew there was trouble, boy...
Height: 38U, Weight: 0 Newtons, Eyes: #0000FF, OS: Gray Matter 1.0 (Alpha)
The graphical version takes slightly fewer resources. You have to run a single buffer through an RLE decompression routine directly out into a linear mapped framebuffer. To display text you actually have to use all of the console code. Remember, there is no hardware console, so you have to actually do all the text element positioning in software, and the graphics card is in exactly the same mode either way.
It does not take appreciably more resources either way, and both code paths are fairly simple and well tested.
... Macs Crash Different
;)
And don't get me wrong, I'm typing this on a Mac and I would not trade it for anything else out there
Obviously you are NOT ready for the Mac. Come see the light, friend.
Do you really think that Apple have decided error codes and detailed crash reports are not important?? No, of course they have not. There are two reasons Apple does this.
1) The truth is that the infamous blue page of kernel farts that windows spews out are only to technicians or sysadmins. The home user, and in fact, the power users, can do nothing with it. Nothing, of course, except Google for the stop code and hope Microsoft has a techhelp article on what it means. You can reply to this and say that
makes perfect sense to you... but you'd be lying. I know that the relevent part is 8E but 99% of users NEVER NEED TO SEE THIS and will NEVER USE IT.
Back to Apple. Apple has a little ditty called the "CrashReporter" and it has an OSX front-end to the system's log filed in
2) What do you do with the BSOD info displayed?? A true nooblar would write it all down. That's a waste of time, becuase its also in Windows' system log. Assuming you're going to Google for it, you would presumably reboot the machine, right? So why did we even need to see the error when it happened? The machine is up not, and the logs are visible...??
Bottom line: Apple's goal is to keep things simple, clean and friendly. What would your parents rather see?
Which one?
P.S. - Don't even think about saying "what happens if you cant boot." If that is the case, remove the new hardware. Otherwise you are in DEEP trouble... the code doesnt really matter and you'd actually be better off reading the error from
There are 10 types of people in the world. Those who understand binary and those who do not.
Excuse me, Sir, but that is a misunderstanding on your part. Mac OS X does not overwrite track zero just because the disk is full.
What you have experienced is the phenomenom of Mac OS X getting caught up in: "ups, the disk is full - so now I can't save any (system) preferences." Any files written during this will end up as zero-byte files.
There is no magic "QuickTime will overwrite vital systemfiles, to which only root has access"-routines.