Re: Y2K

["Christian T. Steigies" <cts@nikocity.de>]

Hi
On Sat, Jan 08, 2000 at 12:46:11PM +0800, Aller Persson wrote:
> 
> It was me that asked for some hint about this hwclock problem. I got a lot 
> of hint from Christian, so now can I add some myself. Or is it waist of 
> time maybe every Linux-running Amiga owner have already solved the problem?
I dont think so, so please go ahead, looks great!

> Waiting in loop for time from KDGHWCLK to change
> ...got clock tick
> Time read from Hardware Clock: 11:53:27
> Invalid values in hardware clock:  0/01/08 11:53:27
> 
> This is saying me that it must be something with Amiga-DOS "setclock" that 
> only put in one digit in the year. Because hwclock will run OK if I set the 
> ate and time with hwclock and not with Amiga WB-Prefs or AmigaShell Date.
> I also changed to year 2010 with Amiga WB-Prefs and the problem was gone.
> 
> Now is my question: Is this really a problem with hwclock? 
> I do not think so, but I am not any specialist of any sort so I can not say. 
> Is it not mktime() that will be confused to only see one digit in the year?
> I leave this to you who knows better than me.
Excellent deduction! From my fast reading over this, I can spot no errors
and all sounds very reasonable. Im not an AOS expert, but I think you should
post this to the new owners of Amiga or to c.s.a.programmers/hardware or
something. Maybe somebody can make a new setclock for AmigaOS 3.1 (did any
of you really waste his money on 3.5? Oups, thats politic, sorry..)
Other option (have to reread your mail again, Im in a hurry, as usual...)
if hwclock recognized one digit years as valid years, everything would be
fine as well?
Maybe I will check that out, but perhaps you allready have a patch ready?

You do not by chance use this AOS programm from Geert which allows you run
run your clock in GMT but still have correct local times? (I mentioned it in
the install guide I think).
-- 
Christian