Slashdot Mirror


BSOD Makes Appearance at Olympic Opening Ceremonies

Whiteox writes "A BSOD was projected onto the roof of the National Stadium during the grand finale to the four-hour spectacular at the Olympics. Lenovo chairman Yang Yuanqing chose to go with XP instead of Vista because of the complexity of the IT functions at the Games. His comment on Vista? 'If it's not stable, it could have some problems,' he said. Evidently Bill Gates attended the opening ceremony, so he must have witnessed it."

521 comments

  1. well by thermian · · Score: 5, Funny

    They paid 40 billion for that ceremony. I can't see this improving their opinion of Microsoft much.

    --
    A learning experience is one of those things that say, 'You know that thing you just did? Don't do that.' - D. Adams
    1. Re:well by baldass_newbie · · Score: 5, Funny

      They paid 40 billion for that ceremony.

      But was it a pirated copy of Windows?

      --
      The opposite of progress is congress
    2. Re:well by mccalli · · Score: 5, Insightful

      I can't see this improving their opinion of Microsoft much.

      In fairness to Microsoft, blue screens are normally due to bad hardware drivers. Whatever that thing actually was, it certainly wasn't a normal monitor and I'll bet the drivers are rather specific. And the less people use them, the fewer bugs are found.

      Cheers,
      Ian

    3. Re:well by kcelery · · Score: 1

      hardware failure also gives BSOD, would be premature to bill the Bill.

    4. Re:well by mweather · · Score: 5, Funny

      It's the Chinese Olympics. What do you think?

    5. Re:well by The+End+Of+Days · · Score: 5, Funny

      That's no excuse. No installation of Linux has ever crashed in the history of the universe. Microsoft should be held to no less a standard.

    6. Re:well by Anonymous Coward · · Score: 2, Informative

      IIRC the commentators stated the amount spent on the ceremony was $30 million. The total renovation of Beijing to host the ceremony was $40 billion.

      Either way it's quite sad that one of the only glitches in such a spectacular show was with a MS product.

    7. Re:well by TheRealMindChild · · Score: 1

      What I don't really understand, is by default for the NT line of Windows (as far back as I can remember it) was to dump a log and reboot on such an exception. And even if this wasn't the case, surely you would rather the computer be in an endless reboot cycle (remove the loading screen too) rather than have a projected blue screen for everyone to see you are having problems. That way it looks like the "machine is on the fritz" which people can accept more than "Look, they used Windows and look where it got them... fools!"

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    8. Re:well by TechnoBunny · · Score: 5, Funny

      'In fairness to Microsoft'

      What are you, some kind of shill?

    9. Re:well by supersnail · · Score: 0, Offtopic

      I get this screen when my old Dell expiron overheats.

      Poor old thing can't manage a virus scan and a Web Page at the same time.

      Given the ROCs forgiven and humanetarian nature I wonder which Sysadmin will be donating his internal organs to the Bill and Melissa marketing foundation?

      --
      Old COBOL programmers never die. They just code in C.
    10. Re:well by DerWulf · · Score: 2, Interesting

      there is an option to turn off rebooting on blue screen. It comes in handy if you actually want to see the error ...

      --

      ___
      No power in the 'verse can stop me
    11. Re:well by hostyle · · Score: 0

      A kung-fued copy then ?

      --
      Caesar si viveret, ad remum dareris.
    12. Re:well by Stooshie · · Score: 1

      Erm, dont you mean 40 billion for the games.

      --
      America, Home of the Brave. ... .and the Squaw.
    13. Re:well by schnikies79 · · Score: 5, Insightful

      Be realistic for a second please, you think on show as grand as the opening ceremonies only had one glitch? Seriously?

      There is no such thing as a show this big without multiple (read a lot) of glitches. They are covered up well, quickly fixed, or not noticed, but they are there. This one was just in the open for everyone to see.

      --
      Gone!
    14. Re:well by Joe+the+Lesser · · Score: 5, Funny

      A Linux installation crashes if and only if it doesn't respect it's user.

      --
      "I only speak the truth"
      Karma: null(Mostly affected by an unassigned variable)
    15. Re:well by ArsonSmith · · Score: 5, Funny

      exactly I hate this crap from Microsoft. It should be able to do like Linux and when there's a hardware problem it just reroutes power through the main deflector to fix it.

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    16. Re:well by Anonymous Coward · · Score: 1, Insightful

      err, it's quite unlikely the RoC government will punish anyone for mishaps at the Beijing Games...

    17. Re:well by Joe+the+Lesser · · Score: 4, Funny

      Perhaps it was shanghaid.

      --
      "I only speak the truth"
      Karma: null(Mostly affected by an unassigned variable)
    18. Re:well by cyfer2000 · · Score: 3, Informative

      Those computers were sponsored by IB, sorry, Lenovo, and Lenovo bought license for all of their computers.

      --
      There is a spark in every single flame bait point.
    19. Re:well by value_added · · Score: 4, Funny

      It's the Chinese Olympics. What do you think?

      Actually, the reality is just as funny:

      Microsoft is designated as an official supplier to the 2008 Olympic Games.

      When you can't or don't need to "embrace, extend, and extinguish", sponsor!

      My own opinion is that not anticipating a blue screen is like attending a Budweiser-sponsored sporting event and expecting to get real beer.

    20. Re:well by andy19 · · Score: 1

      You'd think there'd be some testing before projecting it though. If the drivers are that specific/obscure, then chances are it would have happened prior to opening night.

    21. Re:well by timster · · Score: 5, Informative

      Just a heads-up... the ROC initials usually refer to the Republic of China, which is the government in control of Taiwan. The Chinese mainland is controlled by the People's Republic of China, initials PRC. This is a really, really big distiction.

      --
      I have seen the future, and it is inconvenient.
    22. Re:well by omeomi · · Score: 5, Funny

      there is an option to turn off rebooting on blue screen. It comes in handy if you actually want to see the error ...

      And you feel that this is one of those instances?

    23. Re:well by Anonymous Coward · · Score: 0

      Maybe it choked on spam?

    24. Re:well by Anonymous Coward · · Score: 0

      And dodgy, generic Chinese-made hardware usually has dodgy, generic Chinese-made drivers...

    25. Re:well by kesuki · · Score: 5, Funny

      next thing you'll be telling me BSD never gets hacked unless it's playing a prank on it's admin.

    26. Re:well by Barsteward · · Score: 5, Funny

      Are you sure its not "People's Republic in China" i.e. PRiC :o)

      --
      "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
    27. Re:well by Anonymous Coward · · Score: 1, Funny

      I once ran Linux off of a microwave, a watch battery and a oscilloscope. They call me... McTux

    28. Re:well by thermian · · Score: 1

      Not according to the bbc, they say the opening show cost that much. 20 billion in real money

      --
      A learning experience is one of those things that say, 'You know that thing you just did? Don't do that.' - D. Adams
    29. Re:well by dotancohen · · Score: 5, Funny

      next thing you'll be telling me BSD never gets hacked unless it's playing a prank on it's admin.

      BSD never gets hacked unless it's playing a prank on it's admin.

      --
      It is dangerous to be right when the government is wrong.
    30. Re:well by fishbowl · · Score: 3, Insightful

      Bartscht's Law of Model Railroading:
      The number of problems is directly proportional to the number of spectators.

      --
      -fb Everything not expressly forbidden is now mandatory.
    31. Re:well by pizzach · · Score: 1

      So another words, the blue screen was caused by a faulty driver produced by a chinese company that makes a US company look bad (through a knee-jerk reaction)? I sense a conspiracy here...

      --
      Once you start despising the jerks, you become one.
    32. Re:well by fishbowl · · Score: 5, Interesting

      >They are covered up well, quickly fixed, or not noticed, but they are there

      I learned this when I saw a circus fire and noticed that the clowns put the fire out while making it look like part of the act. It was both comforting and frightening at the same time.

       

      --
      -fb Everything not expressly forbidden is now mandatory.
    33. Re:well by Blakey+Rat · · Score: 1

      It would have, but someone sabotaged the hyperdrive motivator. Bastards.

    34. Re:well by Anonymous Coward · · Score: 0

      And even if this wasn't the case, surely you would rather the computer be in an endless reboot cycle (remove the loading screen too) rather than have a projected blue screen for everyone to see you are having problems.

      Are you sure that's the default? I can swear I've seen a fair amount of NT boxen in places where I'm fairly certain the staff wouldn't know/care how to twiddle an option like that, and they sit around blue screened, patiently awaiting a reboot.

      And don't call me Shirley!

    35. Re:well by Anonymous Coward · · Score: 0

      Hey, they all look the same to me! No, really!

    36. Re:well by Anonymous Coward · · Score: 0

      They paid 40 billion for that ceremony.

      The 40 billion figure is the total cost of hosting the games - quite a large figure really: about half a year of the direct costs of the Iraq occupation.

      Estimates for the opening ceremonies are upwards of 100 million - not really that much: only about half a day of Iraq occupation.

      The new US embassy in China cost about 400 million - enough for a couple days in Iraq.

    37. Re:well by Jugalator · · Score: 0, Troll

      Stop using "it's" when you mean "its", both of you over there!

      --
      Beware: In C++, your friends can see your privates!
    38. Re:well by Anonymous Coward · · Score: 0

      Here's my obligatory anecdotal take: Linux crashes are reproducible. I.e., discounting faulty hardware, if it crashes once with a given set of software/hardware, it will *always* crash. E.g., whenever I use the ATI driver with my FireGL on my Inspiron laptop, running xperf will fail at the same place each time, taking out X with it (yes, I know X is not technically "Linux" but bear with me). Compare this with my XP Thinkpad T42. If I insert my AT&T Sigmatel wireless card, it will sometimes cause the machine to bluescreen. Sometimes it doesn't. Doesn't matter if I just reboot the machine and insert the card or if it's been running for hours. The crashes are random. Don't know why. And that's more annoying than knowing it will always crash.

    39. Re:well by Anonymous Coward · · Score: 0

      -1 didn't get the joke even though all the siblings did.

      (ok, I modded you overrated, cause thats as close as I can get)

    40. Re:well by MrNaz · · Score: 0, Troll

      That joke format is old and retarded. If you're still young, you're halfway there.

      --
      I hate printers.
    41. Re:well by Blakey+Rat · · Score: 2, Informative

      Yes, it "shouldn't" be able to. And celebrities and sports stars "should" be paid relative to their contributions to society. And you "should" treat all women equally, no matter how attractive or unattractive they are.

      You're talking about an ideal, the ideal that drivers should never be able to take down an OS doesn't work here in reality. It doesn't work in Windows, it doesn't work in Linux, it doesn't work in OS X. So while it's a fine ideal, stop talking about it as if it has some relevance in real life.

      (Now, when you manage to code-up an OS that implements this ideal 100%, then you can start being snide.)

    42. Re:well by bev_tech_rob · · Score: 1

      Alright, let's keep the Star Wars and Star Trek jokes straight.... ;P

      --
      You're messin' with my Zen Thing, man.....
    43. Re:well by cliffski · · Score: 1

      At the end of the day, this billion-dollar ceremony was entrusted to Microsoft Windows XP.
      We can all laugh that there was a BSOD, but I'm sure Microsoft will laugh at Mac and Linux, knowing that the system that got chosen was theirs, and not anyone else's.

      Hardly a victory for the anti-Microsoft lobby.

      --
      DRM-free indie games for the PC and Mac: Positech Games
    44. Re:well by Anonymous Coward · · Score: 0

      try $300 million...

    45. Re:well by The+MAZZTer · · Score: 1

      Ubutnu hangs whenever I try to force the mounting of a "dirty" ntfs volume (ie window didn't shut down correctly) with ntfs-3g through truecrypt.

    46. Re:well by ozbird · · Score: 1

      It's rare, but it does happen. Had one today on a RHEL5 server: "modprobe eeprom", splat.

    47. Re:well by Actually,+I+do+RTFA · · Score: 1

      (Now, when you manage to code-up an OS that implements this ideal 100%, then you can start being snide.)

      I did! It doesn't talk to any hardware at all, including the CPU or RAM. It is the single most reliable piece of software ever. And, since there's no hardware, the entire system needed to run it is under the GPL! Take that less free, less robust OS's, like Linux.

      --
      Your ad here. Ask me how!
    48. Re:well by hardlyleet · · Score: 1

      They paid 40 billion for that ceremony. I can't see this improving their opinion of Microsoft much.

      If they'd have chosen open source, I bet it would have only cost 20...

      --
      Fortran is for pimps.
    49. Re:well by Lennie · · Score: 1

      The default is actually to give this error, someone didn't change the default.

      --
      New things are always on the horizon
    50. Re:well by reallyjoel · · Score: 0, Troll

      i dont get it

    51. Re:well by griego · · Score: 2, Insightful

      Could be, but I recall at some point the default was changed to reboot... maybe with XP SP2? It had to be changed because every newbie I help with endless reboot problems always has reboot checked and they never even heard of that setting.

    52. Re:well by sacker12345 · · Score: 1

      I thought it would use the flux capacitor to fix itself the nanosecond it sense an error, without the user ever knowing.

    53. Re:well by Anonymous Coward · · Score: 0

      Or if its admin doesn't know how to use apostrophes.

    54. Re:well by snl2587 · · Score: 2, Informative

      Ubutnu hangs whenever I try to force the mounting of a "dirty" ntfs volume (ie window didn't shut down correctly) with ntfs-3g through truecrypt.

      That's technically a Microsoft thing. While Ubuntu should probably handle the error better and anticipate that sort of thing, NTFS is designed not to mount if chkdsk has not been run after a bad restart from the Windows side, and no substitute for chkdsk has been developed (that I know of). This could easily be avoided by removing all of the important data from your Windows partition and and deleting that partition :).

    55. Re:well by JohnBailey · · Score: 1

      I thought it would use the flux capacitor to fix itself the nanosecond it sense an error, without the user ever knowing

      Only if they reverse the polarity at the right moment.

      --
      It is difficult to get a man to understand something when his job depends on not understanding it.
    56. Re:well by retchdog · · Score: 1

      And like all anecdotes, it is almost useless (and yet it prompts the reader to supply their own!).

      My linux (ubuntu 8.04) on a Thinkpad will fail to resume out of a suspend about 10% of the time, forcing a reboot. With 7.10, it failed about 50% of the time. Every logical explanation I come up with has failed (been falsified by experiment). What happens? What happened with 8.04? I have no clue. Hopefully 8.10 will fix things - it's supposed to have a focus on notebook stability issues.

      --
      "They were pure niggers." – Noam Chomsky
    57. Re:well by mattwarden · · Score: 5, Funny

      Macs only crash when you use the grammatically incorrect version of i

    58. Re:well by cwAllenPoole · · Score: 1

      In that case, wouldn't it be fixing the problem before it happened?

      --
      http://www.allen-poole.com/
    59. Re:well by bhtooefr · · Score: 3, Informative

      IIRC, the default was actually changed to automatically reboot back with Windows 2000. (And, I want to say that NT4 Server also automatically rebooted.)

    60. Re:well by Nutria · · Score: 1

      My linux (ubuntu 8.04) on a Thinkpad will fail to resume out of a suspend about 10% of the time, forcing a reboot. With 7.10, it failed about 50% of the time. ... Hopefully 8.10 will fix things

      It's gone from a 50% failure rate to a 10% failure rate in six months. That's nothing to sneeze at.

      Maybe 8.10 will only have a 1% failure rate...

      --
      "I don't know, therefore Aliens" Wafflebox1
    61. Re:well by Anonymous Coward · · Score: 0

      yes but the olympics only lasts for 2 weeks, the iraq war (and war on terror) will last forever. Much better value for the money you see.

    62. Re:well by Nutria · · Score: 1

      Given the ROCs forgiven and humanetarian

      Geography lesson: The ROC is on that tiny island which the ChiComs have aimed lots of missiles at.

      http://en.wikipedia.org/wiki/Republic_of_China
      http://en.wikipedia.org/wiki/People's_Republic_of_China

      --
      "I don't know, therefore Aliens" Wafflebox1
    63. Re:well by erKURITA · · Score: 1, Informative

      It wasn't pirated. The following link (in Chinese), which is traced from this other link (which comes from the Gizmodo article) says they were 120 HES Axon Media Servers running XPe (Windows XP Embedded).

      Regardless, I can see some heads rolling as result from this failure.

    64. Re:well by Anonymous Coward · · Score: 0

      They paid 40 billion to get Beijing ready for the Olympics, they only paid 300 million for the ceremony.

    65. Re:well by aztektum · · Score: 1

      BSD never gets hacked unless it's playing a prank on its admin.

      Subtle

      --
      :: aztek ::
      No sig for you!!
    66. Re:well by Rick+Bentley · · Score: 1

      It should have been a pirated copy of windows. "XP Ultimate, by Jonny" seems to install easier, work better, and comes with better default settings than any other legitimate version of Windows I've seen. http://www.noeman.org/gsm/internet-computers/49480-windows-xp-ultimate-edition-johnny.html

      I mean, I really wouldn't mind paying for a full version of Windows Vista if it did what I wanted it to do. Windows XP Ultimate, however, does everything I want it to do. It appears to be the best version of Windows at any price ... so I don't feel guilty for using it.

      Maybe MS should put a "click to donate" button on their website for guys like me who don't mind paying for pirated Windows XP. I'd gladly pop in the same price Dell pays for a copy of Vista.

      --
      My favorite quote doesn't fit into 120 characters. Now no one will like me.
    67. Re:well by insomniac8400 · · Score: 1

      No it was the only legal copy in the whole country.

    68. Re:well by Anonymous Coward · · Score: 0

      They wouldn't have to...the infinite improbability drive would kick in and work some magic. Or it might turn the screen into a bowl of petunias. It's hard to predict.

    69. Re:well by hachete · · Score: 1

      IIRC, the whole selling point for Windows is the fact you can plug different bits of hardware into it. That's what Bill Gates means by "freedom of choice". So, this is MS handling their business model *badly*. If you're gonna do this kind of thing, then the system should work properly, no matter what kind of shitty hardware is thrown at it. Putting hardware drivers in userland and keeping them there seems a good idea - as other users have pointed out - but putting them into the kernel is the opposite. I think the need for speed was for driven by greed; rather, the need to grind the opposition into dirt. Whatever. What this is really about is the highly public display of the result of a series of really crap management decisions. And that's what MS now is: a badly managed monopoly. A monopoly doesn't need good management, just a bad one that can wave aside the smell from the occasional turd.

      --
      Patriotism is a virtue of the vicious
    70. Re:well by Prefader · · Score: 1

      You're missing the point. It's great that the failure rate has dropped, but the failures appear to be totally random, countering the GP's point about crashes in Linux being predictable and reproducible.

    71. Re:well by stranger_to_himself · · Score: 1

      Thanks - no wonder I couldn't work out what Receiver Operating Characteristics had to do with anything.

    72. Re:well by Anonymous Coward · · Score: 0

      Obviuosly, "MrNaz (730548)" is John McCain's Slashdot login. Who else could confuse the foot with the football?

    73. Re:well by Wabbit+Wabbit · · Score: 1

      And don't forget to modulate the shield harmonics.

      --
      Nothing is inexplicable; only unexplained -Tom Baker, Doctor Who
    74. Re:well by level_headed_midwest · · Score: 2, Funny

      It was one of the two legit copies in the country?

      --
      Just "gittin-r-done," day after day.
    75. Re:well by Khyber · · Score: 1

      The device was a projector. No driver needed. Just run the video signal to the projector and voila.

      I'll bet more on faulty HARDWARE inside the computer judging by the error message at the bottom.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    76. Re:well by Nutria · · Score: 1

      countering the GP's point about crashes in Linux being predictable and reproducible.

      I know. Linux is just better at having reproducible errors.

      --
      "I don't know, therefore Aliens" Wafflebox1
    77. Re:well by Yvanhoe · · Score: 1

      Yeah, probably one of those Chinese cheap drivers...

      --
      The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
    78. Re:well by slashgrim · · Score: 1

      Should fragile drivers be in kernel-space?

    79. Re:well by igny · · Score: 4, Funny

      I am pretty sure Chinese call their country Translation Server Error

      --
      In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
    80. Re:well by daybot · · Score: 1

      Macs only crash when you use the grammatically incorrect version of i

      Brilliant! Too bad my mod points just expired :(

    81. Re:well by The+End+Of+Days · · Score: 1

      And celebrities and sports stars "should" be paid relative to their contributions to society.

      Where the hell did you get this notion from? Society doesn't pay people, people pay people. Welcome to capitalism.

    82. Re:well by Anonymous Coward · · Score: 0

      But as long as the streams don't cross, everything should be fine.

    83. Re:well by Anonymous Coward · · Score: 0

      I think my deflector is broken. What version are you using? I'm on 0.6.4.1a RC2.

    84. Re:well by treeves · · Score: 1

      I just love reproducible anecdotes.

      --
      ...the future crusty old bastards are already drinking the Kool-Aid.
    85. Re:well by Anonymous Coward · · Score: 0

      In Soviet China, Linux crashes you!

    86. Re:well by Anonymous Coward · · Score: 0

      I'd be willing to bet that MS PAID them to use Windows.

    87. Re:well by Anonymous Coward · · Score: 0

      That's no excuse. No installation of Linux has ever crashed in the history of the universe. Microsoft should be held to no less a standard.

      There are installations of Linux?

      ((ducks))

    88. Re:well by Anonymous Coward · · Score: 0

      you are a fucking idiot.

    89. Re:well by repvik · · Score: 1

      I get this screen when my 6 months old Acer PC is resuming from standby and I try to type in my password to log in. I have to wait a few seconds before I can type. There's no visual cues or anything preventing me from starting to type.

    90. Re:well by ORBAT · · Score: 2, Funny

      Regardless, I can see some heads rolling as result from this failure.

      China being China they might take that a tad too literally.

    91. Re:well by Anonymous Coward · · Score: 0

      Yeah, but when something goes wrong at the Chinese Olympics, people disappear.

    92. Re:well by Anonymous Coward · · Score: 0

      Driver for the monitor? What have you been smoking? I can understand a driver for the graphic card, and some software for calibrating the display, but a driver makes no sense on the monitor.

    93. Re:well by afidel · · Score: 1

      Actually it was a smart projector with a built in media server, and given the length of the ceremony the most likely cause was some sort of thermal problem, I doubt those kind of projectors get run for that long very often.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    94. Re:well by julian67 · · Score: 1

      And during the real and vicious custard pie assault the clowns cleverly integrated a real police officer into the performance and nobody was any the wiser.....the absolutely real and genuine violence was so severe that the damaged squad car is now in the shop having its doors refitted.

    95. Re:well by scott_karana · · Score: 2, Interesting

      ...so because nobody one the FOSS side has implemented fsck.ntfs-3g, it's Microsoft's problem?

    96. Re:well by Repossessed · · Score: 1

      http://arstechnica.com/journals/microsoft.media/olympics_bsod.jpg From what I can see of it, the error code does indeed suggest a driver, however drivers crashing the system just proves the entire development model of letting multiple third parties write critical pieces of code is broken.

      --
      Liberte, Egalite, Fraternite (TM)
    97. Re:well by scott_karana · · Score: 1

      The ROC and the PRC both govern the same land, why bother making a distinction at all? ;)

    98. Re:well by ebonum · · Score: 0, Flamebait

      Awwwwwww, one of the few symbols that all of humanity can understand and relate to. This is an inspired and deeply symbolic part of the opening ceremony that truly captures the trials and struggles we all face.

    99. Re:well by Anonymous+Psychopath · · Score: 1

      Not according to the bbc, they say the opening show cost that much. 20 billion in real money

      Let's not think crazy.

      1) 20 billion British pounds, or about 38 billion USD, is the cost of the games. There are a few big-ticket items included in that figure, like the cost of the Bird's Nest.

      2) 25 million British pounds, or about 47 million USD, is the cost of the opening ceremonies.

      This, of course, is still a hell of a lot of money to put on a nice show.

      --

      Eagles may soar, but weasels don't get sucked into jet engines.

    100. Re:well by Ilgaz · · Score: 2, Interesting

      IMHO , It also perfectly explains why IBM decided to get rid of tiny computers and CPUs running tiny computers (except consoles). I think they got sick of them, really.

      These guys manufacture mainframes which theoretically run forever. Imagine you see that screen in that company culture while a bank calls for a CPU upgrade of a mainframe which runs for 10 years non stop which will be still done without turning it off :)

    101. Re:well by cheater512 · · Score: 1

      For a BSOD to have been displayed, it would have had to been a normal monitor.

    102. Re:well by fishbowl · · Score: 1

      ...and people wonder why i have trouble sleeping at night...

      --
      -fb Everything not expressly forbidden is now mandatory.
    103. Re:well by Chemisor · · Score: 1

      Yes, and if you are running X and Linux crashes, your machine would just lock up, since your drivers don't implement kernel mode switching. Windows has it much better with the BSOD.

    104. Re:well by snl2587 · · Score: 0, Flamebait

      Not Microsoft's problem...Microsoft's mistake. Or, more likely, its clever ploy. Since the filesystem is locked down to a Microsoft operating system in the event of an improper shutdown, NTFS becomes a terrible system to work with when using Linux. If they actually were encouraging interoperability as they like to claim they are, then this wouldn't even be an issue. But they don't release anything to help with the chkdsk issue, and so this persists.

      It is Linux's problem, but Microsoft's fault. As usual.

    105. Re:well by rcw-work · · Score: 1

      surely you would rather the computer be in an endless reboot cycle (remove the loading screen too) rather than have a projected blue screen for everyone to see you are having problems.

      I would rather the computer have two screens with the second one reserved entirely for presentation - BIOS POST, bootup, desktop, and errors go to the second one.

    106. Re:well by certain+death · · Score: 1

      Blame AtosOrigin!!! www.atosorigin.com

      --
      "My immediate reaction is "WTF? What kind of moron doesn't make things 64-bit safe to begin with?" Linus
    107. Re:well by dotgain · · Score: 1

      Yes, believe it or not he was being facetious. I know, I know - for a moment there, I too genuiniely believed he'd researched every Linux install in the history of the universe and confirmed what I suspected to be true.

    108. Re:well by wjsteele · · Score: 1

      Hmmm... I thought they only crashed when you turned them on. Happen every time I try it.

      Bill

      --
      It's my Sig and you can't have it. Mine! All Mine!
    109. Re:well by Deltaway · · Score: 0

      So is that me's fault or u's fault?

    110. Re:well by interstellar_donkey · · Score: 1

      Oh, if only Linux cost money. Then the Chinese would feel more inclined to pirate it, and there wouldn't be this sort of mistake.

      --
      The Internet is generally stupid
    111. Re:well by Tablizer · · Score: 1

      [there is an option to turn off rebooting on blue screen. It comes in handy if you actually want to see the error] And you feel that this is one of those instances?

      In the case of slashdot readers, YES. (Is there a geek olympics, by the way?)
         

    112. Re:well by jo42 · · Score: 1

      40 billion

      To put that into perspective, that is less than 4 months of the cost of the US occupation of Iraq...

    113. Re:well by Anonymous Coward · · Score: 0

      'In Soviet China'? Not only the BSOD hiccup, your perl script has a hiccup too.

    114. Re:well by Anonymous Coward · · Score: 0

      Because from a user's point of view, it's much better to have an OS that almost always crashes when something goes wrong, as opposed to one that tries its best not to crash, and occasionally fails.

      Or in your words, Linux is "better" at failing. Well, I suppose the glass can be 1% full, too.

    115. Re:well by Anonymous Coward · · Score: 0

      I wanted to use Linux's process scheduler on my Windows box. But, stupidly, someone integrated it into the Linux kernel, and no one has bothered to port it to Windows. All the while claiming Linux is more interoperable.
      Windows' problem, but Linux's fault, as usual.

    116. Re:well by Hal_Porter · · Score: 1

      That's technically a Microsoft thing....

      <Loud sigh>

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    117. Re:well by Hal_Porter · · Score: 1

      And you feel that this is one of those instances?

      Someone in the crowd might have been able to read the stacktrace and should out "the problem is with driver x".

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    118. Re:well by snl2587 · · Score: 1

      The code for Linux is open sourced, so if you insist on using the scheduler on Windows, there's no need to blame the community. Port it yourself, wait, or shut the fuck up. Since you're just being a smart-ass, I recommend the third option.

      And if you're talking about cron, use Cygwin. If it's something else, see the above.

    119. Re:well by pipingguy · · Score: 1

      noticed that the clowns put the fire out while making it look like part of the act

      Our CAD Support does this every now and then during important 3D design review sessions with the client. Good to know I'm not alone.

    120. Re:well by Anonymous Coward · · Score: 1, Insightful

      FYI: the scheduler is part of the OS kernel which decides which process/thread to run next. Good luck porting that to Windows. :-)

      The point is, the idea that it's a "design flaw" that NTFS might leave the disk in a bad state after failure is mistaken. This fact is a fundemental truth: if you lose buffered writes, the disk is not guaranteed to be kosher. That's why chkdsk (windows) and fsck (*nix) exist in the first place. So the fact that the community hasn't written a fsck for NTFS is not Microsoft's fault; the burden is on the developers who want to provide NTFS support.

      A better analogy: suppose Microsoft implemented ext2 in Windows, but not fsck. Is it Linux's fault that you can't use volumes from a hard drive that Linux did not mount properly?

    121. Re:well by howlingmadhowie · · Score: 1, Troll

      i think we all know here what a scheduler is. your problem with using one of the linux kernel schedulers in a windows kernel would be in decompiling the windows kernel. apart from that, everything is just a lot of work, but possible.

      calling the huge technical difficulty of implementing ntfs and a specific chkdsk for it a design flaw is maybe the wrong choice of words. microsoft is just going out of their way (as ever) to make sure that nobody else can interoperate, while gnu/linux bends over backwards to make interoperability as easy as possible.

    122. Re:well by snl2587 · · Score: 2, Interesting

      FYI: the scheduler is part of the OS kernel which decides which process/thread to run next.

      Sorry...the first post wasn't specific enough and I read it as a scheduler for processes i.e. cron.

      A better analogy: suppose Microsoft implemented ext2 in Windows, but not fsck. Is it Linux's fault that you can't use volumes from a hard drive that Linux did not mount properly?

      The point I'm trying to get across is that, for example, there is a big difference between Linux wanting to use NTFS and Windows wanting to use ext2. The NTFS spec is a trade secret, and all work that has been done with ntfs-3g has been essentially hacking around a black box. The reason why there is not a chkdsk implementation in Linux is because that box is so secretive in the way it handles internal corruption (which is the nature of file systems, I know) and fixes itself that we can only chip away at it, hoping to get lucky and consistent. If Microsoft wanted to use ext2, then it's much easier: the spec is open, the code is open. Anyone could port fsck at will to Windows in that case if Microsoft didn't do it for them (and if Microsoft decided to close the source for its implementation of ext2, it definitely wouldn't be Linux's fault).

      I know this is Linux's problem, but certainly not the developers' fault. If you really want an analogy, think of it as trying to crack the trade-secret recipe for Coca-Cola. You can get close, but without knowing the exact ingredients and processes...you get the idea. If Microsoft opened up NTFS your arguments would hold, but until then...

    123. Re:well by Anonymous Coward · · Score: 1, Insightful

      To be clear: I'm the AC that posted the parent, but not the AC before that. :-) So the scheduler analogy wasn't mine.

      Question, though, about this notion of creating intentional obstacles for third party implementations... You don't think the complexity in NTFS merely grows out of engineering problems MS had in developing it, or maybe says something about filesystems in general? When they started in the earliest days of NT (1993ish?) I don't think they were thinking about how to screw over Linux. Likewise, over the years of maintenance and features added since then I think they'd probably focus more attention on hacking it enough to make it work at all, especially with the legacy baggage it has.

      I believe I read in a blog about strange designs in MS... Where it's not necessarily that they're purposefully trying to design cryptic file formats and obfuscate them, so much as maintain strange conventions that were optimized for 1993 machines and get carried over from release to release.

      Now, what you say about being more open, I do think that's a fair point and applies. But, as for motives, and attributing MS's actions in 1993 to their current attitude towards open source... I'm not sure that's the first explanation I would think of for that.

    124. Re:well by MichaelSmith · · Score: 1

      Well yeah. This is China. I reckon there were about 100000 chinese guys who really could fix the problem who were watching the olympics at that point.

    125. Re:well by MichaelSmith · · Score: 1

      Maybe they forgot to disable the screen saver...

    126. Re:well by DaVince21 · · Score: 1

      Linux drivers are supposed to be worse off, then, seeing as they're written by thousands of different users. ...Of course, there's stuff like a standard model, and open-sourcing which allows other people to correct someone's faulty code, so I guess that more than makes up for it.

      --
      I am not devoid of humor.
    127. Re:well by Anonymous Coward · · Score: 0

      The problem seem to be that people wanting to implement fsck for ntfs doesn't have any specs from microsoft. If, however, microsoft wants to implement ext[23] (please do!) they have specs AND code.

    128. Re:well by puster2 · · Score: 1

      That's technically a Microsoft thing. While Ubuntu should probably handle the error better and anticipate that sort of thing, NTFS is designed not to mount if chkdsk has not been run after a bad restart from the Windows side, and no substitute for chkdsk has been developed (that I know of). This could easily be avoided by removing all of the important data from your Windows partition and and deleting that partition :).

      Actually there is. It is called NTFSCHECK and in Ubuntu it is part of a package called NTFSPROGS. It does quite everything including deleting the contentes of the $Log-file of the NTFS-partition. It is a commandline only tool.

      --
      Don't argue with idiots. The pull you down to their level and beat you with experience.
    129. Re:well by WgT2 · · Score: 1

      *shrug*

      But, it was certainly the BSOD seen around the world.

    130. Re:well by snl2587 · · Score: 1

      As far as I can tell, there's no program called NTFSCHECK in NTFSPROGS. There is NTFSFIX, but here's the description:

      ntfsfix - Fix common filesystem errors and force Windows to check NTFS.

      So it's not exactly a replacement, then...

    131. Re:well by Anonymous Coward · · Score: 0

      No, it's iFault.

    132. Re:well by retchdog · · Score: 1

      Don't get me wrong, I'm happy that it's improved. I was surprised and delighted to see any improvement in 8.04 since my problem was not a priority for that LTS.

      As for 8.10, I am hoping for a near-zero failure rate (equal to or better than WinXP)! They are after all supposedly targetting these very issues.

      --
      "They were pure niggers." – Noam Chomsky
  2. Bill was there? by Anonymous Coward · · Score: 0

    If bill was there, so what? He's gone from microsoft.

    1. Re:Bill was there? by g0bshiTe · · Score: 1

      Not just that, but people make it out like he is the sole coder on any of the Windows products.

      --
      I am Bennett Haselton! I am Bennett Haselton!
    2. Re:Bill was there? by snoyberg · · Score: 3, Funny

      Please... no single human could code that much bloat.

      --
      Thank God for evolution.
    3. Re:Bill was there? by JCSoRocks · · Score: 5, Funny

      He probably cackled maniacally and shouted over the top of the fireworks, "I made that screen blue! Bill Gates owns the Olympics! Maybe if you dirty pirates had bought a legitimate copy it would have worked better!"

      --
      You are using English. Please learn the difference between loose and lose; they're, there, and their; your and you're.
    4. Re:Bill was there? by wattrlz · · Score: 1

      To be fair he is/was the public face of MS and he seems to have wanted it that way.

    5. Re:Bill was there? by JustOK · · Score: 1

      He coded something that coded bloat and bloated code

      --
      rewriting history since 2109
    6. Re:Bill was there? by Anonymous Coward · · Score: 0

      More like a bevy of bloated blokes coding bloated code.

    7. Re:Bill was there? by Anonymous Coward · · Score: 0

      Maybe if you dirty pirates had bought a legitimate copy it would have worked better!"

      Hrm. Bill would never say such a thing ... Without a 'forward looking statement' thingy, that is ;-)

    8. Re:Bill was there? by Adriax · · Score: 1

      I do not like code bloat and ham, I do not like them microsoft man.

      --
      I don't suffer from insanity, I enjoy every minute of it!
    9. Re:Bill was there? by Anonymous Coward · · Score: 0

      Emphasis on maybe

  3. Oh, stop it! by morgan_greywolf · · Score: 2, Funny

    BSOD's are no longer a problem! They haven't been since Windows XP! BSOD's were only a problem in the Win 9x days! Windows today is wayyyy stable! My Windows box hasn't crashed ever!

    *tongue firmly planted in cheek*

    1. Re:Oh, stop it! by gEvil+(beta) · · Score: 4, Funny

      *tongue firmly planted in cheek*

      You're talking about BillG's asscheek, right? : p

      --
      This guy's the limit!
    2. Re:Oh, stop it! by DerWulf · · Score: 2, Insightful

      If your windows XP crashes more then once in a blue moon you got serious issues with your hardware and/or device drivers. NT never had stability issues provided that hardware and drivers were sound.

      --

      ___
      No power in the 'verse can stop me
    3. Re:Oh, stop it! by drsmithy · · Score: 2, Informative

      BSOD's are no longer a problem! They haven't been since Windows XP! BSOD's were only a problem in the Win 9x days!

      Strictly speaking BSODs were never a problem in Windows 9x because, originally, BSOD was an NT-specific term for the kernel dump screen.

      The explosion of ignorance on the internets in the late '90s, however, means that even the Windows 95 errors that popped up a blue DOS screen are now referred to as BSODs (even though they frequently lacked the "OD" part).

    4. Re:Oh, stop it! by TheVelvetFlamebait · · Score: 4, Funny

      My Windows box hasn't crashed ever!

      Ah! Keeping it in mint condition, I see.

      --
      You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
    5. Re:Oh, stop it! by chaim79 · · Score: 1

      provided that hardware and drivers were sound.

      Oooo, nice play... I seem to remember very serious video card driver problems with early versions of NT that would easily bring down the system. Nice of you to blithely exclude such problems. :)

      --
      DEMETRIUS: Villain, what hast thou done?
      AARON: Villain, I have done thy mother.
      Shakespeare invents 'your mom'
    6. Re:Oh, stop it! by Anonymous Coward · · Score: 2, Informative

      Stop this revisionist nonsense. The phrase was first used in reference to Windows 3.1. Win XP's architectural changes eliminated entire classes of BSODs, but they were still legitimate BSODs. They could even be worse than kernel panics -- a "recoverable" error often lead to a system freeze minutes later.

    7. Re:Oh, stop it! by EXrider · · Score: 1

      Oh, like those wonderful kernel-mode print drivers? Yeah, I don't miss our old NT4 print server so much really. One misbehaving HP print driver could cause so much havoc.

      --
      grep -iw skynet /etc/services
    8. Re:Oh, stop it! by stderr_dk · · Score: 1

      In communist China, BSOD is projected on roof.

      Well, I for one, welcome our new olympic overlords.

      The rice cake is a lie.

      --
      alias sudo="echo make it yourself #" ; # https://pipedot.org/~stderr & http://soylentnews.org/~stderr
    9. Re:Oh, stop it! by morgan_greywolf · · Score: 1

      In Korea, only old people get BSODs.

    10. Re:Oh, stop it! by Xtifr · · Score: 1

      My WinXP never crashes--and neither does my flying car! :)

      On the other hand, your claim that "NT never had stability issues" is pure nonsense. I stress-tested dozens of NT systems to destruction, and it wasn't because of hardware problems. Get the load high enough, and they simply died. If all you do is play the occasional video game and write the occasional memo, it probably works well enough, but put it in a situation where it has to do some real work, and it fell apart like a girl scout in a minefield.

      XP might be more solid than NT. I don't know and don't care. Systems with auto-raise and click-to-focus are unusable IMO. :)

    11. Re:Oh, stop it! by morgan_greywolf · · Score: 1

      XP might be more solid than NT. I don't know and don't care. Systems with auto-raise and click-to-focus are unusable IMO. :)

      So CDE, GNOME, KDE, XFCE, OS X, etc. are completely out for you, at least with the default options?

    12. Re:Oh, stop it! by Anonymous Coward · · Score: 0

      even though they frequently lacked the "OD" part

      I'm sorry but what universe were you using this in? From 95 thru to XP I have got BSODs. And before you correct me by saying that with 95 and 98 it wasn't actually the OD part, how many times did you actually try to continue using your machine after that happened??

      Seriously, 99% of time, the screen turns blue, it gets a ctrl-alt-delue!! (Yeah I know that makes no sense, "wanna fight about it?")

    13. Re:Oh, stop it! by DerWulf · · Score: 1

      "occasional video game". That made me smile because appearantly the simultanious full utilization of CPU, GPU, RAM, VRAM, sound card, ethernet, harddrive and PSU for hours and hours won't turn up driver and hardware faults. In comparison, the servers we use at work have it easy: minimal load on CPU, no graphics or sound to speak of, in an air conditioned room with regulated power connections.

      Anyways, I recently tried installing fedora and some other distro I don't remember. Fedora hang on install already, the other one would randomly lock up with only the gnome running. Mind you, vanilla installations. I don't even want to talk about getting wireless to work without causing kernel panics ...

      No matter, XPs stability considering the wide range of hardware supported right out of the box is very, very good and judging from my and other peoples expirience with linux I would say it's unrivaled. Of course it's never going to be a hundred percent but if your drivers are good and you get BSODs it's a sure bet that you have a hardware fault.

      --

      ___
      No power in the 'verse can stop me
    14. Re:Oh, stop it! by Anonymous Coward · · Score: 0

      Mod parent down for making shit up.

    15. Re:Oh, stop it! by Anonymous Coward · · Score: 0

      Has it been ever powered on?

    16. Re:Oh, stop it! by Anonymous Coward · · Score: 0

      Yeah it must still be rapped up for that to happen.

  4. That was on Stadium... by should_be_linear · · Score: 4, Funny

    ... but for TV audience around the Globe, image was different, they used CG to convert BSOD into neato Compiz Cube animations.

    --
    839*929
    1. Re:That was on Stadium... by _Sprocket_ · · Score: 1

      ...a spinning stadium?

    2. Re:That was on Stadium... by dotancohen · · Score: 1

      ... but for TV audience around the Globe, image was different, they used CG to convert BSOD into neato Compiz Cube animations.

      And fireworks.

      --
      It is dangerous to be right when the government is wrong.
  5. Here's a game by PJCRP · · Score: 5, Funny

    10 points to the first person to can say what went wrong :U

    --
    Knows everything about nothing and nothing about everything.
    1. Re:Here's a game by Corporate+Troll · · Score: 1

      You get a maximum of 5 points here... modpoints that is ;-)

    2. Re:Here's a game by Daimanta · · Score: 1

      Last letter of the STOP hex code is an A, IRQ_NOT_LESS_OR_EQUAL perhaps?

      --
      Knowledge is power. Knowledge shared is power lost.
    3. Re:Here's a game by pipatron · · Score: 1

      Obviously you haven't had any modpoints in a long time! Last time I got 15.

      --
      c++; /* this makes c bigger but returns the old value */
    4. Re:Here's a game by PJCRP · · Score: 1

      Dunno, looks more like an F4 to me :o

      --
      Knows everything about nothing and nothing about everything.
    5. Re:Here's a game by Corporate+Troll · · Score: 0, Offtopic

      Yes, I know.... It's been a very long time. I don't know why. It might have to do with my user name. (That said, my other user name doesn't get any modpoints either)

      Oh, well... I'm not complaining.

      I was also more hinting to the fact that you can't get modded past the 5 points for a post, but I should have formulated it differently.

    6. Re:Here's a game by Daimanta · · Score: 1

      Could go both ways. Can't we get a better picture?

      --
      Knowledge is power. Knowledge shared is power lost.
    7. Re:Here's a game by houghi · · Score: 2

      What 5 points only? The last time I got 15 modpoints. Unfortunatly the time between them is too long and then the time to give them is too short.

      I rather have less points more often, so that the total amount is the same, but I can actually use them all.

      --
      Don't fight for your country, if your country does not fight for you.
    8. Re:Here's a game by PJCRP · · Score: 2

      Looking at both the websites that Gizmondo links, no. Although, F4 does give the same message and a link too :v

      --
      Knows everything about nothing and nothing about everything.
    9. Re:Here's a game by InsaneMosquito · · Score: 1

      I only get 5 :( I had mod points early this week.

    10. Re:Here's a game by MsGeek · · Score: 4, Informative

      Better pic here. Perhaps Lenovo should have used Red Flag Linux for this mission-critical application?

      --
      Knowledge is power. Knowledge shared is power multiplied.
    11. Re:Here's a game by Renderer+of+Evil · · Score: 0, Troll

      Took me a while but I think I decoded the message. It says:

      This copy of Windows XP is not Genuine. To use all Microsoft Windows Features your copy must be validated. Go online and resolve now.

    12. Re:Here's a game by Anonymous Coward · · Score: 0

      It looks like 0x000000F4 which brings up a lot of messages about IDE/hard drive connections and the occasional ram failure. It's not a common one so I'd be willing to bet hardware's the culprit.

    13. Re:Here's a game by Anonymous Coward · · Score: 0

      You mean 'photoshop enhanced version'? It's the same pic.

    14. Re:Here's a game by MsGeek · · Score: 1

      You actually *can* make out the stop error on this picture. Here, I'll type it in for those who don't want to follow the link:

      (STOP: Ox000000f4 0x0000000[can't read number hidden by guy wire] 0x8a014260 0x8a0143d4 0x80609528)

      OK, Windows gurus...have at it. The operating system is XP Embedded according to a very informative post on the other page.

      --
      Knowledge is power. Knowledge shared is power multiplied.
    15. Re:Here's a game by jellomizer · · Score: 1

      If they use Red Flag Linux chances are it wouldn't have detected the displays although it wouldn't crash, it wouldn't have displayed anything anyways. What they should have done was use a Mac.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    16. Re:Here's a game by Daimanta · · Score: 2, Informative

      0x000000F4: CRITICAL_OBJECT_TERMINATION

      One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message. One user, who experienced this on return from Standby mode on Win XP SP2, found the cause was that Windows was installed on a slave drive; compare KB 330100.

      That's probably it.

      --
      Knowledge is power. Knowledge shared is power lost.
    17. Re:Here's a game by dudeinthedark · · Score: 1

      Someone hit control-alt-delete and killed a proccess :O

    18. Re:Here's a game by bhtooefr · · Score: 1

      Sounds like malware can cause it, too, and I've also seen some references to weird behavior on SMP machines with overlapping console windows, which most likely wouldn't be the case on this machine.

    19. Re:Here's a game by Anonymous Coward · · Score: 0

      Well, it appears that a thread or process vital to sysem function (System Idle process?) took a bit of a hit. Never had that one myself.

    20. Re:Here's a game by Anonymous Coward · · Score: 0

      CAn anyone actually see what is on the blue screen well enough to type it out so us blind old geezers can read it? I see a stop code at the bottom, but I cannot read it except for the 0x000000), or most of the rest of the display.
      Us old guys, from the 360 / vax vms / mac / unix world have never seen one of these and are enthralled. heh heh.

      This is what I got:

      A problem has been detected and windows has been shut down to prevent damage
      to your computer.

      A process or thread crucial to system operation has unexpectedly exited or been ..

      If this is the first time you've seen this stop error screen,
      restart your computer. If this screen appears again, follow
      these steps:

      Check to make sure ... ... hardware or software is properly installed.
      If this is a new installation, ask your hardware or software manufacturer
      for any windows updates you might need.

      if problems continue, disable or remove any newly installed hardware
      or software, disable BIOS memory options such as caching or shadowing.
      If you need to use safe mode to remove or disable components, restart
      your computer, press F8 to select advanced startup options, and then
      select safe mode

      Technical information:

      *** STOP: 0x000000.. .... .... .... ....

      All .... are unknown, unreadable.

    21. Re:Here's a game by Anonymous Coward · · Score: 0

      Oh that was simple, it was the 'monitor' driver, that overflowed a text character string. Apparently storing GB characters in an ASCII character reserved space in memory is not the best thing to do, especially if the memory block next of it contains the device instructions mappings of the very same driver. Seriously the windows kernel is pretty stable, it is the manufacturers of cheap Chinese rubbish (pun intended) that usually makes a mess of it.

    22. Re:Here's a game by Handover+Phist · · Score: 1

      Nope, It's a 0xF4

      Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION

      The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

    23. Re:Here's a game by fan+of+lem · · Score: 1

      TRANSLATE SERVER ERROR

    24. Re:Here's a game by MsGeek · · Score: 1

      Of course they should have used Macs, but Lenovo was the sponsor and not Apple. And ultimately not displaying anything is better than displaying Wrong Thing. So if it failed completely it wouldn't have looked as spectacularly bad as having a BSOD up where a graphic or whatever should have been. Yes, Macs are definitely better for anything where you use graphics or video. Unless you are talking about the ones with the cursed/cursable NVidia video chips. Or if you are doing something elaborate in 3D and all you have is Intel built in video.

      --
      Knowledge is power. Knowledge shared is power multiplied.
    25. Re:Here's a game by Anonymous Coward · · Score: 0

      Unfortunately moderators don't know what flamebait is. Taking a large group of smug people then saying there solution wont work just to piss them off is a famebait.

    26. Re:Here's a game by PRMan · · Score: 1

      Race condition in their thread programming lead to a deadlock situation?

      --
      Peter predicted that you would "deliberately forget" creation 2000 years ago...
    27. Re:Here's a game by Anonymous Coward · · Score: 0

      Easy, I read BSOD's for a living:

      http://support.microsoft.com/kb/916199

    28. Re:Here's a game by Nintendork · · Score: 1

      Maybe they should build their computers properly? That looks like a 0xF4. http://support.microsoft.com/default.aspx?scid=kb;en-us;330100

    29. Re:Here's a game by Ilgaz · · Score: 1

      Why doesn't China use their "own" OS anyway? Oh, Microsoft is the sponsor eh? Funny World really.
       

    30. Re:Here's a game by Anonymous Coward · · Score: 0

      Nice try but as the guy that designed the systems being used for this event I can tell you that you are way off here as is most every other post on here.

      About the only detail that has been posted that is correct is that these are XP Embedded.

    31. Re:Here's a game by Heidistein · · Score: 1

      Its not a clear picture, but it *looks* like a machine-check-exception of some sort, possibly an overheated CPU.

    32. Re:Here's a game by Anonymous Coward · · Score: 0

      It looks like a stop 7A or KERNEL_DATA_INPAGE_ERROR. It still could be a driver problem, maybe, but it also could be a memory problem.

  6. Might as well get used to it by elrous0 · · Score: 4, Interesting

    Visible computer glitches pop up in the most unexpected places these days. I went to a 25th anniversay screening of Wargames at a local theater recently. I wasn't even aware that I was in a digital theater until about halfway through the movie their server lost connection to the host and the movie theater screen suddenly turned into a giant Windows desktop. It was a little unnerving (I had thought I was looking at an actual film).

    I think it's something we will just get used to seeing in this increasingly digital age. I just hope I'm not driving down the street one day and see a "lost connection to server" message flashing on a stoplight.

    --
    SJW: Someone who has run out of real oppression, and has to fake it.
    1. Re:Might as well get used to it by Swizec · · Score: 5, Funny

      I just hope someday I'm not driving down the street and see a "lost connection to server" message flashing instead of The Reality!

      That would totally freak me out.

    2. Re:Might as well get used to it by Anonymous Coward · · Score: 0

      You ever see a stoplight go just blinking the red signal all day?

    3. Re:Might as well get used to it by rvw · · Score: 1

      I just hope I'm not driving down the street one day and see a "lost connection to server" message flashing on a stoplight.

      Just wait until your car screen turns blue. That will be a suprise! Anyway, after they have unplugged your brain, you won't remember it anymore, so no harm is done...

    4. Re:Might as well get used to it by JosKarith · · Score: 3, Funny

      Well then don't take the red pill...

      --
      'Don't worry' said the trees when they saw the axe coming, 'The handle is one of us.'
    5. Re:Might as well get used to it by Rub1cnt · · Score: 1

      You ever seen an intersection blue screen? :) (True story.) Bell at Main in downtown Houston, the light rail line installed new signal controllers at all the intersections...said controllers run a headless, hardened version of Windows NT4. One day the lights at the intersection were flashing and a metro tech came out, he plugs in this laptop to a network jack in the box and VNCs to the console. Low and behold, it's a windows NT4 workstation and its bluescreened. A quick reboot later and the lights were working... Scary thought that the traffic lights in a major metropolitan area are controlled by such arcane software.

      --
      Remember, it's not paranoia if they really ARE out to get you... :)
    6. Re:Might as well get used to it by Waffle+Iron · · Score: 1

      I wasn't even aware that I was in a digital theater until about halfway through the movie their server lost connection to the host and the movie theater screen suddenly turned into a giant Windows desktop.

      What's even more unnerving is when the Windows desktop locks up in the projector, then after about 20 seconds it starts melting and smoking, and then an expanding hole consumes the whole screen. I hate when that happens.

    7. Re:Might as well get used to it by Anonymous Coward · · Score: 1, Interesting

      I recall wondering past an ATM one night and it was happily (perhaps) displaying the Win98 boot screen, then nothing, then the Win98 boot screen over and over.

      Although deep down you know these things (desktop OSs) run fairly ordinary objects in our life, it's a little weird when you see signs of it at the surface.

    8. Re:Might as well get used to it by ZERO1ZERO · · Score: 1

      What res did it look like it was running at?

    9. Re:Might as well get used to it by kent_eh · · Score: 1
      We were at an airport last week and my son (7 years old) pointed out that the "arrivals" display screen had a windows taskbar visible, and said "that screen shouldn't be like that, should it?".
      I regularly see someone's desktop displayed on wall-sized displays that normally show an advertising slideshow. Or occasionally on the scoreboard at sporting events.

      And no one thinks it's unusual for these sort of systems to be designed so poorly that stuff that's not supposed to be displayed can be displayed.
      The more mediocrity we see, the more people will grow to expect mediocrity.

      I'm happy that my son recognizes that it's wrong.

      --

      ---
      "I can't complain, but sometimes still do..." Joe Walsh
    10. Re:Might as well get used to it by MsGeek · · Score: 2, Interesting

      The displays in the Red Line/Purple Line subway of LA's Metro Rail system are all on some embedded version of Windows. I've seen bluescreens and other errors, plus one time when you actually saw the desktop. With Internet Exploder and Windows Media Player among the icons on the desktop. It's not as crucial as a stoplight or an ATM but it's disheartening to see. Another place Windows runs in the LA transit system is on the monitors on almost every bus showing entertainment and ad programming to the captive audience on the bus. Seen lots of Windows Fail on that system.

      --
      Knowledge is power. Knowledge shared is power multiplied.
    11. Re:Might as well get used to it by Missing_dc · · Score: 1

      Seeing a 2KW quartz bulb explode because some idiot caught a loop of the coolant line in an access door on the pedestal is impressive. Having to clean it up is not.

      --
      How amazed would you be to suddenly find that you just forgot what I wrote and you needed to reread my post.... again.
    12. Re:Might as well get used to it by fm6 · · Score: 1

      It's all too common in China, where people often resort to machine translation, and don't have a fluent English speaker nearby to check copy. See here and here.

    13. Re:Might as well get used to it by LocoMan · · Score: 1

      I went to a 25th anniversay screening of Wargames at a local theater recently. I wasn't even aware that I was in a digital theater until about halfway through the movie their server lost connection to the host and the movie theater screen suddenly turned into a giant Windows desktop. It was a little unnerving (I had thought I was looking at an actual film).

      So that's why it happens... when I went to see Dark Knight and the projector turned on it was the windows XP loading screen... too bad they turned it off before I could get my cell phone out to take a picture.. didn't knew we had a digital theater in this city.. :)

    14. Re:Might as well get used to it by elrous0 · · Score: 1

      It looked just like regular film to me. But it was hard to tell, since I was with a girl who doesn't understand that sitting way back in the last row of a movie theater defeats the purpose of going to one in the first place. But I'm sure it was at least 2K (2048×1080 at 24 fps).

      --
      SJW: Someone who has run out of real oppression, and has to fake it.
    15. Re:Might as well get used to it by RAMMS+EIN · · Score: 1

      ``I just hope I'm not driving down the street one day and see a "lost connection to server" message flashing on a stoplight.''

      I think I saw pretty much that the other day. I was approaching a traffic light, and it suddenly went from red to blinking yellow. Blinking yellow is normally seen only at night, when they turn off the traffic lights, because the flow is better without regulation. This was in the afternoon, though.

      --
      Please correct me if I got my facts wrong.
    16. Re:Might as well get used to it by Sitten+Spynne · · Score: 1

      It sounds like you were at the theater for a different reason than the girl.

    17. Re:Might as well get used to it by Anonymous Coward · · Score: 0

      Well maybe if they had beefed up security around the WOPR sooner, that wouldn't have happened.

    18. Re:Might as well get used to it by elrous0 · · Score: 1

      If I had been, I wouldn't have sat in the back (and without even a whimper of protest). As far back as we were, I could have saved a lot of money and just watched it at home. But such are the sacrifices we make for the fairer sex.

      --
      SJW: Someone who has run out of real oppression, and has to fake it.
    19. Re:Might as well get used to it by Anonymous Coward · · Score: 0

      But it was hard to tell, since I was with a girl who doesn't understand that sitting way back in the last row of a movie theater defeats the purpose of going to one in the first place.

      Dude, I'm a fucking geek, and even *I* can think of reasons why a girl might prefer to sit at the back row on a romantic trip to the cinema.

      It only "defeats the purpose" if the purpose was to actually pay close attention to the Hollywood potboiler you were ostensibly going to see in the first place!

    20. Re:Might as well get used to it by Bert64 · · Score: 1

      Usually they would be controlled by even more arcane software, probably some simplistic embedded controller made 30 years ago...
      It's actually disturbing that such a simple function is being controlled by such unnecessarily complex software running on such overblown hardware (think of all the energy wasted powering a machine capable of running windows as opposed to a simple microcontroller).

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    21. Re:Might as well get used to it by galoise · · Score: 1
      --
      entia non sunt multiplicanda praeter necessitatem
    22. Re:Might as well get used to it by Myopic · · Score: 1

      Wow, that's an especially odd coincidence considering the movie.

      I had a similarly odd thing happen while watching Powder: in the middle of the movie, for no reason, the lamp in the room I was in slowly dimmed to nothing, then slowly came back to full strength, over a period of ten or fifteen seconds. (That is weird because Powder is a movie about a guy who causes weird things to happen to electricity.)

    23. Re:Might as well get used to it by neurovish · · Score: 1

      I saw an ATM at the AMIBIOS "keyboard error, hit F1 to continue" screen. Unfortunately, none of the ATM keys were F1 and I had to go and find another ATM.

    24. Re:Might as well get used to it by pfleming · · Score: 1

      It looked just like regular film to me. But it was hard to tell, since I was with a girl who doesn't understand that sitting way back in the last row of a movie theater defeats the purpose of going to one in the first place. But I'm sure it was at least 2K (2048×1080 at 24 fps).

      You were with a girl? In the back row? And you were thinking about screen resolution?

    25. Re:Might as well get used to it by Joe+The+Dragon · · Score: 1

      lost connection to server on a stoplight likely will be shown as blinking red

  7. Eh, so what? by Reality+Master+201 · · Score: 4, Insightful

    All computers crash - I've made Linux, BSD, OSX, and Solaris machines kernel panic. Hell, I've witnessed a newer zSeries mainframe crash.

    The fact that it happened at an inopportune moment is unfortunate, but that's life.

    1. Re:Eh, so what? by Anonymous Coward · · Score: 0

      I'm a zSeries systems programmer. I've seen some hardware failures that caused minor problems(eg, tape drive failed), but I've never seen an outright system failure comparable to a windows BSOD. What happened on your system? Jes2 locking up because the spool got full doesn't count. ;)

    2. Re:Eh, so what? by hey! · · Score: 4, Funny

      Actually, a zSeries mainframe crashing at an opportune moment would be more remarkable than it crashing at an inopportune one.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    3. Re:Eh, so what? by Capt+James+McCarthy · · Score: 5, Funny

      "All computers crash - I've made Linux, BSD, OSX, and Solaris machines kernel panic. Hell, I've witnessed a newer zSeries mainframe crash."

      And you seem so proud of that. The goal is to make the systems function, not crash.

      --
      There are no loopholes. It's either legal or it's not.
    4. Re:Eh, so what? by UnknowingFool · · Score: 1

      But life is also about the unexpected and how we deal with it. We can see the humor in embarrassing moments like these and laugh at them or we could take them too seriously. I chose to laugh about them.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    5. Re:Eh, so what? by fbjon · · Score: 1

      Still, Windows XP is still a bit complex for what's needed for a job like this. On the other hand, is there even any FOSS/Linux solution available? It probably needs to at least display video, animation, receive/send timing, etc.

      --
      True confidence comes not from realising you are as good as your peers, but that your peers are as bad as you are.
    6. Re:Eh, so what? by Anonymous Coward · · Score: 0

      I once wiped everything from a DD except for the MBR, the system actually booted Linux until it tryed to mount root, then it couldn't and kernel paniced, the machine frooze dead.

      That was my first and only kernel panic.

    7. Re:Eh, so what? by db32 · · Score: 5, Funny

      But so few fail in such a spectacular fashion. I have never seen a kernel panic delivered in anything other than terminal font on a black and white screen. The BSOD is called the BSOD because MS, in their infinite wisdom, opened themselves up to such a joke by deciding to deliver critical system messages with a "calming" blue background and white text. And then doing so very very frequently in the early days.

      Honestly, they should just make it a black screen with some fireworks and a "Congratulations, You Crashed Windows Again!". You know, make it a more positive experience for the user.

      --
      The only change I can believe in is what I find in my couch cushions.
    8. Re:Eh, so what? by jimicus · · Score: 1

      I once wiped everything from a DD except for the MBR, the system actually booted Linux until it tryed to mount root, then it couldn't and kernel paniced, the machine frooze dead.

      That was my first and only kernel panic.

      Easy enough. The MBR doesn't usually require a working filesystem because it just contains a pointer to a block on the disk which contains the bootloader which itself may only contain a pointer to the location of a kernel.

    9. Re:Eh, so what? by Lobster+Quadrille · · Score: 1

      Are you serious? Really?

      It's not that hard to believe that they used a Windows system to show a video or slideshow or something. Lots of people do that. That's not news.

      The fact that Gates happened to be there is no less normal. He's one of the richest guys on earth, newly retired, and there's a big to-do in China. Of course he wants to be there.

      Lay off the conspiracy theories.

      --
      "The cup is in turn designed for holding hot or cold liquids, and has an open rim and closed base." --US Patent #5425497
    10. Re:Eh, so what? by Reality+Master+201 · · Score: 1

      Actually, I have no idea what caused it - the systems folks were running around in a panic and I could never get a straight answer about it. There had been some recent maintenance (SAN expansions, a newer version of DB2, I think), but I was consulting in a different area of the company and wasn't directly involved.

      I did hear someone say that it'd happened a year before, though, which made me wonder what the hell are their systems programmers doing wrong that the mainframe crashes, and that it's done it more than once in recent memory.

    11. Re:Eh, so what? by nedlohs · · Score: 5, Funny

      Not if you are in QA/testing...

    12. Re:Eh, so what? by gad_zuki! · · Score: 1

      We have no idea what the cause was. Usually a BSOD is driver or hardware related. I wonder what garbage lowest-bidder "state owned" computer producer sold them some junk along with junk drivers. Seems more likely than payola from bgates.

      Im also very surprised their configuration is to stay on the BSOD screen instead of rebooting immediately. I havent seen a real BSOD in years.

    13. Re:Eh, so what? by Chelloveck · · Score: 1

      Not to mention that if there's any custom programming to be done, Windows programmers are a dime a dozen.

      I just want to know, what with China's history of copyright protection, whether or not it was a "Genuine" Windows install? :-)

      --
      Chelloveck
      I give up on debugging. From now on, SIGSEGV is a feature.
    14. Re:Eh, so what? by drsmithy · · Score: 1

      What sort of weird legacy-compatibility requirement does the Olympics have, that imposed the we're-forced-into-using-Microsoft-stuff constraint? Because if you don't have that constraint, it simply doesn't make sense to use Windows.

      Kids, this is what happens to you when you drink the Slashdot kool-aid.

    15. Re:Eh, so what? by Anonymous Coward · · Score: 0

      Where I work we have 2 Sun servers that have been running 24/7 since the summer of 2001. With the exception of hardware failure (bad power supply) and total power failure to the building we have not had a single server crash that required a reboot. We have had a few services have to be restarted, but never a complete server crash. A well maintained Unix systems rarely if ever fails as long as the hardware holds out.

    16. Re:Eh, so what? by X0563511 · · Score: 1

      I shared those views before I knew Slashdot existed. Explain that for me?

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    17. Re:Eh, so what? by The+End+Of+Days · · Score: 1

      My projects get a "SUCCESS!!" dialog with flashing colors and a shower of sparks for an error screen (along with error details), at least during QA. I do so love getting defects that read "the system indicated success and failure at the same time."

    18. Re:Eh, so what? by Anonymous Coward · · Score: 0

      Cajun is assuming that the only reason to use Windows is if you are forced to, which makes him an idiot.

    19. Re:Eh, so what? by Anonymous Coward · · Score: 0
    20. Re:Eh, so what? by dotancohen · · Score: 5, Funny

      All computers crash - I've made Linux, BSD, OSX, and Solaris machines kernel panic. Hell, I've witnessed a newer zSeries mainframe crash.

      You are not invited into my house anymore.

      --
      It is dangerous to be right when the government is wrong.
    21. Re:Eh, so what? by Mex · · Score: 1

      Did any of those happen on a televised broadcast of one of the most (if not THE most) watched events of the world?

      If not, I'd say this is more notable than your OSX crash that you wrote about on your blog. =P

    22. Re:Eh, so what? by westlake · · Score: 1
      The fact that it happened at an inopportune moment is unfortunate, but that's life.
      .

      but for an event like the opening ceremonies, why not have a back-up system running the projection - and simply switch from one to the other?

    23. Re:Eh, so what? by Anonymous Coward · · Score: 0

      what is you're a software tester? Isn't that your job?

    24. Re:Eh, so what? by Captain+Spam · · Score: 1

      And you seem so proud of that. The goal is to make the systems function, not crash.

      Only half of engineering is making things function. The other half is breaking things so you know why they function, or why they don't. Besides, it's just FUN! :-)

      --
      Demanding constant attention will only lead to attention.
    25. Re:Eh, so what? by BPPG · · Score: 1

      We can see the humor in embarrassing moments like these and laugh at them

      Exactly. If only they had gotten rick rolled instead.

      --
      What's the value of information that you don't know?
    26. Re:Eh, so what? by lymond01 · · Score: 1

      The BSOD is called the BSOD because MS, in their infinite wisdom, opened themselves up to such a joke by deciding to deliver critical system messages with a "calming" blue background and white text.

      I'd like to note for the record that the words Black and Blue both begin with the letter B.

    27. Re:Eh, so what? by Kingrames · · Score: 1

      The trick here is marketing.
      You can make any skill sound great, you just need the right words.

      --
      If you can read this, I forgot to post anonymously.
    28. Re:Eh, so what? by RAMMS+EIN · · Score: 1

      ``The goal is to make the systems function, not crash.''

      That depends. I am happy when my testers make the software I have written crash. That means they've found a major bug that I can fix before the customer gets bitten by it.

      --
      Please correct me if I got my facts wrong.
    29. Re:Eh, so what? by YttriumOxide · · Score: 1

      In many ways, it is the only reason to use Windows. Although, it may require some expansion of "forced to" to include such things as, "my boss says I have to", or "I have to/want to use app/game xyz which only exists on Windows". But really, is there any reason to use Windows if you DON'T have to?

      --
      My book about LSD and Self-Discovery
      Also on facebook as: DroppingAcidDaleBewan
    30. Re:Eh, so what? by YttriumOxide · · Score: 1

      Clearly I spend too much time in the digital printing world... the letter for black is "K" (in "CMYK") to distinguish it from "B" for blue (in "RGB"). I did a mental double-take when you said that "black" begins with "B". Really, if someone told me that "KSOD" means "Black screen of death", I wouldn't blink at it.

      Maybe I just need some time off work...

      --
      My book about LSD and Self-Discovery
      Also on facebook as: DroppingAcidDaleBewan
    31. Re:Eh, so what? by cryptodan · · Score: 0

      You do know that you can change the color of the background on a BSOD: Changing your BSOD Background

    32. Re:Eh, so what? by scott_karana · · Score: 1

      Meh, at least their kernel panics are informative. It's a different design decision, not a bad one.

    33. Re:Eh, so what? by runningduck · · Score: 1

      I remember when Microsoft advertised no more UAEs [Unrecoverable Application Errors http://support.microsoft.com/kb/75490%5D. They accomplished this by renaming UAEs to GPFs, more commonly known as BSODs.

      --
      -rd
    34. Re:Eh, so what? by mgiuca · · Score: 1

      Do you actually know this guy? Or do you just have an implicit open invitation to all slashdotters to enter your house?

    35. Re:Eh, so what? by dotancohen · · Score: 1

      I have an implicit open invitation to all humans (and dogs) to visit my house, until they prove themselves unworthy. It is one of the perks of not living in my parent's basement.

      --
      It is dangerous to be right when the government is wrong.
  8. omg! Proof! by urcreepyneighbor · · Score: 5, Funny

    We're living in the Matrix! And the Matrix runs Windows!

    No wonder my life is a pile of shit. :)

    --
    "The fight for freedom has only just begun." - Geert Wilders
    1. Re:omg! Proof! by Joe+the+Lesser · · Score: 5, Funny

      You are about to bend a spoon.

      Cancel or Allow?

      --
      "I only speak the truth"
      Karma: null(Mostly affected by an unassigned variable)
    2. Re:omg! Proof! by Anonymous Coward · · Score: 0

      Wake up, Neo!

      (Cancel | Allow)

    3. Re:omg! Proof! by Rub1cnt · · Score: 1

      Panic: Variable 'Spoon' in undefined state 'bent'... Panic: Variable 'Spoon' is nonexistant. set $Spoon$ = 0 echo $Spoon$ There is no spoon.

      --
      Remember, it's not paranoia if they really ARE out to get you... :)
    4. Re:omg! Proof! by dubbreak · · Score: 5, Funny

      There is no spoon...
      Abort,Retry,Fail

      --
      "If you are going through hell, keep going." - Winston Churchill
    5. Re:omg! Proof! by An+ominous+Cow+art · · Score: 1

      > bend spoon
      I can't see any spoon here.

      >

    6. Re:omg! Proof! by Sponge+Bath · · Score: 1

      You are dual booting Windows and Linux Mr. Anderson.
      One of these has a future, and one of them does not.

    7. Re:omg! Proof! by Anonymous Coward · · Score: 0

      [>Allow
      > That's impossible.

    8. Re:omg! Proof! by ZarathustraDK · · Score: 1

      It looks like you're trying to bend a spoon, would you like to:

      - Try harder?

      - Give up?

      - Spew pseudo-existentialist bullshit and see what happens?

      --
      If you quote this signature there'll be 72 copies of Windows ME waiting for you in Heaven.
    9. Re:omg! Proof! by Anonymous Coward · · Score: 0

      You just bent a spoon. Would you like to reboot Windows now?

      Yes No

    10. Re:omg! Proof! by Looce · · Score: 1

      You missed Ignore, you insensitive clod! It goes before Fail.

    11. Re:omg! Proof! by Anonymous Coward · · Score: 0

      It reminds me of Matrix XP:
      http://www.matrix-xp.com/

    12. Re:omg! Proof! by dubbreak · · Score: 1

      Nope. You fail.

      Yes, there were cases where ignore would be an option too, but "Abort, ignore, fail" is the most common error and the one used in pop culture references.

      --
      "If you are going through hell, keep going." - Winston Churchill
    13. Re:omg! Proof! by Anonymous Coward · · Score: 0

      "We're living in the Matrix! And the Matrix runs Windows!" - by urcreepyneighbor (1171755) on Tuesday August 12, @10:32AM (#24568283)

      Yes, it does:

      APK Matrix ScreenSaver:

      http://www.techpowerup.com//downloads/390/APK_Matrix_ScreenSaver.html

      ----

      "No wonder my life is a pile of shit. :)" - by urcreepyneighbor (1171755) on Tuesday August 12, @10:32AM (#24568283)

      Well, because that screensaver above is written in Borland Delphi 3-7x code (was recompiled thru each as they released)? It can be ported to LINUX quite easily (since it does no work on Tcp/IP (where Linux & Win32 have SOME small diff.'s), diskdrive letters (MS stuff) vs. mounted devices (Linux) work (well, some would have to be done here to compensate for detecting %windir% as I do on Win32 (because screensavers are housed typically in %windir%\system32 by default, I did so), NOR does it use 3rd party VCL controls that may or may not have ports on the LINUX platform into CLX statically inlined compiled libs/addons (like .OCX/ActiveX, but needs no externally distributed component or runtime (true standalone executables produced, the default)).

      APK

  9. Videos by Elektroschock · · Score: 1

    Are there any videos or news coverages of the incident?

    1. Re:Videos by JCSoRocks · · Score: 2, Funny

      From china? Good luck! They've long since taken any digital recording device that was present and "corrected" the images it captured before returning it to its owner (if they were lucky).

      --
      You are using English. Please learn the difference between loose and lose; they're, there, and their; your and you're.
  10. Where the haha tag? by UnknowingFool · · Score: 2, Funny

    Nelson (points finger at Bill Gates): haha

    Seriously where's the haha tag?

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  11. Faked by squoozer · · Score: 4, Interesting

    I wonder if this was faked like the fireworks?

    --
    I used to have a better sig but it broke.
    1. Re:Faked by fbjon · · Score: 1

      The fireworks were simulated, not faked, yes?

      --
      True confidence comes not from realising you are as good as your peers, but that your peers are as bad as you are.
    2. Re:Faked by cyfer2000 · · Score: 1

      The fireworks were real, only the video on your TV was CGI. I doubt if the picture is PSed anyway.

      --
      There is a spark in every single flame bait point.
    3. Re:Faked by yanyan · · Score: 1

      I wouldn't be surprised if China had an axe to grind against m$ and faking an embarrassing incident such as this would serve as a slap to m$.

    4. Re:Faked by rs232 · · Score: 1

      do you get paid to type that BullShit~1 ®

      --
      davecb5620@gmail.com
    5. Re:Faked by OldManAndTheC++ · · Score: 3, Funny
      • Man: Wow! That was the best sex I ever had! Was it good for you too?
      • Woman: Oh, yeah.
      • Man: For real? You weren't faking?
      • Woman: No, not exactly.
      • Man: Huh?
      • Woman: Well, I was simulating...
      • Man: Whew! That's a relief!
      --
      Soylent Green is peoplicious!
    6. Re:Faked by fbjon · · Score: 1

      Not quite. If it really was the greatest for her, but she had a mask on that simulated the experience, it'd be accurate.

      --
      True confidence comes not from realising you are as good as your peers, but that your peers are as bad as you are.
    7. Re:Faked by misterooga · · Score: 1
  12. ... Eh, so what? ... by ninjagin · · Score: 3, Insightful

    Really, how big a deal is this? It's not uncommon to get a BSOD from time to time, and the number and power of the computing resources involved was probably pushing the limit. I'm not surprised and I don't think it's a big deal. The NBC people were practically falling all over themselves to find a flaw in the opening ceremonies, and if this is the biggest thing that surfaces, they went off flawlessly, imho. Who really cares about one little BSOD in such a huge spectacle, really?

    --
    .. pa-ra-bo-la, pa-ra-bo-la, 2 pi R, 2 pi R, where's your latus rectum, where's your latus rectum, 2 pi R
    1. Re:... Eh, so what? ... by Darfeld · · Score: 3, Insightful

      I bet the guy in charge and the Chinese government don't see it your way.

      Glitch happens, but for ceremonies like this one, this isn't a little glitch. If people notice, it's bad, specially if you're trying to impress people.

      --
      (\__/) This is Lapinator
      (='.'=) copy it in your sig
      (")_(") so it can take over the world
    2. Re:... Eh, so what? ... by Anonymous Coward · · Score: 0

      And that attitude is exactly why they still happen with the frequency they do - piss poor quality attitude of the majority of software programmers (not that I said majority, not all.)

      I think it should be mandatory that every software engineer have exposure to embedded systems programming where failure is not an option. IMHO, all software quality would go up drastically because the programmers would then have at least half a clue as to what quality really means.

    3. Re:... Eh, so what? ... by Cajun+Hell · · Score: 1

      It's not uncommon to get a BSOD from time to time

      It's pretty damn uncommon if you don't run Windows!

      I know the Olympics have been around for a long time, but they are so big-money, that it's hard to believe they are still paying for some mistake they made back in the 1980s, such that they have to run Windows. Getting a BSOD on a main display like that, is like seeing a videotape where a lobbyist gives your congressman a bag with a comical "$" on the side of it. It's a fuckup beyond obviousness, into over-the-top ridiculous territory.

      --
      "Believe me!" -- Donald Trump
    4. Re:... Eh, so what? ... by Abcd1234 · · Score: 1

      Really, how big a deal is this?

      It isn't a big deal at all. But it's funny. Laugh, ffs.

    5. Re:... Eh, so what? ... by drsmithy · · Score: 1

      It's not uncommon to get a BSOD from time to time [...]

      It's only "not uncommon" if you don't bother to find the cause and fix it.

      None of my systems have seen a BSOD for nigh-on a decade.

    6. Re:... Eh, so what? ... by IorDMUX · · Score: 1

      Because...

      I laughed.

      And the opening ceremonies were utterly amazing.

      And it's still funny.

      --
      >> Standing on head makes smile of frown, but rest of face also upside down.
    7. Re:... Eh, so what? ... by Anonymous Coward · · Score: 0

      Dude, it's Microsoft! We don't really care whether or not something like this is likely to happen, it's just very convenient placing for a Microsoft bashing. To quote the /. label, "It's funny, laugh!!!"

  13. Bad Memory by tripmine · · Score: 1

    Isn't that the broken RAM BSOD?

    1. Re:Bad Memory by KillerBob · · Score: 1

      What do you expect from Chinese knockoff hardware?

      --
      If you believe everything you read, you'd better not read. - Japanese proverb
  14. Re:Doesnt look like a BSOD... by Darkness404 · · Score: 1

    Or you know, you could just download a *free* Linux ISO with no BSoDs and the same fundamental architecture as OS X but minus the expense.

    --
    Taxation is legalized theft, no more, no less.
  15. It was bound to happen by cjh79 · · Score: 1

    It was probably hardware failure, and given the shear number of lights/projectors/lighted up people/people flying through air going on, something was bound to fail at some point during that ceremony. This seems pretty minor.

    1. Re:It was bound to happen by Anonymous Coward · · Score: 0

      What can't people spell? It's sheer.

  16. In fairness to software engineering by SgtChaireBourne · · Score: 1, Insightful

    In fairness to Microsoft, blue screens are normally due to bad hardware drivers. Whatever that thing actually was, it certainly wasn't a normal monitor and I'll bet the drivers are rather specific. And the less people use them, the fewer bugs are found.

    Cheers,
    Ian

    Jeez. MS apologists always trot out that one. Making bad engineering acceptable will probably be Bill Gates' largest "contribution" to society.

    In fairness to software engineering, if the "bad" hardware driver can crash the system, then the system is not ready for production and has more than a few show-stopping (no pun intended) bugs. Take a look at basic kernel or micro-kernel design principles and stop spreading the view that catastrophically bad design is acceptable.

    --
    Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
    1. Re:In fairness to software engineering by jimicus · · Score: 5, Insightful

      Jeez. MS apologists always trot out that one. Making bad engineering acceptable will probably be Bill Gates' largest "contribution" to society.

      In fairness to software engineering, if the "bad" hardware driver can crash the system, then the system is not ready for production and has more than a few show-stopping (no pun intended) bugs. Take a look at basic kernel or micro-kernel design principles and stop spreading the view that catastrophically bad design is acceptable.

      Linux puts most drivers in the kernel and a bad driver there can cause a panic, bringing the system down.

      Most of the BSDs, AFAIK, have some drivers in the kernel and others in userland processes.

      I'm not sure how it's architected in Mac OS X, but I've certainly seen kernel panics on my Mac Mini.

      There may be an embedded OS which is less susceptible to being killed by a poor driver, but for something like this you probably wouldn't bother with an embedded OS because there's so much more in the way of off-the-shelf software available to do the job for Windows and Linux.

    2. Re:In fairness to software engineering by bunratty · · Score: 2, Interesting

      Back when Windows NT was being developed, I heard that device drivers had to communicate with hardware through the hardware abstraction layer (HAL), and this made Windows NT very stable. Then I heard that they decided to allow hardware drivers to connect directly to hardware because sometimes going through HAL had a performance hit. I can't find much information on the history, but these lecture notes seem to confirm that drivers can now bypass HAL. Is this why bad drivers can still crash Windows?

      Microsoft at least provides tools to verify that drivers work properly.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    3. Re:In fairness to software engineering by hcmtnbiker · · Score: 5, Insightful

      In fairness to software engineering, if the "bad" hardware driver can crash the system, then the system is not ready for production and has more than a few show-stopping (no pun intended) bugs. Take a look at basic kernel or micro-kernel design principles and stop spreading the view that catastrophically bad design is acceptable.

      I'm sorry, do you know of an operating system where talking to hardware cannot cause a panic? Even microkernels such as Mach are prone to these problems. ANY time you touch hardware there can be a problem if it's coded wrong. Even microkernels have to allow DMA for certain hardware, and bad DMA can bring down a whole system without even trying. There's a basic design flaw in how normal computers operate that requires this sort of behavior from kernels, which leads to bad drivers affecting them. If you can name one system ready for general purpose for which this isn't true I would love to hear about it.

      --
      If i had one dollar for every brain you dont have, i would have $1.
    4. Re:In fairness to software engineering by Anonymous Coward · · Score: 0

      I've seen system-crashing bugs happen in OSX, too. Except that it was made to look purdy, though you couldn't do anything other than unplug the whole deal, and then restart it.

    5. Re:In fairness to software engineering by Anonymous Coward · · Score: 1, Interesting

      Oh really? Then I guess Linux is not ready for production . And neither is Mac. Stop acting like a dumbass just to get mod points. Looks like you've succeeded well in baiting some zealot mods though. (Posting as AC since I used some mod points on this article).

    6. Re:In fairness to software engineering by NiceGeek · · Score: 1

      I can count on the fingers of one hand the number of kernel panics I've seen on either my Linux box or my Mac Mini. My Windows machines however.....

    7. Re:In fairness to software engineering by bigstrat2003 · · Score: 3, Insightful

      Jeez. MS apologists always trot out that one.

      No, people who are reasonable and levelheaded always trot out that one.

      --
      "16MB (fuck off, MiB fascists)" - The Mighty Buzzard
    8. Re:In fairness to software engineering by jeremyp · · Score: 5, Interesting

      As somebody who has written a bad device driver for Mac OSX I can confirm that a bad driver can and frequently has crashed my OS X kernel.

      OS X is based on a microkernel, but in practice it is as monolithic as Linux or BSD.

      --
      All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
    9. Re:In fairness to software engineering by chaim79 · · Score: 1

      Number of kernel panics on my MB Pro not relating to a bad third-party usb wifi card: 2

      Number of kernel panics on my MB Pro related to a bad third-party usb wifi card: ... lost count around 20 or so... wouldn't last 30 min of serious network usage before crashing the computer. Be wary of third party usb wifi cards!

      Number of kernel panics on my windows box: None in the last year, it has been unplugged all that time! Before that? Forget it... way to many to count!

      Number of kernel panics on my Linux/BSD boxes: None, very stable.

      So in the end, Linux has the best record so far, windows is terrible, and Mac good without using bad drivers. Sounds about right.

      --
      DEMETRIUS: Villain, what hast thou done?
      AARON: Villain, I have done thy mother.
      Shakespeare invents 'your mom'
    10. Re:In fairness to software engineering by OnlineAlias · · Score: 3, Interesting

      100% true. NT 3.5 and 3.51 had the video outside the kernel. NT 4.0 moved it to kernel level. This was a big to do at the time, with everyone claiming that NT 4 was going to become unstable that way. Ironically, XP probably wouldn't have been used for projecting graphic images on a ceiling if that change had not been made 2 generations back. Damned if you do, damned if you don't...

    11. Re:In fairness to software engineering by tehcyder · · Score: 4, Funny

      No, people who are reasonable and levelheaded always trot out that one.

      So, unlikely to have been seen on slashdot before then?

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    12. Re:In fairness to software engineering by Colonel+Korn · · Score: 0, Troll

      I've seen system-crashing bugs happen in OSX, too. Except that it was made to look purdy, though you couldn't do anything other than unplug the whole deal, and then restart it.

      At the Apple store at Valley Fair in San Jose I always manage to crash any Mac I use within 5 minutes by running programs or opening images and resizing them in the default viewer. Maybe the hardware in the store is the bad stuff or the power is very dirty, but it's been like that for years.

      And it's not pretty, it usually just reboots on its own with no warning.

      --
      "I zero-index my hamsters" - Willtor (147206)
    13. Re:In fairness to software engineering by bigstrat2003 · · Score: 5, Informative

      You were doing something wrong with your Windows box then. I have almost never (either with my own machines or at work) seen a BSOD that wasn't caused by faulty hardware. It happens, but it's something that happens maybe once every couple of years per computer.

      --
      "16MB (fuck off, MiB fascists)" - The Mighty Buzzard
    14. Re:In fairness to software engineering by Blakey+Rat · · Score: 1

      I got a decent amount on my iBook running 10.4. And that was the new one, after the first iBook with the faulty motherboard was replaced. (That thing was a total lemon; it crashed every week.)

      Since I've put Vista on my desktop and laptop I've had 2 crashes on my Desktop and none on my laptop. The desktop crashes were caused by ATI's crummy-ass drivers. (I've also had multiple ATI driver reboots; fortunately this doesn't crash Vista, it just blanks out the screen for a few seconds.)

      From my personal experience, I'd say the two OSes are on par. Of course, I don't buy crappy hardware (on purpose!) and I don't run weird huge Olympics projectors.

    15. Re:In fairness to software engineering by Anonymous Coward · · Score: 0

      I believe there was a study that determined the vast majority of bugs in Linux and FreeBSD kernel bugs over the last $n years are also in the drivers. This is a fact of life: the people who write drivers are usually different from the people writing the core kernel functionality, not as skilled, etc. So it's not an "excuse" but rather backed by real statistics, and Linux is not exempt.

    16. Re:In fairness to software engineering by the_womble · · Score: 1, Informative

      Even microkernels such as Mach are prone to these problems.

      Can, but comparatively how often?

    17. Re:In fairness to software engineering by kwabbles · · Score: 5, Funny

      There's a basic design flaw in how normal computers operate that requires this sort of behavior from kernels, which leads to bad drivers affecting them. If you can name one system ready for general purpose for which this isn't true I would love to hear about it.

      GNU Hurd

      --
      Just disrupt the deflector shield with a tachyon burst.
    18. Re:In fairness to software engineering by dotancohen · · Score: 1

      I can count on the fingers of one hand the number of kernel panics I've seen on either my Linux box or my Mac Mini. My Windows machines however.....

      All the Chinese together have not enough fingers to count embarrassing BSODs that I've seen in university lectures, malls, and the like. Is that because Windows is so widespread? Then it is being spread in all the wrong places.

      --
      It is dangerous to be right when the government is wrong.
    19. Re:In fairness to software engineering by chaim79 · · Score: 2, Interesting

      Not quite, doing development stuff I'd be downloading tools, libraries, and software packages to help out, and just about every time I'd get about 6 months after initial install of windows and it would go into BSOD cycle, eventually it'd be bad enough to reinstall windows and the cycle would start over again.

      So yah, not normal usage... but I'm doing roughly the same thing with my MB Pro and I haven't run into the same problem.

      --
      DEMETRIUS: Villain, what hast thou done?
      AARON: Villain, I have done thy mother.
      Shakespeare invents 'your mom'
    20. Re:In fairness to software engineering by tubapro12 · · Score: 2, Insightful

      While we're already off-topic, I've got to agree with the GP, my Windows box BSODs a few times a year (almost always hardware driver failures, particularly the video card). Running Linux on the same machine, I've yet to actually crash it, I've crashed X a few times, but never the OS.

      Of course, if I count the times I've forced Windows to crash using the CrashOnCtrlScroll trick for fun...

    21. Re:In fairness to software engineering by julian67 · · Score: 1

      Bad drivers can crash any system using a monolithic kernel. I've had the misfortune to use a driver that crashes the Linux kernel this year (Intel iwl3945 on 2.6.25). Only low level problems can cause a Windows BSOD, usually this means driver level i.e drivers for hardware devices or some software like anti-virus and 3rd party firewalls, or tools like anydvd which bypasses copy protection using kernel hooks. btw I'm not an MS apologist, I use Debian and don't like Windows but facts are facts. XP these days is stable (it only took 7 years but they made it) and you won't see a blue screen using signed drivers and hardware that isn't malfunctioning. I'd guess the picture is in any case a fake.

    22. Re:In fairness to software engineering by MobileTatsu-NJG · · Score: 3, Insightful

      I can count on the fingers of one hand the number of kernel panics I've seen on either my Linux box or my Mac Mini. My Windows machines however.....

      I've actually had my Macbook Pro freeze more times in the last year than my Windows machine. In fact, it even hung once when I closed the lid and tried to fry itself with the backlight. That's funny about this is I've had the Macbook for about 4 months, whereas I've had the Windows machine all year.

      I promise you this is a true story. Your mileage may vary, even if you're a Mac user.

      --

      "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

    23. Re:In fairness to software engineering by JakeD409 · · Score: 3, Interesting

      Definitely. I bought a D-Link USB WiFi adapter, downloaded their official Mac drivers, and the thing crashed my Mac every half hour.

    24. Re:In fairness to software engineering by Mr+44 · · Score: 5, Informative

      and now, with Vista, display drivers are back to being in user-mode:
      At a technical level, WDDM display drivers have two components, a kernel mode driver (KMD) that is very streamlined, and a user-mode driver that does most of the intense computations. With this model, most of the code is moved out of kernel mode. That is, the kernel mode piece is now solely responsible for lower-level functionality and the user mode piece takes on heavier functionality such as facilitating the translation from higher-level API constructs to direct GPU commands while maintaining application compatibility. This greatly reduces the chance of a fatal blue screen and most graphics driver-related problems result in at worst one application being affected.

    25. Re:In fairness to software engineering by Anonymous Coward · · Score: 0

      He most certainly *was* doing something wrong with his Windows box if it crashed from a bad OS X device driver!

    26. Re:In fairness to software engineering by Not+The+Real+Me · · Score: 0

      My experience is that Linux tends to tolerate faulty hardware better than Windows. I run http://www.memtest.org/ on a machine for 24 hours. If there are no errors, then it will run WinXP and will be extremely stable. If there are minor non-repeatable errors then I know that I can safely run Linux on it, but not Windows.

    27. Re:In fairness to software engineering by AttillaTheNun · · Score: 1

      How about once every olympiad?

    28. Re:In fairness to software engineering by r_newman · · Score: 0

      Linux puts most drivers in the kernel and a bad driver there can cause a panic, bringing the system down.

      Not being a Linux kernel programmer, I won't comment on this except to ask a question; even if it's true, what bearing does it have on how Windows screwed up at the Olympics?

      I'm not sure how it's architected in Mac OS X, but I've certainly seen kernel panics on my Mac Mini.

      Ummm... "architect" is a noun.

      --
      Bzzzzzt..."AAAAaaaaarrrgh!!!" Thud.
    29. Re:In fairness to software engineering by Anonymous Coward · · Score: 0

      PSP homebrew?

    30. Re:In fairness to software engineering by Anonymous Coward · · Score: 0

      It's mostly related to the design of PC hardware than anything else. For peripherals to work in a PC world they need to talk intimately with low level portions of the OS. In contrast to this, other non-PC architectures talk via other mechanisms so are more insulated from bad hardware/drivers. But this was done for cost reasons. PCs are cheap. They are starting to get high-level features but slowly, very slowly.

    31. Re:In fairness to software engineering by WebCowboy · · Score: 2, Informative

      I'm sorry, do you know of an operating system where talking to hardware cannot cause a panic?

      [...]

      If you can name one system ready for general purpose for which this isn't true I would love to hear about it.

      I haven't worked with QNX lately, but it has historically been a very tolerant OS in my experience. You are correct that at some point the OS MUST access hardware directly, and that faulty hardware will cause a software crash...but there are degrees of vulnerability here.

      Microkernel OSes, especially those like QNX that are used in embedded and/or real-time applications, are extremely fault tolerant. Because hardware subsystems are each accessed by separate, self-contained low-level processes, a hardware fault in fact will NOT cause a systemic software failure as you assert. You DO in fact have to "try" to "bring down a whole system" through hardware faults in such architectures.

      Nothing will stop systemic hardware faults from causing systemic software crashes, but the fact is that when it comes to Windows (and to a lesser but still significant degree, Linux and Mac OSX) hardware fault tolerance is absolutely wretched compared to what it COULD be. Microkernel architecture helps but isn't the magic bullet either--remember that MacOS X AND Windows are BOTH technically "microkernel architectures" and that doesn't keep them from falling over due to a hardware fault or bad driver.

      There's a basic design flaw in how normal computers operate that requires this sort of behavior from kernels

      Linux is very stable relative to Windows even though it is a monolithic kernel architecture because it is a better engineered platform overall, both in terms of security AND because drivers are much better written (owing to the fact that the bulk of drivers are community-written and/or open source instead of supported by an overworked small team of programmers employed by a hardware company that chronically under-invests in software development for its revenue-generating hardware products). In all but TWO cases (one case being a total hard drive failure where the system continued to run without HD access until a page swap was required, and another where several cheap Chinese capacitors dried out and popped in another system, which also would boot and run for hours to days nonetheless) my 11 years of extensively using Linux ALL kernel panics have been due to SOFTWARE bugs in drivers, and in most of those cases they were CLOSED drivers (I'm talking to you NVidia!).

      Even with the problems I've had with closed drivers in Linux, the problems are very small in number and severity in comparison with Windows. NVidia drivers still are relatively unreliable however when there is a problem in Windows it can make the system BSOD. A similar bug in Linux is most likely to cause a fault in X but the rest of the subsystems are unharmed--in fact the latest NVidia drivers haven't caused me a single kernel panic yet. There is no "basic design flaw" in modern hardware systems that cannot be kept to a very small minimum without proper SOFTWARE design.

    32. Re:In fairness to software engineering by ratboy666 · · Score: 3, Insightful

      Wrong. WRONG.

      Yes, Linux (as a specific example) uses drivers directly in kernel mode. HOWEVER, those drivers are PART of the OS, distributed and supported WITH the OS, and are Open Source, along with the rest of the kernel. Redhat supports the whole thing.

      If drivers are to be supplied "in kernel" this is REQUIRED for reliability. Take Solaris as an example. Source is supplied, along with a DDI layer.

      If drivers are supported ONLY via a "DDK" (driver development kit), there must be an isolation between that part of the kernel that CANNOT be understood by the driver developer, and the driver. This was the primary issue with "unreliable" display drivers in the Windows 3.x days -- functionality MUST be implemented, but the reference was not documented, or incorrect.

      Indeed, a lot of vendors took extreme steps to deal with this issue -- permanent staff at Microsoft, or (illegally) reverse engineering the support code (GDI).

      Unfortunately, the promoted Windows driver development path is "Believe in the DDK, and go" without reference source. Of course, this IS prone to failure -- finally recognized in Vista. (but obvious to vendors since Windows 3.x).

      The solution here? Go to a micro-kernel OS. Or, plant parts of device drivers into standard protected mode (user space). Both of which cause performance issues. Or keep part of your software team in Redmond.

      Also, given that the interface and driving layer (what I would call a "driver") is under Microsoft's control, the test suites must come from Microsoft as well. If a "crash path" is then NOT exercised, that is ALSO Microsoft's problem. There should be no way for a higher level application to utilize anything OTHER than a tested path to the driver. If it can, the testing is useless, and "Microsoft Certification" is useless.

      An analogy at the application layer - SUN has the "application guarantee". That consisted of a series of tools that collected API usage (and could be run by the customer). If an application passed, and then a later upgrade of Solaris BREAKS the application, it is SUN's problem. (SUN fixes the OS or Application).

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    33. Re:In fairness to software engineering by WebCowboy · · Score: 2, Interesting

      Bad drivers can crash any system using a monolithic kernel.

      They can crash microkernel based systems severley too--microkernel systems like Microsoft Windows NT/2k/XP/Vista. The quality of the system architecture overall is far more important than the kernel architecture chosen.

      Only low level problems can cause a Windows BSOD

      Not true. Driver issues are the main reason, but user-level software can behave badly too. You cite anti-virus and firewall software, which aren't exactly "low level". Developer tools are usually the worst user-level offenders.

      XP these days is stable (it only took 7 years but they made it) and you won't see a blue screen using signed drivers and hardware that isn't malfunctioning.

      The thing is it can be difficult to find signed drivers for your system. If you want them for Vista you're SOL unless you have a very recent system (by and large, upgrading to Vista is a really dumb idea--everyone should stay with XP until they are willing to get a completely new machine), and if you have XP or 2K the opposite is true (the latest hardware ain't ever gonna have drivers, and its all closed software so no option to backport). I still run into a LOT of hardware with bad, unsigned drivers that is essential to some application yet behaves badly.

      I'd guess the picture is in any case a fake.

      Given the PRC's track record and the fact that they used "performance enhancing" technology on the official opening ceremonies broadcast I do not regard ANY media out of these olympics as trustworthy. To me, it is just as likely that the official Chinese broadcast digitally erased BSODs from the feed as it is that someone doctored a photo to ADD the BSOD and embarrass the Chinese olympic organisers.

    34. Re:In fairness to software engineering by jedidiah · · Score: 1

      So of course this all begs the question: Did the test the damn thing?

      I bet you they did and that the problem didn't surface.

      They probably had at least one full dress rehearsal with everything
      going on including the doo-dad that decided to crap out during the
      real performance.

      Yes... testing. Also known as a dress rehearsal...

      --
      A Pirate and a Puritan look the same on a balance sheet.
    35. Re:In fairness to software engineering by drspliff · · Score: 3, Interesting

      Have you looked at the efforts of the Minix 3 operating system? It's a true microkernel where most drivers run outside of ring0 with limited access to hardware and/or the kernel.

      Not just that, but it has stuff in place to severely limit the impact of a rogue driver and can restart dead or dying drivers, not to mention it embraces message passing with interrupts being passed to the driver as low-latency messages.

      Other operating systems like QNX implement things in a similar way, although QNX also has guranteed near realtime scheduling and resource allocation allowing the whole system to be partitioned from the development stage.

    36. Re:In fairness to software engineering by Skuld-Chan · · Score: 2, Informative

      I know I'll be modded down to -infinity on this, but seriously - my Mac G5 has kernel panicked more than my Windows XP box (keep in mind my G5 has done this maybe twice last year?)

    37. Re:In fairness to software engineering by julian67 · · Score: 1

      My understanding is that the NT kernel is not a true microkernel but a hybrid because the sub processes run in kernel mode, not user mode like with a real microkernel, so in these terms NT kernel reacts exactly as a monolithic kernel when a driver fails. The user-level software like AV and firewalls is not really user level but kernel mode, it has kernel hooks. In effect it works at driver level which is why a failure can bring down the kernel. A true user mode application can't do that. I don't have any evidence one way or the other if those shots were faked but it's a very easy thing to do and similar things have been done millions of times before. Also the BSOD shot is a long running theme, it's easy to believe, there are lots of people who *want* to believe it and everyone enjoys it. I hope most of us are past the stage of believing something happened because there's a picture on the internet "proving" it.

    38. Re:In fairness to software engineering by RAMMS+EIN · · Score: 2, Interesting

      Even still, this is an interesting situation. Assuming that virtually all BSODs and spontaneous resets on Windows are caused by faulty hardware drivers, apparently, these drivers, produced by professionals, even those certified by Microsoft, even those _shipped_ by Microsoft, seem to cause crashes a whole lot more often than those produced by a horde of hobbyists on the open-source side of the OS world.

      --
      Please correct me if I got my facts wrong.
    39. Re:In fairness to software engineering by Foofoobar · · Score: 1, Informative

      No... bad drivers in Linux only halt the process. They do not bring the entire system down. That is a a major architectural difference between Windows and Linux. If a process dies on Windows (or worse, becomes an out of control process), it CAN bring the entire system down with it. On Linux, only the process dies. This is why you can continually remove processes and daemons that you do not want on Linux as they are not all tied into each other like on Windows.

      --
      This is my sig. There are many like it but this one is mine.
    40. Re:In fairness to software engineering by Jah-Wren+Ryel · · Score: 1

      I know I'll be modded down to -infinity on this, but seriously - my Mac G5 has kernel panicked more than my Windows XP box (keep in mind my G5 has done this maybe twice last year?)

      <mac-fanboi>It is pretty rare for a computer that is turned off to panic.</mac-fanboi>

      --
      When information is power, privacy is freedom.
    41. Re:In fairness to software engineering by Anpheus · · Score: 2

      Let's just go ahead and admit that you crashed it, because when X goes down, 99% of programs will just halt immediately losing all of your saved work. I've never had X go down and then, like when Windows Vista's window manager goes down, have everything working just fine. Seriously, I encountered what must be a rare bug in Bioshock because I alt-tabbed into a maximized window, moved the mouse, and the display driver crashed. Windows brought it back online and informed me of that, and everything (including Bioshock) was running.

      An equivalent error on a Linux box would at least take down the system, and lesser errors would usually kill X and thus make me lose all my work.

    42. Re:In fairness to software engineering by Sigma+7 · · Score: 1

      If a process dies on Windows (or worse, becomes an out of control process), it CAN bring the entire system down with it.

      Only on Windows 9x. Windows NT has long fixed that issue by isolating process space.

      Also, if a critical driver fails (such as a keyboard driver - and for this, it doesn't need to crash), the stability of the core operating system is moot for most people, since they need to reboot the system to get the driver working again. (I experienced this with an OEM "Multimedia keyboard" driver, and know how to correct it.) The same applies to the display driver - if you don't see anything on the screen, you can't do much with your system.

      This is why you can continually remove processes and daemons that you do not want on Linux as they are not all tied into each other like on Windows.

      Want to see which processes/services are "core" in Windows? Run it in safe mode. When you reboot normally, you can disable anything that wasn't enabled in safe mode - but you'll risk losing important functionality such as networking. If you take it to enough of an extreme, some applications won't have dependencies that they expect to be installed. The same applies to Linux - most applications expect things to be running.

    43. Re:In fairness to software engineering by Rudolf · · Score: 1

      ANY time you touch hardware there can be a problem if it's coded wrong.

      Thus, if you code it right, you won't crash.

    44. Re:In fairness to software engineering by orasio · · Score: 1

      But also they answer for the drivers, so a "bad driver" issue is actually a kernel issue.
      I don't understand why "bad drivers" are not supposed to be the responsibility of MS. It's possible to design a system resilient to that kind of failure.
      The Linux solution for having good drivers (maintaining them themselves), seems to be working just fine, though.

    45. Re:In fairness to software engineering by Foofoobar · · Score: 1, Troll

      Well NT only partialy fixed this. Otherwise, rebooting your system after each PATCH would NOT be necessary; you would only need to restart the service. Also, safemode does show required services but unfortunately... far too much is required where it truly is not. Can you get rid of the GUI, can you get rid of Explorer, can you get rid of the mediaPlayer? Some say yes but in actuality you dont because they are still there and running. Are these crucials processes to running a server? No but can you shut them down? Hell no... and will they crash your system or cause a backdoor to be opened in your system? Hell yes.

      By tying everything together, they actually made the system more easy to market and sell other products but NOT more easy to secure or stabilize.

      --
      This is my sig. There are many like it but this one is mine.
    46. Re:In fairness to software engineering by jimicus · · Score: 1

      Linux puts most drivers in the kernel and a bad driver there can cause a panic, bringing the system down.

      Not being a Linux kernel programmer, I won't comment on this except to ask a question; even if it's true, what bearing does it have on how Windows screwed up at the Olympics?

      When the parent post is arguing that the problem is Microsoft choosing to put so many drivers at such an elevated position within the kernel, it demonstrates that the alternatives are not necessarily any better.

      I'm not sure how it's architected in Mac OS X, but I've certainly seen kernel panics on my Mac Mini.

      Ummm... "architect" is a noun.

      And when one is describing how a software architect has designed a particular piece of software, IME it is perfectly acceptable to use it in this way. Put "architected" into Google and you'll get back just over 1,000,000 hits and most of the first page hits relate to software design.

    47. Re:In fairness to software engineering by rubycodez · · Score: 1

      Minix 3

    48. Re:In fairness to software engineering by Mr+Z · · Score: 1

      This is English, where just about any noun can be verbed, and Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo is grammatically correct.

    49. Re:In fairness to software engineering by jimicus · · Score: 1

      No... bad drivers in Linux only halt the process. They do not bring the entire system down. That is a a major architectural difference between Windows and Linux.

      If memory serves, they're threads rather than processes and all threads share the same address space. So it's quite possible for one thread to trample all over everything crashing the OS.

    50. Re:In fairness to software engineering by jimicus · · Score: 2, Interesting

      But also they answer for the drivers, so a "bad driver" issue is actually a kernel issue.
      I don't understand why "bad drivers" are not supposed to be the responsibility of MS. It's possible to design a system resilient to that kind of failure.

      Well, this is very true.

      However, you've got to look at the context. Firstly, Microsoft are more concerned about the system being stable on the sort of hardware bought by businesses - half-decent quality PCs and servers - and these tend to use relatively conservative hardware which has decent drivers.

      Secondly, a bit of history - while the idea of true microkernels with practically every driver being a true userland process is not new, the performance penalty they introduce (which is less of an issue on modern hardware) was considered unacceptable when the NT kernel was first designed - and the kind of overhaul that would be necessary to change this is something Microsoft have historically shied away from.

    51. Re:In fairness to software engineering by Monsuco · · Score: 1, Funny

      I have almost never (either with my own machines or at work) seen a BSOD that wasn't caused by faulty hardware.

      Then you must not be using Vista.

    52. Re:In fairness to software engineering by bigstrat2003 · · Score: 3, Informative

      I most certainly am, and can personally attest that there is a very large portion of FUD in the anti-Vista hype. I even game on Vista, with no problems. People are pretty full of shit about Vista, in general.

      --
      "16MB (fuck off, MiB fascists)" - The Mighty Buzzard
    53. Re:In fairness to software engineering by Mr+Z · · Score: 1

      Not only that, but also the fact that driver code paths are traversed much less often per line of code than core code across the entire user base, by a couple orders of magnitude. Thus they get much, much less testing.

      Heap on top of that the rather poor state of documentation for many peripherals, not to mention their quirkiness and bugginess, and it's surprising drivers work at all!

    54. Re:In fairness to software engineering by kelnos · · Score: 1

      In fairness to software engineering, if the "bad" hardware driver can crash the system, then the system is not ready for production and has more than a few show-stopping (no pun intended) bugs. Take a look at basic kernel or micro-kernel design principles and stop spreading the view that catastrophically bad design is acceptable.

      I don't disagree fundamentally, but... what are the options for OSes that make use of that design and are available and enterprise-ready today?

      --
      Xfce: Lighter than some, heavier than others. Just right.
    55. Re:In fairness to software engineering by binford2k · · Score: 2, Interesting

      In all but TWO cases (one case being a total hard drive failure where the system continued to run without HD access until a page swap was required

      I've got a story that I like to tell about a Linux webserver that had a hard drive failure after running long enough to have the entire web root cached into RAM. We hdparm -Yed it to sleep and unplugged the drive, then let the machine run diskless for a few months until we got around to replacing it.

      This hosted some very well known and active open source projects at the time too.

    56. Re:In fairness to software engineering by Anonymous Coward · · Score: 0

      It happens, but it's something that happens maybe once every couple of years per computer.

      Yeah, it's the system being taken over by malware that occurs on a daily basis.

    57. Re:In fairness to software engineering by afidel · · Score: 1

      Ironically, in the experience of the IT professionals I know the complete rewriting of the driver model has meant that there are actually MORE Vista BSOD's than XP ones as the driver for XP are generally very mature with a known codebase stretching back to Windows 98. Sure there is flaky hardware that will cause BSOD's like crazy but those are fairly easy for a large shop to weed out.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    58. Re:In fairness to software engineering by T-Bone-T · · Score: 1

      There is a difference between accepting bugs and accepting that bugs happen.

    59. Re:In fairness to software engineering by king_nebuchadnezzar · · Score: 1

      Ever Heard of protected memory?

    60. Re:In fairness to software engineering by Iced_Eagle · · Score: 1

      It's because when you used your Mac you weren't being hip and cool and drinking a latte and with some fashionable clothes on. Windows lets us slobs use it just fine!

    61. Re:In fairness to software engineering by kelnos · · Score: 1

      Linux is very stable relative to Windows [...] because drivers are much better written (owing to the fact that the bulk of drivers are community-written and/or open source instead of supported by an overworked small team of programmers employed by a hardware company that chronically under-invests in software development for its revenue-generating hardware products).

      I think also a big part of it is that the bulk of drivers that any Linux user would use are maintained with and shipped with the kernel itself. When a kernel dev changes a driver interface that might have an effect on drivers, he goes and fixes up all the drivers along with it.

      --
      Xfce: Lighter than some, heavier than others. Just right.
    62. Re:In fairness to software engineering by T3Tech · · Score: 1

      ANY time you touch hardware there can be a problem if it's coded wrong.

      Thus, if you code it right, you won't crash.

      So that explains my wife wrecking the car!?

      --
      Of course I didn't RTFA... why would I do that? You really are new here aren't you? Don't let my UID fool you.
    63. Re:In fairness to software engineering by Anonymous Coward · · Score: 0

      In fairness to software engineering, if the "bad" hardware driver can crash the system, then the system is not ready for production and has more than a few show-stopping (no pun intended) bugs. Take a look at basic kernel or micro-kernel design principles and stop spreading the view that catastrophically bad design is acceptable.

      You're right. Linux sucks!!!

      That's not a troll. Some OS's are more fault tolerant than others, but no OS can save you from bad hardware. If that actually turned out to be possible, then no other OS out there is 'not ready for production'.

      Some of you twits with mod-points need to choose your battles more wisely.

    64. Re:In fairness to software engineering by domatic · · Score: 1

      Also, if a critical driver fails (such as a keyboard driver - and for this, it doesn't need to crash), the stability of the core operating system is moot for most people, since they need to reboot the system to get the driver working again. (I experienced this with an OEM "Multimedia keyboard" driver, and know how to correct it.) The same applies to the display driver - if you don't see anything on the screen, you can't do much with your system.

      If the machine still has network access then you can regain control of it that way. I've recovered from the NVidia driver hosing up by restarting the login manager with ssh. Of course, this was on Linux where X is more loosely coupled to the system.

      I suppose if RDC or VNC is running you could regain control that way depending on how badly the display system is screwed up. If nothing else, ssh can still be installed on a Windows system. That would allow a proper restart as opposed to just cutting the power.

    65. Re:In fairness to software engineering by orasio · · Score: 1

      However, you've got to look at the context. Firstly, Microsoft are more concerned about the system being stable on the sort of hardware bought by businesses - half-decent quality PCs and servers - and these tend to use relatively conservative hardware which has decent drivers.

      Secondly, a bit of history - while the idea of true microkernels with practically every driver being a true userland process is not new, the performance penalty they introduce (which is less of an issue on modern hardware) was considered unacceptable when the NT kernel was first designed - and the kind of overhaul that would be necessary to change this is something Microsoft have historically shied away from.

      Well, we know that MS marketing department is to blame for a lot of issues with the system, but from the outside, they are just a company that provides bad solutions to problems.

      I know that the fact that microkernels seem to be hard is an issue, too. There are different ways to make your system reliable, and I understand why they didn't choose any of them.

      Anyhow, being run by marketing, selling proprietary software, or lacking knowledge are excuses, but not good reasons not to provide a reliable platform.

    66. Re:In fairness to software engineering by citylivin · · Score: 1

      "I have almost never (either with my own machines or at work) seen a BSOD that wasn't caused by faulty hardware"

      I saw one yesterday that was caused by a virus. Infact I see them all the time, caused by virii or malware. Now if you had said "faulty hardware DRIVERS" then you might have been more accurate. Still not correct though, as having a virus infected screen saver (what BSODed the laptop i was working on yesterday) has nothing to do with the hardware. I've also had SQL server BSOD machines as well as cold fusion. Bad drivers on vista do it too.

      --
      As a potential lottery winner, I totally support tax cuts for the wealthy
    67. Re:In fairness to software engineering by Anonymous Coward · · Score: 0

      Yeah, minix3 but it's not production status yet ... so you're probably stuck with VXworks.

    68. Re:In fairness to software engineering by Anonymous Coward · · Score: 0

      bad drivers in Linux only halt the process. They do not bring the entire system down.

      Drivers in Linux are not user processes. If you ever type "insmod" or "modprobe", if you ever see your driver having the .ko extension, if you can see your driver in "lsmod" output... That is in kernel address space and can theoretically do anything to mess up your system. I have noticed some relative fault tolerance in kernel panics in kernels from the last 2 years or so, I'll give you that... (Same goes for Vista, actually, which is much more fault tolerant than XP.) But that doesn't change the fact that a kernel module can basically shit all over memory, or, to put it more nicely, corrupt important data structures in ways that cause non-recoverable crashes.

      If a process dies on Windows (or worse, becomes an out of control process), it CAN bring the entire system down with it.

      This part doesn't even make sense. Windows in this century does use protected memory, you know. NT is fairly good about that.

    69. Re:In fairness to software engineering by coolsnowmen · · Score: 1

      Also, if a critical driver fails (such as a keyboard driver - and for this, it doesn't need to crash), the stability of the core operating system is moot for most people, since they need to reboot the system to get the driver working again. (I experienced this with an OEM "Multimedia keyboard" driver, and know how to correct it.) The same applies to the display driver - if you don't see anything on the screen, you can't do much with your system.

      ssh (secure shell) F.T.W.

    70. Re:In fairness to software engineering by dotgain · · Score: 1
      Oh my god who modded that Inforamtive? Modules run in kernel space (by virtue of becoming part of the running kernel. They can access any and all of the memory and hardware that the kernel can - that's the point. Because the module / driver doesn't run in process context, there's no "guilty" process to kill. The ability to put the hardware in an unrecoverable state is part and parcel of being able to "drive it".

      To put it another way: Drivers - whether compiled into the kernel or built as modules - have every bit as much ability to crash the system as the kernel itself does. Sure, a processes memory space is kept to itself, meaning it's unlikely that a process itself can bring a system down. But by the time a (bad) driver has done its damage, there's probably not a sane kernel left, letalone one that can recover and kill the process in question - there is none!

    71. Re:In fairness to software engineering by Larryish · · Score: 1

      From what I gather (mostly from 3rd parties, with some hands-on) "the Vista experience" varies according to the hardware in the machine.

      The only Vista box I ever had any experience with was my wife's laptop, a Dell Inspiron 1501 that she bought early last year. 2 gigs of ram, dual-core 1.8 ghz chip, nice fat fuhitsu hard drive, and it ran so slow that we ended up replacing it with Ubuntu.

      A few of my buddies who are hopeless Windows users have Vista machines and one has no problems with it that I hear about, the other two have intermittent issues which are mostly hardware related.

      Go figure.

    72. Re:In fairness to software engineering by ThJ · · Score: 0

      Vista slowed down my wife's computer tremendously. She kept getting crashes in Second Life, the frame rate was low and the whole system just ran sluggishly. Disabling Aero didn't do much good. What idiot at Microsoft managed to consume 200+ MB RAM for a visual presentation layer anyway?

      I installed Windows XP for her and she's never been happier. I too thought there was a lot of "FUD in the anti-Vista hype" but I can see why people are complaining now.

      I'm holding out for Windows 7 or a sudden outbreak of companies porting all my favorite software to Linux.

    73. Re:In fairness to software engineering by Hal_Porter · · Score: 4, Funny

      I've actually had my Macbook Pro freeze more times in the last year than my Windows machine. In fact, it even hung once when I closed the lid and tried to fry itself with the backlight.

      You know you've got an unpleasant personality when computers try to kill themselves rather than work with you.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    74. Re:In fairness to software engineering by Anonymous Coward · · Score: 0

      My Vista tower has BSOD about every 3 weeks. Was purchased 6 months after vista launch and BSOD 15 mins out of the box (ok,... ok,... was the video driver's fault but windows update was the one who installed it...).

      The BSOD I now get are at completely random times. My last one was during shutdown...

    75. Re:In fairness to software engineering by weicco · · Score: 1

      Well NT only partialy fixed this. Otherwise, rebooting your system after each PATCH would NOT be necessary; you would only need to restart the service.

      You are partly correct. NT4 required boot in many situations but NT5 (Windows 2000) corrected a lot of these.

      I used to work at a company which made network security stuff. I was in a team that wrote all the Windows virtual network drivers and made all the installation packages for Windows setup (we had Linux setup also, but it was handled by another team). If I remember correctly we could have done it so that you wouldn't have to reboot when running Win2000 or later. But for safety reasons we required user to reboot after installation. This enabled us to know in exactly what condition system is after installation (because it is rebooted) so we could safely do our little thingies and not to worry about other network drivers messing around and such.

      Can you get rid of the GUI, can you get rid of Explorer, can you get rid of the mediaPlayer? Some say yes but in actuality you dont because they are still there and running.

      Obviously you don't know much about the architecture of Windows and how COM components operate. If you remove Windows Media Player you are just removing the GUI part of it. Various applications like Word, Excel, Explorer etc. use media components so they aren't removed because that would mean that you wouldn't be able to embed media components to your documents or you would have to write your own components to do that. Also removing Explorer wouldn't remove INET library which some browsers, other than IE, also use.

      But even if those components are installed to the system it doesn't necessarily mean that they are running in the fore- or background. They are just dynamically linkable libraries which you must explicitly call in order to make them, well, to do their job.

      NOT more easy to secure or stabilize

      My Windows Vista setup is quite secure and stabile thank you. I admit I had to uninstall some 3rd party stuff from the system which wasn't acting nicely with Vista but apart that it is running fast and reliably.

      And who ever wrote that faulty Linux kernel driver wont crash the whole system should be shot at dawn. In the face. I've seen plenty of such drivers and even wrote some part of a one.

      --
      You don't know what you don't know.
    76. Re:In fairness to software engineering by Anonymous Coward · · Score: 0

      How does Hurd deal with a driver asking a card to DMA something onto the wrong memory address, overwriting the kernel?

      How does Hurd deal with a driver asking the card to lock the PCI bus, or pull all the signal lines high or low?

      Hardware always has the possibility of crashing the system. If the driver sends the instructions to do that, the system will crash. Of course you could add a layer in between, that know how to use and not use the hardware. But this layer is usually called the driver.

    77. Re:In fairness to software engineering by MichaelSmith · · Score: 1

      Seeing that it was so critical they should have had redundancy built in at the hardware level. Something like N projectors going through a switch with a dead man timer to change inputs.

      When the timer doesn't reset the switch changes to a different input.

    78. Re:In fairness to software engineering by ezzzD55J · · Score: 1

      Bad driver != bad hardware

    79. Re:In fairness to software engineering by ezzzD55J · · Score: 1

      OS X is based on a microkernel

      Not meaningfully. The OS X kernel is a monolithic kernel.

    80. Re:In fairness to software engineering by Foofoobar · · Score: 1

      Heh... nice shilling. Obviously you don't know much about how an operating system needs to be built. The kernel should be independent of processes running on it and while NT4 may have gotten BETTER, so has George Bush... but both are pieces of shit.

      --
      This is my sig. There are many like it but this one is mine.
    81. Re:In fairness to software engineering by paving-slab · · Score: 1

      There is already a word for this, and you used it yourself. It's designed.

    82. Re:In fairness to software engineering by jimicus · · Score: 1

      And if language never evolved we'd all be saying "oook" to each other.

      Live with it.

    83. Re:In fairness to software engineering by paving-slab · · Score: 1

      And if language continues to evolve in this way we'll end up saying "oook" to each other again. (In fact we just have).

      What I don't understand is how this sort of nonsense starts.

      I can only imagine an office somewhere, where some idiot in management first uses the word. "How was this architected?". (Hey, my spellchecker doesn't recognise it as a word!)

      Now, surely any sane person would have said "Don't you mean designed?" or "What the fuck does architected mean?", but for some reason they didn't. Maybe they thought it was cool, or they were scared of their boss, who knows?

    84. Re:In fairness to software engineering by weicco · · Score: 1

      I don't see your point. NT kernel is independent from user space processes just like Linux kernel is. Maybe you should get some facts straight behind your trolling?

      --
      You don't know what you don't know.
    85. Re:In fairness to software engineering by Foofoobar · · Score: 1

      Hmmm... methinks the lady doth protest too much. If this is the case, the it wouldn't explain the ongoing problems with the Vista and XP and Server 2003 systems which keep recurring. It also wouldn't explain why I was modded insightful on both my posts for over 5 days until the post went stale and you and you Microsoft shills spent all your points to mod it down. Like I said... methinks the lady doth protest too much.

      --
      This is my sig. There are many like it but this one is mine.
    86. Re:In fairness to software engineering by jZnat · · Score: 1

      But X isn't the window manager. If something like compiz/beryl, kwin, enlightenment, twm, etc., crashes, that doesn't bring X down with it. When Explorer crashes in Windows, that's somewhat similar.

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
  17. Pirated? by jav1231 · · Score: 0, Redundant

    What's worse is the copy of Windows was pirated!

  18. BSOD? Big deal! by cashman73 · · Score: 4, Insightful

    The BSOD is just the icing on the cake of this story. The real interesting bit is the fact that Vista lost out again to the superiority of XP,...

    1. Re:BSOD? Big deal! by PolarBearFire · · Score: 1

      Umm, they went with a CONSUMER operating system made by Microsoft, beating out OSX and all the thousands of Linux variations to put on a one time multimedia extravaganza. If anything I thought Linux would be the most ideal choice according to open source advocates who tout cheaper cost and greater flexibility of open source. Also, be realistic Vista was released 2007 and the Beijing olympics has been planned for at least 4 years. PS. XP was horrible for the first couple of years too.

    2. Re:BSOD? Big deal! by Anonymous Coward · · Score: 1, Insightful

      The BSOD is just the icing on the cake of this story. The real interesting bit is the fact that Vista lost out again to the superiority of XP,...

      No, this is exactly the kind of crap that Vista was meant to prevent. For example, Vista can recover from certain types of driver failure, most notably video card. And the fact that drivers must be signed in 64-bit Vista was meant to address the fact that lots of companies write bad drivers -- MS runs some tests on your driver to see if it is good enough, so that you don't go BSODing people's machines and having your customers say it's Microsoft's fault.

      If the guy from Lenovo wasn't so dogmatic about XP's alleged "superiority" (read: "explorer.exe is more responsive, therefore the entire system is better") that everyone seems to take as gospel, maybe he'd have a more stable system.

    3. Re:BSOD? Big deal! by cwAllenPoole · · Score: 1

      As it should be.

      --
      http://www.allen-poole.com/
    4. Re:BSOD? Big deal! by Anonymous Coward · · Score: 0

      Never thought I'd live to see the day when Windows XP was considered "superior" in any context. Am I the only one who remembers how much Windows XP sucked when it was released? XP gave me nothing but trouble back then. These days XP works OK, but that's nearly eight years and three service packs later. Actually, I would still be using Windows 2000 (assuming Windows is required for the task) if XP hadn't been crammed down my throat. The only advantage XP has over Win2k is fast user switching and better power management, and that's about it. The rest is half-assed (theming) or useless (WGA). The only reason people think XP is the greatest thing since sliced bread now is because, as amazing as it might seem, something worse came along - Vista.

      There is a time and place for Windows (it is actually good for some tasks) but if you think it's an excellent operating system then your standards are embarrasingly low.

    5. Re:BSOD? Big deal! by Efialtis · · Score: 1

      If Microsoft made all their Operating Systems like Vista, NONE of them would ever be pirated...it just wouldn't be worth it...

      --
      --E--
    6. Re:BSOD? Big deal! by Anonymous Coward · · Score: 0

      Never thought I'd live to see the day when Windows XP was considered "superior" in any context. Am I the only one who remembers how much Windows XP sucked when it was released? ...
      No, I'm pretty sure there are many other disillusioned MS-haters on Slashdot.

  19. big deal by speedtux · · Score: 1, Funny

    The copy of Windows probably wasn't licensed anyway. You can't expect unlicensed, unsupported Microsoft software not to crash :-)

  20. making bad engineering acceptable by SgtChaireBourne · · Score: 4, Insightful

    ...It's not uncommon to get a BSOD from time to time.

    And unless you do something about it, like vote with your wallet, you are simply helping Bill and his minions make bad engineering acceptable.

    --
    Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
  21. They were Axon mediaservers running WinXP Embedded by Anonymous Coward · · Score: 3, Informative

    They were Axon mediaservers running WinXP Embedded: http://www.windowsfordevices.com/news/NS4787005167.html

    Some of the video projectors (70 of about 160 if I recall correctly) connected to those mediaservers were equipped with HES Orbital Head ( http://www.highend.com/products/digital_lighting/orbitalhead.asp ), which can explain the odd positioning of BSOD.

  22. May not be the case as much any more. by Anonymous Coward · · Score: 0

    Not sure whether that's true anymore about the blue screen errors being due to hardware issues. A lot of blue screen issues I've dealt with on peoples systems lately seem to be side effects of viruses, root kits, etc. rather than hardware issue. When re-installing windows eliminates the blue screen, it seems fairly clear the problem wasn't the hardware.

    1. Re:May not be the case as much any more. by mhall119 · · Score: 2, Insightful

      The problem isn't the hardware, it's the drivers. I know at least some root kits will install themselves as a driver in order to get at the kernel's internals.

      --
      http://www.mhall119.com
  23. Well.... by jskline · · Score: 0, Offtopic

    ROTFLMAO....

    --
    All content in this message is copyright (c) 2008. All rights reserved. RIAA is prohibited here.
  24. Priceless! by zappepcs · · Score: 2, Funny

    Olympic Ceremony - $40 Million
    Tickets to Olympics - $??????
    Windows Computer - $1000
    Windows XP OS - $400

    Being able to tap the president on the shoulder, then point up at the BSOD screen and say "I did that" - Fucking Priceless

    1. Re:Priceless! by Anonymous Coward · · Score: 0

      OMFG OMFG OMFG you made a spoof of the mastercard advert!!!!!!!!!!!!!!!1
      That is really really really really original and sooooo funny it's incredible.

    2. Re:Priceless! by xerxesVII · · Score: 1

      Would you please shut the fuck up?

      --
      "We shall grapple with the ineffable, and see if we may not eff it after all." - Douglas Adams
    3. Re:Priceless! by iveygman · · Score: 1

      Olympic Ceremony - $40 Million

      It was actually $300 million.

    4. Re:Priceless! by Anonymous Coward · · Score: 0

      Being able to tap the president on the shoulder, then point up at the BSOD screen and say "I did that"

      Bill Gates is no longer the president of Microsoft, and even if the BSOD was your doing, what are the odds that you are standing next to him at the Olympics at that very moment?

  25. BSOD was CGI! by Coolhand2120 · · Score: 4, Funny

    After a closer examination of the evidence it has come forth that the BSOD was actually CGI superimposed on the roof to make the U.S. audience viewing at home feel more familiar with Chinese technology. At selected venues around the world the BSOD was replaced with a kernel panic screen and even a Mac classic bomb.

    1. Re:BSOD was CGI! by Efialtis · · Score: 1

      It was prolly a pirated copy of Windows...

      --
      --E--
  26. I submitted it to FailBlog.org by Nachos+Nakamoto · · Score: 1

    BSOD FAIL!
    Worldwide Audience and XP fails it. Nice.

    --
    Cover me in peppers and lick me, baby.
  27. Re:Doesnt look like a BSOD... by Lobster+Quadrille · · Score: 3, Informative

    Um... Mac still has them, they're just grey screens of death with an apple logo and an even-less-informative error message (in half a dozen languages).

    --
    "The cup is in turn designed for holding hot or cold liquids, and has an open rim and closed base." --US Patent #5425497
  28. What's their motivation.... by midnitewolf · · Score: 3, Insightful

    What's the motivation to write better hardware drivers if any time the system blue screens, people will just blame the OS anyway?

    1. Re:What's their motivation.... by mhall119 · · Score: 5, Funny

      Good point, Windows should identify the offending driver, read it's manufacturer info, then shame the creator on the BSoD.

      "A fatal exception has occurred because CheapHardware's Crappy802.11g device driver was written by mildly retarded gibbons."

      --
      http://www.mhall119.com
    2. Re:What's their motivation.... by Anonymous Coward · · Score: 0

      Actually... Error reporting and crash recovery in Vista does exactly this. I've had a bad copy of Adobe Reader (8.?) that would lock the system, as well as an ATI Video Driver on my Laptop that would periodically cause bluescreens. Vista identified each one after a "cold start" as causing the problem, and to "refer to the vendor's website for a new version".

    3. Re:What's their motivation.... by ShadowRangerRIT · · Score: 5, Informative

      This has actually been proposed a number of times (without the personal attacks), but rejected for two reasons:

      1. Potential lawsuits from the driver developers
      2. Inability to be sure of the actual cause of the crash in kernel mode

      The latter problem is more important. Problem is, kernel mode code can do *anything*, including write to other modules' memory space. So if a driver "baddisplay.sys" accidentally wrote to an uninitialized pointer that just happened to point to the memory space of "goodprinter.sys", but didn't fail as a result (remember, no real memory protection in kernel mode), and "goodprinter.sys" later reads the screwed up memory and fails, it will look like a problem in "goodprinter.sys", even though "goodprinter.sys" behaved correctly (dying when faced with an irrecoverable error).

      This is why the "Problem Reports and Solutions" only provides information after conferring with MS. When it gives you an answer, it's because someone at MS took a look at your crash dump (or someone else's dump which exhibited the same problem), figured out the actual cause of the crash, and linked the crash and solution together. If it blamed the module automatically, you'd spend time harassing a perfectly innocent printer manufacturer, and MS would need to hire even more lawyers.

      (Disclaimer: Former MS employee, this is only what I was told)

      --
      $_ = "wftedskaebjgdpjgidbsmnjgcdwatb"; tr/a-z/oh, turtleneck Phrase Jar!/; print
    4. Re:What's their motivation.... by mhall119 · · Score: 1

      Way to use logic on Slashdot and ruin my +5 Funny.

      --
      http://www.mhall119.com
    5. Re:What's their motivation.... by Ilgaz · · Score: 1

      I am sure you didn't see the Crash report of new Leopard OS X from Apple. I bet Adobe hates it. ;)

      "Application Safari crashed, it may have been caused by Flash Player plugin"

      No kidding.

    6. Re:What's their motivation.... by ignavus · · Score: 1

      I have never seen a mildly retarded gibbon write crappy device drivers.

      Sir, you tarnish their good name!

      --
      I am anarch of all I survey.
    7. Re:What's their motivation.... by Hal_Porter · · Score: 1

      If you analyze the dump in WinDbg it does often blame a driver. And even if it doesn't you can work out which driver is causing the problem by disabling them and seeing if it goes away.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
  29. BSOD in projection system by ljb2of3 · · Score: 2, Informative

    Looks like the BSOD happened with one of the systems running the projection system. I know that the systems running the projection are running XPe, not a normal version of windows. According to the manufactures comments, they had 120 media servers running all the projection. With an event of that scale, you're bound to have something crash eventually.

    --
    // TODO: Witty Signature
    1. Re:BSOD in projection system by Higaran · · Score: 1

      I'm willing to bet that the system was not cooled properly and that's why it BSODed, they were pobably puming the krappy air from outside into it.

    2. Re:BSOD in projection system by RAMMS+EIN · · Score: 1

      ``With an event of that scale, you're bound to have something crash eventually.''

      Really? I realize that, as complexity increases, the chances of something going wrong go up. On the other hand, I don't think this is actually a very complex system. If it worked during the tests, why didn't it work during the ceremony? If they didn't have it working in the tests, why did they have it in the ceremony?

      --
      Please correct me if I got my facts wrong.
  30. Re:Doesnt look like a BSOD... by Anonymous Coward · · Score: 0

    Of course, it won't run most games or use most hardware unless you bend over backwards, sacrifice a virgin (which, if you're using *nix, one is handy) and pray to the gods, old and new.

  31. DL3 media server failure by NimbleSquirrel · · Score: 5, Informative
    I'm surprised this was left unnoticed and was not shut down.

    I believe most of the projections were handled by HighEnd Systems DL2s and DL3s. Essentially a projector on a moving yoke, with a few extra features. Each DL2 or DL3 has its own built-in media server running Win XP Embedded.

    Even if the built-in media server fell over (which is what this looked like), there is still DMX control over the unit. Pan, tilt, focus and more importantly beam blanking and projector power are still controllable. It would have been easy to shut the faulty unit down and still carry on with the show (and yes, I do work with this kind of gear).

    On this scale of event, they would have had multiple operators dedicated to watching over particular areas in case of such a fault. It looks like someone wasn't paying attention.

    1. Re:DL3 media server failure by TimSee · · Score: 1

      There was an article on this company (High End Systems) in today's Austin-American Statesman here http://www.statesman.com/business/content/business/stories/technology/08/12/0812high_end.html

    2. Re:DL3 media server failure by Anonymous Coward · · Score: 0

      The BSOD was only present for a second or so. Someone got lucky, shooting the right place at the right time.

    3. Re:DL3 media server failure by Anonymous Coward · · Score: 0

      IAATPE (I am a theatrical projections electrician) A big part of their system was run off of their standalone axon media servers. (computers in racks) I wonder if there would be a way to hot swap a failed unit with a backup, DMX and all. I had an a/b switch built into one of my projection systems, albeit a much smaller one.

    4. Re:DL3 media server failure by Anonymous Coward · · Score: 1, Informative
      They used Christie projectors along with High End Axon Media Serviers to handle the video projection. Dont think they used any High End fixtures like the DL2/3, most of the Fixtures were Varilite, CP or Martin.
      The scale of the event from a tech point of view is huge:

      "This is the first time that we have used such a massive number of projectors for the opening ceremony - a combination of approximately 150 Christie Roadster S+20K and Christie CP2000-ZX models, with brightness levels up to 20,000 ANSI lumens,"

      Altogether 2,342 fixtures were used for the show which consisted of, amongst others, 308 Vari*Lite VL3500 spot, 316 VL3000 spot, 180 VL3500 wash, 112 Clay Paky Alpha Wash 1200. The first session had 15,921 parameters with 14 MA NSPs and 834 fixtures, the second 13,503 parameters with 16 MA NSPs and 884 fixtures, the third session 15,987 parameters, with 16 MA NSP and 624 fixtures.

      The video system under the creative direction of media artist Andree Verleger from Germany included some 110 media servers, 86 Christie Roadster Projectors with Orbital Heads and 63 Cinema Christie Projectors. HP Pro-Curve 2626 field switches, HP Pro-Curve 8212zl and kilometers of multi mode fiber-optic cable were the backbone of the huge network.

      Think they didnt use the DL2/3's because the brightness is only about 6.5k lumens if I remember correctly, vs. 20k from the projectors they used. Considering they are already using 150 projectors, along with the long throw/brightness issues and limitations on the lens for the DL2/3's, dont think they could have used them.

      The Christie's dont have DMX control (they do have other forms like RS232 and proprietary solutions) so they should still have been able to take the feed offline however.

    5. Re:DL3 media server failure by mattwarden · · Score: 1

      > On this scale of event, they would have had multiple operators dedicated to watching
      > over particular areas in case of such a fault. It looks like someone wasn't paying
      > attention.

      Sorry, we have no record of this person.

      Thanks,
      China

    6. Re:DL3 media server failure by clem.dickey · · Score: 1

      they would have had multiple operators dedicated to watching over particular areas in case of such a fault. It looks like someone wasn't paying attention.

      Maybe that someone was laughing too hard to care.

    7. Re:DL3 media server failure by blazerw11 · · Score: 1

      On this scale of event, they would have had multiple operators dedicated to watching over particular areas in case of such a fault.

      Many folks have commented that in an event this big it's pretty impressive that only one BSOD (or other failure) was noticed. If what you're saying is true, maybe, just maybe, all the operators WERE paying attention and there were a LOT of BSODs. So many that 1 got through all of the backups and redundancies.

      --
      A great many people think they are thinking when they are merely rearranging their prejudices. -- William James
    8. Re:DL3 media server failure by Anonymous Coward · · Score: 0

      ....or maybe the Chinese didn't allow access to the technical crew to be able to view the show from other parts of the stadium to be able to see something like that occurring, so they were never aware of it.

      [hate to insert fact in everyone's fun, but that is what actually happened.]

  32. That's frickin' scary... by MsGeek · · Score: 1

    Windows98. Running an ATM. Not even an embedded version, or an NT-heritage version like NT4, 2K or XP. Real bad. 98 was never meant to be used in applications like an ATM, which demand superior security and resilience. Time was that a lot of these machines used OS/2, or even ran custom code on "bare metal."

    I would have liked to see a picture of the crash.

    --
    Knowledge is power. Knowledge shared is power multiplied.
    1. Re:That's frickin' scary... by bhtooefr · · Score: 1

      Actually, if the ATM has no real network connection, why not run Win98? It'll be single-tasking, might be doing dial-up to contact the bank (with no constant connection,) and with very few infection vectors. And, Win98 doesn't have many ports open by default, so sitting a Win98 box on the open internet is probably safer than doing the same with a WinXP box.

  33. Re:Doesnt look like a BSOD... by bigstrat2003 · · Score: 4, Funny

    I pay Apple alot of money to ensure no BSODs.

    No, you pay them a lot of money for "ooh shiney".

    --
    "16MB (fuck off, MiB fascists)" - The Mighty Buzzard
  34. The article is incorrect by Anonymous Coward · · Score: 0

    The ceremony, which featured 14,000 performers depicting 5000 years of Chinese history, also involved the use of advanced technology to control the sound, lights and projectors.

    Advanced technology? No, it was Windows XP! Perhaps they should have taken some of those boys inside the boxes and had them run manual slide projectors -- would have been more reliable.

    1. Re:The article is incorrect by gparent · · Score: 0, Flamebait

      Linux isn't advanced technology either. Troll.

  35. Mod up: Informative by Anonymous Coward · · Score: 0

    n/t

  36. When at the Olympics by wardk · · Score: 3, Informative

    you perform your very best.

    lets face it, BSOD is the face of Windows.

    you cannot have Windows at a major event without it participating, by doing what it does best. just like the athletes.

  37. blue screen/grey screen by Anonymous Coward · · Score: 0

    9 months since i got this new windows xp computer, 9 months of using it all day every working day, typically running AutoCad 09, Ease, Outlook, and I.E. at any given time, driving 3 24" monitors, grand total of: ONE bsod, which was caused by a security fault in a bootskin mod that a windows update hit.

    4 months since i bought an iMac at home, at least once a week i get a greyscreen.

    As for all of the incessant linux fanboys. the FACT is, linux is not familiar to the typical user, not user friendly to the typical user, and expanding it is nowhere near intuitive enough for the typical user, and in the event that a user DOES have a problem on linux, the typical user is entirely screwed.

    1. Re:blue screen/grey screen by Anonymous Coward · · Score: 0

      You use IE? Turn in your geek card at the door. Lame

    2. Re:blue screen/grey screen by Ash-Fox · · Score: 1

      the FACT is, linux is not familiar to the typical user, not user friendly to the typical user, and expanding it is nowhere near intuitive enough for the typical user, and in the event that a user DOES have a problem on linux, the typical user is entirely screwed.

      I discovered otherwise when observing regular Joe use Linux.

      --
      Change is certain; progress is not obligatory.
  38. Should have used Vista by PPH · · Score: 1

    We would have seen a huge "Cancel or Allow" banner on the stadium roof.

    --
    Have gnu, will travel.
    1. Re:Should have used Vista by ackthpt · · Score: 1

      Would have been several of them, you never catch them all on the first go.

      --

      A feeling of having made the same mistake before: Deja Foobar
  39. Err , if the projector driver had failed... by Viol8 · · Score: 2, Informative

    ... the BSOD wouldn't still be being projected onto the roof!

    1. Re:Err , if the projector driver had failed... by DaVince21 · · Score: 1

      That probably proves that the screen was seen as a 'normal' screen by the actual OS. I don't actually think the video drivers are at fault here, a good video card should be more than enough for that huge display anyway, right?

      --
      I am not devoid of humor.
  40. Re:Doesnt look like a BSOD... by Anonymous Coward · · Score: 0

    Linux ISO with no BSoDs
    HaaaaaaaHahahahahahahhaaaaaaaaa!
    Can we call a Linux panic Black Stack Trace of Death?
    BSToD!

    same fundamental architecture as OS X

    HAHAaaaHAaaaaaaHAHAHAHAaaaaaaaaaa,1!11!!! ZOMFG, ROFLMAO!

    Ohhh.. seriously, you made my day today.
    I'm going to use this to troll on LHB.

  41. Re:Doesnt look like a BSOD... by Darkness404 · · Score: 1

    ...And a lot of games won't run on Mac either. Not to mention that most Mac video cards are low-quality and won't run most games when they are running Windows either

    --
    Taxation is legalized theft, no more, no less.
  42. first SPIN~1 of the thread .. by rs232 · · Score: 1

    subject: "DL3 media server failure"

    If so, how did the DL3 provoke a BSOD in WindowsXP? Please provide the exact error msg from the screen.

    "I believe most of the projections were handled by HighEnd Systems DL2s and DL3s .. It looks like someone wasn't paying attention"

    Do you have any hard facts to support this disengeniously modded up specious speculation, regardless, it still doesn't negate the fact that there was a BSOD in the middle of the opening ceremony.

    --
    davecb5620@gmail.com
  43. the fiendish plot of Fu Manchu .. by rs232 · · Score: 1

    "I wouldn't be surprised if China had an axe to grind against m$ and faking an embarrassing incident such as this would serve as a slap to m$"

    No, it's a plot by the US to sabatge the Chinese economy, but selling them Windows .. ;)

    and yea, they would fuck up their own Olympics just to embarrass Microsoft .. funking DOH !!!

    --
    davecb5620@gmail.com
  44. and if it is an uncertified third party driver? by westlake · · Score: 1
    And unless you do something about it, like vote with your wallet, you are simply helping Bill and his minions make bad engineering acceptable.
    .

    The geek wants it both ways. He wants to run the untested - uncertified - third party driver of his choice -- wile keeping the option to blame Microsoft if anything goes wrong.

    Microsoft's Crash Analysis in Windows often returns a plain English explanation of what went wrong and how to fix it. That can be useful enough to make the rare BSOD palatable.

  45. I'l tell you what .. by rs232 · · Score: 1

    It happened in the middle of the Olympics opening ceremony. It happened on the worlds self professed most advanced Operating System, in the know universe. To achieve five nines kind of reliability, I would recommend only using embedded hardware in such a configuration. Most certanly not XP, never mind the rest ..

    --
    davecb5620@gmail.com
  46. Re:Doesnt look like a BSOD... by Bearpaw · · Score: 1

    I pay Apple alot of money to ensure no BSODs.

    No, you pay them a lot of money for "ooh shiney".

    At least the "ooh shiney" just works.

  47. Déjà vu! Comdex-Chicago '98 anyone??? by BUL2294 · · Score: 1

    This is the 2nd time Bill Gates was in close proximity to Windows BSOD'ing in public... I'm shocked nobody mentioned that when Bill Gates was presenting Windows 98 at Comdex-Chicago in 1998, a big BSOD appeared in front of all the attendees when a USB device was plugged-in--with laughter & cheers. But that was a beta version of Win98--this was running on SP2 or SP3 of XP--a product that has been around for ~7 years!

    --
    Windows 3.1x calc: 3.11 - 3.10 = 0.00
  48. computing resources ... :) by rs232 · · Score: 2, Funny

    "the number and power of the computing resources involved was probably pushing the limit"

    You mean just to project a video onto the roof. I've got an old 500MB, PC that can play DVDs without problem. It runs on Yoper, you should try it, runs encrypted DVDs straight out of the box, no config issues.

    --
    davecb5620@gmail.com
  49. Prank by thwack328 · · Score: 1

    Check out the angle of the shadow cast by the truss... This must have been projected from somewhere in the crowd. Somebody snuck in a prototype of their miniaturized laser projector.

  50. What about Red Flag Linux? by I'm+Don+Giovanni · · Score: 2, Insightful

    They could've used Red Flag Linux for free. Was it not up to the task, period?

    --
    -- "I never gave these stories much credence." - HAL 9000
  51. BSOD Screen Saver? by Culture20 · · Score: 1

    Is there proof that it was a windows machine? Maybe it was a Red Flag Linux install with the BSOD screen saver.

  52. Why? by Slash.Poop · · Score: 0

    In between all the Microsoft bashing and Linux praising I still have not seen an answer to the fundamental question.....

    Why were they using Windows in the first place?

    If you are wearing a tin foil hat please don't bother replying

    ______________
    Q: Why is Vista not being adopted?
    A: XP

  53. Embedded XP .. by rs232 · · Score: 1

    "They were Axon mediaservers running WinXP Embedded"

    How do you manage to make an embedded OS go BSOD. I though that one of the advantages of an embedded system was more reliability, what gives .. ? Or did they just stick parts if it on a ROM and run the rest from a RAMDRIVE .. tell me it ain't soo .. :o

    --
    davecb5620@gmail.com
    1. Re:Embedded XP .. by Anonymous Coward · · Score: 0

      Well usually you don't run ATI DirectX drivers, video capture card drivers and about all possible media codecs on embedded system... ...as is case with Axon. And AFAIK Axon has no rom, only standard flash bios and XPe running from hard disk.

      Technical data of axon: http://www.highend.com/pub/products/digital_lighting/Axon/AxonDS.pdf (pdf)

    2. Re:Embedded XP .. by rs232 · · Score: 1

      "Well usually you don't run ATI DirectX drivers, video capture card drivers and about all possible media codecs on embedded system... ...as is case with Axon. And AFAIK Axon has no rom, only standard flash bios and XPe running from hard disk"

      Then why does it say here that Windows XP Embedded powers Olympics and what technical reasons are there for not running ATI DirectX drivers on embedded systems. Are there references in the litrature, to avoiding drivers on embedded systems? And what's the difference between XPe running on a harddrive and 'real' embedded XP not running on a hardrive .. :)

      --
      davecb5620@gmail.com
  54. excuses so far .. by rs232 · · Score: 1

    It overheated (blame the stingy slant-eyed chinks) It was Chinise sabatage It was a CGI BSOD .. It was a bad hardware drivers It was not properly cooled .. It was probably hardware failure .. It was the fault of the DL2 media units .. It was too much computing resources to handle

    --
    davecb5620@gmail.com
    1. Re:excuses so far .. by Anonymous Coward · · Score: 0

      Because nobody here knows anything about the actual hardware or setup or anything else. Anything *you* say will also be speculation.

    2. Re: excuses so far .. by rs232 · · Score: 1

      "Because nobody here knows anything about the actual hardware or setup or anything else. Anything *you* say will also be speculation"

      What exactly did I say that speculated on the causes of the BSOD?

      --
      davecb5620@gmail.com
  55. Of course... by Junta · · Score: 1

    If your video driver crashes, then the lack of a blue screen wouldn't particularly be a significant improvement in this scenario either.

    I.e. linux is mostly userspace for most video driver stuff, but when X crashes, the fact it can be sshed into would be of little comfort here either.

    --
    XML is like violence. If it doesn't solve the problem, use more.
    1. Re:Of course... by jedidiah · · Score: 2, Interesting

      ...assuming the error is not completely unrecoverable:

              Then Linux can restart X and chug happily along.

              It still won't look pretty if you are using it as
      a projector in front of a billion people but you also
      won't have a door stop.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    2. Re:Of course... by Colonel+Korn · · Score: 2, Interesting

      In Vista, the only driver crashes I've seen cause only a brief screen flicker.

      Of course, also in Vista, no one can hear you scream.

      --
      "I zero-index my hamsters" - Willtor (147206)
    3. Re:Of course... by Anonymous Coward · · Score: 0

      My mother-in-law's vista box was flickering and BSOD-ing (er, can you use BSOD as a verb?) approximately every 15 minutes the last time I used it.

      The fact that she's on dial-up (lives in the country) makes it very interesting to try to download new drivers and updates.

      Thankfully, her son is a windows sysadmin, so I made it his problem.

  56. What a wonderful desktop picture! by chaosmind · · Score: 1

    I'd like to set this as my desktop pic.

    Anyone got a higher-res photo of this?

  57. F4 is usually bad paging space... by Anonymous Coward · · Score: 0

    Often an error or misconfiguration of the drive containing the page file. Something like bad sectors or corrupted data in the page file, or the slave drive with no master mentioned in the other comment.

  58. Fruty Bats in the Bellfree Software by Efialtis · · Score: 1

    Maybe now they will move to Linux to avoid further embarrassment...
    "Yo soy emberassado" does not mean "I am embarrassed" and using Windows software does not mean you are a professional organization...

    --
    --E--
    1. Re:Fruty Bats in the Bellfree Software by RAMMS+EIN · · Score: 1

      ``"Yo soy emberassado" does not mean "I am embarrassed" and using Windows software does not mean you are a professional organization...''

      You are right. But I wonder what you think "Yo soy emberassado" means.

      If you had said "soy embarazada" that would have meant "I am pregnant". But "emberassado" is not so clear... ;-)

      --
      Please correct me if I got my facts wrong.
    2. Re:Fruty Bats in the Bellfree Software by pandrijeczko · · Score: 1

      Being of the male gender, I doubt I will ever have a need to use the phrase - but as a Spanish student, would pregnant woman not say: "Yo estoy embarazada" due to the fact that it is not a "permanent" state of being? For example "Yo estoy cansado" means "I'm tired" (a "temporary" condition) but "Yo soy alto" means "I am tall" (a "permanent" condition). Just curious...

      --
      Gentoo Linux - another day, another USE flag.
    3. Re:Fruty Bats in the Bellfree Software by RAMMS+EIN · · Score: 1

      Yes, you are right. I am not sure it is permanent vs. temporary conditions so much, but, in this case, the right verb to use would definitely by "estar".

      --
      Please correct me if I got my facts wrong.
    4. Re:Fruty Bats in the Bellfree Software by pandrijeczko · · Score: 1

      That's the problem with learning Spanish - it's a great language to learn and 95% of it is covered by some good grammatical rules which you just need to learn. Unfortunately, it's the 5% of irregular stuff that isn't covered by rules that is best just remembered as a complete phrase rather than trying to slot it together before saying it. Still, an Englishman has a much easier time of learning Spanish than a Spaniard has of learning English! With my Spanish friends, I always get a kick of showing them English words containing "ough" like "cough", "rough", "bough", "through" and "though" - five different pronunciations of "ough" and not one rule in sight!

      --
      Gentoo Linux - another day, another USE flag.
  59. Re:Doesnt look like a BSOD... by ShadowRangerRIT · · Score: 3, Informative

    More accurately, you pay Apple a great deal of money so you have exactly one person to blame if you get a crash. BSODs in Windows are (99% of the time anyway) a matter of bad third party drivers. Apple has an easier time of it because they only support a small range of hardware in predictable configurations; MS has to test enormous numbers of drivers for every conceivable x86/amd64/ia64 configuration. Linux splits the difference; in theory they support the greatest number of configurations, but in practice support for new hardware comes slowly, and with no guarantees.

    --
    $_ = "wftedskaebjgdpjgidbsmnjgcdwatb"; tr/a-z/oh, turtleneck Phrase Jar!/; print
  60. IT was really... by up2ng · · Score: 1

    CGI folks,

    they couldn't have a BSOD so close to Mr. Bill G, it wouldn't be safe

    --
    Success is not the result of spontaneous combustion, you must set yourself on fire.
  61. obvious justification: brand identity by Narcocide · · Score: 5, Funny

    ...after all, if it had just done its job flawlessly there'd be no way for the crowd to know it was a microsoft product.

    1. Re:obvious justification: brand identity by skerit · · Score: 1

      Strangely enough that makes a lot of sense.

    2. Re:obvious justification: brand identity by Anonymous Coward · · Score: 0

      ...after all, if it had just done its job flawlessly there'd be no way for the crowd to know it was a microsoft product.

      If it would have done it's job flawlessly, then it actually would have been sure it wasn't microsoft product.

  62. fuck subjects by newr00tic · · Score: 0

    The opposite of prostitution is constitution, so what is new?

    --
    A horse can't be sick, you know, even if he wants to.
  63. Stop 0xF4? by earthling1023 · · Score: 1

    Anybody has an idea of what the real problem may be? It may be related to overloaded network or a faulty network card. See http://support.microsoft.com/kb/954311.

  64. Re:Doesnt look like a BSOD... by YttriumOxide · · Score: 1

    I've (un?)fortunately never got to see one of these in the real world. You wouldn't know an easy way to force one would you?

    Actually, I do wonder sometimes what the difference between my Macs and other peoples are... current uptime on the box I'm typing on is 105 days (yes, I ignore most updates that require a reboot unless/until I decide I need them) and I use this box pretty heavily for web browsing, watching movies, playing Nethack and coding (although admittedly, about 75% of my coding is done under Windows in VMWare Fusion, since it's work related stuff - and THAT crashes from time to time)
    I'm well aware my Mac CAN crash, and I've probably been very lucky so far, but after two years of owning it, I haven't seen that "grey multilingual screen of death" and I'd kind of like to.

    --
    My book about LSD and Self-Discovery
    Also on facebook as: DroppingAcidDaleBewan
  65. certify == pay-for-pay, != quality assurance by SgtChaireBourne · · Score: 1

    Stop peddling the idea that it is acceptable for systems to fail catastrophically. Sure MS is synonymous for unreliable, but no need to turn it into a case of sour grapes and pretend that everything else is as poorly designed or manufactured.

    MS certification of drivers has not improved "quality" of the drivers over the years. It is, as predicted, more related to the ability to pay and accept harsh licensing terms. It simply allows MS to further restrict development of Windows devices and applications to parties willing to toe the party line.

    A "bad" driver should not be able to bring down the system. Using MS products is simply helping Bill and his minions make bad engineering acceptable. Some anthropologists and psychologists might claim that acceptance for failure becomes generalized beyond that one domain and into society in general. Now that's evil with hair on it.

    --
    Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
  66. Running z/Linux on it? by FatSean · · Score: 1

    Could be..

    --
    Blar.
  67. Re:Doesnt look like a BSOD... by Anonymous Coward · · Score: 0

    At least the "ooh shiney" just works.

    Yeah, until you want to do something that's slightly out of the ordinary. And of all the goddamn saying, "it just works" is one of the worst. iTunes, for example, doesn't JUST work. It pisses the user off to high hell deciding "Ah, you're looking through your media library. Of course that means you want to listen to exactly what you're looking at instead of the playlist you spent the last ten minutes setting up". And then you plug an iPod into a computer with iTunes and it thinks "Wow, I've never seen this iPod before. I'd best wipe it clean just to make sure!"

    Don't even get me started on the goddamn iPhone. I buy my tech for what I WANT TO USE IT FOR, not what apple thinks I should use it for!!

  68. Re:Doesnt look like a BSOD... by shutdown+-p+now · · Score: 1

    A shiny BSOD? Does your desktop slowly implode and then burn on a kernel crash in full 3D, or what is it?

  69. (OT) Re:well by orasio · · Score: 1

    Esp. coming from the only country where football is not actually played with your feet!!

  70. fireworks by Afrix · · Score: 1

    oh noes, the fireworks (screensaver) are broken.

  71. Re:Doesnt look like a BSOD... by Lobster+Quadrille · · Score: 1

    My old powerbook used to get them all the time before I upgraded to Leopard. Never did figure out a reliable way to force them, but it often happened when I was borking around with wifi drivers, internal and external cards, and kismac.

    --
    "The cup is in turn designed for holding hot or cold liquids, and has an open rim and closed base." --US Patent #5425497
  72. Re:You're dead wrong. by nedlohs · · Score: 1

    And I assume you NEVER mastered reading simple English statements.

    After all that is exactly what I said.

  73. They mostly run Unix by belmolis · · Score: 1

    Although they evidently used XP for that presentation, the real IT infrastructure that makes the Olympics run is mostly Unix according to this Computer World Hong Kong article.

  74. Mac by PRMan · · Score: 1

    Mac used to have the little cartoony Mac guy with X's over his eyes AND NO ERROR MESSAGES!

    Thanks, Apple, that's real helpful to have to hold a switch on the side of the machine and get dumped into a debugger to find out what's wrong.

    --
    Peter predicted that you would "deliberately forget" creation 2000 years ago...
    1. Re:Mac by db32 · · Score: 1

      Given that MS error messages typically all say "Something bad happened, call an administrator" like an administrator is supposed to know what happened with no information included in the "something bad" section. The loads of nonsensical garbage (unless of course you can read memory addresses and the like) is not very useful to the vast majority of users anyways and they would probably have enjoyed a little frowny face X eyed guy.

      My personal favorite actually came from a linux box. "The printer is on fire." I was actually very disappointed to learn that the printer was not actually on fire as the error message continued to state.

      --
      The only change I can believe in is what I find in my couch cushions.
    2. Re:Mac by Anonymous Coward · · Score: 0

      There is a real explanation for that "on fire" message.

      Back in the good old days, there were drum printers. These were fast printers, a bit like typewheel printers, but instead of hammering one letter on to the paper at a time, these printers had one wheel per character, and when they were arranged, it would hammer an entire line onto the paper. Very noisy, and you could feel the floor shaking in the next room, but they were very fast.

      Now, these letter wheels rotated with speeds around 1200 rpm, the printers were cleaned with ethanol (flamable), and generated quite an amount of paper dust.

      Sometimes printers jam. Happened in those days too. For this, the parralel port has two signal. "Error" and "Offline". Offline alone is easy, someone hit the button to bring the printer offline, maybe to clean it. Error+offline: The printer jammed, and went offline. An operator needs to clear the jam, and hit the button to bring the printer back online.

      But error without offline? The paper jammed, but the printer did not go offline. Remember those wheels spinning at 1200 RPM? They are now spinning while touching the paper, generating an awful amount of heat. Cleaning ethanol and paper dust just adds to the problem.

      The printer may not be on fire when the message appears. But it may very well be when you get to it (noone is working in the same room of the printer because of the noise and vibrations).

      From memory, details may be wrong.

    3. Re:Mac by db32 · · Score: 1

      You sir have made me feel terribly young, I used to feel a bit old having worked on tractor feed dot matrix type jobs. I have never encountered a drum printer. It was with a parallel printer, so it makes sense that something tripped it up signal wise. If I remember correctly the printer did indeed continue to operate while "The printer is on fire!" message kept popping up in the logs. I bet it was a signaling/cable problem tripping the Error without Offline.

      --
      The only change I can believe in is what I find in my couch cushions.
  75. Re:Doesnt look like a BSOD... by pandrijeczko · · Score: 1

    And with all the unpatched DNS and Safari holes, it will also "just work" for just about any cracker as well.

    --
    Gentoo Linux - another day, another USE flag.
  76. Re:Doesnt look like a BSOD... by pandrijeczko · · Score: 1

    Actually, I've used Linux for 10+ years now and I've seen quite a few kernel panics - but just about everyone of them has been at the point of reboot when I've just installed a new kernel and done something stupid it the kernel configuration. But then I just boot the old working kernel again and retry the compilation.

    I've also had a couple of freezes while using X-Windows but, again, if you're good enough to be fiddling about with Linux in the first place then you're good enough to retrace your steps back to the point at which your system was stable.

    In either case, neither of the above is a particularly difficult issue to at least work around temporarily, unlike trying to decipher what might be causing a BSOD. (And yes, I bow to any more experienced Windows sysadmins than I out there who would disagree with my statement.)

    And in almost 30 years of both working and playing with computers, I have always favoured UNIX & Linux, frequently had a need to work with Windows (and indeed need to keep XP around for some stuff I can't do as easily in Linux) but never ONCE had the slightest compulsion or need to even think about using a Mac.

    I have never once owned a single Apple product and as long as they continue to lock users in with proprietary formats and DRM more heavily than Microsoft does, then I never will. At least Microsoft have sometimes "forced" me to use Windows, far more than Apple ever will...

    --
    Gentoo Linux - another day, another USE flag.
  77. Re:They were Axon mediaservers running WinXP Embed by Anonymous Coward · · Score: 0

    The Axom was developed in house by High End(HES) who, quite frankly, can't write software for shit. The Hog 3 desk has been a disaster, especially the later Win XP based models. It's never worked properly and newer versions of the software seem to introduce as many bugs as they solve. They still haven't got the windowing system to work as well as it did on the Hog 2, but they did manage to oversee the loss of the entire development team, and (allegedly) many of their replacements.
        We wait and see whether the new owners will be able to stop the rot. The Hog 2 ran the Sydney Olympic Opening Ceremony with no (obvious) issues, the Hog 3 hasn't really been involved in too many big events after it was deemed too unreliable. This latest disaster will only reinforce this view. The new owners Barco may well be regretting their latest purchase...

  78. Everyone is missing the point by Daetrin · · Score: 2, Insightful

    I wouldn't be surprised if Microsoft didn't view this as a great piece of PR. They've been trying to convince everyone that XP is old and busted and Vista is the hot newness. They want people switching to Vista, not sticking with XP. Now an Olympic official has gone on the record as saying that Vista wasn't good enough/stable enough for the opening ceremonies so they were going to use XP instead. They use XP, and they get a BSOD. Now Microsoft can just nod and sagely say "XP was a great OS for it's time, but as everyone knows it still has some bugs in it. If only they'd used the new and improved Vista OS then they could have avoided that unfortunate bit of unpleasantness."

    It doesn't matter if using Vista would have cost twice as much, taken three times as long to set up and resulted in four times as many errors during the opening ceremony. What people saw fail was XP, and that's what Microsoft will stress.

    --
    This Space Intentionally Left Blank
  79. I wonder about that... by Anonymous Coward · · Score: 0

    IRQ_NOT_LESS_THAN_OR_EQUAL

  80. A reason why TV stations keep on using old fashion by Ilgaz · · Score: 1

    If a machine will only do one thing and it won't be connected to Internet, my choices would be Windows 2000 with WHQL drivers installed old but very stable/non overheating card or Mac OS X 10.2.8 , yes the one from 2003.

    XP isn't conservative enough, really.

    Of course note: They shouldn't be connected to Internet, even Modem should be disabled via hardware settings or people may see something else than BSOD ;)

  81. Re:You're dead wrong. by Khyber · · Score: 1

    And you assumed wrong. Sorry, I meant to hit reply to the post above yours - Slashdots comment system is still fucking broken on FireFox 3.

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
  82. I don't think this is so.... by gbutler69 · · Score: 1

    I'm pretty sure that under GNU Hurd, hardward drivers resid in the Micro-Kernel, they are not "servers" per se. Please correct me if I am wrong (provide link please).

    --
    Over-the-top Response Guy! Giving "Over-the-Top Responses" since 1970.
  83. Funny or Sad? by Anonymous Coward · · Score: 0

    Funny or Sad? Sigh. Oh Microsoft. Windows dies with blue screen at Olympics [VOTE] - http://www.thriveorfail.com/60a75

  84. Looks like a STOP 0x000000F4 by Anonymous Coward · · Score: 0

    and that is caused by faulty hardware. Lenovo machines suck :)

  85. Obligatory Sir Humphrey Appleby quote by Anonymous Coward · · Score: 0

    Sir Humphrey Appleby: East Yemen, isn't that a democracy?
    Sir Richard Wharton: Its full name is the Peoples Democratic Republic of East Yemen.
    Sir Humphrey Appleby: Ah I see, so it's a communist dictatorship.

  86. maybe..... by Anonymous Coward · · Score: 0

    it's a BSOD screensaver.....ahhaha

  87. They could have gone with Apple by qzulla · · Score: 1

    But Jobs ego would have blocked the fake fireworks.

    qz, posted from a Mac

  88. Hardware drivers by Neva · · Score: 1

    ..and chinese manufacturers have been known to make a multitude of device models, of which not nearly all get Microsoft's WHQL testing and bug-fixing.

    It wouldn't be at all surprising if the Olympic games' machines used chinese brand (cheaper) devices.

  89. Why is software blamed instead of hardware? by master_p · · Score: 1

    The problem with kernel modules is that they are not isolated from the rest of the system, because the CPU design does not provide a mechanism for such a type of isolation, forcing O/S designers to revert to schemes like a microkernel, where each module is a separate process. CPU designers are to blame, not software designers.

  90. Sydney Olympics - Near Disaster with the Flame by tezza · · Score: 1

    My girlfriend at the time was one of the techies in the Sydney Olympics opening ceremony.

    After connecting up the wires to that "Little Girl who Sings then Flies", she got called to an emergency.

    The computer which controlled the flame mechanics crashed. It was a windows box.

    They had a big rope attached to the flame. Hidden behind the falling water the tech crew struggled to pull the flame assembly back on to the rails.

    During this time the misbehaving window box rebooted.

    What no one mention was that the flame initially was a discreet gas supply, which had only a little capacity. All the tech crew thought the mini flame would extinguish before it reached the summit.

    What a close call!

    --
    [% slash_sig_val.text %]
  91. A mainframe crashed? by Anonymous Coward · · Score: 0

    I'm going to jump in and ask exactly what that mainframe was, and what it was doing when it crashed?
    Was it a Production server, or still being installed / tested? Was the event unusual? You comment makes it appear that it is a Prod server and that it was doing something valuable / critical at the time.

    In comparison, if you said that you've seen a mainframe crash and burn on IPL or just fail.. or more likely CICS (particularly CWI, greatly enhanced chances when manual editing of system macros is abundant) bounce.. I'd say, yes, been here, watched that.. tick tock tick tock.. and let's see that one again Fred, perhaps with a better Last Known Good.. (or, more liklely 'good god, wtf did you DO?').

    For the peanut crowd observing, it's useful to note that the main hallmarks of mainframes are stability and reliability.. although you need to be in the noc to hear the ops mutter 'once it is up... sure.. '

    ---

    And, see that big red button on the wall behind the glass plate that says 'do not press'? Right. No newbie jokes about it please.