Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!rochester!cornell!johnhlee
From: johnhlee@CS.Cornell.EDU (John H. Lee)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: How to get the internal clock STARTED again?
Message-ID: <1991Apr24.182830.18440@cs.cornell.edu>
Date: 24 Apr 91 18:28:30 GMT
References: <1991Apr23.080445.29874@fwi.uva.nl>
Sender: news@cs.cornell.edu (USENET news user)
Reply-To: johnhlee@cs.cornell.edu (John H. Lee)
Organization: Cornell Univ. CS Dept, Ithaca NY 14853
Lines: 23
Nntp-Posting-Host: oboe.cs.cornell.edu

In article <1991Apr23.080445.29874@fwi.uva.nl> rtbakker@fwi.uva.nl (R.T. Bakker (I85)) writes:
>as a result after a specific major fatal CRASH (one of many I regret to say)
>the call 'setclock load' produced the following message:
>
>	Battery backed up Clock not found
>
>In other words, no running internal clock.
>I have no clue how to get it started again, but it should be possible
>to get it going with a poke command in AmigaBasic.
>Only the 'big' mystery is (for my anyway) what are the specifics.
>Could somebody help me out?

Use either the WB 1.2 or WB 1.3.2 SetClock command (the original 1.3 SetClock
won't work) and issue the following command from the CLI:

	1> setclock RESET

That should kick your clock back on-line.

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