Free Republic
Browse · Search
News/Activism
Topics · Post Article

To: Swordmaker

“Windows7 was running on a piece of avionics test equipment in 2008 when this accident occurred? Not by a long shot. “

Nope

“My considered opinion is that it would be likely WindowsXP... and maybe even Windows98. .. and probably not updated.”

Please read the story, your slip is showing. The plane wasn’t running any windows OS and the accident wasn’t caused by the malware. The accident was pilot error.

The story claims that a poorly maintained maintenance computer caused the crash. Just another microsoft hit job.


34 posted on 08/22/2010 3:37:43 PM PDT by driftdiver (I could eat it raw, but why do that when I have a fire.)
[ Post Reply | Private Reply | To 33 | View Replies ]


To: driftdiver
Please read the story, your slip is showing. The plane wasn’t running any windows OS and the accident wasn’t caused by the malware. The accident was pilot error.

Thank you, your assumption that I did not read the story is incorrect. You are reading far too much into this, driftdiver. No slip here. The story referred to the fact that the software failed to warn that a human error was occurring. That software failure was not detected due to the fact that the ground based test equipment was infected by a trojan. The concatation of events led to, or contributed to the disaster.

Quit defending Microsoft for their software errors of the past.

37 posted on 08/22/2010 5:28:04 PM PDT by Swordmaker (This tag line is a Microsoft product "insult" free zone!)
[ Post Reply | Private Reply | To 34 | View Replies ]

Free Republic
Browse · Search
News/Activism
Topics · Post Article


FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson