----------------------------------------------------------------------------- Installing the NetWare 3/4 ODI Server Driver on NetWare 3 Servers ----------------------------------------------------------------------------- This \NOVELL\SRVODI\3_1X subdirectory contains the following files: README.TXT - This file. MSM31X.NLM - Novell Media Support Module for NetWare 3 and NetWare SFT III 3.11 servers (v2.50). LSLENH.NLM - Novell Link Support Layer (LSL) chaining and filtering enhancement module (v1.01) that is loaded on NetWare 3.11 servers prior to loading MSM31X.NLM. PATCHMAN.NLM - Novell Patch Manager for NetWare 3.11 servers (v2.30). Required for LSLENH.NLM. ***TRADEMARKS*** DEC, Digital, and DECpc are trademarks of Digital Equipment Corporation. Novell, NetWare, and LAN WorkPlace are registered trademarks and NetWare Loadable Module, NLM, NetWare MultiProtocol Router, and NetWare SFT are trademarks of Novell, Incorporated. Section 1 INSTALLING THE NETWARE 3/4 ODI SERVER DRIVER ON NETWARE 3 -------------------------------------------------------------------- You can install and use the NetWare 3/4 ODI server driver on NetWare 3 file servers by loading some operating system patches and driver support files in addition to the driver. To install the NetWare 3/4 ODI server driver on a NetWare 3 file server, perform the following six steps: I. Verify that the network interface card (NIC) is properly configured and installed. Refer to your adapter documentation for instructions. II. Copy the NetWare 3/4 ODI server driver files to either a DOS partition (Step IIA.) or a NetWare partition (Step IIB.) of your NetWare server hard disk. NOTE The LSLENH.NLM patch should only be installed and loaded on NetWare 3.11 servers. NetWare 3.12 does not require this patch. A. To copy the files to a DOS partition, enter the following commands: 1. If installing on either NetWare 3.11 or NetWare 3.12: COPY A:\NOVELL\SRVODI\DEPCA.LAN C:\ COPY A:\NOVELL\SRVODI\ETHERTSM.NLM C:\ COPY A:\NOVELL\SRVODI\3_1X\MSM31X.NLM C:\ 2. If installing on NetWare 3.11 only, copy the following additional files: COPY A:\NOVELL\SRVODI\3_1X\LSLENH.NLM C:\ COPY A:\NOVELL\SRVODI\3_1X\PATCHMAN.NLM C:\ You may substitute C:\ with another DOS partition and subdirectory. B. To copy the files to a NetWare partition, you need to use the NetWare 3.x Command Processor (NWSHELL). Contact Novell for information on acquiring NWSHELL.NLM. Once you have NWSHELL.NLM, perform the following steps to copy the files: 1. Load the NetWare 3.x Command Processor (NWSHELL.NLM) by entering the following command at the server System Console prompt: :LOAD NWSHELL 2. Change to the SYS:SYSTEM directory by entering the following command: CD SYS:SYSTEM 3. Copy the driver files to the current directory by entering the following commands: a. If installing on either NetWare 3.11 or NetWare 3.12: COPY A:\NOVELL\SRVODI\DEPCA.LAN COPY A:\NOVELL\SRVODI\ETHERTSM.NLM COPY A:\NOVELL\SRVODI\3_1X\MSM31X.NLM b. If installing on NetWare 3.11 only, copy the following additional files: COPY A:\NOVELL\SRVODI\3_1X\LSLENH.NLM COPY A:\NOVELL\SRVODI\3_1X\PATCHMAN.NLM 4. Enter "exit" to log out of the session then press any key to return to the System Console prompt. III. Perform substeps IIIA. and IIIB. to configure the NetWare 3 server to use the NetWare 3/4 ODI server driver. A. You can automatically load the server driver by adding the appropriate instructions to the AUTOEXEC.NCF file. You can also issue these commands directly from the System Console. 1. While still in the INSTALL program, select "Edit AUTOEXEC.NCF file." Add the following lines to AUTOEXEC.NCF to automatically load and bind the new driver every time the server is brought up: NOTE The "slot," "frame," and "net" values given below are examples. The slot number is the physical slot number in which the DE422 (in this example) was installed. The frame type is one of the four supported frame types "ETHERNET_802.2", "ETHERNET_II", "ETHERNET_SNAP", or "ETHERNET_802.3" frame types. The net address is the external network address. Refer to the Novell NetWare documentation on "Bind" for more information. a. If you installed the driver files on NetWare 3.12 using Step IIA1., enter the following commands: LOAD C:\DEPCA slot=4 frame=ETHERNET_802.2 BIND IPX TO DEPCA net=00000001 b. If you installed the driver files on NetWare 3.11 using Steps IIA1. and IIA2., enter the following commands: LOAD C:\LSLENH LOAD C:\DEPCA slot=4 frame=ETHERNET_802.2 BIND IPX TO DEPCA net=00000001 c. If you installed the driver files on NetWare 3.12 using Step IIB3a., enter the following commands: LOAD DEPCA slot=4 frame=ETHERNET_802.2 BIND IPX TO DEPCA net=00000001 d. If you installed the driver files on NetWare 3.11 using Steps IIB3a. and IIB3b., enter the following commands: LOAD LSLENH LOAD DEPCA slot=4 frame=ETHERNET_802.2 BIND IPX TO DEPCA net=00000001 A drive path is not included for the load statements in the third and fourth examples. This is because the DEPCA.LAN driver files are copied to the SYS:SYSTEM directory, which is the NetWare 3.1X default server path. In the above examples, note that LSLENH.NLM is only loaded under NetWare 3.11. Also, note that PATCHMAN.NLM is auto-loaded when loading LSLENH.NLM. Similarly, loading DEPCA.LAN auto-loads ETHERTSM.NLM which in turn auto-loads MSM31X.NLM. This allows for fewer load statements in the AUTOEXEC.NCF file and less opportunity for driver load errors. NOTE Before saving the AUTOEXEC.NCF file, it is important to verify that no older NetWare 3 server drivers are loaded prior to loading LSLENH.NLM and/or MSM31X.NLM. Even though older NetWare 3 server drivers do not require the LSLENH patch or MSM31X, unexpected behavior may result if LSLENH or MSM31X are loaded after the driver. If using both older NetWare 3 and newer NetWare 3/4 server drivers, be sure to load LSLENH.NLM and MSM31X.NLM separately before loading any drivers. e. Save the file with the changes. Answer "Yes" to the exit prompt. IV. Shut down the server by entering "DOWN" at the system console and then enter "EXIT" to return to the DOS prompt. V. Follow the instructions in your adapter documentation for connecting the controller to the network. VI. Restart the server with the ODI server driver. Enter the following command at the DOS prompt: SERVER The changes made to the STARTUP.NCF and AUTOEXEC.NCF files in step III above take effect.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.