Connecting Workstations to Netware Servers Using Client 32

This page provides information about:

Overview of Client 32

Client 32 is Novell's current NetWare client architecture. It is based on 32-bit networking components (drivers, protocol stacks and clients) and allows 32-bit HSM drivers, such as CMDGODI.LAN to be loaded on client workstations as well as NetWare servers.

At the heart of Client 32 is the NetWare I/O subsystem (NIOS). This software layer provides partial NetWare operating system emulation and acts as a loader for NLM format executables such as LAN drivers. It provides the interface between the host operating system and the 32-bit networking components.

Client 32 for DOS/Windows 3.x

This release of LSS supports DOS Client 32 with the CMDGODI.LAN driver for use in Novell NetWare environments.

Under DOS, NIOS is implemented as a single executable called NIOS.EXE. An extended memory (XMS) manager, such as HIMEM.SYS, must be loaded prior to loading NIOS. Once NIOS.EXE is loaded the "LOAD" and "UNLOAD" keywords may be used at the command prompt to dynamically load and unload NLMs (including .LAN drivers and protocols) in extended memory.

The use of extended memory (memory above 1Mb) means that the sub-1Mb memory footprint of Client 32 under DOS is very small, typically around 4Kb. NIOS will use upper memory blocks (UMBs) if they are available in preference to conventional memory. UMBs are blocks of memory allocated by a memory manager, such as EMM386, in the 640Kb-1Mb region. To make UMBs available, a memory manager must be loaded and the "DOS=UMB" command must be added to CONFIG.SYS.

Refer to your memory manager documentation for more details. 16-bit ODI drivers can be used in the Client 32 environment. A 16-bit ODI driver is loaded as normal into conventional memory and the Novell provided 32-bit virtual LAN driver, PC32MLID.LAN, is used to allow protocols executing in 32-bit protected mode to communicate with the 16-bit driver. This configuration is not recommended - 32-bit ODI drivers give greater performance and conventional memory savings.

Novell provide IPX and TCP/IP protocol support with IPX.NLM and TCPIP.NLM.

The client requester, Client 32.NLM, is used to provide access to NetWare network services. The Client 32 requester is backwards compatible with the NETX and VLM APIs so existing NetWare applications should still function. Client 32.NLM supports packet burst transfers for increased performance, file caching and NetWare Directory Services (NDS) functionality.

Client 32 for Windows 95

The Client 32 protocol stack and requester for Windows 95 replaces the NetWare client provided by Microsoft.

Previously Novell supported the use of 32-bit HSM drivers with Client 32 for Windows 95. They now recommend that you use an NDIS 3 miniport driver. Therefore, we recommend that you install MDGMPORT.SYS.

Installing Client 32

  1. Install the adapter hardware into the PC (see Installing PCI Adapters or Installing CardBus, PCMCIA, or PC Card Adapters, as appropriate)

  2. Install the driver software (see Installing MDGMPORT.SYS)

  3. Run the Client 32 install program following the documentation provided by Novell. During this installation, Client 32 will detect the adapter is installed and you can complete the installation without selecting a driver.

See Also: