Location of driver: \DOS\E100BODI.COM

Sample Load Commands

CD\NWCLIENT
LSL
E100BODI
IPXODI
CD\

General Instructions

1. From the \DOS directory on the Intel Configuration and Drivers disk, copy LSL.COM, E100BODI.COM, IPXODI.COM, and NET.CFG to a directory on your hard disk called C:\NWCLIENT.

2. Create a batch file, or add to your AUTOEXEC.BAT file the following commands to run before you start Windows for Workgroups:

   CD\NWCLIENT
   LSL
   E100BODI
   IPXODI
   CD\

3. After the ODI drivers are loaded, start up Windows for Workgroups using the /N parameter.

   Example: C:\WINDOWS WIN /N

4. After Windows for Workgroups comes up, select the NETWORK SETUP icon in the Network Group.

5. Click NETWORKS.

6. Select INSTALL MICROSOFT WINDOWS NETWORK and click OK.

7. <Optional> Click SHARING and configure for printer and file sharing and click OK.

8. Click on DRIVERS.

9. If you are replacing a previously installed LAN adapter, click REMOVE to delete that adapter.

10. Click ADD ADAPTER.

11. Select IPXODI SUPPORT DRIVER [ETHERNET] from the Add Network Adapter list and click OK.

12. From the Network Drivers menu, click CLOSE.

13. From the Network Setup menu, click OK.

14. Windows for Workgroups asks if you want to replace the files currently installed with the version you are installing now. Click YES TO ALL.

15. Windows for Workgroups prompts you for Windows for Workgroups Disk 7 & Disk 8 as it updates the files.

16. After the files have been updated, Windows for Workgroups notifies you that it has modified NET.CFG, CONFIG.SYS, SYSTEM.INI, WIN.INI, and PROTOCOL.INI. Click OK.

17. Windows for Workgroups prompts you to reset your computer for the changes to take effect. Click RESTART COMPUTER.

Windows for Workgroups creates the PROTOCOL.INI for you. This sample is provided for reference:

C:\WINDOWS\PROTOCOL.INI

[network.setup]
version=0x3110
netcard=ms$odimac,1,MS$ODIMAC,4
transport=ms$nwlinknb,NWLINK
transport=ms$netbeui,NETBEUI
lana0=ms$odimac,1,ms$netbeui
lana1=ms$odimac,1,ms$nwlinknb

[net.cfg]
PATH=C:\NWCLIENT\NET.CFG

[MS$ODIMAC]

[Link Driver E100BODI]
data=Frame Ethernet_SNAP
data=Frame Ethernet_802.2
data=Frame Ethernet_II
data=Frame Ethernet_802.3

[NWLINK]
BINDINGS=E100BODI

[NETBEUI]
BINDINGS=E100BODI
LANABASE=0
SESSIONS=10
NCBS=12

Windows for Workgroups will modify CONFIG.SYS, AUTOEXEC.BAT, and NET.CFG files for you. These samples are provided for reference:

C:\CONFIG.SYS:

device=c:\dos\himem.sys
device=c:\dos\emm386.exe
stacks=9,256
files=50
buffers=25
device=c:\windows\ifshlp.sys

C:\AUTOEXEC.BAT:

c:\windows\net start
path=c:\dos;c:\nwclient;c:\windows
set temp=c:\windows
prompt $p$g
cd\nwclient
lsl
e100Bodi
ipxodi
c:\windows\odihlp.exe

C:\NWCLIENT\NET.CFG:

Link Driver E100BOD
frame ethernet_802.2
frame ethernet_802.3
frame ethernet_II
frame ethernet_SNAP

Troubleshooting Tips

• Check the version of EMM386.EXE that you are using. You must be using EMM386.EXE v4.49 or later. This version of EMM386.EXE ships with DOS 6.22.

