Networking Connectivity
Intel® PRO/100 PCI and EISA Adapters
Windows* for Workgroups using ODI drivers

General Instructions

  1. From the \NWCLIENT directory on the EtherExpress™ PRO/100 driver disk, copy LSL.COM, E100ODI.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
      E100ODI
      IPXODI
      CD\

  3. 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. Select NETWORKS.

  6. Select INSTALL MICROSOFT WINDOWS NETWORK and click OK.

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

  8. Select DRIVERS.

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

  10. Select 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 will ask if you want to replace the files currently installed with the version you are installing now, select YES TO ALL.

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

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

  17. Windows for Workgroups will prompt you to reset your computer for he 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 E100ODI]
    data=Frame Ethernet_SNAP
    data=Frame Ethernet_802.2
    data=Frame Ethernet_II
    data=Frame Ethernet_802.3

    [NWLINK]
    BINDINGS=E100ODI

    [NETBEUI]
    BINDINGS=E100ODI
    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
    e100odi
    ipxodi
    c:\windows\odihlp.exe

    C:\NWCLIENT\NET.CFG
    Link Driver E100ODI

        frame ethernet_802.2
        frame ethernet_802.3
        frame ethernet_ii
        frame ethernet_snap

Troubleshooting Tips

  • Check what 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 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 correct 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/100 adapters without a hub, this requires a special cable called a cross-over cable. A cross-over cable will have the Transmit and Receive pairs crossed instead of running straight through. There is a diagram of a cross-over cable included in the information files on the EtherExpress PRO/100 driver diskette you can view by running README.EXE from the driver diskette, select View Help Files, then select 10 Mbps Cabling Specifications. The cross-over cable will work for 100 Mbps or 10 Mbps, but it is to be used for test purposes only and is not 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 setup networking in Windows for Workgroups or had another adapter installed before the EtherExpress PRO/100 adapter, it may be necessary to restore the PROTOCOL.INI to the default and then install the driver for the EtherExpress PRO/100 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 PROTOCL.INI. Click 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.

  • 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 E100ODI. 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 E100ODI].

    3. In the PROTOCOL.INI, under the section headings [NWLINK] and [NETBEUI], change both occurrences of "BINDINGS=XXXX" to "BINDINGS=E100ODI"

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

    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 EtherExpress PRO/100 adapter driver diskette. You can get these files by downloading the self-extracting file, WINDR3.EXE, from Novell.

This applies to:

Intel® PRO/100 PCI and EISA Adapters



Solution ID: CS-016078
Last Modified: 07-Oct-2013
Date Created: 05-Oct-2004
Back to Top