One final Y2K (LYD) Bug to hit embedded systems today. : LUSENET : Grassroots Information Coordination Center (GICC) : One Thread

This A.P. article below mentions the presence of one more Y2K Bug, now at hand; that is more than just a Century Date Bug "spike" date, due to once-a-year type program Y2K bugs manifesting for the first time. The key excerpt cited indicates that this imminent Y2K Bug is a variant of the Leap Year Date Bug. Expect, and be on the lookout for, a fresh wave of refinery, power plant, pipeline, and other such failures soon. These failures will probably be few and scattered, but the U.S. is already "Living On The Edge"; with pre-existing low infrastructure margins of safety, for natural gas in the East and electricity in the West. Hence, this last Y2K L.Y.D.B. could be the "straw that breaks the camel's back", causing infrastructure emergencies in some areas, sending us OVER the Edge. So, Stay Prepared! ---------- Y2K Hubbub Largely Forgotten Another Y2K date is coming on Dec. 31 for computers that calculate dates strictly on the basis of a 365-day calendar. Because 2000 is a leap year, Dec. 31 is Day 366. Major problems, however, are not expected. (copyright, Associated Press)

-- Robert Riggs (, December 30, 2000


URL and/or date for this item? Thanks!

-- Paula Gordon (, December 31, 2000.

Reference URL for Associated Press article commemorating the anniversary of the Y2K "Moment of Truth", briefly mentioning the day365yr00 rolling to day001yr01 (day366yr00 is correct) problem.

. . . . Wait a minute! It gets worse! There's another very overlooked "late breaking" date-related computer Bug ALSO! It isn't a Y2K Bug, its concurrence with the Year 2000 is an unfortunate coincidence. Alas, this is the first year since 1972 (before many computer programs were written) to have 54 fractions of weeks, based on the week starting Sunday. Reference URL:

-- Robert Riggs (, December 31, 2000.

From a previous post.

The Health and Safety Executive says offices closed over the New Year may find a series of problems caused by their computers skipping 31 December and going straight to 1 January.

Confusion over calendar arrangements for leap years means that some software packages do not recognise that 2000 has 366 days. Action 2000 identified 21 packages that could be affected, including Filemaker Pro 3, Windows for Workgroups 3.11 and Outlook 98. in_review_id=347300&in_review_text_id=291640

-- Martin Thompson (, December 31, 2000.

Moderation questions? read the FAQ