Xref: utzoo comp.sys.amiga:52882 comp.sys.amiga.tech:10744
Path: utzoo!attcan!uunet!cs.utexas.edu!usc!brutus.cs.uiuc.edu!psuvax1!rutgers!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: clock driving me crazy
Keywords: clock,time
Message-ID: <10381@cbmvax.commodore.com>
Date: 27 Mar 90 17:39:10 GMT
References: <2592@medusa.informatik.uni-erlangen.de>
Reply-To: daveh@cbmvax (Dave Haynie)
Organization: Commodore, West Chester, PA
Lines: 24

In article <2592@medusa.informatik.uni-erlangen.de> posch@medusa.informatik.uni-erlangen.de (Stefan Posch ) writes:

>SYPMTOMS:
>	After booting (and using SETCLOCK OPT LOAD) the time is
>	correct (i.e. the buffered clock seems to be OK).
>	But using DATE, CLOCK or anything I tried which gives the time,
>	shows, the time runs 1min20secs, then jumps back the same time,
>	and the same again and again and ...
>	My system time is now nearly static after boot.

I've actually had this problem on my home system.  Well, actually, my clock
was being set back every 70sec, but the same basic idea.  The way to find
the problem is to realize you have two clocks in an A2000.  One is the
realtime clock, which works like a computer-readable watch and sets your 
system time every time you run the SetClock program with the "load" option.
The other is the runtime clock, which is based on a counter in one of the
8520 chips that counts pulses of the 50Hz or 60Hz line frequency.  If
the runtime behavior of the clock looks wrong, you more than likely have a
problem with the counter in the 8520.  I certainly did -- replacing that
8520 (U300 on the 2000) should solve the problem.
-- 
Dave Haynie Commodore-Amiga (Systems Engineering) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
                    Too much of everything is just enough