Hi Jim,
We have talked about the complexity of the redirector, read/write caching and oplocking previously, as to whether MS will ever get it right, hopefully they will.

The problem is every time there is a security patch/update the performance/reliability changes, which makes it difficult NOT to recommend disabling it all, but I have been told in no uncertain terms that the new flush commands in VFP9 will fix it, that is why I am still testing, with no recommendations at present.

With UPS's being that cheap these days the need for an expensive HD adapter have dropped somewhat, especially when most have inbuilt power filtering as well, which overcomes the memory corruption errors etc of the old days.

With the problem you experienced with the XP loss of edits problem with MS Word with the write caching enabled, I have found it has a lot to do with the quality of the hardware components i.e. higher error rates with entry level components & virtually non existent with high end components.



>Hi Neil,
>
>I'd say that it should always be off, and not just for VFP applications, unless the HD adapter is the expensive type designed to retain the data after a sudden power stoppage auto-complete the writes during reboots.
>
>cheers
>
>>Hi,
>>Below VFP9 yes, with VFP9 you can (supposedly) use the new Flush commands, we are still testing, so I can't confirm.
>>
>>>Can't remember what was the reasoning behind the recomendation to turn write-behind caching off on a VFP file-server (and workstation?).
>>>Is it still there? For all OS?