> > 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,
I'll defer to a couple of URLs as I'm still trying to understand this all
myself...
How TD Occurs on Personal Computers:
http://www.nethawk.com/~jcrouch/second.htm
My main TD web wite:
http://www.nethawk.com/~jcrouch/dilation.htm
Mike Echlin's main TD web site:
http://www.intranet.ca/~mike.echlin/bestif/index.htm
And for people who missed the beginning of all this last August:
http://www.nethawk.com/~jcrouch/td01.txt
<<<John>>>
Received on Tue Oct 27 1998 - 11:27:31 GMT