Universal Thread # 825413 Message ID 826511

I realize that the original message to which I am responding is from September, 2003, so if bells don't go ringing, I won't be surprised.

In the message to which this is a reply, Doug made a quote "We always tell our users to turn write caching off".

Where I am working on contract, we are having a problem which appears to be connected in some way to a "corrupt" index. When set to a particular tag, even browse will not allow getting past a record, we call it "the" record, since it is the last transaction the user sees as the machine locks up, trying to retrieve the next record in the index order.

In researching the problem, your suggestion came the closest to a potential answer that we have found to date. The problem with the potential answer is that we do not know how to turn off write caching for a network volume.

KB # Q259716 walks us through "Enabling or Disabling the Disk Write Caching". In doing this at a work station ( personal computer ), we only see the local hard disks. This is not where our data resides.

1) Are you suggesting that users turn off write caching on their Windows 2000 / 2003 servers ?

2) Do you have any further evidence to present to the customer IT staff, should we approach them with a suggestion to touch "their" server?

Thanks in advance for any help you can provide with this problem.