Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!jesup
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Copper mystery
Message-ID: <20244@cbmvax.commodore.com>
Date: 2 Apr 91 04:18:29 GMT
References: <5343@mindlink.UUCP> <1991Apr2.005933.28315@menudo.uh.edu>
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA
Lines: 16

In article <1991Apr2.005933.28315@menudo.uh.edu> honp9@menudo.uh.edu (Jason L. Tibbitts III) writes:
>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.

	You force a flush (ACTION_FLUSH) before going back into your tight
loop.

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com  BIX: rjesup  
Disclaimer: Nothing I say is in anything other than my personal opinion.
Thus spake the Master Ninjei: "To program a million-line operating system
is easy, to change a man's temperament is more difficult."
(From "The Zen of Programming")  ;-)