We have just moved both our OI and AREV system from Novell to NT Server have applied servic pack 1.5 and performance is still appauling.

We have looked through the previous discussions on this subject (which seems at times contradictory), how critical is the file REVPARAM and if it is critical can anyone post a copy of an optimised example

It is critical that you have the REVPARAM file and a copy of the same file in all directories/subdirectories, containing the Linear Hash Filesfiles with extensions *.ov & *.lk

The REVPARAM file should say SERVERONLY=1

This file when placed in the directories will not let anyone access the application/data files on the server, if the NT Service is not running. Running the application without the REVPARAM file would mean by-passing the NT Service alltogether and you will not get the performance benefits of the service and it also may cause GFEs to take place.

As you have converted from NOVELL to NT and if you were using the NLMs previously, make sure you do not have the following files on your NT machine: LH.NLM, LHIPXTSR.NLM. If these files exist, delete them maually.

If you run AREV from a shortcut, make sure you allocate 4096 EMS memory, to it.

Here are some tips to speed up the NT Service.

It is important that the server be up when the workstations reboot, and that the workstations are not logged into the server at the time of reboot.

*Make sure you do not have PROTOCOLS stacked, use as few as possible!

1a)If you have a DOS FAT formatted hardrive:

 Check the "files= parameter in all workstations config.sys    -files. 

 The number of files should be over 100.

 Try using "files=101".

1b)If you have a Windows NT NTFS formatted hardrive:

 Check the "files= parameter in all workstations config.NT files.

 The number of files should be over 100.

 Try using "files=101".

2) Log out all users and stop the service (lhsrvc stop).

 Remove the service (lhsrvc remove).

 Recreate the service (lhsrvc create).

3) Unmap all of the workstations from the server.

4) Reboot the server.

5)Reboot the workstations.

6)Remap the workstations to the server.

This usually will fix most of the NT server slowdowns.

Tony,

Also make sure you don't have a 3D screen saver on the Server.

Tim

View this thread on the Works forum...