Microsoft Shuts Down Nearly All Southern California Air Traffic
from the that'll-get-you dept
Whoops. Having just flown back from southern California this past weekend from the DEMOmobile conference, I'm glad this "glitch" didn't happen until Tuesday. Apparently, there was a "radio breakdown" that left almost all air traffic in SoCal without guidance. The culprit? Microsoft. Apparently, the air traffic control system being used is now run on Microsoft, after recently replacing a Unix-based system. Just one problem: the system needs to be rebooted every 30 days to avoid a "data overload," and someone forgot to manually run the reboot. Beyond the shock of discovering that this air traffic control system can't handle very much data, you have to wonder why the reboot system can't be automated, or at least have a "reminder" go off at some point.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Reader Comments
Subscribe: RSS
View by: Time | Thread
Is this the only reason?
Not that I am fond of Microsoft systems for such mission-critical applications, but this seems to be a distraction introduced to cover up what exactly happened.
[ link to this | view in chronology ]
Re: Is this the only reason?
Thank God no one was killed!
[ link to this | view in chronology ]
I was one of the ones stuck
[ link to this | view in chronology ]
What if
[ link to this | view in chronology ]
No Subject Given
[ link to this | view in chronology ]
Re: Read EULA
But you are very right in that the only possible entity that can be blamed is the system designer, since they have no recourse with Microsoft. The deep pocket stop there. Microsoft has absolved itself of any accountability associated with Windows usage. Surprised? Read Windows XP EULA paragraphs 16 and 17. See URL above.
Microsoft doesn't really stand behind the actual OS product, you get it AS IS. It simply stands behind the retail box...it has authorized software in it and you puchased it. You might be eligible for a refund in some states if the media is defective...which to Microsoft means it passes an ISO checksum test. Here's a couple tidbits from the URL referenced above.
"...Microsoft and its suppliers provide the Software and support services (if any) AS IS AND WITH ALL FAULTS, and hereby disclaim all other warranties and conditions, whether express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of reliability or availability, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses, and of lack of negligence, all with regard to the Software, and the provision of or failure to provide support or other services, information, software, and related content through the Software or otherwise arising out of the use of the Software. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THE SOFTWARE."
I suspect the system got bit by an automatic application of SP2. Based on the EULA, automated updates by Microsoft and approved third parties are to be expected. It would be the responsibility of the System designer to test to see if Windows still behaves the same after Microsoft delivers automated SPs from Microsoft or trusted third parties.
Yep, that's got to be the deal we need on mission critical software. Variables that can't be controlled altering the system...this will please the customer greatly.
[ link to this | view in chronology ]
Re: No Subject Given
It's the little things that count. If it can't run a secure environment for the home, how the hell is it supposed to do that for mission critical apps?
[ link to this | view in chronology ]
No Subject Given
Article from 1999 on 49.7 day bug
[ link to this | view in chronology ]
Microsoft Shuts Down Nearly All Southern Californi
Are they Insane???
I wouldn't trust Microsoft to run a traffic light system, let alone a critical airport radar system....
[ link to this | view in chronology ]