Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!rutgers!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.amiga
Subject: Re: Serious amiga 2000 clock problems!
Message-ID: <13387@cbmvax.commodore.com>
Date: 23 Jul 90 23:14:33 GMT
References: <1990Jul21.142922.959@dhw68k.cts.com>
Reply-To: daveh@cbmvax (Dave Haynie)
Distribution: na
Organization: Commodore, West Chester, PA
Lines: 27

In article <1990Jul21.142922.959@dhw68k.cts.com> jtb@dhw68k.cts.com (John Gibbons) writes:

>    If I at ANY time do a "setclock opt load" the correct time and date is
>loaded in perfectly without problem. However within 1 minute the current
>time will be incorrect. 

The problem is that the "software clock", part of one of the 8520 chips that
uses a 60Hz/50Hz line frequency to give you time while the machine is running,
is bad.  I had very much the same problem about two years ago; my clock would
count for about 70 minutes, then jump back.  Amusing to watch, but it certainly
sends "make" and other date dependent tools to the funny farm.

The proper solution is to have the offending 8520 CIA chip replaced.  There is
a chance simply swapping the two 8520s would solve your problem without 
creating another problem, since there's not much chance of the TOD counter
being used in the other part, assuming it's only the TOD counter that's at
fault.  When mine died, I replaced the 8520 (I will admit a much easier job
if you keep a few in your parts bin at home like I do).

>John Gibbons
>Internet: jtb@dhw68k.cts.com       UUCP: ...{spsd,zardoz,felix}!dhw68k!jtb


-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
           The Dave Haynie branch of the New Zealand Fan Club