[Coco] Y2K fixes ever developed or posted?

[jdaggett at gate.net]

That is a work around the problem RTC chips had for not storing or 
keeping track of the century digits. Thus it works from 1970 to 2069. 

I think by then most of us will not care if it works after that.


james
 
On 14 Dec 2003 at 14:03, Dave Kelly wrote:

> 
> ----- Original Message -----
> From: "Theodore (Alex) Evans" <alxevans at concentric.net>
> > > Microware did not fix the Y2K problem in OS9 until version 3.1 or
> > > 3.2.
> >
> > In reality, the OS itself doesn't have a problem with y2k, though
> > most utilities which use the date do.  OS9 uses a single byte for
> > the year with the epoch being 1900, the year 2003 being represented
> > by the value 103 or 0x67.  Unfortunately the date command only
> > accepts two digit decimal dates.  Some commands will end up printing
> > the year as 103, some as 67, and some as 19103.  On top of that the
> > support for many clock chips do have y2k problems.
> What was told to me:
> Microware installed another routine that check the 2 digit year and if
> it was less than 70, printed the date as 20??.
> 
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco