[no subject]

Well clearly this could have been avoided, as I am sitting at a Windows XP
workstation that routinely runs for over 100 days without problems. I have a
Windows 2000 server that is currently showing 64 days uptime, and 4 Windows
2003 servers that are all at 53. Of course, there's a Linux box in the same
room that will probably be up for at least the remainder of this calendar
year, barring any power failures or catastrophic event...but that's beside
the point. The point here is that shoddy coding caused this problem, and it
wasn't code coming out of Redmond. I find it disturbing that the FAA uses
Windows for critical functions, but I find it downright alarming that they
have no better sense than to leave crappy software like this in place. This
system should have never made it out of the testing phase and into
production. 

--
Jonathan "resist temptation to bash MS and be fair, people" Rickman


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00732" href="msg00732.html">[ale] Windows crashes L.A. Airport</a></strong>
<ul><li><em>From:</em> kevinostoll at yahoo.com (Kevin O'Neill Stoll)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00736.html">[ale] Anti-virus</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00738.html">[ale] Anti-virus</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00732.html">[ale] Windows crashes L.A. Airport</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00754.html">[ale] Windows crashes L.A. Airport</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00737"><strong>Date</strong></a></li>
<li><a href="threads.html#00737"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>