Slashdot Mirror
Public BSOD Sightings?
Sanksa Wott asks: "My travels over the weekend brought me to a very popular fast food restaurant, where, in the drive-through I was greeted with, what else... a blue screen! Since BSOD's can show up almost anywhere, I thought I would ask: 'What has your funniest/most interesting/noteworthy/etc. encounter with public displays of the BSOD been like?' Note: This isn't meant to be a troll, so lets be nice ;)"
My personal favorite BSOD is the one where Bill Gates was doing a keynote showing off the new features of Windows 98 and it crashed on a massive screen in front of hundreds of people.
:-)
Priceless
I would expect such blatant racism on Fark, but on Slashdot? Mods please ban this asshole.
Something like this?
The computer model was human high-school female type, and the human assistant was a manager.
C:\>
Lets see...
I've seen a BSOD on the local access cable channel.
I've seen a BSOD on the ATM at defcon (sorta. Wasn't really blue, but it was a major crash)
The best, though by far was when I went to Target and they had 3 consoles set up side by side. X-Box on the left, PS2 in the center, and GameCube on the right. The PS2 and GameCube were working just fine, demoing Tony Hawk and StarFox I think. The X-Box on the other hand was sitting there at a Black-Screen-Of-Death that was the same as a BSOD only black. (wow! great upgrade, Microsoft! No more Blue Screen of Death!) That really says a lot about the comparative reliability of those three systems. I'm glad Target was kind enough to provide the public with this demonstration: comparison shopping it its best!
At the top-10 American university I go to, there's a big plasma screen behind the main information desk that shows a slideshow of school events.
Imagine my surprise when, one day, the screen informs me that I can get a
U.N.I.V.E.R.S.I.T.Y D.I.P.L.O.M.A
from home, courtesy of Windows Messenger!
One of the most mind boggling was a recent M$ ad campaign where they provided a "cut out" BSOD that you could tape on your monitor "in case you missed them". I could not believe the gall that would be required for M$ to taunt is own users for being so stupid as to have used a previous version of their OS.
I was staying at a nice brand new hotel, part of a popular chain. [Names omitted to protect the other guilty parties.] The in-room video system box had a noisy fan, so I unplugged it so I could sleep. The next day I plugged it in and saw the NT 4 boot screen on the TV. So I took a closer look at the box. It had an RJ-45 connector plugged into the wall.
So of course, I plugged my notebook into that wall jack to see what I could find. I got a DHCP address -- nice! So I looked at my default route and telnetted to it. A prompt. Some sort of IOS knock-off. Hmm, what would the password be? It took me about 3 tries -- it was the name of the company that sold the video system, which was written on the remote control. I didn't know enough about routers back then to know what to look for beyond that. I don't know if I might have been able to somehow connect to the Internet, or download their movies, or get into their reservation system. I really didn't want to get into that much trouble anyway. But just the fact that their router password was that obvious blew my mind.
Software sucks. Open Source sucks less.
The famous Bill Gates crash video (1.63 MB)
-metric
I once saw the on screen scrolling Guide (now owned by TV Guide) crash and it was sitting at an AmigaDOS console prompt.
:)
One time, at 3 AM, I was surfing, and when I got to the TV Guide channel, what did I see? A MacOS 9 desktop, with some pebbles as the desktop wallpaper. I must have watched that sit there doing nothing for 2 hours before the mouse started to move and then I got to watch some guy launch the TVGuide program
Hehe, you should've Goatse'd it and walked off.
"Proudly Posting Without Reading The Article"
The ones at Minneapolis International run Windows 95! Windows 95!!!! They're constantly crashing. I wonder which H-1B suggested that one.
Actually, many of them do, for a variety of reasons.
I used to work installing and managing a FIDS (Flight Information Display System) at Toronto's Pearson International Airport. Several pictures of the FIDS systems I used to manage are in those BSoD picture pages that a couple of other posters have mentioned.
The company that wrote the FIDS had precisely one programmer. He was excellent, but the company was crap, constantly over-extending him and making ridiculous promises to airports and their stuff.
Working with FIDS systems requires a lot of reverse-engineering. Airports don't like to change their technology; they're even more conservative than banks. (Consider the potential real-world implications: two planes colliding in mid-air over a city.)
Consequently, things are old, and usually the people who wrote them didn't document very well, or the documentation can't be found, or the systems are completely proprietary. Then there's the almost weekly cycle of airport amalgamations, airline mergers, fuelling contractor changes, etc. The IT department has to run around patching existing stuff together to try to keep up.
There was one VAX system in the GTAA (Toronto airport administration) headquarters building which, according to legend, hadn't been touched in 6 years because no one knew if it would come back up on its own after a reboot.
You can imagine in this environment that people are loathe to give you a space on a hub to sniff records off an airside server. Cut off one pin and serial is a one-way street; it's pretty hard for an outside contractor's computer systems to screw things up.
The displays around the terminals tended to be ANSI color dumb terminals all driven off serial data. Very reliable, but very hard to upgrade. Data feeds for new FIDS systems typically have to come from several sources, all of different data formats, and be merged.
At Pearson, we had three data streams for three terminals. Two of them came from one source, down a serial line, simultaneously but with completely different data formats. A third was yet another completely different format, provided by an airline which would change the format of the data at a whim.
Our software to read this stuff had to be reading directly off the serial port with direct hardware access (needed to be able to make the weird handshaking requirements on some systems). The programmer who wrote it did so before Windows NT, and certainly before Linux hit it big, and didn't have time to port it.
The other big issue, of course, is the computers themselves. Arrivals, departures and gate monitors frequently receive the same data streams and therefore have to be independenly configured on what to display and what to ignore. Not to mention the internal stuff for fuelling and maintenance companies, baggage throwers, food services, cargo flights, etc. Almost all of these displays are driven by PCs which are usually stuffed into horrible places - ceilings, under desks, janitor closets. Half the runaround of maintaining these things is actually getting four security escorts (even if you have all the security clearances in the world!) to let you into some room somewhere where you THINK there might be a computer where you THINK the power supply fan might be failing because you keep on having vmm.vxd crashes.
You'll note that a vmm.vxd BSoD is usually caused by a hardware failure. In my not inconsequential experience with public display computers, usually caused by overheating because some idiot decided to store his large collection of empty Tim Horton's coffee cups in the little space behind the mysterious computer under his desk. Or because of the massive dustbunnies which accumulate in a suspended ceiling 25 feet above the International Departures concourse.
If you had the opportunity to do the whole thing over from scratch, of course, you'
Fire and Meat. Yummy.