Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.
Free Republic Y2K Watch : 5-Jan-2000
Free Republic Y2K Watch Report Date: 5
Jan 2000
|
Report Entries : Color Code Scheme
| Navy - Archived Items | Blue - Today's New Items | Gold - Special Interest |
| |
| Nation | City | System | Date | Description | Damage | News Media |
| Australia | Sydney | Bank Computers | 4 Jan 2000 | Incorrect Date | None | Internet Link | ||
| Australia | Nth | Fuel Card Transactions | 4 Jan 2000 | Incorrect Expiration Date | None | Internet Link | ||
| China | Guangzhou | ATMs and Banks | 3 Jan 2000 | No Cash and Date Errors | None | Internet Link | ||
| China | Hong Kong | Bank Computers | 3 Jan 2000 | Incorrect Date | None | Internet Link | ||
| China | Ningxia Region | Weather Station | 3 Jan 2000 | Data Relay System | None | Internet Link | ||
| Denmark | Copenhagen | Bank Computers | 3 Jan 2000 | Data Erased | None | Internet Link | ||
| Germany | Cologne | Bank Computers | 3 Jan 2000 | Accounting Errors | None | Internet Link | ||
| France | Paris : Effiel Tower | Clock | 1 Jan 2000 | Year Display : 19100 | None | "Not Y2K Related" ??? | ||
| Italy | Rome | Sewage System | 3 Jan 2000 | Non-Operational | None | Internet Link | ||
| Italy | Naples | Prison System Computer | 3 Jan 2000 | 100 Yrs More Jail Time | None | Internet Link | ||
| Jamacia | Capital City | Traffic Lights | 3 Jan 2000 | Non-Operational | None | Internet Link | ||
| Russia - Ukraine | Rovno | Nuclear Power Plant | 3 Jan 2000 | Power Reduction | Unknown | Internet Link | ||
| Japan | Ishikawa Prefecture | Nuclear Power Plant | 1 Jan 2000 | Radiation Monitors | None | Internet Link | ||
| Japan | Onagawa Prefecture | Nuclear Power Plant | 1 Jan 2000 | Cooling Water Monitor | None | Internet Link | ||
| Japan | Tokyo | Telephones | 3 Jan 2000 | Service Interuptions | None | Internet Link | ||
| Norway | Olso | Hospital : X-Ray Machine | 3 Jan 2000 | Minor Inconvenience | None | Internet Link | ||
| Norway | Olso | AMTs and Cash Registers | 3 Jan 2000 | Minor Inconvenience | None | Internet Link | ||
| Spain | Madrid | Nuclear Power Plants (2) | 4 Jan 2000 | Unknown | Unknown | Internet Link | ||
| Tanzania | Zanibar | TV Station | 3 Jan 2000 | Temporary Shutdown | Unknown | Internet Link | ||
| Turkey | Istanbul | Stock Exchange | 1 Jan 2000 | Data System Failed | Unknown | Internet Link | ||
| Turkey | Istanbul | Accounting Software | 4 Jan 2000 | Temporary Shutdown | Unknown | Internet Link | ||
| South Korea | Pyongchon | Apartment Heat & Water | 3 Jan 2000 | Service Interuptions | None | Internet Link | ||
| US | Florida, Melbourne | Television & Cable | 1 Jan 2000 | Channels Off-Air | Unknown | "Not Y2K Related" ??? | ||
| US | New York : ABC News | Website Time Display | 1 Jan 2000 | Year Display : 19100 | Unknown | Internet Link | ||
| US | Texas, Kentucky, California, New Mexico | Power Plants (8) | 1 Jan 2000 | Minor Problems | Unknown | See Below Reuters Report | ||
| US | Washington | Spy Satellite | 1 Jan 2000 | Communications Loss | Unknown | Internet Link | ||
| US | US Naval Observatory | US National Clock | 1 Jan 2000 | Year Display : 19100 | Unknown | Internet Link | ||
| US | Atlanta, Chicago, Denver, Orlando, St. Louis | Air Ports | 1 Jan 2000 | Windshear Systems | Unknown | Internet Link | ||
| US | Iowa : SW Region | Air Ports (20) | 1 Jan 2000 | Communications Down | Unknown | Internet Link | ||
| US | Limmerk, PA | Nuclear Power Plant | 1 Jan 2000 | Transformer Malfunction | Unknown | Internet Link | ||
| US | Delaware & Pennsylvania | Gambling Machines | 1 Jan 2000 | Date Look-Ahead Error | Unknown | Internet Link | ||
| US | Catawba, SC | Nuclear Power Plant | 2 Jan 2000 | Turbine Malfunction | Unknown | Internet Link | ||
| US | Oak Ridge, TN | Classifed | 2 Jan 2000 | Classifed | Unknown | Internet Link | ||
| US | Hawaii | Power Plants | 2 Jan 2000 | Two (2) brief Power Outages | Unknown | Internet Link | ||
| US | Colonie, New York | Retail Mechanise Billing | 2 Jan 2000 | Minor Inconveniences | None | Internet Link | ||
| US | Various Locations | Banks, Power, Water | 2 Jan 2000 | Minor Inconveniences | None | Internet Link | ||
| US | Sacramento, CA | ATM Machines | 3 Jan 2000 | Inconveniences | None | Internet Link | ||
| US | New Mexico | Motor Vehicle Computers | 3 Jan 2000 | Inconveniences | None | Internet Link | ||
| US | Al Gore Presidential Campaign | Internet Website | 3 Jan 2000 | Year Display : 19100 | No More Internet Inventions | Internet Link | ||
| US | New York City | Air Traffic Control | 4 Jan 2000 | Flight Delays | None | Internet Link | ||
| US | Boston : MA | Air Traffic Control | 4 Jan 2000 | Flight Delays | None | Internet Link | ||
| US | US Gov't : BATF | Gun Registration System | 4 Jan 2000 | 5 Day Shutdown ? | None | Internet Link | ||
| US | Utah : Salt Lake City | Computer Inventory System | 4 Jan 2000 | Complete Data Loss | None | Internet Link | ||
| US | Nebraska : Omaha | Door Access, Federal Bldg | 4 Jan 2000 | Lock-Out | None | Internet Link | ||
| US | South Carolina | Motor Vehicle Registration | 4 Jan 2000 | Inconvenience | None | Internet Link | ||
| US | Illinois : Springfield | Retail Transactions | 4 Jan 2000 | Inconvenience | None | Internet Link | ||
| US | Washington State | Weather Monitoring & Website | 4 Jan 2000 | Inconvenience | None | Internet Link | ||
| US | Wisconsin : Milwaukee | Boiler System | 4 Jan 2000 | Shut Down | None | Internet Link |
|
|
Seven U.S. nuclear
plants see minor Y2K glitches WASHINGTON (Reuters) - Seven U.S. commercial nuclear reactors experienced minor Year 2000 computer-related problems after the New Year's rollover, but none affected safety systems and were quickly fixed, government officials said Saturday. The seven plants saw malfunctions with computer systems used to support physical plant access control, the monitoring of operating data and the calculation of meteorological data. "None of the affected systems impacted continued safe operations," according to a statement from John Koskinen, President Clinton's Y2K trouble-shooter. There are 103 operating nuclear plants in the United States, providing roughly 20 percent of the nation's power. The plants and their problems follow: -- Arkansas Nuclear in Russellville, Ark. A personnel entry dosimeter went down after a software fix was not uploaded. It was uploaded and fixed. -- Indian Point 3 in Buchanan, N.Y. Transmission of atmospheric data to plant failed. Computer was rebooted and fixed. -- Millstone 2 in Waterford, Conn. Averaging of wind speed at a meteorological tower and averaging of certain radiation monitor readings. Failed programs were reset successfully. -- Nine Mile Point 1 in Scriba, N.Y. Transmission of meteorological tower data to computers failed. The system was transferred to manual entry and corrected. -- Palo Verde in Wintersburg, Ariz. A clock in a non-critical monitoring system did not synchronize. System ran fine on internal clock. -- Pilgrim 1 in Plymouth, Mass. A computer program failed and was fixed in a few minutes in a non-safety system. -- Monticello in Monticello, Minn. An interface with a plant process computer failed. The system was later fixed. Carl Paperiello, a spokesman for the Nuclear Regulatory Commission, said everything went well during the Y2K rollover, with no safety systems challenged by computer problems. "No critical functions were affected," Paperiello said.
|
bump
- Y2K FTP problem
- Y2K funny computer error in Talking Clock
- Y2K compliant? Not possible!
- Microsoft MSIE Y2K Insanity
- Giga-byte Javascript Y2K
- Unix98 localtime
- Risks in poor library design
[This item is retitled and adapted from the IP list of Dave Farber <farber@cis.upenn.edu>.] KCBS radio is reporting this morning that the Oakland 911 Emergency call system has determined its call prioritization algorithm is, well, technically speaking, /not/ fully Y2K compliant yet. Apparently incoming calls are timestamped with just a two-digit year code. Normally the call routing software gives top priority to the oldest (=earliest) calls, as one would expect. Alas, this means that as of the Friday midnight roll-over, all pending calls will instantly be kicked to the bad end of the priority list. As I interpret the news reports, the post-rollover calls will be stamped 1/1/1900, and, naturally, anyone who "just" called -- at 11:58 Friday evening, say -- is in far less dire straits than people who have been on hold for nearly 100 years. Oakland's solution, the 911 officials say, will be that, starting at 11:50pm or so, all not-yet-dealt-with calls will be transferred to a different phone system to ensure that they don't get lost. Dispatchers can then continue dealing with existing emergencies while newer calls queue up normally until dispatchers again become available. (The moral? It's probably best /not/ to have an emergency in Oakland during those last few minutes before midnight...) >===== My first impression was that this was a terribly embarrassing oversight, for this problem not to have been "fixed" months ago. Date-stamps being processed backwards is /exactly/ the textbook example of what happens when the year field overflows. On the other hand, it /does/ seem the problem will be terribly short-lived, affecting maybe five or ten minutes' worth of calls -- ever. After 12:10am or so, then, and for the remainder of the next century, the original call prioritization algorithms should continue to work just fine. Whereas re-opening the program source, rejiggering the code, augmenting the data structures and so forth could quite plausibly introduce new problems and incompatibilities that might bedevil emergency call processing for months. Leading one to wonder: was this just an embarrassing oversight? Or a deliberate, rational cost-benefit decision to leave sleeping codes lay? --John Wharton [Note added later in Dave Farber's IP from John: (If) unchecked, this WOULD have been a most-life-threatening oversight.]
Paris Clock: Year Display : 19100
The glaring sign of a Microsoft operating system behind the wheels. Morons...
:) ttt
Indianapolis television stations are advising if you got a new driver's license this week, you must return to the issuing office of the Bureau of Motor Vehicles since the expiration dates are wrong. Bureau of Motor Vehicles said it might be a Y2K problem.
bump
bump
Prism,
Can you provide any more details, such as newspaper reports, etc.
Thanks for the report.
You can e-mail the "update" directly to coggeshall@iol15.com .
Patton-at-Bastogne
Good Morning! bump
REPORT: My 486 compaq rolled over to y2k no problemo, am on inet using AOL 4.0. Roger, out.
From front page of quote.com:
Attention Futures Traders: Futures contracts with a delivery month in the year 2000 are updating under a temporary symbol indicating an expiration in the year 2010. For example: SP00H in now updating under the symbol SP10H. We are working to fix the problem and will keep you updated on our progress.
Richmond, VA (USA) -- Problem with: flashlights (lasted more than 24 hours)
Lihue, Hawaii (USA) -- Problem with: flashlights (lasted more than 24 hours)
Still having to deal with those nasty flashlight problems in VA and HI. Oh my, what will we do? </sarcasm>
This isn't directly related to Y2K, but can any of you techies tell me why my connection to FR keeps timing out in San Francisco?
over a maximum of 30 hops:
1 <10 ms 10 ms <10 ms 209.137.81.193
2 20 ms 20 ms 20 ms [209.137.81.225]
3 10 ms 20 ms 20 ms [209.4.197.1]
4 20 ms 20 ms 20 ms [209.137.54.65]
5 30 ms 30 ms 40 ms 206.72.129.1
6 30 ms 40 ms 30 ms atl1-core4-fa0-0-0.atlas.digex.net [165.117.61.18]
7 41 ms 40 ms 30 ms atl1-core2-pos1-1.atlas.digex.net [165.117.60.161]
8 50 ms 50 ms 50 ms dfw3-core2-pos2-0.atlas.digex.net [165.117.52.62]
9 50 ms 60 ms 60 ms dfw2-core1-s2-1-0.atlas.digex.net [165.117.51.113]
10 50 ms 50 ms 61 ms dfw2-core2-fa5-1-0.atlas.digex.net [165.117.52.102]
11 50 ms 50 ms 60 ms intermedia.cw.net [165.117.59.14]
12 50 ms 60 ms 50 ms corerouter2.dallas.cw.net [204.70.9.150]
13 90 ms 90 ms 91 ms corerouter1.sanfrancisco.cw.net [204.70.9.131]
14 150 ms 90 ms 110 ms bordercore2.sanfrancisco.cw.net [166.48.14.1]
15 110 ms 90 ms 100 ms media-city-world.sanfrancisco.cw.net [166.48.15.250]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * *
Toaster - your toast!
Paris Clock: Year Display : 19100. The glaring sign of a Microsoft operating system behind the wheels. Morons...
Firstly, the Paris Eiffel Tower clock didn't display "19100". It froze a few minutes before midnight.
Secondly, it wasn't being run by a MS operating system. It was keyed to the atomic clock in Greenwich England.
Thirdly, "Morons" don't check their facts.
Here are a few things that may not be coincidental: two trains ran head-on in Norway. I heard that was unusual and unexpected for their rail system. It was predicted that embedded chips might fail and allow trains to run in opposite directions on the same tracks, since they control switches, though that seems not to have happened in the U.S.
Also heard from a vendor that a good customer's credit card would not verify on a mail order, although he knows it should. Another friend had his credit card account cancelled temporarily after Christmas, similarly to the problems experienced in England. It was reinstated in a few days.
It's doubtful that any Y2K failures will be reported as such, if they are even known.
>>>> Also heard from a vendor that a good customer's credit card would not verify on a mail order, although he knows it should. Another friend had his credit card account cancelled temporarily after Christmas, similarly to the problems experienced in England. It was reinstated in a few days. <<<<<
All of the above has happened to me from time to time with NO relationship to Y2K. At any given time, I suspect that there are myriad glitches going on in credit verification systems, many of which have to do with "GIGO" problems, not Y2K. After reading the entire list of alleged Y2K problems on this thread, I'd bet that some, or even many, are not related after all. I am not denying that Y2K problems exist, but there seems to be a need to vindicate the dire predictions by blaming all problems on the millenium bug.
BTTT.
FOR WHAT IT'S WORTH DEPARTMENT:
Plenty of 2000 date issues in a certain business park. Letters dated wrong, files being date stamped wrong. Lots of itty bitty problems.
Hope they are resolved before it starts to snowball.
I live in Santa Monica and experienced no electrical interruptions.
Jump
to Updated Thread
to
Free Republic's Y2K Watch :
7-Jan-2000
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.
[
Top
|
Latest Posts
|
Latest Articles
|
Self Search
|
Add Bookmark
|
Post
|
Abuse
|
Help!
]
FreeRepublic , LLC, PO BOX 9771, FRESNO, CA 93794 Forum Version 2.0a Copyright © 1999 Free Republic, LLC |