Re: [hatari-devel] Error in SetClock / ReadClock

[Thomas Huth <th.huth@xxxxxx>]

Am Sat, 22 Dec 2012 16:09:53 +0100
schrieb Nicolas Pomarède <npomarede@xxxxxxxxxxxx>:

> So, would someone object if I changed ikbd.c to behave the same :
>   - check BCD encoding in setclock and store bytes
>   - return BCD bytes in readclock
>   - add an update function (called from the VBL for example) that
> would maintain the ikbd clock by updating it every second (in
> emulation time, not in real system time)
> 
> This means we completly remove OS specific date/time conversions
> (time, localtime, mktime) and all the possible nightmares that go
> with them.

Fine for me - we've had enough trouble with the old way in the past, so
if these changes really ease the situation, please go ahead!

> In that case, the emulated machine would default to 1985 or sthg like 
> that at first boot, which can be annoying when dealing with harddisk 
> mounted on the real filesystem.
> So, we could have an option "init ikbd clock on boot" that would do
> only one localtime() call.

As Eero already mentioned, I also think that the normal RTC should be
enough, no need for an extra option here.

> This way, the machine has a correct date/time at boot, but then it 
> updates independantly of the system (which means if you pause
> emulation for 8 hours in 'Captain Blood' or 'Zombi' for example, you
> don't loose your game when you unpause it)

Ack. I've add the two games now also to the compatibility list so that
we do not forget about them in the future (in case we ever have to do
regression testing in that area again).

 Thomas