To: David Eddy who wrote (9387 ) 2/9/1998 11:57:00 AM From: Jeffrey S. Mitchell Read Replies (1) | Respond to of 13949
Re: Another Millennium Glitch Lurks Weeks After Jan. 1 By MATTHEW L. WALD of the New York Times WASHINGTON -- Computers that survive New Year's Day 2000 by pretending it is 1900 may function fine -- but only for 59 days. In a new twist on the so-called year 2000 problem, experts say, Feb. 29 will offer new opportunities for computers to fail. <snip> But there is another anomaly. The Federal Aviation Administration, which has some of the oldest hardware and software, including some of the last vacuum tubes, says its survey of its 400 computer systems uncovered a leap year problem. Why? 2000 is a leap year. 1900 was not. <snip> Any computer that believes it is 1900 will not allow Feb. 29 to exist. Every day, the FAA loads thousands of flight plans for scheduled airline flights into its computers, but it discovered that using its current software, it could not accept flight plans for Feb. 29. Experts there say this is one reason they are determined to correct all year 2000 bugs. At the Air Transport Association, an airline trade group that is watching to assure year 2000 compliance for computers used for everything from air traffic control to maintenance scheduling, Jack Ryan, an air traffic control expert, said jokingly that the 59 days might be a godsend "for those procrastinators among us." Personal computer users may find leap day glitches in odd ways. For example, Windows 3.1 accepts Feb. 29, 2000, as a valid date. But Telecommuter, a word processor and modem program copyrighted in 1988, when asked to put that day's date into a document, will respond that day with Feb. 30, 2000. On March 1, 2000, it will respond with March 2. Full link:nytimes.com - Jeff