View Single Post
  #17  
Old January 21st 06, 09:52 PM posted to microsoft.public.win98.setup
external usenet poster
 
Posts: n/a
Default why won't write-behind stay disabled?

Why not use Windows (provided you disable the write-behind feature)? It's
available and it's already running.

Or if you object to that one so much, perhaps I have a logging application
that buffers its disk writes within the application so that I can implement
very aggressive disk drive power management. Write-behind has to be
disabled or the disk drive stays active for much longer causing a reduction
in battery time.

Or perhaps I use one of those data base systems where the manufacturer has
warned me that data corruption can occur in a multi-user environment when
write behind is enabled.

Or perhaps I am using a high performance raid system where the manufacturer
advises disabling write behind so that the intelligent algorithms in the
controller can operate most efficiently.

Or any number of other possible reasons.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Noel Paton" wrote in message
...
In that case, you don't use Windows to do it, but a direct-access OS

--
Noel Paton (MS-MVP 2002-2006, Windows)

Nil Carborundum Illegitemi
http://www.crashfixpc.com/millsrpch.htm


"Jeff Richards" wrote in message
...
I didn't say system, I said disk system. I don't know why you want to test
your disk system, but I want to test it to compare hardware, and to do
that you have to turn off write behind caching in the operating system.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Noel Paton" wrote in message
...

"Jeff Richards" wrote in message
...
It must be turned off if you want to do any serious disk system
performance testing.


That is total BS! - the whole point of system benchmarking is to test
the system "as it will be used" - not in some airy-fairy-land of the
dealer's choice!