Novell Specification 3.3 32-bit ODI driver
E100B.LAN Version 1.47
Files contained in this archive:
E100B.LDI 11,489 06-19-96
E100B.LAN 43,313 06-20-96
E100B.INF 11,859 07-03-96
Note: This driver is not for use as a NetWare* Server Driver on v4.10 or below, unless the NetWare server NLMs have been updated to the v3.30 Assembly Specification. Also, be sure that v3.12 and v4.x servers have been updated with latest operating system patches from Novell.
Refer to the appropriate section for either the Windows* 95 or DOS/Windows v3.1x Client 32 installation.
General installation of Client 32 with Windows 95
The Novell archives used for this installation were:
C3295N_1.EXE v2.1 02/05/96
C3295D.EXE 07/19/96 (latest patch)
- Microsoft's Windows 95 operating system installed.
- NetWare Client 32 for Windows 95 archive file and patch have been extracted onto the computer's hard drive.
- Access to the Windows 95 CD or CAB files, since the Client 32 installation will ask for it.
Hints and tips for Client 32 in Windows 95
- Copy the supplied E100B.INF and E100B.LAN onto a diskette.
- Open the Network configuration screen (My Computer » Control Panel » Network » Configuration). Look for any reference to the Intel EtherExpress PCI adapter. Highlight each one with the mouse and click Remove. When all instances of the adapter are gone, click OK and allow the machine to restart.
- As Windows 95 is restarting, it may display the message "Windows has found new hardware and is installing software for it." Select the option labeled Do not install a driver (Windows will not
prompt you again), and then click OK.
- Open the Device Manager (My Computer » Control Panel/System » Device Manager). Look for an entry labeled OTHER DEVICES. If it exists, double-click on it. If it lists an entry labeled PCI ETHERNET CONTROLLER, click it once and click Remove.
- Run the SETUP.EXE program for Client 32. It is located in the \ENGLISH subdirectory of the Client 32 software.
- On the NetWare Client 32 Installation screen, do not check the option to upgrade NDIS drivers to ODI automatically. Select Start.
- Select the have disk option on the Select Device screen. Enter the drive and directory where the E100B.LAN and E100B.INF files are located.
- Highlight the correct selection for the adapter you have installed, PRO/10+ PCI or PRO/100B PCI adapter, and select OK.
- On the Recommended NetWare Client 32 properties screen, set the appropriate settings for the version of NetWare you are using.
- The Client 32 installation program will copy files. It may ask for the source of the Windows 95 installation files. Click OK and then enter the correct path to the files.
- The Client 32 installation will finish, and you must restart in order for the changes to become effective.
General installation of Client 32 with DOS/Windows 3.1x
- Message - Module c:\novell\client32\e100b.lan did not remain resident:
Occasionally on restarting Windows 95 after the Client 32 installation, this NetWare Alert message appears. If you click on ok, another message says that "The hardware configuration conflicts E100B.LAN-NW-Adapter 0-Board-0". The ODINSUP device did not load properly (Device Manager doesn't show it under Network Adapters). Shut down the system and reboot. This action should load ODINSUP successfully.
- PRO/10+ PCI adapter driver loads indicating it is a PRO/100B adapter:
If a problem occurs loading the driver, the driver may default to indicating it is a PRO/100B. This condition will not cause any problems since these two adapters use the same drivers. The only consideration to be aware of is if any advanced settings have to be made for the adapter. Speed is not a valid option for the PRO/10+ PCI, and it will always operate at 10mbps. The Force Duplex option defaults to Auto-negotiate which isn't supported on the PRO/10+ PCI. It will operate in half duplex. If you need Full Duplex, set it specifically for Full.
The Novell archive used for this installation was: DW32N1.EXE v2.1 06/25/96
Hints and tips
- From the Novell NetWare Client 32 software, run INSTALL.EXE.
- Select the NetWare Client 32 products you want to install on your workstation from the list:
- [X] NetWare Client 32 for DOS
- [X] NetWare Client 32 for Windows
- [ ] NetWare TCP/IP protocol stack
- [ ] NetWare IP (TCP/IP Required)
- [ ] Desktop SNMP
- [ ] HOSTMIB for SNMP (SNMP Required)
- [ ] NetWare TSA for SMS
Note: "NetWare Client 32 for DOS" and "NetWare Client 32 for Windows" are usually selected by default.
- From the Customize Support for Windows menu, specify if you want to use multiple country codes or if you want to set the shared Windows path. The default for both of these is NO.
- From the Select LAN Driver Type menu, select 32-bit LAN drivers.
- From the 32-Bit Network Board Drivers menu, select USER SPECIFIED 32 BIT DRIVER.
- From the Insert the Driver Disk menu, insert the disk with the Intel EtherExpress E100B.LAN and E100B.LDI, and then specify the path to those drivers.
- From the 32-Bit Network Board Drivers menu, select either the Intel EtherExpress™ PRO/10+ LAN Adapter or Intel EtherExpress™ PRO/100B LAN Adapter, depending on which adapter you have installed.
- OPTIONAL: Specify the following settings for the Intel EtherExpress LAN adapter:
Speed (100B only)
0 (auto detect)
0 (auto negotiate)
Note: The default settings will work for most installations. If you use multiple frame types, please see Hints and Tips section below.
- From the Installation Configuration Summary, verify the default settings for Client 32 are correct, or modify as necessary.
Modify AUTOEXEC.BAT and CONFIG.SYS [YES]
LAN driver type:
32-bit LAN drivers
Intel EtherExpress™ PCI Adapters
- Novell NetWare will now copy the files to your workstations and modify the configuration files to match your selected configuration.
- If you are using multiple frame types, you will get the following message when you load the driver:
- "Do you want to load another frame type for a previously loaded board? Y/N ".
The way to avoid this is to add the slot number to the load line for the driver in the STARTNET.BAT (by default it is located in the
\NOVELL\CLIENT32 directory). The only way to determine the slot number Novell is expecting is to put an invalid value on the load line. For example (the load line should be all on one line):
LOAD C:\NOVELL\CLIENT32\E100B.LAN SPEED=0 IOMAPMODE=0
FORCEDUPLEX=0 FRAME=ETHERNET_802.2 SLOT=eu
When you next reboot, you will be prompted with the correct value. Modify the STARTNET.CFG again, and use that value. If the slot
is not specified correctly, only the first frame type will load.
- Check for a LASTDRIVE statement in the CONFIG.SYS file. You must have LASTDRIVE=Z in config.sys when using Client 32.
- Verify that you have FIRST NETWORK DRIVE = F in the NET.CFG file under the NetWare DOS Requester section.
Note: NET.CFG is position sensitive, so be careful to indent lines with one space or one tab as shown above in the example.
- Verify that the EtherExpress adapter passes the diagnostics test by running SETUP.EXE on the EtherExpress driver disk. If the adapter fails diagnostics it will not function correctly running Client 32.
Below are sample files from a Novell NetWare Client 32 workstation with a EtherExpress adapter installed using the default installation:
LOAD C:\NOVELL\CLIENT32\E100B.LAN SPEED=0 IOMAPMODE=0 FORCEDUPLEX=0 FRAME=ETHERNET_802.2 SLOT=2
LOAD C:\NOVELL\CLIENT32\E100B.LAN SPEED=0 IOMAPMODE=0 FORCEDUPLEX=0 FRAME=ETHERNET_802.3 SLOT=2
Note: If you are loading multiple frame types, you will need to specify the slot number of the adapter on the load lines. See Hints and Tips section above for detailed information.
NetWare DOS Requester
FIRST NETWORK DRIVE F
NETWARE PROTOCOL NDS BIND
IPX SOCKETS 40
This applies to: