Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!samsung!caen!uakari.primate.wisc.edu!aplcen!wb3ffv!ka3ovk!barn!hoptoad!farcomp!murat From: murat@farcomp.UUCP (Murat Konar) Newsgroups: comp.sys.mac.programmer Subject: Re: TicksCount Message-ID: <384@farcomp.UUCP> Date: 19 Jun 91 22:25:14 GMT References: <1991Jun11.092513.14329@cs.uri.edu> <1991Jun12.184613.3650@viewlogic.com> <1991Jun13.144441.14539@eng.umd.edu> Reply-To: murat@farcomp.UUCP (Murat Konar) Organization: Farallon Computing Inc. Berkeley, CA Lines: 27 (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 - -Mine too. :-( - - -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... Coincidentally, I've been thinking about writing such a utility. The question is: why is the Mac's clock inaccurate? Is it just slow (or fast)? If so, a simple periodic correction would solve the problem. If itUs because the clock loses ticks now and then due to interrupt processing, things could get real weird. Anybody know what the story is? -- ____________________________________________________________________ Have a day. :^| Murat N. Konar murat@farcomp.UUCP -or- farcomp!murat@apple.com