Path: utzoo!utgpu!attcan!uunet!cbmvax!andy
From: andy@cbmvax.UUCP (Andy Finkel)
Newsgroups: comp.sys.amiga
Subject: Re: A501 clock failure
Message-ID: <5637@cbmvax.UUCP>
Date: 6 Jan 89 16:58:47 GMT
References: <6224@louie.udel.EDU> <318@antares.UUCP>
Reply-To: andy@cbmvax.UUCP (Andy Finkel)
Organization: Commodore Technology, West Chester, PA
Lines: 29

In article <318@antares.UUCP> pnelson@antares.UUCP (Phil Nelson) writes:
>>Wasn't there a posting a while ago stating that the 1.3 version of
>>setclock had a deficiency where it would not work sometimes after a
>>crash with this exact error message?  They claimed that using the 1.2
>>setclock would fix this situation.
>>
>>                              John G. Ata
>
>
>I don't remember this posting, was it a long time ago? If this happens to
>me again, I will try the 1.2 setclock, in the meantime, does anyone know
>more about this?


Setclock 1.3 has improved testing as to whether or not a real time
clock exists on the machine.  Setclock 1.3 also has the new RESET
option, to get the clock out of test mode.  Unfortunately, I forgot,
and put the code for the reset after the improved validation routines :-(

			andy
-- 
andy finkel		{uunet|rutgers|amiga}!cbmvax!andy
Commodore-Amiga, Inc.

"Possibly this is a new usage of the word 'compatible' with which
 I was previously unfamiliar"

Any expressed opinions are mine; but feel free to share.
I disclaim all responsibilities, all shapes, all sizes, all colors.