Go back
another reason not to use Windows:  BSOD

another reason not to use Windows: BSOD

General

zeeblebot

silicon valley

Joined
27 Oct 04
Moves
101289
Clock
23 Jul 10
1 edit
Vote Up
Vote Down

another fateful appearance of the Blue Screen of Death.

zeeblebot

silicon valley

Joined
27 Oct 04
Moves
101289
Clock
23 Jul 10
Vote Up
Vote Down

Originally posted by zeeblebot
another fateful appearance of the Blue Screen of Death.
http://www.foxnews.com/us/2010/07/23/report-alarm-gulf-rig-disabled-oil-spill/

Disasters

Rig Worker: Fire Alarm System on Gulf Rig Disabled Before Oil Spill

Published July 23, 2010

The fire alarm system on the Deepwater Horizon oil rig was partially disabled prior to the catastrophic explosion that caused the oil spill in the Gulf of Mexico, a rig worker testified Friday.

The rig's chief electronics technician told a federal panel that the Horizon's general alarm system was deliberately set in "inhibited" mode so that sirens would not wake the sleeping crew in the middle of the night.

"They did not want people woken up at 3 a.m. from false alarms," Michael Williams told the six-member panel. As a result, the alarm failed to trigger during the emergency, and workers were forced to sound the alarm through the loudspeaker system on board.

Williams said the craft's computer systems were a "wreck" when he started working on the rig in 2009. Equipment constantly malfunctioned, computers that were supposed to monitor the rig would lock up showing a "blue screen of death," and work was marred by many faulty detectors.

Williams said he tried to repair the systems but faced problems with equipment, and that replacement hardware -- ordered before the explosion -- had not been installed when disaster struck.

...

C
Not Aleister

Control room

Joined
17 Apr 02
Moves
91813
Clock
23 Jul 10
Vote Up
Vote Down

Sounds like 3rd party software and interfacing hardware causing Windows to crash. Not Microsoft's fault, but who cares as long as it sells the papers.

zeeblebot

silicon valley

Joined
27 Oct 04
Moves
101289
Clock
24 Jul 10
Vote Up
Vote Down

stability of an OS is the OS manufacturer's responsibility.

have fun with your MS-no-3rd-party-software box.

S

Joined
19 Nov 03
Moves
31382
Clock
24 Jul 10
Vote Up
Vote Down

Originally posted by zeeblebot
stability of an OS is the OS manufacturer's responsibility.

have fun with your MS-no-3rd-party-software box.
How do you figure it's the OS that's at fault? The guy even says the hardware was an issue. Third party software integration with an already established operating platform is the third party's responsibility. What don't you get about that, or are you just tool busy hating Microsoft to see it?

zeeblebot

silicon valley

Joined
27 Oct 04
Moves
101289
Clock
24 Jul 10
Vote Up
Vote Down

Originally posted by Starrman
How do you figure it's the OS that's at fault? The guy even says the hardware was an issue. Third party software integration with an already established operating platform is the third party's responsibility. What don't you get about that, or are you just tool busy hating Microsoft to see it?
http://en.wikipedia.org/wiki/Comparison_of_Windows_and_Linux#Stability

For an operating system to be subjectively “stable”, numerous components must operate synchronously. Not all of these components are under the control of operating system vendor; while Linux and Windows kernels may be stable, poorly written applications and drivers can hamstring both. Much of stability, then, is the extent to which the operating system is structured to thwart the consequences of bad behavior of third party installations.

S

Joined
19 Nov 03
Moves
31382
Clock
24 Jul 10
Vote Up
Vote Down

Originally posted by zeeblebot
http://en.wikipedia.org/wiki/Comparison_of_Windows_and_Linux#Stability

For an operating system to be subjectively “stable”, numerous components must operate synchronously. Not all of these components are under the control of operating system vendor; while Linux and Windows kernels may be stable, poorly written applications and drivers can hamstring both ...[text shortened]... ng system is structured to thwart the consequences of bad behavior of third party installations.
So what? That doesn't remove the responsibility of the third party to build a program which works on whichever OS it chooses to implement its software and hardware on. The article you post suggests the better OS is the one that better assess potential issues of third party integration and that's fine, but it certainly does not mean the blame for any problem rests with the OS manufacturer. It even goes so far to say that poorly written stuff will cripple the OS. What is it about this that you don't get?

C
Not Aleister

Control room

Joined
17 Apr 02
Moves
91813
Clock
24 Jul 10
1 edit
Vote Up
Vote Down

If this was a *nix system there would have been an explosion still, because buggy software stays buggy software, and buggy driver/hardware interfacing doesn't magically sort itself out because the OS doesn't fatally crash.

*nix probably wouldn't have crashed, but that doesn't sell sensation...

K
Happier Now!!

Home!!

Joined
19 Oct 04
Moves
176085
Clock
24 Jul 10
Vote Up
Vote Down

Even I would prefer a linux based OS over Microsoft, but it is without question, the 3rd parties responsibilty to incorporate it's software into the current standing OS.

Added note: Even though the "blue screen of death" appeared, it doesn't mean it is Microsoft. The problem could also be from other OS systems as well. Since it is a hardware issue that, reasonably thinking, causes it's software to error out.

h

Joined
09 Jun 04
Moves
39731
Clock
24 Jul 10
Vote Up
Vote Down

"Fire Alarm System on Gulf Rig Disabled Before Oil Spill"

Alarm deliberately disabled.

It's clearly Microsoft's fault.



I'm going to the computer shop to buy Linux right away for my oil rig! What's the latest version? I don't want to look like an idiot.

C
Cowboy From Hell

American West

Joined
19 Apr 10
Moves
55013
Clock
24 Jul 10
Vote Up
Vote Down

Originally posted by hopscotch
"Fire Alarm System on Gulf Rig Disabled Before Oil Spill"

[b]Alarm deliberately disabled.


It's clearly Microsoft's fault.



I'm going to the computer shop to buy Linux right away for my oil rig! What's the latest version? I don't want to look like an idiot.[/b]
Too late

h

Joined
09 Jun 04
Moves
39731
Clock
24 Jul 10
Vote Up
Vote Down

Originally posted by ChessPraxis
Too late
It's like you're trying to make a sad attempt to be witty without realising... oh nevermind. I've seen worse things on the internet.

Carry on.

sbacat
Eddie's Dad

Raving Mad

Joined
13 Jun 08
Moves
268608
Clock
24 Jul 10
Vote Up
Vote Down

I disagreed with the drilling moratorium before all this stuff started coming out. If the other rigs are run in the same slipshod manner, we do need to take a hard look at them before starting them back up.

Completely disgraceful and willfully negligent. MS not to blame here; 1,000% BP.

DS
I'm A Mighty Pirateā„¢

PaTROLLING the forum

Joined
01 Dec 04
Moves
36332
Clock
24 Jul 10
Vote Up
Vote Down

I heard that the Windows BSOD was the cause of the Challenger disaster AND it was the second gunman on the grassy knoll.

w
If Theres Hell Below

We're All Gonna Go!

Joined
10 Sep 05
Moves
10228
Clock
24 Jul 10
Vote Up
Vote Down

Originally posted by Daemon Sin
I heard that the Windows BSOD was the cause of the Challenger disaster AND it was the second gunman on the grassy knoll.
I heard unix was walking on water at the time challenger blew up. what a convenient alibi. maybe a little too convenient...

Cookies help us deliver our Services. By using our Services or clicking I agree, you agree to our use of cookies. Learn More.