NT Registry Settings

Incorrect registry settings due to compatibility problems with NETBIOS protocal settings in the NT operating system may cause errors and data corruptions. Microsoft admits to these possible error messages and problems:

The file is in use
The file is already open
Unable to write to drive X:
The network drive X: is no longer available

Other possible problems may include: data corruption, application failure, access denied messages, network device does not exist messages, and read errors.

As per Microsoft recommendations these registry settings are recommended when running CAPITAL on an NT based network:

Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft does guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD).

Perform the following steps to disable opportunistic locking and caching of open files:

Start Registry Editor (Regedt32.exe) and go to the following subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

On the Edit menu, click Add Value and add the following:

Value Name: EnableOplocks
Data Type: REG_DWORD
Data: 0

Value Name: CachedOpenLimit
Data Type: REG_DWORD
Data: 0

Value Name: autodisconnect
Data Type: REG_DWORD
Data: ffffffff

Shut down and restart the computer.

18/12/01