NLM Speedup Instructions

***Client Settings

Errors can occur due to problems with Network Protocols. 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. Repeat this procedure until all unneeded protocols are
deleted. Another important Protocol tip is to make sure that the IPX protocol is
first in the protocol order (on top of IP) of Novell client protocol preferences. If
IPX is not on top, remove all current protocols (as mentioned above) and
reinstall (click on "add" button) on top of IPX. You should also choose IPX as
the "Default Protocol" by selecting the Advanced Tab on the properties screen.

The method for setting frame types will vary depending on type of machine. To
set frame type on Win95/98 workstations, press the Start Button, open Control
Panel, click on the Network icon, and select the Configuration tab. You may have
either IPX/SPX-compatible, or IPX-32 bit Protocol, or both. For IPX/SPX-
Compatible, select "IPX/SPX-Compatible Protocol" from the installed network
components list, and then click on Properties. From the Protocols Properties
window, select "Frametype" and enter the correct frame type. [Click OK on both
windows to save and exit]. For IPX-32 bit Protocol, select "IPX-32 bit Protocol for
the Novell Network Client" from the installed network components list, then click
on Properties. From the Protocols Properties window, select "Frametype" and
enter the correct frame type [Click OK on both windows to save and exit].

For Windows NT workstations, press the Start Button, open Control Panel, click
on the Network icon, and select the Configuration tab. Select the correct frame
type from the scroll down list.

***Miscellaneous Tips
a. Edit config.sys(config.nt for NT/2000 based machines) and increase file
handlers by setting "FILES=200"

b. Verify that the application is not being run from the root folder of a mapped
drive. If so, map to parent folder of application folder.

Launch the NETDRV.EXE utility from your DSI\DMW folder.

In the section titled "OpenInsight Network Driver Information", you should see
IPX/Netware Multiuser Driver. In the Available Drivers section you will see a
highlighted driver - disregard this, the active driver is the one specified above.

If you see any other driver (All Network Driver, Byte Range Lock, etc.) you must
change the driver.

***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.

The NLM is not compatible with Novell Intranetware Client32 version 3.1 with any
of the client support packs. If you have Novell Intranetware Client32 version 3.1
with a client support pack installed on your workstation, you must remove this
client along with support packs and reinstall the Novell Intranetware Client32
version 3.1 without support packs. The Novell Client 32 version 3.2 is not
supported. Your best bet will be to load the Client 32 version 3.3. This version
is fully supported, and should not pose any problems.

***REVPARAM File
To create the REVPARAM file, follow these steps:
a. Create a new text file, and type the following for its contents:
ServerOnly = True

Save the file as REVPARAM (do not use an extension).

Copy the REVPARAM file that you have created into the DM, DMW, DOCAPPR,
LENDER folders in the DSI folder on the server.

***Server Settings

Setting Frame Types
It is important that one does not make any assumptions regarding the frame
type on the Novell Server, or trust that setting frame type to "auto" on the
workstation will automatically set the correct frame type. Error messages of
FS466, FS472, and FS477 are frequently the results of a mismatch of frame
types.

Frame type 802.3 was developed before IEEE standards were completed and,
according to Novell, is "therefore slightly out of compliance" and "does not
include flow control information." The 802.2 frame type is fully IEEE compliant
and is the default frame type for Netware 3.12 and 4.x. Although it is possible to
allow support of both 802.2 and 802.3 frame types simultaneously, Novell
recommends against this. All workstations and servers should use the same
frame type.

To set frame types on the Novell Server, you would enter a command of the
following form on the server console:

LOAD NE# INT=# PORT=# FRAME=ETHERNET_802.2 NAM=ETHERNET8022
BIND IPX TO ETHR8022 NET=#

For details on setting parameters, consult Novell documentation.

***Routers
If you have a router on your network, you must configure the router to allow the
SAP (Server Advertising Protocol) broadcast message to get through. The SAP
number is Ox5B8.

If you still have error messages, or slow performance in DocMagic. You can
modify the autoexec.ncf file in the SYSTEM folder, replace LHSTART with:

Load LH.NLM /s: #.
Load LHIPXSER.NLM

The number on the /s: parameter should be between 1 and 16, the default being
16 if the parameter is not specified. This parameter changes the NLM?s priority
on the Server. The lower this number is the better the performance of the NLM,
but it will decrease NetWare?s response time to service other requests. If you
get the message Error FS466 ?No Server Response? this parameter is set too
low.

Adding additional RAM to the NetWare server generally improves the overall
performance of the server and may significantly improve the performance of the
Revelation NLM.