Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!rochester!udel!new
From: new@udel.edu (Darren New)
Newsgroups: comp.sys.amiga.tech
Subject: Re: AmigaDOS help...
Message-ID: <1833@nigel.udel.EDU>
Date: 16 Oct 89 22:15:22 GMT
References: <1484@nigel.udel.EDU> <126319@sun.Eng.Sun.COM>
Sender: usenet@udel.EDU
Reply-To: new@udel.edu (Darren New)
Distribution: na
Organization: University of Delaware
Lines: 16

Ok, another question about AmigaDOS:

Is it possible to force the file-system(s) to write out their buffered
data?  In my program, I write a (sometimes) large file (>400K) and then
inhibit the filesystem in order to read bitmaps, etc.  Right now I just
Delay(300) or so to let the FS finish flushing bitmaps and such.  However,
this seems like a bad way of doing it, especially since it is possible that
the FS won't get a chance to run due to other procs running at a higher
priority.  There are packets for "ACTION_DISKCHANGE" but I think that
these are obsolete.  The Inhibit packet seems to cause troubles if 
DoIO()'ed while the bitmaps are bad.  I think I remember experimenting
and finding that C:DiskChange will screw up a disk if issued right
after writing to a disk, which leads me to believe there is no
good way to do it right.
Right now, the Delay() seems to be OK, but I'm interested in knowing 
if there is a better way. Thanks!!!  -- Darren