Path: utzoo!mnetor!uunet!husc6!ut-sally!joe
From: joe@ut-sally.UUCP (Joe Hitchens)
Newsgroups: comp.sys.amiga
Subject: Re: Spirit Technologies (Formerly: internal RAM expansion)
Message-ID: <10033@ut-sally.UUCP>
Date: 9 Jan 88 17:42:38 GMT
References: <378@boole.acc.virginia.edu> <10001@ut-sally.UUCP> <2903@drivax.UUCP>
Reply-To: joe@ut-sally.UUCP (Joe Hitchens)
Distribution: na
Organization: University of Texas at Austin
Lines: 18

In article <2903@drivax.UUCP> davison@drivax.UUCP (Wayne Davison) writes:
>The "ReadClock" software supplied with my board began setting the Amiga's date
>one day too far starting with the new year.  Though the program displays, say,
>"01/01/88", it sets the OS clock to "01/02/88".  To get around this, I have
>set the date back a day, and now use "Date" in my startup to display the date
>as the Amiga sees it.  I think I'll write my own version of read/setclock soon
>just for kicks.
>

Yeah, strange isn't it?  Mine does the same thing.  When I first got it,
I set the date and it seemed to work fine.  I must not have been paying 
attention.
Then, later I kept noticing that the date didn't seem right, like it was a day
off.  So I would think, "Well, I must have given it the wrong date".
I did that twice before really checking.
Sure enough, you tell it today is the 1st, and it sets the clock to the 2nd.
Strange.
j.h.