1. Log out all users and stop, remove and recreate the linear hash service. This
step must be performed physically on the server. From a command line, change
directories to the Windows 2000 Service folder. Then, stop, remove, and
recreate the linear hash service by typing at a dos prompt in the
c:\revsoft\NTservice folder:

lhsrvc stop
lhsrvc remove
lhsrvc create

2. Slowdown may be the result of loss of "Trusted Status" between client and
server following Revelation Windows 2000 Service install. In general, logging out
the client user, then logging back in will restore this Trusted Status and increase
performance. The following steps accomplish this task.

a. Unmap all of the workstations from the server. From within Explorer menu,
choose "Tools," then "Disconnect network drive," and select the appropriate
drive letter.

b. Reboot the server and workstations.

c. Remap the workstations to the server. From within Explorer menu,
choose "Tools," then "Map network drive," and select the server from the
dropdown list.

d. Launch your application.

Setting Network Protocol Order

Excessive Network protocols can slow down the NT/2000 Service. Therefore, all
unused protocols should be deleted. To remove unnecessary protocols, bring up
Control Panel (from Settings on Start menu), and then double click
on "Network." Under the "Configurations" tab, select the protocol you wish to
delete, and click on the "remove" button.

Background processes

Background processes such as anti-virus software and backup software may
cause slowdowns during application execution. Performance improvements may
be obtained by shutting these applications down during execution of your
application. For anti-virus software, we suggest you specify that the .ov linear
hash files not be examined for viruses. The anti-virus software frequently
confuses .ov files with .ovi files, which are frequently a source of viruses. Power
Management may also be turned off.

Server:

1. REVPARAM file: The Revparam file should be placed only the DM, DMW,
DOCAPPR, and LENDER directories on the server. The service will attempt to
control all directories where the Revparam file is located in. The database files
only exist in those directories and should be the only files that the service
controls. When using the Revparam file to work with the NT/2000 Service, it
need only contain the following: ServerOnly=true

2. Make sure the NT/2000 Service (listed as Linear Hash) has been started and
is automatic on the server. This can be checked from the server's Services
dialog box (Control Panel->Services) or from the c:\revsoft\NTservice folder on
the server using lhsrvc.exe (the linear hash service executable) by typing:
lhsrvc status from the working folder's command line.

3. Make sure that the System User has been added to any and all
directories/files for which the NT/2000 Service will be utilized, specifically the
DSI folder. This is the operating system user and can be added to this folder.
Make sure that this user has FULL rights and the 'replace permissions of
subdirectories' and 'replace permissions on existing files' are checked while
adding the SYSTEM user account.

Client:

1. Try to run as FEW protocols as possible on workstations that will be utilizing
the NT/2000 Service. The Service uses named pipes, which can be commuted
via NetBEUI, TCP/IP protocols. The NT/2000 service works fastest in the
following order NetBEUI > TCP/IP > IPX/SPX. Multiple protocols will impact
performance with each additional and/or unnecessary protocol stacked. Banyan
Vines protocol has proven to cause FS1019 errors in many cases and is not
recommended for use with the NT/2000 Service.

2. Edit the system Config file to increase the file handlers to a value greater
than 100, but less than 254 (the maximum file handlers). For DOS FAT formatted
hard drives, the config file is called C:\config.sys. For Windows NT NTFS
formatted hard drives, the config file is called C:\config.nt. Open up your config
file with notepad, and insert the line:

Files=200

3. Currently (as of 03/29/2000), there is an issue with running the NT/2000
service on a server with Service Pack 5+ and Windows NT/2000 workstations
with Service Pack 6. This issue does not exist with Windows NT/2000 Server
Service Pack 6 running the NT/2000 service and Win2000 Professional
workstations.