Windows for Workgroups v3.11 v1.00 Microsoft Windows* for Workgroups 3.11 Installation Notes for Intel's EtherExpress(TM) 10 ISA LAN Adapter ===================================================================== Location of Driver: \WFW\EX10.38_ Novell NetWare* files may be required ------------------------------------- 1 If you install Novell NetWare support on this workstation, you need these Novell NetWare files: NETWARE.DRV, NETWARE.HLP, NWPOPUP.EXE, VIPX.386, VNETWARE.386 These files are not on the Intel Configuration and Drivers disk. To obtain these files, do one of the following: - Download the self-extracting file WINDR3.EXE (or latest offering from Novell's website (http://support.novell.com) or Novell's FTP server ftp.novell.com). - Call Novell (1-800-NETWARE) to have the files sent to you. - Contact a Novell NetWare* dealer in your area. 2 To install proper driver support for Windows* for Workgroups and Novell NetWare on the same workstation, you must set up the workstation for NetWare first using the DOS ODI client. EX10Set can install the DOS ODI network driver for you. However, you may need to alter your CONFIG.SYS, AUTOEXEC.BAT, and NET.CFG files so they comply with your network. 3 After logging into your NetWare file server, start Windows for Workgroups, then run Network Setup. Before you start ---------------- You must configure and test the 10 ISA adapter with EX10SET.EXE before adding the adapter to Network Setup in Windows for Workgroups. You must boot the workstation to DOS, then insert the Intel Configuration and Drivers disk into drive A. At the DOS prompt type A:EX10SET 1 Select "Automatic Setup" and let EX10Set configure the EtherExpress(TM) 10 ISA adapter to work in your computer. Select "Change Adapter Configuration" if you want to specify which interrupt and I/O address the EtherExpress 10 ISA adapter will use. If your computer has a Plug and Play BIOS, you will need to turn off Plug and Play on the adapter in order to set the interrupt and I/O address manually. Disable Plug and Play by going to the Advanced Options Menu under Change adapter configuration menu. When EX10Set asks for a network frame type, select the frame type appropriate for your LAN. If you want to add extra frame types, do so in your NET.CFG file. 2 Select "Test Adapter" from the main menu to test the configuration you have selected. If the EtherExpress 10 ISA adapter fails diagnostics, it may not function correctly under Windows for Workgroups. NOTE: EX10Set is a DOS program and will not run in Windows for Workgroups. You must run EX10Set from DOS. If Windows for Workgroups loads automatically on your computer, you can boot to DOS by inserting a DOS boot disk into your floppy disk drive A when rebooting, or you can exit Windows for Workgroups to get back to DOS. General Installation -------------------- 1 Start Windows for Workgroups (WFW) with the /N parameter. This starts WFW without starting any of the networking software. At the DOS prompt, type C:\WINDOWS\WIN /N 2 Select the "Network Setup" icon in the Network Group. 3 Click the "Networks" button. Select "Install Microsoft Windows Network" and click "OK". To add Novell NetWare support to this workstation, click "Other," then select "Novell NetWare Shell 3.x" if you're using NETX, or select "Novell NetWare Shell 4.x" if you're using VLMs. Click "OK". To share files and printers on this workstation, click the "Sharing" button, then click "OK". 4 Click the "Drivers" button. 5 Click the "Add Adapter" button. Select "Unlisted or Updated Network Adapter" and click "OK". 6 Insert the Intel Configuration and Drivers disk into a drive and for the path, type: A:\WFW 7 Select "Intel EtherExpress(TM) 10 ISA" adapter from the list and click "OK". 8 Specify the Interrupt, Base I/O port, and Transceiver type settings. If you're not sure what they should be, make a selection here and after WFW installation is complete, run EX10Set to make sure they are correct. NOTE: If you load Novell NetWare ODI drivers, these settings are assigned automatically for you. 9 In the Network Drivers window, click "Close". 10 In the Network Setup window, click "OK". 11 In the Microsoft Windows Network Names window, enter a unique User Name, the name of your new or existing Workgroup, and a unique Computer Name for your workstation, then click "OK". 12 Choose "Yes To All" when WFW asks if you want to replace the files currently installed with the versions you are installing now. 13 Insert the WFW disks when WFW asks for the driver update files. If prompted for the NetWare files, insert the Novell disk containing the drivers from the Novell file WINDR3.EXE. If prompted for the path of EX10.386, insert the Configuration and Drivers disk into a drive and for the path, type A:\WFW If prompted for the path of EX10.DOS, insert the EtherExpress 10 ISA Configuration and Drivers disk in drive A and type A:\NDIS 14 When finished updating the files, WFW reports that it modified several files. Click on "OK". WFW changes your last drive to P. You may change this setting in your CONFIG.SYS file. WFW also alters your NET.CFG file. Check this file to make sure your frame types load in the correct order for your network. 15 When WFW prompts you to restart your computer for the changes to take effect, click on "Restart Computer". Remember to log into your NetWare server before starting WFW. Hints and Tips -------------- 1 ERROR 58: WHILE LOADING PROTOCOL NUMBER 0... -------------------------------------------- If WFW fails to detect or initialize the EtherExpress 10 ISA adapter, you get this error message when starting WFW: 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. Try these steps: a Verify that the I/O address and interrupt used by the EtherExpress 10 ISA adapter are not used by any other device (like sound cards, faxmodems, serial ports, parallel ports, etc.) in your computer. Look at the documentation or run the setup programs for the other adapters in your computer to verify which I/O address and interrupts they are using. Some sound cards use multiple interrupts and I/O addresses. For example, a typical sound card will use an I/O address of 220 and IRQ 5 for the sound port, an I/O address of 330 and IRQ 11 for the CD-ROM, and IRQ 2/9 for the MIDI/Joystick port. b Verify that the EtherExpress 10 ISA adapter passes all diagnostic tests by running EX10SET.EXE from DOS and selecting "Test Adapter". If the EtherExpress 10 ISA adapter fails diagnostics, it will not function correctly under Windows for Workgroups. If On-Board diagnostics fail, try setting the EtherExpress 10 ISA adapter to a different I/O address, a different interrupt, or change Force 8 bit operation to "Yes". If On-Network diagnostics fail, there is likely a cable, connector, or hub problem. Verify that the cabling you are using is connected properly and that the cable isn't defective. For more information on cable specifications, view the TPE or BNC Cabling Specification readme files on the Configuration and Drivers disk. Note: "Responder not found" is NOT an error. This message will be displayed IF YOU ARE NOT RUNNING THE EX10SET RESPONDER ON ANOTHER MACHINE with an EtherExpress card or if the card cannot actually communicate with the responder card. If you don't have a responder running, or if the two cards can't communicate, the diagnostic will try to send packets back to itself. c If you use Novell NetWare, and 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. Because Windows for Workgroups was unable 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 "EX10ODI". When this error occurs, you will need to manually edit the NET.CFG and PROTOCOL.INI that Windows for Workgroups created to replace all instances of "XXXX" with "EX10ODI". Here are the entries that need to be changed: In the PROTOCOL.INI, under the section heading [net.cfg], verify the path specified for your NET.CFG is correct. In the PROTOCOL.INI, change the section heading [Link Driver XXXX] to [Link Driver EX10ODI]. In the PROTOCOL.INI, under the section heading [NWLINK] change both occurrences of "BINDINGS=XXXX" to "BINDINGS=EX10ODI". In the NET.CFG, change "Link Driver XXXX" to "Link Driver EX10ODI" 2 Windows for Workgroups won't load or locks up --------------------------------------------- After installing the EtherExpress 10 ISA adapter, if WFW won't load or locks up, make sure the I/O address and interrupt used by the EtherExpress 10 ISA adapter are not used by any other device (like sound cards, faxmodems, serial ports, parallel ports, etc.) in your computer. If you are using the BNC (coax) connector, you must have a terminated cable attached to the EtherExpress 10 ISA adapter when you start Windows for Workgroups. If you don't, Windows for Workgroups may hang. 3 Adapter passes diagnostics but still does not work with WFW ----------------------------------------------------------- If the adapter passes diagnostics but still doesn't work with WFW, there could be a problem with the PROTOCOL.INI file. If you've made several attempts to configure WFW or had another adapter installed before the EtherExpress 10 ISA adapter, you may need to restore the PROTOCOL.INI file to its default settings and reinstall the EtherExpress 10 ISA adapter driver. Here's how: a Start WFW with the /N parameter. At the DOS prompt type C:\WINDOWS\WIN /N b Click the "Network Setup" icon in the Network group. c Click the "Networks" button. Select "No Windows Support For Networks" and click "OK". d In the Network Setup window, click "OK". e When WFW reports that it modified several files, click "OK". f When WFW prompts you to reset your computer for the changes to take effect, click "Restart Computer". After the workstation reboots, continue at step 3 of the "General Installation" section of this document. 4 Can't see other workstations ---------------------------- If Windows for Workgroups loads without error messages, but you can't see any other computers on your network, verify that the name of the workgroup is correct and that you are logged on to the network. Here's how: a From the Control Panel, click the "Network" icon. b Verify the workgroup name on your computer is the same as the workgroup name on a working computer. c If your Logon Status is "Not Logged On", click on "Log On." This can also be a cable, connector, or hub problem. Verify that the cabling you are using is connected properly and is not defective. Also, try running diagnostics on the adapter\cabling by selecting "Run Diagnostics on Network" in EX10Set. 5 Sample PROTOCOL.INI ------------------- Windows for Workgroups creates the PROTOCOL.INI for you. This is provided for reference. This is a sample with Microsoft NetBEUI and IPX/SPX Compatible Transport with NetBIOS. [network.setup] version=0x3110 netcard=ms$EX10,1,MS$EX10,3 transport=ms$nwlinknb,NWLINK transport=ms$ndishlp,MS$NDISHLP transport=ms$netbeui,NETBEUI lana0=ms$EX10,1,ms$netbeui lana1=ms$EX10,1,ms$nwlinknb lana2=ms$EX10,1,ms$ndishlp [protman] DriverName=PROTMAN$ PRIORITY=MS$NDISHLP [MS$EX10] DriverName=EX10$ INTERRUPT=5 IOADDRESS=0x300 [EX10] Adapters=MS$EX10 [NWLINK] BINDINGS=MS$EX10 [MS$NDISHLP] DriverName=ndishlp$ BINDINGS=MS$EX10 [NETBEUI] DriverName=netbeui$ SESSIONS=10 NCBS=12 BINDINGS=MS$EX10 LANABASE=0 * Third-party trademarks are the property of their respective owners.