• Make sure that the adapters will pass diagnostics - both on board diagnostics and the network test in SETUP.EXE. If the adapters will not pass network diagnostics, verify your network cable is wired correctly and/or try another network cable. Windows for Workgroups will not run correctly if the network diagnostics do not pass.

• If you are connecting two EtherExpress™ PRO/100B adapters without a hub, you need a special cable called a crossover cable. A crossover cable will have the Transmit and Receive pairs crossed instead of running straight through.

  There is a diagram of a crossover cable included in the information files on the EtherExpress PRO/100B driver diskette. To view the diagram, run SETUP /readme from the Intel Configuration and Drivers diskette, select Hardware specifications and cabling information, and then select 10 Mbps cabling specifications.

  The crossover cable will work for 100B Mbps or 10 Mbps, but is intended for test purposes only and is not a supported cable configuration.

• If the adapters pass network diagnostics but still do not work in Windows for Workgroups, there could be a problem with the file C:\WINDOWS\PROTOCOL.INI. If you have made several attempts to set up networking in Windows for Workgroups, or had another adapter installed before the EtherExpress PRO/100B adapter, it may be necessary to restore the PROTOCOL.INI to the default and then install the driver for the EtherExpress PRO/100B adapter. You can set this file back to default by following these steps:
  1. Start up Windows for Workgroups using the /N parameter.
     Example: C:\WINDOWS WIN /N

  2. After Windows for Workgroups comes up, select the NETWORK SETUP icon in the Network Group.

  3. Click on NETWORKS.

  4. Select NO WINDOWS SUPPORT FOR NETWORKS and click OK.

  5. From the Network Setup menu, click OK.

  6. Windows for Workgroups will notify you that it has modified NET.CFG, CONFIG.SYS, SYSTEM.INI, WIN.INI, and PROTOCOL.INI. Click OK.

  7. Windows for Workgroups will prompt you to reset your computer for the changes to take effect. Click RESTART COMPUTER.

  This process will set the file C:\WINDOWS\PROTOCOL.INI back to default and disable the Windows for Workgroups network. After the workstation reboots, start Windows for Workgroups and reconfigure the Network Setup as described above under General Instructions.

• If Windows for Workgroups fails to detect that the ODI drivers are loaded while running Network Setup, you will receive the following error message when starting Windows for Workgroups:

  "The following errors occurred while loading protocol number 0: error 58: the network has responded incorrectly. You may need to reconfigure the protocol using network setup."

  Because Windows for Workgroups was not able to detect which ODI driver was loaded, it will add the variable "XXXX" to the NET.CFG and PROTOCOL.INI files where it should have specified "E100BODI". When this error occurs, you will need to manually edit the NET.CFG and PROTOCOL.INI that Windows for Workgroups created to match the sample NET.CFG and PROTOCOL.INI shown above.

  Here are the entries that need to be changed:

  1. In the PROTOCOL.INI file, under the section heading [net.cfg], change "PATH=C:\Windows\net.cfg" to "PATH=C:\nwclient\net.cfg".

  2. In the PROTOCOL.INI file, change the section heading [Link Driver XXXX] to [Link Driver E100BODI].

  3. In the PROTOCOL.INI file, under the section heading [NWLINK], change both occurrences of "BINDINGS=XXXX" to "BINDINGS=E100BODI".

  4. In the NET.CFG file, change "Link Driver XXXX" to "Link Driver E100BODI"

  Compare your changes to PROTOCOL.INI and NET.CFG to the sample files provided previously in this document for examples of the correct format and syntax.

• If you choose to add Novell NetWare* support to Windows for Workgroups when selecting Networks, you will be prompted for the following Novell NetWare files:

  NETWARE.DRV, NETWARE.HLP, NWPOPUP.EXE, VIPX.386, VNETWARE.386

  These files are not on the Intel Configuration and Drivers diskette. You can get these files by downloading the self-extracting file, WINDR3.EXE, from Novell*.

This applies to:

Intel® PRO/100B Adapter