Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!spool.mu.edu!samsung!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!claris!UUCP!peirce
From: peirce@outpost.UUCP (Michael Peirce)
Newsgroups: comp.sys.mac.programmer
Subject: Re: TicksCount
Message-ID: <0B01FFFB.ihunr8@outpost.UUCP>
Date: 18 Jun 91 23:05:21 GMT
Reply-To: peirce@outpost.UUCP (Michael Peirce)
Organization: Peirce Software
Lines: 26
X-Mailer: uAccess - Mac Release: 1.1.b3


In article <54082@apple.Apple.COM>, keith@Apple.COM (Keith Rollin) writes:
> In article <1991Jun17.193130.1@lure.latrobe.edu.au> lhccjeh@lure.latrobe.edu.au (James Hale) writes:
> >
> >One tick is 1/60 of a second or 16.67 msec. 
> >a 20 msec accuracy is not an improvement.
> >_____________________________________________________________________________
> >James Hale     			Lincoln School of Health Sciences
> 
> I think this is a rare case in which Michael misspoke. The original Time
> Manager was rated at 1 millisecond, but there was no provision for
> drift-free alarms. The current Time Manager (as provided in System
> 6.0.3 or later, and documented in technotes and IM VI) is documented as
> providing 250 microsecond drift-free timing, but you can push that down
> to 20 microseconds if you want to try getting away with it.

Rare case where I misspoke?  I make mistakes all the time!

I did mean to say microsecond rather than millisecond.  What's a few
zeros between friends? :-)

-- michael

--  Michael Peirce         --   outpost!peirce@claris.com
--  Peirce Software        --   Suite 301, 719 Hibiscus Place
--  Macintosh Programming  --   San Jose, California 95117
--           & Consulting  --   (408) 244-6554, AppleLink: PEIRCE