Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!husc6!m2c!ulowell!cbmvax!carolyn
From: carolyn@cbmvax.UUCP (Carolyn Scheppner CATS)
Newsgroups: comp.sys.amiga.tech
Subject: Re: <invalid> <invalid> <invalid>
Keywords: B2000 real-time clock slammed dead 16 bit compress multiple arguments
Message-ID: <3763@cbmvax.UUCP>
Date: 12 May 88 17:01:26 GMT
References: <2504@k.cc.purdue.edu>
Reply-To: carolyn@cbmvax.UUCP (Carolyn Scheppner CATS)
Organization: Commodore Technology, West Chester, PA
Lines: 26

In article <2504@k.cc.purdue.edu> ahg@k.cc.purdue.edu (Allen Braunsdorf) writes:
>
>[description of program trashing the real-time clock]

If a program crashes spectacularly and hits the IO area it can leave the
real-time clock in a bad state.

Turning off your machine, then turning it back on fixes part of the problem,
but setclock opt load will get you <invalid> at that point because you have
not yet reset the clock to a valid date and time.

Correct procedure should be:

1. Turn off your machine
2. Turn it back on and reboot
3. Use the DATE command to set the correct system date and time
4. Setclock opt save  to save the correct time to the real-time clock

Now  setclock opt load  should work fine.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Carolyn Scheppner -- CATS   >>Commodore Amiga Technical Support<<
                     UUCP  ...{allegra,ihnp4,rutgers}!cbmvax!carolyn 
                     PHONE 215-431-9180
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=