Steve Ballmer Authored the Windows 3.1 Ctrl-Alt-Del Screen
Nerval's Lobster writes According to Microsoft developer Raymond Chen, Steve Ballmer didn't like the original text that accompanied the Ctrl-Alt-Del screen in Windows 3.1, so he wrote up a new version. If you used Windows at any point in the past two decades, you can thank him for that infuriatingly passive 'This Windows application has stopped responding to the system' message, accompanied by the offer to hit Ctrl+Alt+Delete again to restart the PC (and lose all your unsaved data).
Update: 09/09 15:30 GMT by S : Changed headline and summary to reflect that Ballmer authored the Ctrl-Alt-Del screen, not the BSoD, as originally stated.
This story belongs in idle.
Hail Eris, full of mischief...
E pluribus sanguinem
Nothing will ever top "Guru Meditation" :)
I'd rather get some cryptic information about stop codes or an error message than a condescending sad face accompanied by a reboot request. At least I can look up the code and get a ballpark idea what the issue is without firing up windbg.
Well, at least it doesn't have a childish sad-face imoticon like the Windows 8 version.
Brave Sir Robin ran away. ("No!") Bravely ran away away. ("I didn't!")
+++OUT OF CHEESE ERROR+++
A feeling of having made the same mistake before: Deja Foobar
Applying critical patch 42 of 13,699,364...
So this is something you'd prefer?
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Did he also decide to produce the Hex output that is entirely useless and without merit? I understand that's for debugging purposes, but who decided that was a good idea to leave in for a consumer-level OS? Seriously.
If telephones are outlawed, then only outlaws will have telephones.
BSOD happens when the kernel detects memory corruption. With a hybrid monolithic kernel like Windows that means all bets are off and continuing could very well case damage more damage.
Even if the memory corruption happens in an USB driver, it can overwrite critical kernel memory.
Incidentally, you *do* get more information. The kernel will initiate a kernel dump which can be investigated later.
Reading slashdot one-liner: (irm http://rss.slashdot.org/Slashdot/slashdot).rdf.item | fl title,desc*