Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site bbncca.ARPA
Path: utzoo!linus!vaxine!wjh12!bbncca!sdyer
From: sdyer@bbncca.ARPA (Steve Dyer)
Newsgroups: net.micro.6809
Subject: Re: Slow Clock:  a problem?
Message-ID: <246@bbncca.ARPA>
Date: Wed, 2-Nov-83 12:27:55 EST
Article-I.D.: bbncca.246
Posted: Wed Nov  2 12:27:55 1983
Date-Received: Sun, 6-Nov-83 02:27:43 EST
References: <1777@ihnss.UUCP>
Organization: Bolt, Beranek and Newman, Cambridge, Ma.
Lines: 15

I found that my OS-9 loses time, too.

The key here is NOT that the clock is wrong, but that many CoCo OS-9 operations
(like disk I/O) require interrupts to be turned off.  Naturally, when this
happens, the system 'loses time', since its conception of time-of-day is driven
off of the 60hz clock interrupt.  Every 60 clock ticks, the time is incremented
by one second.

My own feeling is that the line clock is suitable for scheduling, but a true
time-of-day clock card is needed if you are looking for accuracy.  What I
would love to see is a multi-function board containing 2 serial ports, one
parallel port, and such a clock.

/Steve Dyer
decvax!bbncca!sdyer