dbk@teroach.phx.mcd.mot.com (Dave Kinzer) (07/25/89)
I am having a strange problem with my Amiga's run time clock. Configuration: A2000(B) Rev 4.2 K/S 1.3 A2090a W/ ST506 type drive A2052 Problem: 1) Set the system clock with a 'setclock load' 2) Using the 'date' command time marches forward (at apparently the correct rate) 3) 65 seconds later, the time resets to the time of the setclock command. 4) Repeat 2 and 3 and 4. Tried: Rebooting Turning system off and restarting Original WB 1.3 disk Is this weird, or what? It seems to be a software related thing since time marches on correctly. The real-time clock keeps time correctly, that is, the time is correct at the setclock load. I have my 1.2 ROM I could swap in if it seems like a thing to try, I just thought I'd see if anyone out there had seen this before since swapping the rom requires a major stripdown of the machine. | // GOATS - Gladly Offering All Their Support Dave Kinzer (602)897-3085| | // >> In Hell you need 4Mb to Multitask! << uunet!mcdphx!teroach!dbk | | \X/ #define policy_maker(name) (name->salary > 3 * dave.salary) |
dbk@teroach.UUCP (Dave Kinzer) (07/29/89)
The strange problem of the resetting time-of-day clock has been traced to one of the 8520 chips not working. I also noted last night that my parallel port would send not data to the printer (also fixed). Of course, I needed to print right then, so I casually switched to using the serial port until I replaced the chip. Gawd, I love this machine. Suspected cause of failure: Thunderstorm last weekend. I normally leave the machine running, and I was out at the movies so I couldn't pull the plug. Much lightning, much heartache (well, a little anyway.) This chip also gets it's timing reference directly from the power supply (A2000 mode) with no on-board protection. Tisk Tisk. :^) -- * * * Imminent use of deathnet predicted. * * * // Dave Kinzer (602)897-3085 asuvax!mcdphx!teroach!dbk Opinions are mine. \X/