bmacintyre@watsol.waterloo.edu (Blair MacIntyre) (03/08/88)
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.
ie. setclock 01-01-88 <- I'm not sure of the syntax, but this is the
Date is Jan 1, 1988 idea. Same for the output.
readclock
set internal time to xx:xx:xx, Jan 1, 1988
Now, if right after that I do a DATE, I get:
date
Time is xx:xx:xx, Jan 2, 1988
So, I believe, the problem is in the readclock program. This is not a serious
problem, but it is annoying. I was wondering if anyone else has this problem
and has a fix for it ( aside from setting the date to 1 day early ).
Also, any idea what exactly is going wrong?
Blair
===========================================================================///=
Blair MacIntyre (bmacintyre@watsol.waterloo.edu) ( Long live the Amiga!! )///
University of Waterloo, Centre for the New Oxford English Dictionary \\\///
=======================================================================\XX/====
--
===========================================================================///=
Blair MacIntyre (bmacintyre@watsol.waterloo.edu) ( Long live the Amiga!! )///
University of Waterloo, Centre for the New Oxford English Dictionary \\\///
=======================================================================\XX/====barsh@stsci.EDU (John Barshinger) (03/10/88)
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
bryce@eris (Bryce Nesbitt) (03/11/88)
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