Frequently asked EtherWORKS 3 questions ======================================= Q: How can I obtain the latest EtherWORKS 3 drivers?: A: To obtain the latest EtherWORKS 3 TURBO software from the Internet: 1. Perform an ftp connect to ftp.digital.com. Your login name is anonymous. 2. Enter your password. (Use your Internet address as your password.) 3a. To obtain the currently RELEASED (shipping) EtherWORKS 3 kit (matching upper/lowercase lettering) change your directory as follows: cd /pub/DEC/adapters/ethernet/ewrk3/release 3b. To obtain the latest drivers prior to a major release of an EtherWORKS 3 kit. We maintain an interim kit. This kit is the currently released (shipping) kit plus any drivers that were released/completed thereafter. (Matching upper/lowercase lettering) change your directory as follows: cd /pub/DEC/adapters/ethernet/ewrk3/interim 4. List all the files in the directory to determine the kit number. Released and Interim kits will have the following syntax e3kitn. Where "n" is a version number. For example for a released kit "n" could be 22(meaning V2.2). For an Interim kit "n" could be 226(meaning V2.26). ftp> ls 5. Select ftp image mode: ftp> i 6. Perform a get command on the e3kitn.zip file. (where "n" is the kit number determined in step 5.) ftp> get e3kitn.zip 7. Type quit to exit ftp: ftp> quit To obtain the latest EtherWORKS 3 TURBO software from CompuServe: 1. Type GO DECPCI to select the depci forum and enter the LAN Controllers library. 2. Select the Browse option to scroll through the library titles. 3. Click on the EtherWORKS title, then press Return to display the description of the EtherWORKS 3 TURBO card. 4. Select the Retrieve option to copy the file to your system. For information on obtaining a CompuServe account in the U.S., call (800)848-8990. To obtain the latest EtherWORKS 3 TURBO software from the DECpc Bulletin Board Service: 1. Using a modem (parameters 2400-9600 baud, 8 bits, no parity, 1 stop bit), connect to the DECpc Bulletin Board Service by dialing 508-496-8800. 2. Follow the screen's menu-driven instructions to download the driver files. Q: What is the certification status of the EtherWORKS 3 drivers? (These drivers will be shipping with the V2.3 kit this month) A: o NetWare ODI Server driver, V2.02, which passes the NetWare "Yes, NetWare Tested and Approved" tests for NetWare V3.12 and NetWare V4.01. The bulletin number is L-2273. This driver will be included with the soon to be released Netware V4.10. o NetWare ODI Client driver, V3.03, which passes the NetWare "Yes, NetWare Tested and Approved" tests for NetWare V3.12 and NetWare V4.01. The bulletin number(s) are: Card Bulletin ==== ======== DE203 L-2458 DE204 L-2459 DE205 L-2460 This driver will be included with the soon to be released Netware V4.10. Changes for the Netware ODI Client driver V3.03 include: o PathWORKS Certification: NDIS driver V2.81 PathWORKS Native driver V5.0.25 Q: What drivers/Remote Boot protocols do the EtherWORKS 3 card support? A: DOS NDIS3 driver DOS NDIS2 driver Linux Driver Novell NetWare ODI Client Driver Novell NetWare IPX Client Driver Novell NetWare ODI Server Driver Native PathWORKS driver OS/2 NDIS2 driver (Clarkson) Packet Driver SCO Unix Driver Univel driver Windows NT driver RPL Remote Boot(Can be used in Netware/Novell Environments) MOP Remote Boot(Can be used in PathWORKS environments) Other Network Operating Systems which are supported/use by one of the drivers above: Windows For Workgroups (This can use the DOS NDIS2 and/or the NDIS3 driver) IBM LAN Requestor (This uses the OS/2 NDIS driver) LAN Manager (This uses the DOS NDIS2 driver) Lantastic (This uses the DOS NDIS2 driver) Mosaic (This uses the Packet Driver) Possible Diagnostic Error Messages(Diagnostics SHOULD be run from NICSETUP) =========================================================================== Q: NICSETUP diagnostics won't run properly A: RAMDIAG.COM needs to exist in the same directory from which NICSETUP is executing. Q: Customer got the error msg: "FF, invalid diagnostic code error message." A: This could mean a conflict with the PC's Shadow RAM. The user needs to enter his/her BIOS SETUP (some PC's its the ADVANCED BIOS SETUP) and disable any memory area that would conflict with the memory area that the EtherWORKS 3 Network Buffer may be using. (This problem may be seen on Gateway 2000 P5-66 models) BIOS defaults to Shadowing the Upper Memory Blocks on these PCs, in particular C0000 and D0000. To enable Etherworks cards to be able to put their ROM info into the UMB, you must first create a "hole" in the UMB which is not shadowed. You can only create 1 such "hole"- in 16, 32, or 64K sizes. The steps to create this "hole" in the UMB(example uses D0000 w/ 2K mode): 1-During Boot, hit F1 to enter CMOS SETUP 2-Select "ADVANCED CMOS SETUP" (return twice) 3-Select "DISABLE SHADOW MEMORY BASE" - Set address to 'D0000h' 4-Select "DISABLE SHADOW MEMORY SIZE" - Set to '16K' (or to amount needed) 5-ESC once to return to previous screen 6-Select "WRITE TO CMOS AND EXIT" Q: Customer got the error msg: "Queue, Memory Page Register Test Failed. Check that D0000 - D007F range is eXcluded if using EMM" A: This means that the customer is running an Extended Memory Manager and did not exclude the memory range that the card's Network Buffer is configured for. (The configuration of the card's Network Buffer can be determined from running NICSETUP). Extended Memory Managers are usually invoked in CONFIG.SYS. Examples of appending the exclude statement are as follows: device = c:\dos\emm386.exe NOEMS x=d000-d07f device = c:\qemm\qemm386.sys x=d000-d07f (Note: The card is defaulted to use memory range d000-d07f) Q: Customer got the error msg: "IRQ Test failed" A: This means that another card in the PC is using the same IRQ as the EtherWORKS 3 card. Check for conflicts. Nicsetup can be used to switch the card to another IRQ. (The card defaults to IRQ 5). ================================================================================ Q: Board is not found by driver or NICSETUP A: Check for IOport conflicts with other adapters. If you run NICSETUP and the board is reported as busy even though the EtherWORKS 3 driver has not been loaded. This is a sure sign of an IOport conflict with another card. The card is default shipped at IOport 300h. Since the IOport is the main communications avenue for NICSETUP to talk to the card the customer will need to power down his system and manually strap the card to another IOport setting: W1 W2 IOport Address ---- ---- -------------- IN IN 200h IN OFF 280h After this is completed the customer needs to power up his/her system and and run NICSETUP. At this point the card is ONLY configured for an IOport address according to your jumper selection. You MUST now select the IOport, Memory address and IRQ you wish your card to operate at. Once this is complete the system needs to be powered down and the jumpers (W1 & W2) should be removed. (The card will NOT run with the jumpers installed). Now the system can be powered up and used as normal. ================================================================================ Q: Machine will not boot after configuring the card for an F0000 address range A: NICSETUP (NICSETUP.EXE) gives the option of setting the RAM address in the F0000-F0080 range. This conflicts with many PC's system ROM BIOS. DO NOT choose any part of the F0000 range for the RAM address. The customer will need to power down his system and manually strap the card to one of the following settings: W1 W2 IOport Address ---- ---- -------------- IN IN 200h IN OFF 280h After this is completed the customer needs to power up his/her system and and run NICSETUP. At this point the card is ONLY configured for an IOport address according to your jumper selection. You MUST now select the IOport, Memory address and IRQ you wish your card to operate at. Once this is complete the system needs to be powered down and the jumpers (W1 & W2) should be removed. (The card will NOT run with the jumpers installed). Now the system can be powered up and used as normal. ================================================================================ Q: Is it possible to determine the EtherWORKS 3 unique Ethernet address? A: Yes, run NICSETUP and select MODULE STATUS from the main menu. At that point hit twice and you will see a big box of information on the right of your screen. In it is the Ethernet address. ================================================================================ Q: What does "fast bus enabled" do? A: The Fast Bus option in NICSETUP can be used whenever the PC that the EtherWORKS 3 module is plugged into is running a bus speed greater than 8.33MHz (the industry standard speed). The most popular fast bus speed is 10MHz. Neither the type of CPU (286, 386, 486) nor the CPU speed (25MHz, 33MHz, 66MHz) has anything to do with the problem. Please note for the MAJORITY of PC's Fast Bus should be DISABLED. In most cases where there is a fast bus, the PC clone will have a SETUP utility that will allow the machine to fall back to the standard ISA bus speed of 8.33MHz. That would also be an option if the fast bus speed poses a problem. However, not every PC running at greater than 8.33MHz will pose a problem to the EtherWORKS 3 module. Only use the Fast Bus Enabled option if there is a problem that you're trying to solve. ================================================================================ Q: Using the EtherWORKS 3 with Lantastic networks previous to V6.0 A: To use the EtherWORKS 3 NDIS driver the customer needs to access the LANTASTIC BBS at (602)884-8648 and download the file AINDIS.EXE. This file needs to be unZIPped to a diskette. The customer then needs to type INSTALL. The customer needs to select the following menu choice: LANtastic NDIS for Other Network Adapters Reference the AI-NDIS.DOC for further instructions.