Railway glitch -- Dec. 31 the 366th day of 2000

greenspun.com : LUSENET : Unk's Wild Wild West : One Thread

http://www.norwaypost.no/content.asp?folder_id=1&cluster_id=14943

Link

31. Desember 2000

The Y2K problem a year late

The Norwegian Railways were hit by the Y2K problem a year late. On December 31, the new Signatur trains and the Oslo Airport Express ground to a halt, as the data controlled operating systems refused to function.

However, the fault was overcome by turning the computer clocks back one month, and only minor delays were experienced on the last day of the year 2000.

The experts believe the problem occured because this year was leap year, and December 31st was the 366th day of the year 2000.

(NRK)

Rolleiv Solholm

-- (in@computer.news), January 01, 2001

Answers

http://dailynews.yahoo.com/h/ap/20010101/tc/norway_y2k_bug_1.html

Link

Monday January 1 2:29 PM ET

Y2K Bug Belatedly Hits Norway Trains

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.

-- (in@computer.news), January 01, 2001.


“31. Desember 2000”

Houston, we have a problem.

-- Barry (bchbear863@cs.com), January 01, 2001.


We're all going to die.

(does this mean I am officially back?)

-- FutureShock (gray@matter.think), January 02, 2001.


December 31, 2000 was listed as a possible critical date in the NRC's 1998 contingency plan.

http://www.nrc.gov/NRC/COMMISSION/COMS/com1998-036/y2kcplan.html

Link

December 31, 2000 (366th Day of Uncommon Leap Year)

Some programs operate by counting the days in the year. If the writers of these programs were unaware of the uncommon-leap-year situation, their systems may not fail until December 31, 2000, the (unexpected) 366th day of the year.

-- (in@computer.news), January 04, 2001.


Moderation questions? read the FAQ