Ian Dall wrote:
> It looks like we have the Y2K bug.
>=20
> I just happened to be looking through clock.c and noticed:
>=20
> static long
> clk_get_secs()
> {

...=20

>         if (dt.dt_year < 70)
>                 dt.dt_year +=3D 100;

Doesn't this make our problem a Y2k70 problem :-)?

> 1900 was not a leap year but 2000 is. The question is will the clock
> roll over to year 00 (as opposed to doing something completely
> unpredictable) and if it does, will it think it is a leap year? My
> guess is that is is not sophisticated to know about the 100 year and
> 400 year rules for leap years and will happen to get it right!

I'll do a y2k test (and a 27.02.2000 test) with my pc532. But don't
hold your breath, it may take a couple of days.

Matthias
--=20
Matthias Pfaller                            Software Entwicklung
marco Systemanalyse und Entwicklung GmbH    Tel   +49 8131 5161-41
Hans-B=F6ckler-Str. 2, D 85221 Dachau         Fax   +49 8131 5161-66
http://www.marco.de/                        Email leo@dachau.marco.de