Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!mtxinu!unisoft!hoptoad!peora!rtmvax!bilver!bill
From: bill@bilver.UUCP (bill vermillion)
Newsgroups: comp.unix.xenix
Subject: Re: timekeeping
Keywords: time, clocks, AT
Message-ID: <521@bilver.UUCP>
Date: 22 Apr 89 14:17:24 GMT
References: <275@mplex.UUCP>
Reply-To: bill@bilver.UUCP (bill vermillion)
Distribution: na
Organization: W. J. Vermillion, Winter Park, FL
Lines: 22

In article <275@mplex.UUCP> fff@mplex.UUCP (Fred Fierling) writes:
>Can someone tell me why it is that Xenix keeps such lousy time?
>
>We are running various flavours of SCO Xenix on true blue IBM AT's
>and Hewlett Packard Vectra RS/20's (386) and none of these machines
>keeps time better than a $20 watch.  Systems are often 5 minutes slow
>in a week.

I have one site with 10 SCO installations.  Time keeping varies primarily
depending on hardward.

Go to your "Run Time Environment" SCO manual, turn to the HW section, and look
at the command clockrate.  You will have to try different values until you get
it right for the machine you are running on.

This works while the machine is running.   Since you only look at the clock on
boot-up Xenix is keeping time the rest of the time.  If time changes when the
machines are powered off it is hardware.

-- 
Bill Vermillion - UUCP: {uiucuxc,hoptoad,petsd}!peora!rtmvax!bilver!bill
                      : bill@bilver.UUCP