Additional Software Required for TCP/IP and/or MCP/IPX

As mentioned above, Novell’s 16- and 32-bit protocol stacks require additional supporting modules to access network drivers installed on the machine. 16-bit protocol stacks use the same supporting modules, as do 32-bit protocols stacks. If both TCP/IP and IPX are in use, the protocol stacks should be of the same form: 16-bit IPX with 16-bit TCP/IP, or 32-bit IPX with 32-bit TCP/IP. (Mixing 16- and 32-bit protocol stacks is theoretically possible, but there is no practical reason or advantage to doing so, and the configuration is overly complicated.)

Novell's 16-bit protocol stacks require two additional software modules: LSL.COM and a 16-bit ODI-compliant driver for each active network adapter installed in the machine. (Normally there is only one network adapter in a machine, but there can be more).

The 32-bit protocol stacks require several supporting modules, including LSLC32.NLM and a 32-bit ODI-compliant driver for each active network adapter installed in the machine. (32-bit protocol stacks can utilize existing 16-bit ODI drivers if 32-bit ODI drivers are not available, but this configuration is complicated.)

The Link Support Layer (LSL), formed by LSL.COM or LSLC32.NLM, standardizes service collection. The LSL enables protocol stacks to send and receive network data without concern for the underlying hardware. Even more importantly, the LSL allows both protocol stacks to share access to a single network adapter. (For advanced installations, the LSL also facilitates the use of multiple network boards in a single machine.)

An Open Data-Link Interface (ODI) driver implements the standardized services of the Link Support Layer for a particular make and model of network adapter. Every network adapter manufactured today has a 16-bit ODI-compliant driver available. 32-bit ODI drivers are usually available as well, as they are the same drivers used to support Novell's 32-bit Netware Servers. If a diskette containing the driver(s) does not ship with the adapter itself, the driver(s) are available from the manufacturer, usually via BBS (Bulletin Board Service) or Internet download.