Re: Question: How will the Year 2000 bug impact your work?

> There is another very important year 2000 problem that is not in the > above list. > > Most PC's built before this year have a hardware problem (or firmware) > dealing with the year 2000. So no matter what you do to your software, > your PC will roll from 12/31/1999 to 01/01/1980 instead of 01/01/2000. Big deal. You have to set the clock ONCE, and you know years ahead of time that you're going to have to set the clock. Chances are that stupid CMOS battery will die on you between now and the year 2000 anyway, so you'll have to set the clock before then. (Remember digital clocks that don't even HAVE battery backup?) Except for PCs being used to do real-time control, as in air traffic control or nuclear reactors, I see this as a minor annoyance, not a very important problem. And doesn't this only happen if the computer is POWERED OFF during the rollover, which would seem to exclude real-time control systems? Now, if your hardware won't LET you set the date to 01/01/2000, now you've got a serious problem. There are some much older systems that have this problem, but it's not nearly as common as the rollover problem. > There's going to be a shitload of PC's going into dumpsters in January > of 2000. Why is it easier to throw a PC into the dumpster rather than set the darn clock once? Gordon L. Burditt sneaky.lerctr.org!gordon