Blue Screen of Death, Move Over

As if the dreaded "Blue Screen of Death" that plagues users of existing Windows variants weren't enough, some beta testers are reporting that they've encountered a new "Red Screen of Death" in early versions of Longhorn.

The first Red Screen of Death (RSOD) reports surfaced this past weekend on various Weblogs, including one written by a Microsoft employee.

Michael Kaplan, a technical lead with Microsoft's Globalization Infrastructure, Fonts, and Tools unit, posted [link|http://blogs.msdn.com/michkap/archive/2005/05/07/415335.aspx|a screen shot of the RSOD in Longhorn on his blog] on May 7.

"Windows Boot Manager has experienced a problem" read the text accompanying the red screen.

"I am not sure I would class the change as an improvement," Kaplan wrote. "I mean, the old message ("Windows cannot start because the following file is missing or corrupt: \\WINDOWS\\System32") is one I understand since I know what the destructive operation was. But if I did not have that knowledge then I would not know much about what was going on.

"The new message, though, is even harder to understand (though an internet search of 0xc000000f will see it relates to Windows File Protection, which I guess is a hint," continued Kaplan.

[link|http://www.eweek.com/article2/0,1759,1814679,00.asp|source]

Post #206,952 by lincoln 5/11/05 2:40:57 PM Reply	Blue Screen of Death, Move Over As if the dreaded "Blue Screen of Death" that plagues users of existing Windows variants weren't enough, some beta testers are reporting that they've encountered a new "Red Screen of Death" in early versions of Longhorn. The first Red Screen of Death (RSOD) reports surfaced this past weekend on various Weblogs, including one written by a Microsoft employee. Michael Kaplan, a technical lead with Microsoft's Globalization Infrastructure, Fonts, and Tools unit, posted [link\|http://blogs.msdn.com/michkap/archive/2005/05/07/415335.aspx\|a screen shot of the RSOD in Longhorn on his blog] on May 7. "Windows Boot Manager has experienced a problem" read the text accompanying the red screen. "I am not sure I would class the change as an improvement," Kaplan wrote. "I mean, the old message ("Windows cannot start because the following file is missing or corrupt: \\WINDOWS\\System32") is one I understand since I know what the destructive operation was. But if I did not have that knowledge then I would not know much about what was going on. "The new message, though, is even harder to understand (though an internet search of 0xc000000f will see it relates to Windows File Protection, which I guess is a hint," continued Kaplan. [link\|http://www.eweek.com/article2/0,1759,1814679,00.asp\|source] lincoln "Until the revolution, we are only useful for our private information and our money." [link\|mailto:bconnors@ev1.net\|contact me]
Post #206,954 by Yendor 5/11/05 3:06:10 PM Reply	For Longhorn... ...That should be a Burnt Orange Screen of Death. I mean, come on... -YendorMike "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759 Historical Review of Pennsylvania
Post #206,957 by jbrabeck 5/11/05 3:15:01 PM Reply	With the appropriate brand displayed ..\|.. A good friend will come and bail you out of jail ... but, a true friend will be sitting next to you saying, "Damn...that was fun!"
Post #206,958 by jbrabeck 5/11/05 3:17:07 PM Reply	For the tech writer From [link\|http://www.ubersoft.net/d/20050511.html\|Help Desk] we have the description of the error messages. A good friend will come and bail you out of jail ... but, a true friend will be sitting next to you saying, "Damn...that was fun!"
Post #206,966 by mmoffitt 5/11/05 4:19:41 PM Reply	They had to make it Red. They owe so much to the Republican DOJ what choice did they have? bcnu, Mikem Eine Leute. Eine Welt. Ein F\ufffdhrer. God Bless America.

Welcome to IWETHEY!