Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!agate!eris!bryce
From: bryce@eris (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Re: Reading the Spirit 1.5 MB clock ...
Message-ID: <7585@agate.BERKELEY.EDU>
Date: 11 Mar 88 04:58:24 GMT
References: <3518@watcgl.waterloo.edu>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 17
Keywords: bugs, memory, clock

In article <> bmacintyre@watsol.waterloo.edu (Blair MacIntyre) writes:
>
>Whenever I read the internal clock, it is one day fast.... 
>
>So, I believe, the problem is in the readclock program....

I tried it again, and can find no bug.  If there was one, I should be able
to find it.  After all, I wrote both readclock and setclock.

Either you have bad hardware, software or procedure.

Also, remember, this is a leap-year.  If software was bad, it would be
off by one day *until* Feb 29.  Sun had a problem along these lines :-).

|\_/|  . ACK!, NAK!, EOT!, SOH!
{O_o} .     Bryce Nesbitt
 (")        BIX: mleeds (temporarily)
  U	    USENET: bryce@eris.berkeley.EDU -or- ucbvax!eris!bryce