papa@pollux.usc.edu (Marco Papa) (05/12/88)
In article <2504@k.cc.purdue.edu| ahg@k.cc.purdue.edu (Allen Braunsdorf) writes: |I use (16 bit) compress on my Amiga 2000. It works great except that the |version I use (one from a FF disk, not the one in the archives here) does ||terrible< things when you give it multiple file names. |The first time I did this (months ago), there was an impressive graphic display |with incredible sound effects. When I rebooted, my real time clock said it |was sometime in 1939! This was strange, but it gets worse: | |The machine said (this is from memory, so it might be wrong): Internal clock |not functioning. That's all it would say from the setclock command (whether |loading or saving). | |I then cold started the 2000. The setclock command then only returned the |incredibly baffling: <invalid| <invalid| <invalid|. | |We decided that the clock was in a funny state and sought a hardware solution. |We opened the box and decided to (very) momentarily short the battery (it |doesn't come out). This fixed the clock problems, but doesn't seem to me to |be a healthy thing to do. | |First, how did the clock get "slammed"? Secondly, is there a software solution Almost ALL the time I crash the 2000 when testing my software the clock gets screwed up. Running setclock works 50% of the time. The other 50% I have to COLD boot and then run setclock and everything gets back in order. -- Marco Papa 'Doc' -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= uucp:...!pollux!papa BIX:papa ARPAnet:pollux!papa@oberon.usc.edu "There's Alpha, Beta, Gamma and Diga!" -- Leo Schwab [quoting Rick Unland] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
carolyn@cbmvax.UUCP (Carolyn Scheppner CATS) (05/13/88)
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 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=