Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!umd5!uvaarpa!virginia!boole!pmy
From: pmy@boole.acc.virginia.edu (Pete Yadlowsky)
Newsgroups: comp.sys.amiga
Subject: Re: internal RAM expansion
Message-ID: <382@boole.acc.virginia.edu>
Date: 7 Jan 88 15:42:12 GMT
References: <10001@ut-sally.UUCP> <181@stsci>
Distribution: na
Organization: Academic Computing Center, University of Va.
Lines: 18

In article <181@stsci>, barsh@stsci.EDU (John Barshinger) writes:
> 
> I've had my [Spirit] 1.5MB board for about six months approx.  All of the
> sudden out of the blue, I get the error "Clock not found" when
> executing Spirit.readclock.  Anybody know what's wrong?  My
> battery can be dead already, can it?  They say it should last
> ~17 years depending on the weather...

Yep, I've seen that one, too. I tried re-booting a couple of times, 
then I ran setclock. The problem went away. Hasn't come back. So,
setclock'll fix it, but that doesn't explain anything. Weird.


-- 
Pete Yadlowsky
Academic Computing Center
University of Virginia
e-mail: pmy@vivaldi.acc.virginia.EDU