Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!news.arc.nasa.gov!haven.umd.edu!mimsy!mojo!russotto
From: russotto@eng.umd.edu (Matthew T. Russotto)
Newsgroups: comp.sys.mac.programmer
Subject: Re: TicksCount
Message-ID: <1991Jun19.153937.11431@eng.umd.edu>
Date: 19 Jun 91 15:39:37 GMT
References: <1991Jun12.184613.3650@viewlogic.com> <1991Jun13.144441.14539@eng.umd.edu> <B+J-M9@smurf.sub.org>
Sender: news@eng.umd.edu (C-News)
Organization: College of Engineering, Maryversity of Uniland, College Park
Lines: 23

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...

Easy enough, but not worth it-- I can correct it to my watch manually when
it really starts getting off.  How about a hardware solution?
--
Matthew T. Russotto	russotto@eng.umd.edu	russotto@wam.umd.edu
     .sig under construction, like the rest of this campus.