Just how thick is Microsoft?

Send to a friend Print

Help more people find out about this story

Del.icio.us
StumbleUpon

Dan Warne16 November 2007, 11:39 AM

Just how thick is Microsoft? Everywhere you go, there are advertisements for how unstable Windows is. They're big. And blue. And deathly.


Just how thick is Microsoft? Everywhere you go, there are advertisements for how unstable Windows is.

You can see the ad on train arrival displays, airport screens, on the LCD display in elevators, on video games in entertainment parlours, on massive projections on the sides of buildings or even while Bill Gates is on stage demoing Windows.

BSOD in Times Square: high profile advertising for WindowsBSOD in Times Square: high profile advertising for Windows

Your bus is arriving: but you'll need to run CHKDSK /F first to find out whenYour bus is arriving: but you'll need to run CHKDSK /F first to find out when

Stable. Reliable. Dependable: as demonstrated by this Vista PC right here...Stable. Reliable. Dependable: as demonstrated by this Vista PC right here...

Thank god: Boeing doesn't use Windows to fly the autopilot.Thank god: Boeing doesn't use Windows to fly the autopilot.

Yes -- you know what I'm talking about: the dreaded bluescreen of death. Or if you're really behind the times and still running a beta version of Vista, you might even get the infamous red screen of death.

It's when Windows just throws up its hands and ditches its slick-as-spit Aero GUI altogether, in favour of a stark DOS-style text-mode screen that reels off some technical data that is largely unintelligible to the average user, like "0x0000001E, KMODE_EXCEPTION_NOT_HANDLED".

There's a whole group on Flickr dedicated to public bluescreens of death. There are some fricking huge examples. Like whole sides of buildings showing the bluescreen for days.

World's biggest BSOD?: Toronto's The Bay department storeWorld's biggest BSOD?: Toronto's The Bay department store

It has been giving Apple's Fake CEO endless material to work with.

Case in point from the Secret Diary of Steve Jobs: "See here. This woman says Dell shipped her a defective machine and when she complained they sent her four more, all of them also defective. The "defect," which still plagues her fifth machine is that her computer "goes to a blue screen, which indicates a serious error that requires the PC to be restarted." Poor lady didn't realize, apparently, that in the world of Windows this is not a defect. It's normal operating procedure."

Or this, also from Fake Steve, about the massive Toronto department store bluescreens above: "A few people have sent me this and asked if this was our work. They think maybe we rented these screens and did this on purpose. You know what? We didn't. You know why? We don't have to. That's the beauty of Windows. The wow is now. As in, Wow, that OS is wicked unstable, isn't it?"

It's confounding that Microsoft hasn't twigged to what an image problem the BSOD creates.

For all its multigazillion dollar marketing campaigns dreamed up by the "wow is now" geniuses, nobody at Microsoft seems to have twigged that the best thing they could do is do away with the ubiquitous bluescreen.

Nothing says "sloppy programming" better than a tech-dump bluescreen which says "yeah, ok, somebody's crummy software caused our kernel to fail, but we couldn't handle the fault elegantly enough to actually stay in graphics mode."

Apple twigged to this years ago in OS X, introducing an unassuming semi-translucent charcoal screen overlay that says "you must reboot your Macintosh" in multiple languages. Simple. Unintimidating. Actually quite visually attractive.

Kernel panic: much less panic-inducing than Microsoft's bluescreenKernel panic: much less panic-inducing than Microsoft's bluescreen

Admittedly, Apple's relatively elegant handling of a total system failure is a first in computing terms. It used to have a "sad Mac" face if there was a boot problem, and in really bad cases, the Mac would actually have a black screen and make a very alarming car crash noise.

The Amiga had "guru meditation " -- a cryptic error message upon total system failure

It seems to be a running joke among software engineers to make system failures either humorous or full of technical info to help the infinitesimally small proportion of users who happen to be software developers debug their software.

But I ask again: how thick is Microsoft? Seriously, nobody likes to get a BSOD. Isn't it time it was replaced with something slightly less offensive?


Post your comment



Comments

RSS feed Email alert

Jarrod Spiga:

Make it green, orange, red, whatever.

The one good thing about the BSOD (as far as I'm concerned) is that it often can tell you specifics about what caused the problem - especially when dealing with poorly written third-party system drivers. All the info that you need to diagnose many issues is there, in your face and in hue tones.

The BSOD (and the Linux kernel panic) has a place in my heart

My problem with the MacOS "black screen of lifelessness" (that sounds less harsh than BSOD) is that it tells you nothing. Yes, it may induce less panic to users who expect "everything to 'just work'", but the cause of the issue is neatly hidden away, only accessible after a reboot. The fact of the matter is, things stuff up from time to time, and no code is perfect - so you may as well go out with a bang! I don't want to die quietly - I want fireworks!

Or at very least, a "Flagrant System Error".

Maybe they should get rid of the blue and have animations of explosions in the background. Now THAT would be cool!

Perhaps it's just me. Maybe I like things more complicated? Maybe I cannot stand operating systems that are dumbed down to the point that anyone can use a computer? Maybe I need the occasional BSOD or Kernel Panic to keep me sane... Perhaps they should go even more offensive (yet not vulgar).

All that I know is that when I walk past an ATM/Departure Screen/Advertising Billboard/Kiosk that is displaying a BSOD, I, along with other IT bretheren, share a knowing smile. For the BSOD is more than just a kernel crapping its pants (OK, let's now change it to a brown screen) - it's proof that the more we rely on machines in day to day life, the more they rely on us to keep running.



29 February 2008, 8:32 PM (9 months ago)report abuse Send to a friend reply

Anonymous23132132:

It is accessable if it continues every reboot. just add -v for verbose mode to startup after pressing F8 during startup

29 February 2008, 8:49 PM (9 months ago)report abuse Send to a friend reply

David Flynn:

I see where Jarrod's coming from with this... maybe Microsoft needs to have a Mac-like friendly screen for the end user (after all, we're the mug punter  faced with this thing) but also dump the necessary tech details into a error reporting log, timestamped and accessible through a friendly error reporting app (call it 'WinWTF'!) on the Help menu.

This is where the tech would go (or the user, if on a phone call) to find specific details of the flaw -- ideally presented in a better-looking and easier-to-navigate UI than just a text dump, of course.

Just as long as we don't see The Return Of Clippy to put a friendly face on PC meltdowns. ("Hi! It looks like your PC is screwed. Would you like restart everything?") 



29 February 2008, 8:49 PM (9 months ago)report abuse Send to a friend reply

Mestara:

First time ever (4 years using mac) that I got the mac version so that in itself is something. But when I did boot back into OSX it gave me the option of reading a detailed report or continuing as normal.

29 February 2008, 8:49 PM (9 months ago)report abuse Send to a friend reply

Unko:

Dam Anonymous23132132 beat me too it.

29 February 2008, 8:49 PM (9 months ago)report abuse Send to a friend reply