Y2K Redux, copyleft Peter G. Neumann, January 2020 I pulled together a historical list of Y2K-related problems, after a request from Eric Hofnagel. It is now on my website at http://www.csl.sri.com/neumann/neumann.html and directly accessible at http://www.csl.sri.com/neumann/y2k-pgn.txt PGN] Peter G. Neumann Chief Scientist Computer Science Lab SRI International EL-243 333 Ravenswood Ave Menlo Park CA 94025-3493 Work 1-650-859-2375 Cell 1-650-804-1802 Neumann@CSL.sri.com or pNeumann@ACM.org for other than SRI business http://www.csl.sri.com/neumann Eric: How early did you realize that Y2K could be a real problem? Were there serious doubts at first? * PGN: 1965. In Multics we realized that COBOL had a Y2K problem, and we addressed it much more generally in the Multics hardware/software by using a microsecond clock that would still not roll over yet today (when Multics exists only in open-source code that runs on various VMs here and there). We had no doubts in 1965 that it would be a problem in 2000, and were surprised that others did not anticipate it more systemically. However, Multics also solved the buffer-overflow problem (in hardware and software) in 1965, which even ten years ago was perhaps the biggest source of security flaws. Multics also addressed the direct-memory access security problem, as we noted in a recent paper showing that problem is still rampant: http://thunderclap.io/thunderclap-paper-ndss2019.pdf http://thunderclap.io https://www.cam.ac.uk/research/news/most-laptops-vulnerable-to-attack-via-peripheral-devices-say-researchers https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/ * PGN: I was on the GAO Executive Council on Informatation Management and Technology, beginning in 1997. The GAO was just beginning a quarterly scorecard of every U.S. Government agency/organization's status with respect to Y2K remediation. The GAO and our ECIMT group were tracking this in each of our usually twice-yearly meetings. The general lack of awareness by many government sectors was horrendous. DoD usually received a score of F or D- even up to the last quarter. Eric: Can you explain the origins of Y2K? I believe it has something to do with the technological limitations of the first computers. * PGN: COBOL used two-digit years. Lots of critical systems used COBOL. That's just one example. Eric: For its January 18, 1999 issue, *Time* magazine rang in the year with the words ``The End of the World!?!'' on its cover, with a story about the Y2K crisis. Was this, in your opinion, overly alarmist? * PGN: Typical hype attributable to journalism and selling the magazine. Eric: Lots of people prepared by hoarding food and cash. And some publications offered *Y2K Checklists*, which advised people to prepare for the Y2K bug by stocking up on medicine, cash, and paper financial records. Was this an over-reaction? * PGN: That was overkill. But there were many problems before and after 1 Jan 2000. See below. Eric: Some in the media called the whole thing a hoax or a non-problem that we probably never needed to worry about in the first place. How were they wrong? Was the media just embarrassed that a real "doomsday" didn't occur, and it made them seem foolish? * PGN: They were wrong. Many critical systems would have failed on 1/1/2000 had they not been remediated. Eric: Do you have any personal stories about living through Y2K fever in 1999? Like a client who asked your advice on a particularly crazy Y2K "danger"? Or friends or relatives asking you to "fix" their computing systems? I'm looking to show the human side of Y2K preparations. * PGN: My mail system had the Y2K problem with two-digit years. A fix was presented, and that failed on 1/1/2001, because it was a short-sighted temporary fix. Eric: In hindsight, what was done wrong in fixing the bug? Or to put it another way, what safeguards were put in place that really made no difference? And what ultimately stopped it from happening? * PGN: Except for Multics, an almost total lack of foresight until it was almost too late for many organizations. ============================================================ Here's PGN's list ..... in three sections, BEFORE, DURING, and AFTER. .... Y2K Manifestations: approaching 1/1/00 Here are some items from my Illustrative Risks document http://www.csl.sri.com/neumann/illustrative.html, which explains the coded prefixes: $rfed Many of the following Y2K problems are the result of decades of collossal short-sightedness, in requirements specification in the first place, as well as throughout the development process. Note that in 1965 the Multics development effort recognized the 35-year-away Y2K problem and addressed it quite constructively, using a 71-bit date-time field lasting long after Y2K. The costs are staggering. The lessons that should be learned from this experience are profound. It is not just the Y2K remediation that is relevant - it is the entire software development process. [I have not even bothered to insert the new "r" descriptor in those cases below in which faulty requirements are obviously implicated!] f Discussion of date and century roll-over problems: Fujitsu SRS-1050 ISDN display phones fail on two-digit month (10); 1401 one-character year field; COBOL improvements; IBM 360 (S 20 2:13) f Year 2000? Don't forget 1752 and 30 February 1712; two references (S 20 5:11) $f Estimated costs of 1999-to-2000 date fix (S 21 2:16) $f When the Clock Strikes 2000: U.S. Fed Govt cost $30 billion? Only 70% to be fixed in time? (S 21 5:18) f$ More Y2K problems: Visa credit-card expiration-date problem and legal liabilities (R 18 63,74,75) $ Lawyers look forward to the year 2000 (S 22 2:23) f$$ Lots more on Y2K (R 18 74-80,82,83-84,87-88), including the unforesightful use of "12/99" as an out-of-band date flag (R 18 88); more on Y2K and other date/calendar/daylight arithmetic problems (R 19 02,03,06,08-12); costs to reprogram in UK (R 19 07); Y2K cost estimates worldwide now up to $600 billion (R 19 10) Vf More on Y2K: sliding window approach, year-2069 problem (R 19 13); (R 19 14) $f Y2K problem blocks UK divorcing couples from splitting pensions (S 22 1:19) ? Millenium fears lead to Virgin Birth insurance policies (in addition to alien impregnation policies) (S 22 1:19) SH Nasty scam exploiting Y2K authorization expirations (R 18 68) fde Y2K: Tcl 8.0 bytecode compiler Y2K risks; 00-38 now 2000-2038 (R 19 35-37); Y2K and C (R 19 37-38,40); non-Y2K problems with Java Date classes (R 19 38) Vfe DoD Global Command and Control System (GCCS) fails Y2K test (R 19 38) $ Y2K lawsuit: Produce Palace International sues Tec-America (R 19 29) - American Megatrends: "Year 2000 compliance means that the internal BIOS date and time clock will continue above the date 1999. It will not reset itself after 1999 to the date of 1980. It will continue to the date of 2099 before resetting to 1980." (R 19 60) H Y2K spam scam: jobs offered with no experience required (R 19 46) - Ottawa firm registers "Y2K" as trademark (R 19 47) f Freecell degenerates on erroneous date: Y2K and random numbers (R 19 48) f Potential risks of backup and recovery after Y2K (R 19 55) Vf PDP-11 Y2K leap-year bug with German clock board (R 19 56) f Risks of testing Y2K by setting clocks ahead (R 19 56) fe IRS Y2K fix threatens 1,000 taxpayers erroneously; IRS needs to check at least 62M lines of source code for Y2K (R 19 57) $f More on Y2K lawsuits: North Carolina contemplating suing computer industry (R 19 57); California legislation proposed to limit Y2K liability (R 19 59) f Canned-goods rejected with Y2K expiration dates (R 19 47,48) f Miniature Enthusiasts with Y2K expiration dates deleted from address DB (R 19 57) f Canadian guaranteed investment certificates with Y2K maturity vanish from DB (R 19 58) e Euro changeover makes Y2K bug look easy! (S 23 4:23, R 19 69) fh Gore congratulates 71-year-old Senator on birth of twins (S 23 4:23, R 19 64) $ffffe... As of March 1998, only 35% of Federal Agency computer systems checked for Y2K compliance, 3,500 systems remain (R 19 64); IRS to spend $1B (R 19 68); Effects on the aviation industry (R 19 64); Financial risks (R 19 69); Y2K in Britain (R 19 64); Y2K in China (R 19 65); Australian simulated results of effects on public health and public infrastructure (R 19 71) f Testing bugs that result from trying to test Y2K compliance, particularly when setting dates back to their correct value! (R 19 71) f Report that only 1/3 of popular Microsoft apps are Y2K compliant (R 19 68) with further clarifications (R 19 69-70) // f Leap years: MS Excel 6.0 Office 95 version and 7.0 Office 97 version believe 1900 is a leap year (R 19 64) Vf Summer time: in Britain (R 19 64), voicemail backup system fails (R 19 67); in Germany, Deutsche Telekom adjusted clocks twice in Lübeck (R 19 65) f Year 2100 problems (AMI BIOS, R 19 60), IBM PCs and Network Time Protocol balk at 2100-Feb-29 (R 19 61,62); ? Fable of Y2K and 1979 Toyotas: shutdown if 00 in year field? (R 19 69,71); Computer insists on cataloguing Chateau Margaux 1900 as Ch. Margaux 2000 (R 19 67); Y2K and tombstones (R 19 61); Eagle Talons alleged Y2K problem (R 19 68) bogus (R 19 69) - Need for contingency plans, not just questionable remediation (R 19 85,88-89) fh$, etc. CIA worries about Y2K as an opportunity for hostile intent (R 19 84); Senate considers need for martial law after Y2K breakdowns (R 19 78); Potential Y2K railroad problems, with no more manual backups (R 19 84); Y2K risks to world shipping (R 19 82); Senate Y2K committee suspects power grid could collapse (R 19 82); Wells Fargo study shows millions of small firms at risk (R 19 77); Y2K insurance and financial risks (R 19 79); Swedish corporate insurance explicitly excludes Y2K (R 19 78); Y2K problem in Swedish personal identification numbers (R 19 74); Microsoft Y2K (non)compliance; Excel believes in 29 Feb 2000 and 29 Feb 1900, for Lotus 1-2-3 compatibility (R 19 73); More on Y2K forced-upgrade strategies (R 19 73); 102-yr old gets a birthday card for 2-yr olds (R 19 73) f$ SIR-C processor Y2K problem in shuttle imaging (R 19 81) and its economic implications (R 19 83) - Y2K priorities delayed security upgrades at bombed U.S. embassies (R 19 93) *$fd UK Railtrack (former BritishRail) has no safety-critical computer systems, because of past underfunding! Y2K preparations simplified by delaying upgrades! (R 19 90); UK Railtrack online timetable information has errors for holiday weekend schedules Xmas 1999 and NewYear 2000 (R 20 67); Railtrack running a year behind and £3 billion over budget in rebuilding London-Glasgow line, with workers being sent to Army training for discipline! (R 20 84) f Sloppy date handling in Perl scripts (R 19 88) + Wall Street test simulation gives good marks to 29 brokerage firms (R 19 89) $ No UK Y2K insurance for household electrical items (R 19 89); Canadian insurance not likely to pay off; also another 100+ year anomaly, from Rob Slade! (R 20 03) + Canadian RCMP blocks vacations to ensure Y2K emergency coverage (R 20 02); Wisconsin National Guard mobilizing (R 20 03) - White House calm, DoD nervous about Y2K (R 19 90) f Win98 date problem detected (R 19 91); occurs in 5-second window when booting around midnight (R 19 92) Sf Internet Explorer 4.0 instructions on how to bypass firewalls! (R 20 01-02) fe IE2 cannot read www.microsoft.com for upgrade (R 20 55) f Y2K risk in Javascript cookies despite 4-digit standard (R 20 01) Vf Consignment of corned beef with intended expiry 2001 rejected as too old: appears as 1901 (R 19 92); cf. the leap-day Xtra supermarket meat problem, below! (There's more than meats the eye.) $SPH Business Software Alliance finds 1400 unlicensed software copies in Los Angeles Unified School District, valued at $5M? (R 19 92) $ Clothing retailer sues for cost of non-Y2K-compliant 1991 system (R 19 94) Vf$ Product Palace settles with Tec America over Y2K-noncompliant software: entire system crashed on single 00 credit-card (R 19 96) fe Saga of another Y2K bug, after being "fixed", a letter dated 3 Aug 2098 sent mistakenly to half-million recipients (R 19 95) + Y2K problem resolved that had threatened the production of scotch whiskey (R 20 03) f New Vancouver Hospital pathology system default misses updates to patient files for many months (R 20 23); CORRECTION (R 20 30) - 400-year-old time machine (in Liverpool museum) to suffer from millennium bug: time runs out at year 2000! (R 19 79,81) + Memo on Y to K conversion: Januark, Februark, ... (S 20 23:, R 20 21) *$ Y2K-related panic may be more serious than Y2K computer problems (R 20 11) fH DoD Special Weapons Agency falsely claimed successful Y2K tests on 3 or 5 critical systems (R 20 10) $(f?) Hospital spends $700K on new digital nuclear medicine machine because vendor would not certify Y2K compliance of well functioning analog machine (R 20 10) *f UK MoD admitted that Rapier anti-aircraft missile was not Y2K compliant (R 20 13) $f 1 Jan 1999: Y2K hits Singapore and Swedish taxi meters (R 20 15) f Windows/Visual C++ daylight saving cutover one week early on 1 Apr 2001 (no fooling!), affecting 95,98,NT (R 20 15-16) ef Enator AdeEko Y2K update turns Malmo Sweden seriously disrupts city's bill paying (R 20 18) +? China contemplating making all airline executives fly on Y2K boundary (R 20 17) fm Store Baelt Bridge not Y2K-safe (R 20 22-23) h 2,000 Texans get false overdraft notes from Bank One in Y2K test (R 20 13) h Y2K "fix" test results in traffic offenses dated 2097 (R 20 21) $h PSE&G Y2K test of billing program results in false billing (R 20 23) - As of early 1999, GAO report says U.S. states lagging in Y2K readiness (R 20 20); CIA predicts serious Y2K problems around the globe (R 20 23) *h VPA's Peach Bottom nuclear-power Y2K-check crashed monitoring systems (R 20 24) fh Boston bank's Y2K problems blamed on IE5, but apparently not! (R 20 25) +? Sri Lankan Banks to close on 31 Dec 1999 for Y2K tests (R 20 25) SH Scam using Y2K bank problems as bait eh Pilgrim nuclear plant Y2K readiness questioned by NucRegComm (R 20 40) + Standards needed now for Y10K? (not April Foolery) (R 20 30) f Nottingham weather images dated "FEB 28 2000, 2330" and "FEB 28 2000, 2400": Y2K leap-testing? (R 20 42) Vf Y2K test knocks out Fiji's telecommunications (R 20 43) f Downloading Y2K fixes to Internet Explorer leads to clock problem (R 20 42) *f Y2K test sends sewage flowing in Los Angeles (R 20 46) S Another Y2K scam (R 20 51) Vfe* London Electricity Y2K upgrade left 2000 customers without power for days (R 20 54) +P Canadian govt recommends encrypted e-mail (R 20 54) ? Y2K in China (R 20 55); Indonesia: wait to see what happens in New Zealand and fix it quickly (R 20 58); Iraq decides to wait and see on Y2K oil disruption; concerns that oil nations are not ready (R 20 62) f$ Northwest Metrology stung by Y2K bug (R 20 56) f? Unix needs 10th decimal digit for timestamp on 9 Sep 2001; risks of format problems? (R 20 58) f Unix billion-seconds hits medical archiving application fixed-length label (R 21 69) f Bank switch to 4-digit years blows up on 1 Oct 1999, with 10/01/1999 truncated to 0/01/1999 (R 20 59) SHf FBI warns some Y2K fixes may be suspect (R 20 61); general concerns over Trojan horses in Y2K-remediated code fe NT, SP5, SP6 Y2K problems (R 20 62) f Maine year-2000 vehicles classified as "horseless carriages" from 1900 (R 20 63-65) f Cornell University registration system welcomes students to the spring 1900 semester (R 20 64) $? Businesses could owe millions for Y2K sliding-window fix if 1998 patent holds up, despite this being an old technique (used at least in the 1960s) (R 20 65) $ Microsoft Y2K liability claim: "... Microsoft does not warrant or make any representations regarding the use or the results of the use of any Microsoft Year 2000 statement in terms of its correctness, accuracy, reliability, or otherwise." (R 20 65) $efh Irish telephone network upgrade failed, backup failed, caused domino propagation in Dublin; independent cell-phone system failure; outage brings Y2K fears of lack of disaster recovery (R 20 66-67) efh $.5M fire-station fire blamed on Y2K computer fix; breaker disabled due to Y2K incompatibility (R 20 66) efh IEEE standard Y2K compliance attained by rendering software unusable (R 20 67) SH Flagrant antisocial behavior of Y2K virus competitions promotions (R 20 68) SH Y2K-related viruses: Worm.Mypic (R 2067), W95.Babylonia and others (R 20 69) fm Y2K test takes out all power in German Department of Justice, 11 Dec 1999 (R 20 69) $H Y2K fears lead Philippine man to withdraw his life savings, then robbed of everything (R 20 69) fff Australian Y2K readiness news page clock sticks at 31 Dec 1999 23:56:15, then 15 Dec 1999 00:23; New Zealand airport Web site update time-stamped 1 Jan 100; in Y2K test, Henderson NZ clock flashed "GAME OVER" at midnight; 20,000 UK credit-card machines incapable of coping four days before Y2K, with settlement date in 2000; Pentagon DefenseLINK Y2K info site accidentally disabled; Oakland CA 911 system not Y2K compliant, prioritizes earliest calls (seemingly from 1900); glitch with NIST's Automated Computer Time Service; Wells Fargo CD renewal notices dated 1900; many digital certificates expire with Y2K because old browsers could not accept 2000; date field called Shirley harder to detect; risks of last-minute FAA HOCSR patch ..... Y2K and Similar Manifestations: on and after 1/1/00 f,h,e Y2K dates: Numerous cases of 1 Jan 100, 1 Jan 19100, Jan 1 2100. An Australian online media news gateway had 3 Jan 3900 on 2 Jan 2000, while appple.com and happypuppy.com should get a prize for year 20100, which beat out the U.S. Naval Observatory calendar with the year 19,000 and others with 19100. Amazon announced a Sonic Youth CD would be available on 10 Oct 2011. Startrekcontinuum.com noted the next Voyager episode would air on 1 Jan 1900. *The New York Times* Website said 1 Jan 1900. Compaq sites said it was 2 Jan on 1 Jan. Several counts of time until Y2K went negative in funny ways. An old 486 PC reset its clock to 4 Jan 1980. The atomic clock at UK's NPL read 31 Dec 1999 27:39 UTC at 2:39am GMT (off by an hour, at that). Various Web sites were hacked. www.2600.com had a humorous spoof. Toronto abandoned its on-line bus information service at midnight because it was not Y2K compliant. (R 20 72) feh A Pentagon computer system processing satellite intelligence data lost its capabilities at midnight GMT, for 2.5 hours, due to preventive human mistake (R 20 72); data from 5 satellites was reduced to a trickle for several days (R 20 75) f Automated New Zealand radio station repeats 31 Dec 1999 11pm news hourly, due to 99 > 00; Nokia phone not Y2K compliant?; effects on mobile and phone nets; more on cost of Y2K fixes vs. preventive measures; Filemaker Pro; Word Perfect 5.1 and medical transcription; lots more on bad arithmetic date programs, including Javascript problem; X-10 controller; New York Times correcting 102-year-old issue number glitch; nuclear-power glitches; Win95 Y2K bug?; California DMV snafu; ftp date problems; Talking Clock; count-down to Y2K programs go negative (R 20 73) f Y2K: repeated billings result from uninstalled fix; Bills for 100 years back interest; Sprint PCS network problems at Y2K; MKS Toolkit Y2K glitch: next backup 9 Jun 2005!; Barbara's Cereal expires July 1900; driver's license expires in year 1000!; NTSB website has Y2K test data mixed in with real data; Bogus message in live service for Quicken 2000; With stepped-up Y2K wariness, NAI WebShield blocks RISKS issues (R 20 74) f Newborn Y2K baby birth certificates dated 1900 (R 20 76); Satellite orbit predictor software fails (R 20 76); Flight Sim 2000 Professional Edition (R 20 76); abcnews.com continued copyright year of 1999 (R 20 78) $f New Y2K Tulsa County Court computer system fails for weeks thereafter (R 20 81) $f Nevada man registered his car late, billed for $378,426.25, accrued interest since 1900 (R 20 84) f Commentary on Lessons of Y2K by Toby Gottfried (S 25 3:18-19, R 20 77) *fm Berlin Fire Department dispatching system Y2K problem (R 20 75) also a Leap-Day problem; caused by faulty network cards (R 20 82) Y2K bug as well? (R 20 84); Yes, Y2K fix failed: date incompatibilities because of leading zeros (R 20 93; S 26 1:19-20) f Fax driver/app "Delrina WinFax Lite 3.0 Fax Administrator" can't recognize years 00 to 09 as the send date; Starfish Sidekick98 Y2K bug; Kremlin press office cannot send e-mail after Y2K (R 20 75) f Yet another Y2K bug in Jun 2000! (R 20 91) fh 54-week anomaly in American calendars every 18 years (R 21 19), but not in Europe and elsewhere; ISO standard 8601 (R 21 19-21,23); Vf Norwegian trains halted 31 Dec 2000 (R 21 18, S 25 2:11; also R 21 19,21) Vf 7-Eleven unable to process credit cards since 1 Jan 2001 (R 21 18, S 26 2:11) f Y2K+1 bug in Sharp Organizer? (R 21 18 S 25 2:11, also R 19,21,23,25) f In 2001, Oregon's Multnomah County residents summoned for jury duty in 1901 (R 21 20) f Motorola flex page blew 2000 (R 21 09) f Postscript Jan 2001 monthly calendar off by several days (R 21 19) f Millennium clock has a millennium bug (R 21 20) f Y2K-leapyear hangover: CDMA GTE wireless date 31 Jun 00 (R 20 92) American Express bill date confusion beginning Jan 2001: Y2K aftermath (R 21 24,25) Merlin travel-agency system credited Jan 2001 reservations to Jan 2000 accounts, affecting 200 agencies (R 21 25) Extreme Ultraviolet Explorer (EUVE) satellite launched Jun 1992 lived until 31 Jan 2001; planning system failed on 1 Jan 2001 - because the legacy data solar/lunar/planetary ephemeris file extended only to 31 Dec 2000 (R 21 21) Failure to bill pet fees cost Toronto $700,000 in 2000; Y2K problem? (R 21 24) f Y2K flaw blamed for Down's Syndrome test errors; four positives went unnoted (S 27 1:10, R 21 67) $fe Y2K malady lingers on in Brevard County, Florida: cities must repay county over $1M in erroneous disbursements (S 27 3:8, R 22 04) f 1 Jan 2003 Yorkshire Evening Press front page dated 1 Jan 2002: short-sighted hard-coded JavaScript calendar date fails! (R 22 45,51) f? Y2K bug at Macdonalds: July 1903 use-by date on birthday cake (R 22 70) f Y2K still around in 2004: the date on 23 Dec 2004 is "Jeudi 23 décembre 104"; See the ECMAScript and subsequent discussion (R 23 63-64; S 30 2:22-23) fhi Javascript Y2K glitch on 1 Oct 2005: October 1 105 (R 24 06; S 30 6:20) f Year 2106 and 2038 problems in Unix (R 19 15); year 65,536, leap seconds, UTC vs TAI (R 19 16); DEC OpenVMS expired on 19 May 1997 (R 19 18); clock synchronization (R 19 18); Java Y2K problem arises in the year 292271023 (R 19 21) f POSIX time counter expires one bit early on 9 Jan 2004, instead of 2038. breaking Pro/ENGINEER, Pro/INTRALINK, Windchill products (R 23 12; S 29 2:11) fe More calendar arithmetic problems: time_t wrap-around in 2038, (R 23.12-13,16); h Rotorooter schedules advance appointment in new year as an emergency: dispatcher omitted year (R 23 09; S 29 2:11) f OCLC interlibrary loan system rolls over 130th time, record numbers only 6 digits (R 22 95; S 29 2:11) ..... Y2K and Similar Manifestations: on and after 1/1/20 From RISKS-31.54,6 January 2020:: Y2K Strikes Again! Martyn Thomas and PGN (R 31 50,54) This might be a genuine Y2K problem -- are there more? (Martyn Thomas, R 31 50) In the run-up to Y2K, one of the fixes was "windowing", where two-digit years below 20 (for example) were treated as in the 21st century and years above 20 were in the 20th century. There was some speculation that there might be problems when the end of the window arrived. Martyn [Martyn noted a product that was written after 2000, where a pre-2000 library was used. ``If it is a Y2K end-of-window problem, there may be similar problems about to appear.'' SEE BELOW! PGN] People who weren't involved in solving the Y2K problem seem to think is wasn't a serious issue. But it was and despite the billions of dollars spent and the tens of thousands of people who worked to identify and fix the problems, 15 nuclear reactors shut down on January 1st 2000. I led the Y2K service line for Deloitte Consulting for a few years and I have described what really happened. Martyn [Two Y2K+20 problems that resulted from the windowing scheme were noted in the online Risks Forum, RISKS-31.53. PGN] The Ghost of Y2K hits Hamburg DTS trains on 1 Jan 2020; 95 of 120 trains still were not operative on 2 Jan 2020. A ticket purchased on 1 Jan 2020 is not valid until 1 Jan 2040. (R 31 53); Software Glitch Affects 14,000 New York City Parking Meters (R 31 53) A lazy fix 20 years ago means the Y2K bug is taking down computers now (New Scientist via Paul Saffo, R 31 54) I'm sure more will be added later. See http://www.csl.sri.com/neumann/neumann.html and directly accessible at http://www.csl.sri.com/neumann/y2k-pgn.txt PGN