[Coco] Y2K fixes ever developed or posted?

Arthur Flexser flexser at fiu.edu
Mon Dec 15 03:04:27 EST 2003


On Sun, 14 Dec 2003, Gene Heskett wrote:

> On Sunday 14 December 2003 17:26, Arthur Flexser wrote:
> >On Sun, 14 Dec 2003, Gene Heskett wrote:
> >> Of the ones I played with, the dallas semi and the mm6242, neither
> >> of these clocks can handle the rollover at 99>100.  The dallas
> >> semi used in the B&B XT-RTC did take the rollover, but then failed
> >> on the next minute IIRC, apparently stopping completely.  The
> >> mm6242 apparently threw away any effect of the rollover and
> >> continued on its merry way thinking it was now the year 1900.  I
> >> don't recall if I ever published the dallas semi clock in any
> >> event as it has other, far more pressing problems that would
> >> prevent its use by me in any design I would ever have
> >> contemplated.
> >
> >The Dallas Semi clock, the SmartWatch, keeps only a 2-digit year,
> > and has no hardware problem with the rollover.  Any particular
> > driver for it may, of course, have software problems.
> >
> >Art
> 
> That may be, but I'm not sure if the dallas semi used in the B&B was a 
> "smartwatch".  It was never called that by Chris that I know of.  And 
> it did, or at least the one I had, did have problems with the 
> rollover.
> 

It may not have been called SmartWatch by Dallas Semi, but it was
functionally identical, and could be read or set by the identical
software.  Maybe the only chips actually called SmartWatch were the ones
you could piggypack a ROM on top of.  But, the B&B version was basically
the same thing.

Art





More information about the Coco mailing list