Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!mcsun!unido!fauern!fauern!immd4.informatik.uni-erlangen.de!mlelstv
From: mlelstv@immd4.informatik.uni-erlangen.de (Michael van Elst )
Newsgroups: comp.sys.amiga
Subject: Re: system clock
Message-ID: <587@medusa.informatik.uni-erlangen.de>
Date: 20 Nov 89 14:08:58 GMT
References: <89110701494798@masnet.uucp> <32315@auc.UUCP> <5135@sun.acs.udel.edu>
Organization: IMMD IV, University of Erlangen, W-Germany
Lines: 21

sjm@sun.acs.udel.edu (Steve Morris) writes:

>I have not had any problems with the real time clock in my A500, but
>if I leave the machine on for extended periods of time I find that
>the Amiga DOS clock seems to lose ~5 min / day. Anyone else notice this?

The system clock is not very accurate (at least on an A500).

The A500 timer is clocked from the video frequency (VBLANK signal) since
the power supply does not generate a 50Hz (or 60Hz) signal. Maybe they
(Commodore) changed the power supply with later A500s.
Nevertheless, you can feed in a separate clock signal to get it more
accurate.

The battery-backed up clock is not influenced by the problem listed above.
Yet, it is only used when initializing the system clock with the
SetClock command.

				Michael van Elst

E-mail: UUCP: ...uunet!unido!fauern!immd4!mlelstv