SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Discuss Year 2000 Issues

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: J.L. Turner who wrote (5620)4/29/1999 4:39:00 PM
From: B.K.Myers  Read Replies (2) of 9818
 
My wife and I just scheduled a week's sailing vacation in the Grenadines.

My wife made the transportation arrangements with a travel agency in Florida. The travel agent told her that they were having all kinds of problems with their reservation system with flights in 2000. She was told that their systems were crashing in a variety of ways and affecting downstream systems. The travel agent told her that the problems were being caused by Y2K fixes to the reservation system. The problems didn't show up immediately, but started occurring at later dates. The travel agency is suggesting special flight insurance in case there are problems with year 2000 reservations.

Although the success of the airline industry to fix their systems for Y2K is widely used as an example that the Y2K problem can be fixed, it looks like there were some bugs in the fix. Maybe more importantly, the bugs don't show up until one or two months after the appearance of Y2K data.

If we get past January 2000 without any serious embedded systems problems, this delayed effect will start to cause problems in the spring and summer of 2000. There is simply too much concentration on 1/1/2000. We have to start looking at the long-range effects.

B.K.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext