Longhorn: Fewer BSODs, More RSODs
Jan Theofel writes "Windows Loghorn will present you less BSOD. Joi Ito reports that Windows Longorn will get additional ROSD (red screen of death) for 'really bad errors.' So you will get less BSOD but some new RSOD. You can find a ROSD screenshot in a virtual machine in his weblog entry."
It's always nice to see Microsoft adding new "features". Now they can tout Longhorn's decreased BSOD occurrences. Although I'd think they'd wanna avoid red screens as they are angry colors.
Microsoft Sucks, F/OSS Rocks. I get mod points now right?
So where are the yellow and orange? Looks like MS has been taking advice from Tom Ridge.
Dont forget NetworkMirror :)
. ito.com/archives/2005/05/07/bsod_upgrades_to_rsod_ in_longhorn.html
http://www.networkmirror.com/adYJGbG8ajC3f55y/joi
What exactly is a really bad error? I mean, a bad error versus a really bad error? That warrants a color change, anyways?
Frankly, I think customers ought to get rsod's for actually buying the damn product. That seems like a really bad error to me.
Longhorn is red-shifting... the release date must be receeding!
is add a Green Screen of Death. Then they'll be able to add together death colors to get much needed functionality for TrueColor Screens of Death.
If you are seeing BSODs almost daily, you either have faulty hardware or some seriously buggy drivers. Honestly folks, XP, and even 2000, BSOD very rarely.
Exactly. I have never seen my XP machine at home BSOD, even when the video card was failing to the point that it was adding random horizontal lines across the display.
At work, I saw 2000 BSOD on several servers when we applied an MS hotfix that conflicted with some sort of secret kernel patch they'd given us a few years previously for those same machines.
I saw 2k bluescreen one other time, when a workstation had a zip drive and the user installed drivers for it from 1997 or so.
Other than that, the only time I've seen it happen is if I make an OS image on one machine and then try and use it on another with different hardware. That's still stupid, but at least I know how to avoid it.
This is in an environment with close to 1000 Windows servers and about 25,000 Windows workstations.
"...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
In all seriousness though, XP isn't nearly as prone to BSODs ( or any other color :P ) , as 9x was. I'd still prefer my Debian or Gentoo though.
Stop the Slashdot effect! Don't read the articles!
That's innovation for you!
Engineering is the art of compromise.
I remember reading about the press conference where the Xbox was being hyped up.
The MS guy said "There will be no blue screen of death on the xbox"
I wish I'd been there, I'd have stuck my hand up and asked "What color will it be instead?"
In the free world the media isn't government run; the government is media run.
Is it related to this:
http://www.bbc.co.uk/wales/rsod/
Why, oh why, didn't I take the blue screen?
blog
No, it restarts the machine.
(If it could just restart explorer, that means it's recoverable and in user-space. I.e., not a BSoD, which happens in kernel-space. After all, explorer is just a shell.)
And yes the restarting is a pain, since then you have no idea what just happened. Even worse is when it happens on boot - yay restart loop. AFAICT, checking the event log does not give all the information available in the BSoD.
Actually, it isn't in the registry, it's in system.ini. I haven't been able to verify whether this works, as the computer I'm on hasn't had a BSOD since I got it. I take good care of it.
warning: This post is likely to contain gobs of dripping sarcasm. Consume at your own risk.