Windows 95/98/Me


System Key: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\FileSystem]
Value Name: DriveWriteBehind
Data Type: REG_BINARY (Binary Value)
Value Data: (00 00 00 00 = disable, 01 00 00 00 = enable write behind)


Windows NT

Start Registry Editor (Regedt32.exe) and go to the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters
Click Add Value on the Edit menu.
Enter the following:
Value Name: UseWriteBehind Data Type: REG_DWORD
Data: 0 1-true 0-false (default: 1) UseWriteBehind - Enables the write-behind optimization for write Only files.

Go to the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
\Lanmanworkstation\parameters

Click Add Value on the Edit menu.
Enter the following:
Value Name: UtilizeNTCaching Data Type: REG_DWORD
Data: 0 1-true 0-false (default: 1) UtilizeNTCaching - Indicates whether the redirector uses the cache manager to cache the contents of files. Disable this parameter only to guarantee that all data is flushed to the server immediately after it is written by the application.


Windows 2000/XP see:

http://support.microsoft.com/default.aspx?kbid=332023

For opportunistic locking see:

http://support.microsoft.com/default.aspx?scid=kb;en-us;296264



>We have a large app on a winNT4 server that is read/write from many pc's of these OS's... 95/98/NT/2K/XP.
>
>We have a lot of table locking issues. errors 1, 13, 1705, 111, 41, 3, 1104, etc.
>
>Based on reading here and on the net, we have found that disabling OPLOCK setting in the registry of the winNT4 server has greatly reduced these errors!!! But they have not disappeared.
>
>Based on more reading, it seems like the next step is to disable WRITE CACHING/OPLOCK settings on the CLIENTS. The fun thing mentioned is we have 95/98/NT/2K/XP clients.
>
>DOES anyone know if disabling these settings on the client helps prevent these table locking issues?
>
>NEXT.. HOW do I do this!! Exact registry lines would be perfect. I just can't find any 'one answer solution' on this stuff.
>
>THANK YOU!