Check This Outgreenspun.com : LUSENET : TimeBomb 2000 (Y2000) : One Thread
Sorry-i'm in major rush at work....Later
-- Mike Lang (firstname.lastname@example.org), January 05, 1999
Thanks, Mike! How validating when one of our YourDoneIte tipsters gets backed up in a big news article. We're on top of it, guys!
xxxxxxx xxxxxxx xxxxxxx
-- Leska (email@example.com), January 05, 1999.
Mike, Does not seem to be working at 1:48 P.M.
-- flierdude (firstname.lastname@example.org), January 05, 1999.
Interesting... Officials deny it was related to Y2K, yet it struck at precisely midnight on New Year's Day?! Hmmmmmmm.
-- Steve Hartsman (email@example.com), January 05, 1999.
I believe it said midnight 12/31...not New Year's Day. As far as being Y2K related I can see why it wasn't. The expiration date could have been any date, not just 12/31 "00:00". I think the issue was why some computers didn't automatically update the expiration to 12/31/99. Probably human error...someone typed in 98 instead of 99. Heck, I'm still writing "98" on my checks, and will probably do so 'til February.
-- I (I@I.I), January 05, 1999.
Okay, so "it's not related to the millemium bug". It's just a practice run so they know what the Y2K type problems are going to look and feel like.
Be prepared. Isn't that the motto? These guys are actually testing to be sure they can respond to failure. We ought to congratulate them.
-- Robert A. Cook, P.E. (Kennesaw GA) (firstname.lastname@example.org), January 05, 1999.
Ahhh....Refreshing to see 'real' y2k discussion going on in here anyhow. Been gone a week and WOW cant believe teh bs that has no y2k meaning at all...think i'll venture on into some other new answer forums and see 'IF' y2k is being talked about. What happened while I was gone ????? Alot of flaming and nonsense going on now. NOW is WHEN we all should be exchanging info, not fighting.
-- consumer (email@example.com), January 06, 1999.