Revelation NLM Installation & Follow-up Tips (Installation)
Created at 27 APR 2000 04:52PM
Introduction
This document describes a few of the most important and most common procedures used to avoid and/or correct Revelation NLM problems. In addition, customers may experience errors such as FS461, FS466, FS472, and FS477 following the Revelation NLM installation. In most cases, these errors can be easily avoided by following a few basic precautions. Except where noted, these procedures are generally recommended whether or not one receives these specific FS errors.
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. As the Revelation NLM Installation Guide states, this is not a reliable way to set the frame type. Error messages of FS466, FS472, and FS477 are frequently the results of a mismatch of frame types.
In order to better understand the importance of matching frame types on clients and the server, we have to look at the purpose served by the frame type. According to the Netware 3.12 System Administrator s Reference Guide, the frame type is designed to provide a predictable means for clients and servers to communicate across the network. If frame types do not match, miscommunication may occur, as if the client and server are speaking two different languages.
Novell Netware supports Ethernet frame types: 802.3, 802.2, SNAP, and Ethernet_II. Ethernet_SNAP and Ethernet_II are used for Macintosh and TCP/IP (respectively) and are not supported by Revelation NLM product (which uses the IPX protocol). Frame type 802.3 is used only with IPX/SPX on a NetWare LAN. This frame type was developed before IEEE standards were completed and, according to Novell, is therefore slightly out of compliance and does not include the additional 802.2 reliability and flow control information. Frame type 802.3 is the default for NetWare 2.2 and 3.11 Ethernet LANs. 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.
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. 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.
Setting Network Protocol Order
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 Preferred Protocol by selecting the appropriate tab and entry in the scroll down list.
NLM Upgrade Considerations
When performing a Revelation NLM upgrade or trade up, ensure existing REVPARAM files are deleted, renamed, or edited to setServerOnly=FALSE until after the upgrade is performed. The REVPARAM files will then need to be restored (with ServerOnly set to TRUE) once the upgrade has been completed. If errors persist, you may also need to delete any existing LH.nlm and LHIPXTSR.nlm files during the upgrade.
Advanced Revelation Specific Settings
Because Advanced Revelation is a DOS-based system, there are a number of procedures that must be performed specifically for Advanced Revelation applications. To run Advanced Revelation applications under NLM 5.0, you must verify memory settings are set properly on the application DOS shortcut property. Right click on the Advanced Revelation shortcut, and select Properties, then choose the Memory tab. From the appropriate dropdown menu, set extended (XMS) memory to none , and set EMS to 4096.
Mapping drives through DOS instead of Windows Explorer may also eliminate errors. This may be performed by entering the DOS map command from within the DOS Command Prompt window, followed by the appropriate drive letter and folder name. Consult your DOS documentation for more details on use of the DOS Map command.
During periods of inactivity, PC power management functions may cause a loss of connectivity resulting in application lockup. Display monitor Sleep Options should not be turned on and Background - Always Suspend should not be checked in the application shortcut properties Misc tab. Also within the application shortcut s Misc tab, screensaver should be disabled during Advanced Revelation application DOS session.
Application lockups can occur through timeouts. To correct this, increase the number of retries and time-out variable by setting LHIPXTSR parameters /r and /c, respectively. Also set the corresponding LHIPXSER /m parameter on the server. For further explanations concerning the setting of these variables, query Revelation Software s web site, and refer to the NLM Troubleshooting Knowledge base article.
Miscellaneous Tips
Edit config.sys/config.nt and increase file handlers by setting FILES=200
Verify that the application is not being run from the root directory of a mapped drive. If so, map to parent directory of application directory.
The Revelation 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, as well as the Revelation NLM.
For Novell 4.1x Server, you must load the Turbodis.nlm. For further information, query Revelation Software s web site, and refer to the Likely Cause of NLM GFEs Knowledge base article.
Verify that all Revelation NLM components (workstation, application, file server) have the same version level.