1. intelpro.exe Driver
2. NWWFW311.TXT File Contents

NWWFW311.TXT Driver File Contents (intelpro.exe)

   Windows for Workgroups 3.11 with ODI
                                                                    v1.00


Microsoft Windows* for Workgroups 3.11 installation notes for Intel's
EtherExpress(TM) PRO/100B LAN Adapter using ODI drivers.
=====================================================================

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 on "NETWORKS".

6  Select "INSTALL MICROSOFT WINDOWS NETWORK" and click on OK.

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

8  Click on "DRIVERS".

9  If you are replacing a previous installed LAN adapter, click on
   "Remove" to delete that adapter.

10 Click on "Add Adapter".

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

12 From the NetWork Drivers menu, click on "CLOSE".

13 From the NetWork Setup menu, click on OK.

14 Windows for Workgroups asks if you want to replace the files currently
   installed with the version you are installing now. Click on "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 on OK.

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


Hints and tips
==============

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
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 E100BODI
   frame ethernet_802.2
   frame ethernet_802.3
   frame ethernet_II
   frame ethernet_SNAP


Troubleshooting tips
====================

A  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.

B  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.

C  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.

D  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 setup
   networking in Windows for Workgroups, or had another adapter installed
   before the EtherExpress PRO/100B, it may be necessary to restore the
   PROTOCOL.INI to the default and then install the driver for the
   EtherExpress PRO/100B.  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 on OK.
   
   5  From the NetWork Setup menu, click on OK.
   
   6  Windows for Workgroups will notify you that it has modified
      NET.CFG, CONFIG.SYS, SYSTEM.INI, WIN.INI, and PROTOCOL.INI. Click
      on OK.
   
   7  Windows for Workgroups will prompt you to reset your computer for
      the changes to take effect. Click on "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.

E  If Windows for Workgroups fails to detect that the ODI drivers are
   loaded while running NetWork Setup, you will get this 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, under the section heading [net.cfg], change
      "PATH=C:\Windows\net.cfg" to "PATH=C:\nwclient\net.cfg".
   
   2  In the PROTOCOL.INI, change the section heading [Link Driver XXXX]
      to [Link Driver E100BODI].
   
   3  In the PROTOCOL.INI, under the section heading [NWLINK], change
      both occurrences of "BINDINGS=XXXX" to "BINDINGS=E100BODI".
   
   4  In the NET.CFG, 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.

F  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 Novell NetWare files and are not on the Intel
   Configuration and Drivers diskette.  You can get these files from
   CompuServe in Novell's forum called Novell NetWire by downloading a
   self-extracting file called WINDR1.EXE. If you are not a member of
   CompuServe, you can call Novell to have them mailed to you. Or contact
   a Novell NetWare dealer in your area.