Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!ncar!boulder!pratt
From: pratt@boulder.Colorado.EDU (Jonathan Pratt)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Extended Time Manager in System 6.0.7
Message-ID: <29537@boulder.Colorado.EDU>
Date: 11 Nov 90 05:09:20 GMT
References: <2252.273af53c@waikato.ac.nz> <29523@boulder.Colorado.EDU> <46475@apple.Apple.COM>
Sender: news@boulder.Colorado.EDU
Reply-To: pratt@boulder.Colorado.EDU (Jonathan Pratt)
Organization: University of Colorado, Boulder
Lines: 29
Nntp-Posting-Host: fred.colorado.edu

In article <29523@boulder.Colorado.EDU> I wrote:

(Asked how to determine time left in a TM task, to which Tom Dowdy
<dowdy@apple.com> kindly replied:)

According to [new docs], after calling RmvTime, the time remaining until the
completion of the task will be in tmCount.

>In article <46475@apple.Apple.COM> keith@Apple.COM (Keith Rollin) wrote:

(In response to my complaint about troubles having TM tasks reinstall
themselves:)

>I use the Time Manager -- even in the brackground -- in the DTS sample
>code FracApp 2.0. I've never noticed any problems.

I'm afraid I'm guilty of not giving the whole story in my original post.
I ran into trouble when I tried to get several dozen tasks running at
one millisecond intervals to simulate how the Mac would behave with
Nubus interrupts occurring at frequencies from 10khz to 100khz.  Perhaps
there should be an addendum to the tech note titled "Don't Abuse the
Managers" :-)

Jonathan

/* Jonathan Pratt          Internet: pratt@boulder.colorado.edu     *
 * Campus Box 525              uucp: ..!{ncar|nbires}!boulder!pratt *
 * University of Colorado                                           *
 * Boulder, CO 80309          Phone: (303) 492-4293                 */