Slashdot Mirror

← Back to Stories (view on slashdot.org)

Longhorn: Fewer BSODs, More RSODs

Posted by timothy on from the more-colors-still-available dept.

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."

9 of 573 comments (clear)

  1. BSOD by Dante+Shamest · · Score: 3, Informative

    I've not seen one of those in a long, long time.

    1. Re:BSOD by Myen · · Score: 5, Informative

      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.

  2. Page already Slashdotted... by Ninwa · · Score: 5, Informative

    Dont forget NetworkMirror :)

    http://www.networkmirror.com/adYJGbG8ajC3f55y/joi. ito.com/archives/2005/05/07/bsod_upgrades_to_rsod_ in_longhorn.html

    1. Re:Page already Slashdotted... by dotpavan · · Score: 3, Informative

      and there is mirrordot and it doesnt have that many ads as n/w mirror and looks a lot better than n/w mirror

  3. Alternate View by guaigean · · Score: 3, Informative

    Well, here's a link to the pic... til I get slashdotted... http://209.193.18.52/RedScreen.jpg

    --
    Microsoft Sucks, F/OSS Rocks. I get mod points now right?
  4. Comment removed by account_deleted · · Score: 3, Informative

    Comment removed based on user account deletion

  5. Re:I see BSOD's a lot. by blincoln · · Score: 5, Informative

    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
  6. How to get a Red screen of Death even in '95 by Artifakt · · Score: 4, Informative

    Edit your system.ini file as follows:

    Under the [386Enh] header, add these two lines:

    MessageTextColor=B
    MessageBackColor=3

    That will give you a bright cyan text on dark cyan background screen of death. Feel free to substitute other colors 0-F as desired. This works in 95, 98, and Me, at least. Red's in there somewhere - don't remember exactly where - just try a pair of values, wait the usual 15 minutes for a SOD, and see if you like the combination. I can honestly say I haven't seen a BSOD on my screen in months.

    --
    Who is John Cabal?
  7. Re:New Feature by niteice · · Score: 3, Informative

    Only in 3.x/9x. NT kernels have white-on-blue hardcoded. (if you have the leaked source, i think it's bugcheck.c)

    --
    ROMANES EUNT DOMUS