Newsgroups: comp.sys.amiga.hardware
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!cornell!johnhlee
From: johnhlee@CS.Cornell.EDU (John H. Lee)
Subject: Re: An odd A500 Clock Problem.
Message-ID: <1991May21.014904.23238@cs.cornell.edu>
Sender: news@cs.cornell.edu (USENET news user)
Nntp-Posting-Host: hermod.cs.cornell.edu
Reply-To: johnhlee@cs.cornell.edu (John H. Lee)
Organization: Cornell Univ. CS Dept, Ithaca NY 14853
References: <cPi521w164w@ersys.edmonton.ab.ca>
Date: Tue, 21 May 1991 01:49:04 GMT
Lines: 26

In article <cPi521w164w@ersys.edmonton.ab.ca> kenh@ersys.edmonton.ab.ca (Ken Huisman) writes:
>I ran this program in another attempt to try to get it running, to no
>avail.  This time, however, something really wierd happened.  As it was
>reading the files from my A590 hardrive with a 52MB quantum, random
>dots appeared on the screen, then the screen went black and the computer
>just hung - no guru, just froze up.  Upon reboot, I got the message
>"battery backed clock not found" - I had fried my little 512k ram
>expansion's clock.  This happened about 2 weeks ago.

No need to worry.  The real-time clock can be "messed up" if a program
writes random data to its registers.  Your clock is still OK--it just needs
a little help to straighten it out.

Reset the clock with the setclock command:

	1> setclock reset

and that should revive it.  Set and save the system date and time and the
clock will be back to normal.  Make sure you use either the WB 1.2, 1.3.2,
or later version of setclock.  The setclock distributed with WB version 1.3
has a bug and won't work.  

-------------------------------------------------------------------------------
The DiskDoctor threatens the crew!  Next time on AmigaDos: The Next Generation.
	John Lee		Internet: johnhlee@cs.cornell.edu
The above opinions are those of the user, and not of this machine.
