Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mailrus!sharkey!atanasoff!jwright
From: jwright@atanasoff.cs.iastate.edu (Jim Wright)
Newsgroups: comp.sys.amiga
Subject: Re: Battery Backed Up Clock Not Found
Message-ID: <1303@atanasoff.cs.iastate.edu>
Date: 6 Aug 89 15:23:04 GMT
References: <43865@bbn.COM>
Reply-To: jwright@atanasoff.cs.iastate.edu.UUCP (Jim Wright)
Organization: Iowa State U. Computer Science Department, Ames, IA
Lines: 29

This is largely based on my memory of past c.s.a. postings.  If my
ramblings can be verified, or a real solution can be found, it might
be useful in the intro posting.

In article <43865@bbn.COM> cosell@BBN.COM (Bernie Cosell) writes:
| What is my 2000 trying to tell me?
| 
| I was doing some hacking (trying to get
| Ferrari Formula I to run off of my hard disk) and the machine had just
| trashed itself and crashed (real interesting: patterns streaming
| across the screen, the control LEDs on my modem went wild, etc).  I
| ctrl-A-A'ed the beast and it came up complaining about its clock.  I
| tried "setclock reset" but it, too, just complained about "clock not
| found".  And there I sit.

This happened to me earlier.  I "fixed" it by doing nothing.  About the
second or third day I booted, the problem simply disappeared.

As I understand it, a register in the clock is getting trashed.  The normal
startup then can't find a (proper) clock.  The solution is to get the
registers in the clock back the way they should be.  Between version 1.2
and 1.3 of the "setclock reset" commands, one works and one doesn't.  (I
believe 1.2 works.(?))  Another possible fix is the program which claims
to "cure" the fabled "clock virus".  Apparently it just resets the registers
in the clock.  (Available at an anti-viral archive site near you.)

-- 
Jim Wright
jwright@atanasoff.cs.iastate.edu