Slashdot Mirror
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.
I guess they've FINALLY fixed the last issue that casues a blue screen of death with Longhorn. :)
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!
Speaking of reliability, I was just thinking how Microsoft could reduce the complexity of the next version of Windows, Longtooth, due in 2009.
Longtooth will include a tremendous amount of new features implemented in completely new code. Many, but not all, existing features would be reimplemented in VisualBasic.NET just for the heck of it, even if mature versions are already implemented in C or C++. Programmers making the new VisualBasic.NET code would not be allowed to look at the code that already exists, so that new ideas might be better implemented. The features will be chosen by random for reimplementation.
All Microsoft code would assume that any Microsoft code (the OS and any Microsoft applications) is secure. This code will always execute with no checks to make it run faster. All other code will be subject to Longtooth's new security system, dubbed Microsoft Longtooth Security Center 2003. This feature will give users more control over processes that execute in their computers. I will explain some of its features here:
To maximize security, Microsoft Longtooth Security Center 2003 will make certain assumptions about the user. For example, users who use Microsoft products are assumed to know what they are doing. However, users of 3rd party applications not made by Microsoft are always assumed to be complete idiots. Therefore, all user interface events occurring outside of Microsoft applications will trigger a safety mechanism.
For example, each time the user moves the mouse in an area not controlled by a Microsoft application, the user will see crosshairs moving across the screen to indicate where the mouse will be located. When the user stops moving the mouse, an authentication window will appear and state: "The user has requested that the mouse be moved to the location on the screen indicated by the crosshairs. This area of the screen is controlled by untrusted code that may cause damage to your computer, your documents, or your network. Do you wish to allow the mouse to move to this location?" Buttons for "yes", "no", "details", and "help" will be displayed.
Selecting "no" will cause the mouse cursor to remain at its previous location. Selecting "yes" will bring up another window, requesting the user's password to authenticate the movement of the mouse. If the user enters the correct password, the mouse cursor movement will be authenticated to that user and the cursor will be placed at the new location. Selecting "details" will display the X and Y coordinates of the new position, followed by warnings against using untrusted rogue code such as Linux.
For additional protection, clicks, keys pressed on the keyboard, items selected in a menu, or other input events will trigger similar security mechanisms. Since Microsoft code is considered secure, these checks will not occur in windows owned by Microsoft code. Also, the mouse may be used to click on the above buttons and fields during mouse movement authentication. If any such movement of the mouse takes place during the authentication process, the mouse will still be moved to the location indicated by the crosshairs, but a bug in Windows will cause the cursor to immediately "bounce" back to the location where it was last used during authentication. Microsoft will refuse to fix the bug unless Linux is outlawed in all countries, even those countries that have no computers.
Many other authentication checks will be made by Windows. I'll return to this topic in a moment. First, let me mention that Clippy, the talking paperclip, along with other Microsoft characters, will appear during this proces
A mac then? :P
"Who says nothing is impossible? Some people do it every day!" - Alfred E. Neuman
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.
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.
You brain dead moron. Microsoft takes advantage of the next generation directx 9 3d acceleration hardware available in all longhorn-supporting computers to blend the blue and red into a dark, rich purple using sophisticated algorithms, lighting effects, and large textures.
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.
In case you were wondering, we know this because we stole a prerelease copy of Longhorn at musketpoint.
Is it related to this:
http://www.bbc.co.uk/wales/rsod/
Ah.... I see that you are familiar with ATI's Catalyst drivers* then. Either that, or VIA's Hyperion drivers*. :-)
* Disclaimer: I use the term "drivers" very loosely.
Why, oh why, didn't I take the blue screen?
blog
How the hell do you expect to get a warning before your kernel crashes?
"WARNING: Your kernel will crash in ten seconds. Owing to the very nature of the event, there is nothing you can do about it."
there's more than one way to do me.