Path: utzoo!mnetor!uunet!husc6!hao!noao!stsci!barsh
From: barsh@stsci.EDU (John Barshinger)
Newsgroups: comp.sys.amiga
Subject: Re: Reading the Spirit 1.5 MB clock ...
Message-ID: <263@stsci>
Date: 10 Mar 88 15:20:49 GMT
References: <3518@watcgl.waterloo.edu>
Organization: Space Telescope Science Institute, Baltimore, MD 21218
Lines: 33

in article <3518@watcgl.waterloo.edu>, bmacintyre@watsol.waterloo.edu (Blair MacIntyre) says:
> 
> 
> While e-mailing a reply to someone's query regarding the Spirit 1.5MB
> memory board for the A1000, I remembered something I wanted to ask about.
> 
> Whenever I read the internal clock, it is one day fast.  This includes reading
> it by using DATE or by using a program such as RSLCLOCK.  The interesting part
> is this: the date is set using the provided setclock function and read using
> the readclock function ... both programs print what they think the date is
> and they do print the correct date.  
> 
> Blair

The problem is indeed in the readclock program supplied by Spirit Technologies.
I got their board about a year ago now, (I really like it).  I ran into a 
problem where it acted like the clock wasn't there (i.e. the old clock not
found trick).  Apparently, this happened when something went crazy on my
system and took off writing to memory everywhere.  Anyway, back to the point
to remedy the situation, Spirit sent me their latest disk with the updated
programs which reset the clock module.  I started using the new readclock
program and found the same problem you are having, so I went back to my
old version, it still works correctly.  You may want to contact Spirit to
let them know the problem, they are pretty good with customer service.  I
don't know if I can legally give the old program out, if there is interest,
I'll call Spirit and ask.  But in any case, Spirit should be made aware of
this bug in the readclock program.

-- 
	        John Barshinger	
		Space Telescope Science Institute
		Baltimore, MD 21218
		plink:jrbii | bix:jrbii | barsh@stsci.edu