Real Glitch (YEAR LATE) solved fastgreenspun.com : LUSENET : Poole's Roost II : One Thread |
BOTTOM LINE:``We didn't think of trying out the date 31/12/00,'' said Ronny Solberg of Adtranz, the German producer of the new trains.
Sunday's problem was quickly solved on a temporary basis by resetting the computers to Dec. 1, 2000, and the trains started upon ignition.
---------------------------- -----
Y2K Bug Belatedly Hits Norway Trains
The Y2K computer glitch hit Norway's national railroad company a year later than expected.
http://www.nytimes.com/aponline/technology/AP-Norway-Y2K-Bug.html
-----
January 1, 2001 Y2K Bug Belatedly Hits Norway Trains
A.P. INDEXES: TOP STORIES | NEWS | SPORTS | BUSINESS | TECHNOLOGY | ENTERTAINMENT
By THE ASSOCIATED PRESS
Filed at 2:29 p.m. ET
OSLO, Norway (AP) -- The Y2K computer glitch hit Norway's national railroad company a year later than expected.
The bug was discovered when none of the company's new 16 airport express trains or 13 high-speed, long-distance Signatur trains would start early in the morning of Dec. 31.
The computers on board the trains apparently did not recognize the date, something not anticipated by experts who checked the systems thoroughly last year in anticipation of problems feared worldwide when the clocks rolled to Jan. 1, 2000, a spokesman said.
``We didn't think of trying out the date 31/12/00,'' said Ronny Solberg of Adtranz, the German producer of the new trains.
Sunday's problem was quickly solved on a temporary basis by resetting the computers to Dec. 1, 2000, and the trains started upon ignition.
``Now we have one month to find out what went wrong so we can fix the problem for good,'' Solberg was quoted as saying by the daily newspaper Dagbladet.
The older trains that still make up most of the NSB state railroad's fleet were not affected.
The problem had little impact on train traffic as the airport express trains were quickly put back on schedule, and some older trains were used on the two long-distance routes affected by the glitch. All trains were running as usual by Monday, according to the Norwegian news agency NTB.
Y2K was caused by decisions by computer makers decades ago to use two digits to represent the year. The shortcut saved money on memory and storage, but also caused some computers to wrongly interpret 2000 as 1900.
After billions of dollars and months of preparation worldwide, few problems were recorded last year.
-- Anonymous, January 02, 2001
Yep,the Y2.001K glith strikes again! Good find cpr, I searched for other examples and didn't find any, other than my own nuclear plant one: Y2.001K Problems affect nuclear plantI first submised the Y2.001 bug might bite us here:
Unfortunately, what I forgot to do was to set up a web site to warn the world of this impending disaster and offer survival rations and doomsday books, with a hefty markup. I coulda had a banner that said "Y2.001K, IT CANNOT BE FIXED!" ;)
-- Anonymous, January 03, 2001
The link to the thread where I first submised the Y2.001 bug might bite us:
-- Anonymous, January 03, 2001