Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!pacbell.com!ames!ucsd!hub.ucsb.edu!ucsbuxa!6500rgls
From: 6500rgls@ucsbuxa.ucsb.edu (Randall S Geels)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Strange results from using TimeMgr with THINK C
Message-ID: <8780@hub.ucsb.edu>
Date: 3 Feb 91 08:36:46 GMT
References: <27A8A3C4.8227@ics.uci.edu>
Sender: news@hub.ucsb.edu
Distribution: usa
Lines: 15


>tm.Count gives me back
>a long int which doesn't seem to correspond to much

Huh? According to my IM IV documentation of the time manager, tmCount
is simply a reserved variable and it doesn't say it's supposed to
correspond to anything. I have been trying to use the time manager and
I find it works pretty much as advertised. I am using the new call
InsXTime in an attempt to not lose any time in processing the interupt.
After repeated calls, however, I find that the time between interrupts
is actually about 10 microseconds less than what I specify in PrimeTime()
when I'm running on a Mac Plus. The error is smaller on the Mac II.
If you need any further info, just let me know.

Randy Geels