Xref: utzoo comp.sys.amiga:25309 comp.sys.amiga.tech:2449
Path: utzoo!censor!hugh
From: hugh@censor.UUCP (Hugh Gamble)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: 1.3 setclock bug?
Keywords: AmigaDos 1.3 bugs setclock
Message-ID: <120@censor.UUCP>
Date: 17 Nov 88 08:17:21 GMT
Organization: Bell Canada, Business Development, Toronto
Lines: 44

I think I've run into a bug in 1.3 setclock, here's the story:

I was doing a HD backup with quarterback while reading the 
net news from a host using Handshake 2.10a when a Gomf 2.2
window came partway up on my 2000.  The window was there, but
the text & gadgets never showed up.  Then quarteback started
acting strange, then Handshake started acting strange, then I
rebooted.

When my startup sequence got to the setclock line I got a
message something like "Battery Backed up Clock not found"
I tried a cold boot, same thing.  Everything else was working
fine though.

OK, check the battery and find it's happily putting out 4V.

Then with a briliant flash of lack of stupidity I suspect
S/W rather than H/W trouble.  I checked the setclock
program in my c: was still the same as one on a backup floppy.
Yup.

With "setclock reset" giving the same not found message as
the setclock load in my startup, I then tried the 1.2
"setclock opt load".  It loaded the S/W clock & my system
then thought it was sometime in Dec. 1981.  After that
the 1.3 setclock works fine again!

My analysis:

I think a program running wild messed up the clock (set the
test bits?).  
I think the 1.3 setclock did not like it
that way & the reset option does not work properly.
I think the 1.2 setclock load *did* reset the test bits.
I think I'm happy I don't need to send my box out to get
fixed just after the 90 day warrantee is up.

What does anyone who *knows* something think about what
I think?

-- 
| Hugh D. Gamble  (416) 581-4354  {lsuc, utzoo}!censor!hugh  (Std. Disclaimers)
| I can push any computer to its limits.
| Any computer can push me to *my* limits.