> The discussion here is how to get windows to ACTUALLY write
> to disk rather than holding the information in it's own disk
> cache until something else forces it to disk ( or not if the
> power fails ) even after the information has been commited.

And I thought the discussion is about how to eat cake and have it,
i.e. how to ensure that data are written to disk like with forced writes on,
with actually setting forced writes off to increase speed.

See:

> From: Phil Shrimpton
> I thought that Windows would eventually flush the pending writes to the file
> in idle time, but in a test...
>
> - I imported 200Mb of data in to a blank database
> - Left the server and client app idle for 4 hours
> - Pulled the power cord
>
> ...the database was blank after boot up

Even if Windows flush data sooner than after 4 hours, there is still chance
that you pull power cord right in the middle of write; if in that time pages written
were reordered by OS, you get corrupted database. Period.

Ivan
http://www.volny.cz/iprenosil/interbase