Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!uw-beaver!Teknowledge.COM!unix!mxmora
From: mxmora@unix.SRI.COM (Matt Mora)
Newsgroups: comp.sys.mac.programmer
Subject: Re: TicksCount
Message-ID: <25574@unix.SRI.COM>
Date: 19 Jun 91 16:09:03 GMT
References: <1991Jun11.092513.14329@cs.uri.edu> <1991Jun12.184613.3650@viewlogic.com> <1991Jun13.144441.14539@eng.umd.edu> <B+J-M9@smurf.sub.org>
Reply-To: mxmora@unix.sri.com (Matt Mora)
Organization: SRI International, Menlo Park, CA
Lines: 40

In article<B+J-M9@smurf.sub.org>urlichs@smurf.sub.org(Matthias Urlichs) writes:
>In comp.sys.mac.programmer, article <1991Jun13.144441.14539@eng.umd.edu>,
>  russotto@eng.umd.edu (Matthew T. Russotto) writes: 
><In my experience, the Mac keeps fairly inaccurate time, whether on battery or
>< plugged in.  It gets off several minutes per month.  
>
>Mine too. :-(
>
>Is there any way to change that?
>
>It should be fairly easy to write a cdev that can be told to correct the
>clock N seconds per months, and which does an incremental change every day or
>every time the Mac is started, whatever occurs more often. ;-)
>
>Fairly easy, that is, for somebody with more time for things like that than I
>have...


Its been done already. I have seen a cdev that does exactly what you describe.

I think it is in the archives on sumex. I think its called clock adjust.

Of course you could just connect to a time server and have it update your
mac clock. :-) (apple.com has pretty accurate time)











-- 
___________________________________________________________
Matthew Mora                |   my Mac  Matt_Mora@sri.com
SRI International           |  my unix  mxmora@unix.sri.com
___________________________________________________________