Server Driver for NetWare 4.11 v3.04 NetWare* 4.11 Server Driver Installation Notes for Intel's EtherExpress(TM) PRO/10 ISA LAN Adapter ========================================================== Location of Driver: \NWSERVER\EPRO.LAN IMPORTANT: NetWare servers using the 3.30 specification NLMs require a Plug and Play configuration manager to be loaded in order to configure Plug and Play enabled ISA adapters. If you don't use a configuration manager, you MUST DISABLE PLUG AND PLAY on the PRO/10 ISA adapter. Use SoftSet2 to disable Plug and Play on the adapter. From the main menu of SoftSet2, choose Change Adapter Configuration, Advanced Option Menu, and set Plug and Play to Disabled. Also, note the I/O Address of the adapter. This information will be needed later. Sample Load Commands -------------------- If a Configuration Manager is loaded and Plug and Play is enabled on adapter: LOAD EPRO SLOT=xxx FRAME=ETHERNET_802.2 BIND IPX TO EPRO NET=xxxxxxxx Without a Configuration Manager and with Plug and Play disabled on adapter: LOAD C:\EPRO PORT=xxx FRAME=ETHERNET_802.2 BIND IPX TO EPRO NET=xxxxxxxx General Installation -------------------- 1 If you are performing a new installation of NetWare 4.11, configure the LAN adapter(s) using SoftSet2 and make note of the I/O address. During the installation of 4.11, you will be prompted for the LAN driver. At that time insert the LAN adapter driver disk and complete the information NetWare 4.11 requires. The NetWare 4.11 installation program will automatically add these statements to your AUTOEXEC.NCF file. Note: NetWare 4.11 also ships with a driver for the PRO/10 ISA adapter which you may select instead of using the driver disk. 2 We recommend you get the most recent updates of the NLMs listed below. Earlier versions may not work properly. These files can be obtained from Novell's on-line services. See the Hints and Tips section for notes on contacting Novell. MSM.NLM ETHERTSM.NLM 3 If you already have NetWare 4.11 installed, copy the PRO/10 ISA server driver, and any updated NLMs, to the NetWare server's hard drive. If you can't log in to the server, then before starting the server, copy the EPRO.LAN driver from the \NWSERVER directory on the Intel Configuration and Drivers disk to the server's hard drive. Also, copy any updated NLMs to the same directory. If you can log into the server, copy the driver and any updated NLMs to the SYSTEM subdirectory. If you do this, you won't need to specify a path on the server's load line. If you copy it to another directory, make sure the LOAD statement includes the correct path. 4 Bring up the server. At the server console issue the load and bind statement(s) as required. ETHERTSM and MSM will be autoloaded with the EPRO.LAN driver. See the example above and substitute "xxx" with valid parameters for that adapter. PORT=x specifies the I/O address. Substitute x with the valid value for the adapter. You will be prompted with a valid port number if you don't specify a number. SLOT=x specifies the Plug and Play slot ID. Substitute x with the valid value for the adapter. You will be prompted with a valid slot number if you don't specify a number. NET=xxxxxxxx is the unique network address for that LAN segment. The default frame type is 802.2. If your workstation needs to use the 802.3 frame type, see the section later in this document about using multiple frame types on one adapter. 5 Add the load and bind statements you need to the server's AUTOEXEC.NCF file so the EtherExpress PRO/10 ISA adapter driver will load automatically each time the server starts. Hints and Tips -------------- 1 Installing multiple EtherExpress PRO/10 ISA adapters If you have multiple LAN adapters in a single server, each adapter must have a different network number and a different port number. You may also want to name each adapter for ease of management. Example: LOAD C:\EPRO PORT=300 NAME=LAN_A BIND IPX TO LAN_A NET=222 LOAD C:\EPRO PORT=320 NAME=LAN_B BIND IPX TO LAN_B NET=333 2 Installing one EtherExpress PRO/10 ISA adapter with multiple frame types When binding multiple frame types to one adapter, enter a load and bind statement for each frame type. Each load statement will use the same port number, but a different network number is required on the bind statement. You need to supply a name on each load line to avoid being prompted for which board to bind IPX to. If you do not have the name option in the AUTOEXEC.NCF, it will not execute completely without user intervention. Example: LOAD C:\EPRO PORT=300 FRAME=ETHERNET_802.3 NAME=LAN8023 BIND IPX TO LAN8023 NET=77777 LOAD C:\EPRO PORT=300 FRAME=ETHERNET_802.2 NAME=LAN8022 BIND IPX TO LAN8022 NET=88888 3 For updated NLMs, download LANDRx.EXE (x being the latest offering) from one of Novell's services: Novell BBS: 801-221-5197 World Wide Web: WWW.NOVELL.COM * Third-party trademarks are the property of their respective owners.