Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!sdd.hp.com!wuarchive!uunet!cbmvax!grr From: grr@cbmvax.commodore.com (George Robbins) Newsgroups: comp.sys.amiga.tech Subject: Re: A501 Clock Problem Message-ID: <22274@cbmvax.commodore.com> Date: 8 Jun 91 07:58:34 GMT References: <1991Jun3.174934.3543@csusac.csus.edu> <1991Jun6.131156.12025@cs.uow.edu.au> Reply-To: grr@cbmvax.commodore.com (George Robbins) Organization: Commodore, West Chester, PA Lines: 31 Keywords: Amiga, A501 In article <1991Jun6.131156.12025@cs.uow.edu.au> u8705377@cs.uow.edu.au (Paul Anthony Wilkinson) writes: > kelson@ais.org (David Lewis) writes: > > >wangf@athena.ecs.csus.edu (Out of Mind) writes: > > >>My clock on my A501 seems like it went dead...The computer now books up > >>and says it can't find the clock? Is the battery dead? If so, how do ... > >-- > > >Internet: Kelson@ais.org > after this the time was either wrong, or "clock not found". > The first way to try and fix this is to use the command "setclock reset" > from the CLI. First line of defense... > If this does not work then you have to resort to more drastic > measures. Remove the 501 board. If the clock chip is socketed then simply > remove it and then replace it. This will reset the chip. If the chip is > not socketed you can either unsolder the chip or the battery (or just let > the board sit for about 3 years to let the battery run down 8-) ). Yoo, that is a lot of work. Since there is a resistor in series with the battery you can safely short out the power at the chip for a few seconds to do a "hard reset". Just tap a little jumper across C9. You really shouldn't have to do this, but if it works for you... -- George Robbins - now working for, uucp: {uunet|pyramid|rutgers}!cbmvax!grr but no way officially representing: domain: grr@cbmvax.commodore.com Commodore, Engineering Department phone: 215-431-9349 (only by moonlite)