Windows for Workgroups v3.11 v3.04 Microsoft Windows* for Workgroups 3.11 Installation Notes for Intel's EtherExpress(TM) PRO/10 LAN Adapter ===================================================================== Location of Driver: \WFW\EPRO.38_ \WFW\OEMSETUP.INF (setup file) 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 from the Novell NetWire forum on CompuServe or Novell's FTP server on the Internet (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. SoftSet2 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. 4 Refer to Installation Notes for PRO/10 ISA and NetWare DOS Client for more information. Before you start ---------------- You must configure and test the PRO/10 ISA adapter with SOFTSET2.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:SOFTSET2 1 Select "Automatic Setup" and let SoftSet2 configure the EtherExpress(TM) PRO/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 PRO/10 ISA adapter will use. Note: If your computer has a Plug and Play BIOS, the BIOS will handle the configuration of the adapter and the Automatic Setup option won't be available. However, you will still need to know what settings are assigned to the adapter because the Windows for Workgroups setup requires these entries. If you will be adding additional devices to the computer in the future, it is best to disable the Plug and Play capability of the adapter and assign the resources manually. This will ensure the resources originally assigned to the adapter won't change (which would require a change in Windows for Workgroups Network Setup). 2 Select "Test Adapter" from the main menu to test the configuration you have selected. If the EtherExpress PRO/10 adapter fails diagnostics, it may not function correctly under Windows for Workgroups. NOTE: SoftSet2 is a DOS program and will not run in Windows for Workgroups. You must run SoftSet2 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". 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 add support for other networks, click other then select the appropriate Network Operating System. To share files and printers on this workstation, click the "Sharing" button. When all options are set correctly, 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) PRO/10 LAN Adapter" from the list and click "OK". 8 Specify the values for Interrupt, Base I/O Port, Transceiver type, Link Speed (half or full duplex), and Power Management. If you're not sure what they should be, make a selection here and after the Windows for Workgroups installation is complete, run SoftSet2 to make sure they are correct. If you are using the AUI connector, select the AUI/DIX option for Transceiver type. The last four settings should only be changed by a Network Administrator. See the Hints and Tips section for details on these parameters. 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 WINDR2.EXE. If prompted for the path of EPRO.386, insert the Configuration and Drivers disk into a drive and for the path, type A:\WFW If prompted for the path of EPRO.DOS, insert the EtherExpress PRO/10 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 PRO/10 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 PRO/10 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 PRO/10 adapter passes all diagnostic tests by running SOFTSET2.EXE from DOS and selecting "Test Adapter". If the EtherExpress PRO/10 adapter fails diagnostics, it will not function correctly under Windows for Workgroups. If On-Board diagnostics fail, try setting the EtherExpress PRO/10 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 SOFTSET2 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 "EPROODI". 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 "EPROODI". 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 EPROODI]. In the PROTOCOL.INI, under the section heading [NWLINK] change both occurrences of "BINDINGS=XXXX" to "BINDINGS=EPROODI". In the NET.CFG, change "Link Driver XXXX" to "Link Driver EPROODI" 2 Receiving error message 400 or 401 when installing the adapter -------------------------------------------------------------- When installing the adapter, if you receive a message indicating the disk doesn't contain information about your adapter, check the \WINDOWS\SYSTEM subdirectory for files that begin with OEM#. The # sign stands for numbers 0 - 9. If you have 10 of these files, Windows for Workgroups can't install addition adapters. Move or rename the OEM*.INF files. 3 Windows for Workgroups won't load or locks up --------------------------------------------- After installing the EtherExpress PRO/10 adapter, if WFW won't load or locks up, make sure the I/O address and interrupt used by the EtherExpress PRO/10 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 PRO/10 adapter when you start Windows for Workgroups. If you don't, Windows for Workgroups may hang. 4 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 PRO/10 adapter, you may need to restore the PROTOCOL.INI file to its default settings and reinstall the EtherExpress PRO/10 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. 5 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 SoftSet2. 6 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$epro,1,MS$EPRO,3 transport=ms$nwlinknb,NWLINK transport=ms$ndishlp,MS$NDISHLP transport=ms$netbeui,NETBEUI lana0=ms$epro,1,ms$netbeui lana1=ms$epro,1,ms$nwlinknb lana2=ms$epro,1,ms$ndishlp [protman] DriverName=PROTMAN$ PRIORITY=MS$NDISHLP [MS$EPRO] DriverName=EPRO$ INTERRUPT=5 IOADDRESS=0x300 [EPRO] Adapters=MS$EPRO [NWLINK] BINDINGS=MS$EPRO [MS$NDISHLP] DriverName=ndishlp$ BINDINGS=MS$EPRO [NETBEUI] DriverName=netbeui$ SESSIONS=10 NCBS=12 BINDINGS=MS$EPRO LANABASE=0 7 Collision Reduction Keywords for TCP/IP Protocol ------------------------------------------------ This functionality is provided by the v3.01 EPRO.386 driver (10/22/96) and OEMSETUP.INF (10/28/96) or greater. Below are the keywords that enable and adjust collision reduction for the EtherExpress PRO/10 ISA Adapter. The inter-frame gap may be adjusted between all frames that the adapter transmits, or the gap may be adjusted dynamically "on the fly" for those packets which are transmitted in back-to-back fashion. Only one method of collision reduction (i.e., AllFrames or Dynamic) should be enabled at a time. For either method, optimal setting(s) may vary between networks. To adjust the inter-frame gap for all frames, independent of the collision rate, use AllFramesCRT: AllFramesCRT suggested setting: 0x0040 Range: 0x0000 through 0x009f Default: 0x0000 (no adjustment) Description: Adjusts the inter-frame space between all packets. Increases the standard inter-frame gap of 9.6 microseconds by 0.1 increments. The Dynamic keywords below allow for automatic "On the fly" adjustments of the inter-frame gap between back-to-back packets. The adapter continually monitors the rate of collisions, and will increment the interval between packets as the rate of collisions increases. Before enabling Dynamic collision reduction, make sure AllFramesCRT is set to 0x0000. DynamicCRTMax suggested setting: 0x00C8 Range: 0x0000 through 0x00ff Default: 0x0f Description: sets the maximum adjustment value that will be used by collision reduction technology. This value affects the amount of time, in 0.02 microsecond increments, that will be added to the inter-frame gap between back-to-back packets. DynamicCRTIncrement suggested setting: 10 Range: 0 through 20 Default: 5 Description: provides the increment value that will be used by the Dynamic Collision Reduction Technology. If an adjustment is deemed appropriate by the Dynamic Collision Reduction adjustment routine, this number is added or subtracted from the adjustment value. DynamicCRTInterval suggested setting: 5000 Range 1000 through 10000 Default: 2000 (2 seconds) Description: sets the time, in 1-millisecond increments, between samples by the Dynamic Collision Reduction adjustment routine. The minimum setting for this value is 1000 (1000 milliseconds or 1/4 second), and the maximum is 10000 (10 seconds). Supplemental information regarding TCP/IP Protocol and Collision Reduction ---------------------------------------------------------------- The collision reduction technology at a single station works best if it is on the station that is supplying the data. For example, if you have a client copying files from a server and were only applying the collision reduction at one of these two points, it would be best to put the collision reduction at the server. The collision problem that is seen with Microsoft implementations of TCP/IP is due to the fact that they use asynchronous ACKs. ACKs are ACKnowledgment packets that are used to notify the sending station that the packet has arrived safely and does not need to be re-sent. With protocols that use synchronous ACKs, (NetBEUI - IPX/SPX compatible protocol) the sending station waits for a packet to be acknowledged before sending the next one. This scheme eliminates the possibility that a data packet will collide with a previous packet's ACK. Microsoft TCP/IP does not wait for the ACK before sending the next packet and greatly increases the chance that a packet will collide with a previous packet's ACK. High-performance Ethernet cards like the EtherExpress PRO/10 are designed to get data onto the network as fast as specifications allow. Under Microsoft TCP/IP, however, this aggressiveness can result in a "harmonic" effect where many collisions between the data packets and previous packets' ACKs occur. The collision reduction technology is designed to make the EtherExpress PRO/10 slightly less aggressive under these circumstances and to disrupt the harmonic effect. * Third-party trademarks are the property of their respective owners.