home *** CD-ROM | disk | FTP | other *** search
- Path: comma.rhein.de!serpens!not-for-mail
- From: mlelstv@serpens.rhein.de (Michael van Elst)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: GetSysTime() accuracy
- Date: 14 Apr 1996 11:37:32 +0200
- Organization: dis-
- Distribution: inet
- Message-ID: <4kqh0s$gid@serpens.rhein.de>
- References: <4khkab$7p2@toad.stack.urc.tue.nl> <jdj91fzso39.fsf@hyppynaru.cs.hut.fi>
- NNTP-Posting-Host: serpens.rhein.de
-
- oahvenla@hyppynaru.cs.hut.fi (Osma Ahvenlampi) writes:
-
- >The precision of GetSysTime() is 1 microsecond, although the accuracy
- >may be off by several orders of magnitude, depending on how well
- >adjusted the CIA timers and the clock frequency of the machine really
- >are.
-
- Ugh.. It rather depends on the software :) The system time is derived
- from the 50Hz/60Hz clock and thus just has a resolution of 20 or 16.6ms.
- The increment of the microseconds value is done so that subsequent calls
- to GetSysTime() always generate an increasing value.
-
- >I don't think you will gain any significant increase of accuracy by
- >using the CIA directly. GetSysTime() is about as low-level a call as I
- >can imagine.
-
- ReadEClock() is really low-level, it also runs with E-Clock precision
- (of about 1.4 microseconds).
-
- Regards,
- --
- Michael van Elst
-
- Internet: mlelstv@serpens.rhein.de
- "A potential Snark may lurk in every tree."
-