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.
Gold/Mining/Energy : Gold Price Monitor -- Ignore unavailable to you. Want to Upgrade?


To: IngotWeTrust who wrote (49662)2/28/2000 12:52:00 PM
From: long-gone  Respond to of 116801
 
Monday February 28 9:15 AM ET
Japan Watches for Leap Year Glitch

TOKYO (AP) - The Japanese government said it will monitor computer operations Monday and Tuesday on concern that the leap year day in February may cause Y2K-like glitches.

About 10 staff members in a computer task force set up at the prime minister's residence will be on duty to handle any emergencies, an official at the office said.

The Meteorological Agency reported Monday afternoon that computers at six local observatories had failed to correctly recognize Feb. 29, the extra day on the calendar, because of a computer bug.

The agency said the computer error would be rectified later Monday, said agency spokesman Ippei Eguchi.

In the private sector, Kansai Electric Power Co. said 80 extra workers will be on duty through Tuesday evening.

``We have fixed problems that occurred at the start of the year and basically we don't foresee any new trouble,' said company spokesman Takeshi Kato.

Sony Corp (NYSE:SNE - news). said that two kinds of 8-millimeter video cameras sold between 1986 and 1988, and three types of word processors sold between 1987 and 1989 may fail to recognize Feb. 29.

Though Japan last year said it had conquered the millennium glitch, in January there were reports across the country of computer problems caused by Y2K, including data transmission errors at some nuclear power plants and financial institutions.

The Y2K bug is caused by computers confusing the year 2000 for 1900.

Computers long have had difficulty in leap years - treating Feb. 29 as March 1, or March 1 as Feb. 30.

This year, risk of error is greater because 2000 is an exception to an exception.

An extra day is added to the calendar every four years. But years that end in '00' do not get the extra day unless they are divisible by 400. So 2000 is a leap year, but 1900 was not.

dailynews.yahoo.com