On 7 Jan 2000 07:41:07 -0800, [EMAIL PROTECTED] (Bob Hayden)
wrote:
...
> Another tests and measurement issue -- I heard one report on a talk
> show that one facility found all its computers reading 4 JA 1980 on
> New Year's Day. A y2k bug? Not exactly. I noted that one of the
> test programs I used left the system clock set wrong. How wrong?
> Well, if you did not notice the problem, then on New Years's Day the
> clock would have read 4 JA 1980. I suspect this problem was caused by
> the test program, not by a y2k bug!
By the way, if anyone is interested, something like that is what
corresponds to an internal date of "0".
Once-upon-a-time,
January, 1980 dates were not uncommon on files of shareware. I am
thinking of what I saw, back in my old, DOS days. For whatever
reason, stuff had been created without a date.
--
Rich Ulrich, [EMAIL PROTECTED]
http://www.pitt.edu/~wpilib/index.html
