Path: utzoo!utgpu!attcan!uunet!lll-winken!ames!mailrus!sharkey!atanasoff!jwright From: jwright@atanasoff.cs.iastate.edu (Jim Wright) Newsgroups: comp.sys.amiga Subject: Re: A501 clock failure Message-ID: <628@atanasoff.cs.iastate.edu> Date: 7 Jan 89 02:40:54 GMT References: <6224@louie.udel.EDU> <318@antares.UUCP> Reply-To: jwright@atanasoff.cs.iastate.edu (Jim Wright) Organization: Iowa State U. Computer Science Department, Ames, IA Lines: 19 In article <318@antares.UUCP> pnelson@antares.UUCP (Phil Nelson) writes: ->>In article <8901011415.AA07578@MATH.Tau.Ac.IL> writes: ->>> The clock module of my A501 has stopped functioning. ->>> Battery Backed up clock not found ->>> I tried using the 'setclock opt reset' but it didn't help. ->About a week ago, after a guru, I noticed the "Battery backed up clock not ->found" message. ->Well, neither the local Amiga dealer or electronics store had the chip, and ->before I could check any further, The clock started working again (although ->it did lose about three days). My 2000 did the same thing. For three days it booted with the clock not found message. On the fourth day it found it, but said it was something like July 1937 (this was in late 88). On the fifth day it restored itself to normal. I know I didn't open the case to try anything, and I don't think I tried much fiddling with the setclock program. (All this with 1.2) What I found most strange was the 1937 part. A lot of computers think time began in (1960|1970|1980). Only the Amiga makes it possible.