23 Oct
1998
23 Oct
'98
3:44 a.m.
Date: Thu, 22 Oct 1998 16:51:25 -0400 (EDT)
Reply-to: classiccmp(a)u.washington.edu
From: John Ruschmeyer <jruschme(a)exit109.com>
To: "Discussion re-collecting of classic computers"
<classiccmp(a)u.washington.edu>
Subject: Re: Y2K and immortal executables
Snip!
The root cause has been traced to unbuffered real-time
clock chips. On
a system with such a chip, the BIOS may attempt to read some data during
a time when it is being updated and during which a flag value is present,
instead of a real date. It only seems to occur post-1/1/2000 because the
longer code path taken to calculate the Y2K date may take longer than the
grace period the clock chip provides prior to an update.
Messy stuff...
Yeah! Y2K is messy! Is that unbuffered part is because of low
quality and cost cutting condition? What can I identify that by look
on boards or by software?
Jason D.
<<<John>>>
email: jpero(a)cgocable.net
Pero, Jason D.