Newsgroups: comp.sys.amiga.programmer
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!honp9
From: honp9@menudo.uh.edu (Jason L. Tibbitts III)
Subject: Re: Copper mystery
Message-ID: <1991Apr2.005933.28315@menudo.uh.edu>
Organization: Blob Shop Programmers
References: <5343@mindlink.UUCP>
Date: Tue, 2 Apr 1991 00:59:33 GMT

In article <5343@mindlink.UUCP> Ed_Meyer@mindlink.UUCP (Ed Meyer) writes:
>> dillon@overload.Berkeley.CA.US writes:
>> 
>>     Actually, as per my previous message, all that is really necessary
>>     is that you make your task the highest priority, period.
>> 
>>     I am happy to see that others have caught on to this excellent method.
[...]
>>                                         -Matt

I hate to do this, but what happens if your hard disk controller employs
delayed writes?  (Some do.)  If you are the highest priority task and the
OS returns control to you before a write occurs, then when does it happen?
Probably the next time you WAIT(), but that might be a long time.

I'd like to know more on how the machine functions when your task is CPU
intensive and running at maximum priority.

-- 
Jason L. Tibbitts III  | Moderator: comp.sys.amiga.reviews
"Blob Shop Programmers:| Send submissions to HONP9@menudo.uh.edu
 Because We're Bored!" | Check comp.sys.amiga.reviews for submissions
Disclaimer: Opinions...| guide, disclaimers, etc.               Fnord.