Path: utzoo!censor!hugh From: hugh@censor.UUCP (Hugh Gamble) Newsgroups: comp.sys.amiga Subject: Re: A501 clock failure Summary: 1.2 setclock is worth a shot. Message-ID: <249@censor.UUCP> Date: 9 Jan 89 04:47:07 GMT References: <6224@louie.udel.EDU> Organization: Bell Canada, Business Development, Toronto Lines: 57 In article <6224@louie.udel.EDU>, Ata@radc-multics.arpa (John G. Ata) writes: > In article <8901011415.AA07578@MATH.Tau.Ac.IL> writes: > > Help! > > > > 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. > > > > I opened my A501 unit. The Battery output is 4.12V, and according to > > the schematics it should to be 4.5V. Is this the problem? ... > The voltage you mention is probably OK if measured at the clock chip, > it's a little bit suspect if measured at the battery. You should check > that the battery is charging when the machine is powered up - it is > trickle charged through a resistor. > -- > George Robbins - now working for, uucp: {uunet|pyramid|rutgers}!cbmvax!grr > but no way officially representing arpa: cbmvax!grr@uunet.uu.net > Commodore, Engineering Department fone: 215-431-9255 (only by moonlite) > > 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 One time the clock on my 2000 was giving the "not found" message consistently through several days of trouble shooting including leaving the machine turned of for a day, "setclock reset" and everything else I could think of. This *might* be a coincidence, because I never reproduced the problem and tried it again, but when I ran the 1.2 "setclock opt save" that fixed the clock and everything has worked fine since. My guess is that the 1.3 setclock reset wasn't clearing whatever strange state the clock chip had gotten into, but the 1.2 setclock did. If you find this or something else specific fixes your problem please post the details. I'm also curious about any details of the conditions surrounding your clocks ceasing to function. In my case, more processes in the machine got sicker and sicker, then the display got *very* strange, the machine didn't reboot very nicely the first time (sorry, don't remember the details.) After that the machine would boot fine, and everything else was OK except for the clock not found messages. I thought that some process had gone really wild trashing memory, and set a test bit in the clock chip in the process. Hope some of this helps.