[hatari-devel] IKBD clock year

Thomas Huth huth at users.berlios.de
Fri Apr 22 09:49:13 CEST 2011


Am Thu, 21 Apr 2011 00:19:07 +0300
schrieb Eero Tamminen <oak at helsinkinet.fi>:

> On keskiviikko 20 huhtikuu 2011, Thomas Huth wrote:
> > > to see whether it still shows the correct date?
> >
> > I've just checked it ... and yes, at least TOS 2.06 now calculates
> > the year wrongly,
> 
> Without RTC, both TOS 1.6 & TOS 2 seem to get the date wrong, but TOS
> 3 & 4 get it right.

TT and Falcon use the new NVRAM chip for querying the time, not the
IKBD, so they are surely not affected of this function.

> Reverting the BCD calculation fixes the date only for TOS 2, not TOS
> 1.6.

TOS 1.x versions don't query the IKBD at all, they either use the RTC
or they will boot up with a default time.

> With RTC the date is fine also for all TOSes (at least for
> anything with which xcontrol.acc works).

Sure, why should TOS query the IKBD when there is an RTC?

> Btw. Funnily, if I use "--rtc off --machine st", xcontrol.acc bus
> errors on TOS 2 startup.  TOS 2 works fine with "--rtc on --machine
> st" and "--rtc off --machine ste" though.

Works for me ... maybe you got an old version of XCONTROL (I am using
1.31) or a bad CPX installed?

> > new files get the timestamp 2039 instead of 2011.
> 
> File timestamps (at least on GEMDOS HD) were fine, I saw the issue
> only in xcontrol.acc.  What you do to get the timestamps wrong?

Well, of course filestamps on GEMDOS HD are generated by the host, not
by TOS, so they should always be accurate. Try a floppy image!

 Thomas



More information about the hatari-devel mailing list