Instruction/ maintenance manual of the product PRO Intel
Go to page of 146
i EtherExpress ™ PR O/100 CardBus Mobile Adapter User’ s Guide How to Use This Manual This User’s Guide contains the latest and most complete information available at press time on the installation and operation of the PRO/100 CardBus adapter.
ii Copyright © 1997 Intel Corporation. All rights reserved. Intel Corporation 5200 N.E. Elam Young Parkway Hillsboro, OR 97124-6497 Intel Corporation assumes no responsibility for errors or omissions in this guide. Nor does Intel make any commitment to update the information contained herein.
iii Contents Har d ware Installation .............................................. 1 Before Installing Hardware ................................................................... 1 Installing the Hardware ............................................
iv CONTENTS IBM Local Ar ea Network Support Progr am ....................................... 38 IBM Local Ar ea Network Suppor t Progra m ( version 1.2) ................. 39 IBM PC LAN and IBM DOS LAN Requester ................................... 40 Manual Installation .
v C O N T E N T S Network Operating System T roubleshooting ................................... 104 T roubleshooting Chec klist ................................................................ 116 Intel A utomated Customer Support ................... 119 Specifications .
vi CONTENTS.
1 Follow the instructions in this chapter to install the PRO/100 CardBus adapter hardware and network cabling. See Chapter 2, Software Installation for instructions on how to install network software.
2 CHAPTER 1 Verify Other Required Equipment To install the PRO/100 CardBus adapter, you need the following: 1 A portable PC with a CardBus slot. Note that CardBus slots are different from 16-bit PCMCIA slots. If your CardBus adapter does not fit in your slot, it may be a 16-bit slot.
3 Hardware Installation Installing the Hard ware Insert the PRO/100 CardBus adapter 1 Grasp the PRO/100 CardBus adapter by the edges with the Intel label facing upward and the wide PC Card connector next to the insert slot. 2 Insert the card into a CardBus slot and push it in until it is firmly seated.
4 CHAPTER 1 Removing the PRO/100 CardBus adapter Follow the PC card removal instructions specified in the documentation for your computer. Connecting the LAN Adapter Cable to the Card • Attach the 15-pin connector at the end of the Intel adapter cable to the mating connector on the end of the adapter (see illustration below).
5 Hardware Installation Connecting the Network Cable to the LAN Adapter Cable • Plug the network cable into the female RJ-45 connector, as shown in the figure. Connecting to the Network Cable to LAN Adapter Cable What to Do Next After installing the hardware and connecting cables, proceed to Chapter 2.
6 CHAPTER 1.
7 Car dBus Installation Guidelines The PRO/100 CardBus adapter can be used in Windows 3.x, Windows 95, Windows NT, and MS-DOS environments, and with most common network operating systems. However, some current operating systems or Card and Socket Services versions do not yet support CardBus technology.
8 CHAPTER2 Installing with Windows 95 The first release of Windows 95 (4.00.950 or 950a) included built-in support for 16-bit PC Cards but not for 32-bit CardBus. However, your PRO/100 CardBus adapter can still be installed under Windows 95. See the procedure on the next page.
9 Software Installation Installing with Windows 95 V ersion 4.00.950 or 4.00.950a Windows 95 does not include ‘Hot Swap’ support for CardBus adapters. The PRO/100 CardBus adapter includes a driver that will let you use the device within Windows 95.
10 CHAPTER2 11 Under “Manufacturers,” click “Intel.” 12 Select the “Intel EtherExpress PRO/100 Mobile CardBus 32 manual load ." Note that this is the second driver listed. You may need to scroll the text to see the entire driver name. 13 Click OK.
11 Software Installation 1 In the Control Panel, double-Click the System icon. The System Properties window opens. 2 Click the Device Manager tab. 3 Double-click PCMCIA Socket. 4 Click PCIC or compatible PCMCIA controller. 5 Click Remove. A removal confirmation window opens.
12 CHAPTER2 Re-enabling PC Card support with Windows 95 Version 4.00.950 or 4.00.950a If you have disabled PC Card and Socket support in order to use the PRO/100 CardBus adapter, and now want to use a.
13 Software Installation 8 Click OK. The System Properties window reopens. 9 Click Close. 10 Click Start. 11 Select Shut Down. 12 Select Restart the Computer and click Yes. Your computer is now set to use other PC Card devices. Installing Toshiba Computers with Windows 95 Version 4.
14 CHAPTER2 8 Press the space bar until the PC Card Controller Mode is set to CardBus/16-bit. 9 Press the End button on your keyboard and press Y when prompted. 10 Reboot your computer. 11 Perform steps 1 through 17 under the heading “Installing with Windows 95 version 4.
15 Software Installation 14 Press the End button on your keyboard and press Y when prompted. 15 Reboot your computer. 16 After your system has rebooted it is ready to support PC Cards under Windows 95. Installing with Windows 95 V ersion 4.00.950b (OSR2) or Later Windows 95 OSR2 and later versions support CardBus.
16 CHAPTER2 Installing NetW are Client 32 ODI Drivers under Windows 95 When installing the PRO/100 CardBus adapter under Windows 95 you have the option of installing either an NDIS3 driver (also known as Miniport) or a 32-bit ODI client driver (Client 32).
17 Software Installation if installing from a Novell NetWare Server you are connected to. 3 Once you have selected the proper path, run SETUP.EXE and follow the Novell instructions.
18 CHAPTER2 Installing with Windows NT 3.51 and 4.0 Windows NT 3.51 and 4.0 include full support for PC Cards and partial support for CardBus. The PRO/100 CardBus adapter includes a driver that will let you use the device within Windows NT. When loaded, this driver disables support for PC Cards in Windows NT.
19 Software Installation 11 Click OK. The Network Settings window reopens. 12 Click OK. The Network Settings Change window opens. 13 Click Restart Now to restart your computer. Re-enabling PC Card Support in Windows NT 3.51 The PRO/100 CardBus adapter cannot be used simultaneously with a PC Card in Windows NT 3.
20 CHAPTER2 9 Insert the Intel Network Drivers Disk . 10 Click OK. The Select OEM Option window opens. 11 Click OK. Windows NT Setup window briefly displays. 12 PRO/100 CardBus adapter Settings window opens, displaying the default settings. NOTE: In most circumstances, the default settings will properly operate the PRO/100 CardBus adapter.
21 Software Installation Installing with Windows 3.x and Windows fo r W orkgr oups To install under Windows 3.x or Windows for Workgroups , use the Intel Installation Program.
22 CHAPTER2 NOTE: Even though older Card and Socket Services software for MS-DOS and Windows 3.X may not support CardBus, it may be possible to use another PC Card simulta- neously with the PRO/100 CardBus adapter. Please refer to the README.TXT file or the Intel website for the latest information and tips regarding Card and Socket Services.
23 Software Installation 6 Set the path as A:NDIS and click OK. 7 Back at the LAPS Configuration window, in the Network Adapter section, select the PRO/100 CardBus adapter by clicking on it and then clicking Add. 8 In the Protocols section, select the protocols you wish to use by clicking on the protocols and then clicking Add.
24 CHAPTER2 5 In the ‘Requester Installation’ window, select the the option ‘Edit CONFIG.SYS and copy all files’ and click OK. 6 In the ‘Step 1- choose the ODI LAN Driver’ window, click on the list box to display the list of LAN drivers. An Installation Message window will appear.
25 Software Installation Installing Netw ork Software Use the instructions under this heading in the following circumstances: • To complete the installation of network software after you have run the Intel Installation Program : Find your network operating system in the alphabetical listing that follows.
26 CHAPTER2 Ar tisoft LANtastic version 6.0 NDIS 2.0 Driver 1 Run the Intel Installation Program from the Installation Disk. 2 Choose Artisoft LANtastic from the Select Network Operating System screen. 3 Follow the prompts to complete the Intel segment of the installation.
27 Software Installation 5 Write down the IRQ number to use when you proceed with the installation. For example, if the IRQ=6, write down the number 6. Now continue with the Banyan Vines installation as follows: 1 Run the Intel Installation Program from the Installation Disk.
28 CHAPTER2 DEC P A THW ORKS ver sions 5.x or 6.x NDIS 2.0 Driver These instructions are based on PATHWORKS documentation for configuration of a PC as a client workstation, using a system service already installed on a LAN Manager server and the LAN Manager SETUP diskette.
29 Software Installation ;NI_IRQ = [IRQ VALUE FROM STEP 5 OF THE FIRST PROCEDURE ABOVE] to read NI_IRQ = [IRQ VALUE FROM STEP 5 OF THE FIRST PROCEDURE ABOVE] The NI_IRQ value must be the same as the interrupt value you will use for the Intel adapter. 6 Run the SETUP program from the PATHWORKS SETUP disk for LAN Manager.
30 CHAPTER2 15 Highlight the logical drive mapped by the SETUP program, and press Enter to run PWSETUP. 16 Press Enter to confirm the Software Destination C:PW. 17 Choose Express (or Custom if you have a lot of prior installation experience). 18 Select an appropriate Workstation Template, or create one.
31 Software Installation FTP Software LANW atch Packet and NDIS 2.0 Drivers FTP Software’s LANWatch network monitor software can be installed using Intel’s packet or NDIS 2.0 drivers. For information on which driver is appropriate for your network environment, refer to the FTP LANWatch documentation.
32 CHAPTER2 FTP Software LANWatch NDIS 2.0 Driver Installation 1 Run the Intel Installation Program from the Installation Disk. 2 Choose FTP LANWatch from the Select Network Operating System screen. 3 Follow the prompts to complete the Intel segment of the installation.
33 Software Installation FTP Software PC/TCP Packet, NDIS 2.0, and ODI Drivers FTP Software’s PC/TCP Generic Ethernet Kernel ETHDRV.EXE can be installed using Intel’s Packet, ODI, or NDIS drivers. PC/TCP can also be used concurrently with NetWare.
34 CHAPTER2 13 Use a text editor to modify the AUTOEXEC.BAT file as follows (PCTCP is the default installation directory): • Move the line containing the STARTNET.BAT command or the lines containing the network driver files to immediately above the line SET PCTCP=C:PCTCPPCTCP.
35 Software Installation • In the section PCTCP ifcust 0 change the line INTERFACE-TYPE=NDIS to read INTERFACE-TYPE=PKTDRV. 10 Save the file and exit the text editor. 11 Change to the C: (root) directory. 12 Use a text editor to modify the AUTOEXEC.
36 CHAPTER2 7 Edit the AUTOEXEC.BAT file and add the following lines: C:PCTCPM32APD.COM C:PCTCPETHDRV.EXE 8 (This step is not required for PC/TCP versions 2.10 and later.) Using a text editor, add the following lines to your CONFIG.SYS file: DEVICE=[ PATH ]IPCUST.
37 Software Installation where [ path ] is the drive and directory specified in the PC/TCP installation. 6 Copy NET.CFG from the C:INTELM32A directory and the files LSL.COM and M32AODI.COM from the root directory of the Intel Network Drivers Disk to the PC/TCP directory created in the PC/TCP install procedure.
38 CHAPTER2 IBM Local Area Network Support Program IBM Local Area Network Support Program (version 1.36) NDIS 2.0 Driver 1 Run the Intel Installation Program from the Installation Disk. 2 Choose IBM LAN Support Program from the Select Network Operating System screen.
39 Software Installation IBM Local Area Network Support Program (version 1.2) NDIS 2.0 Driver 1 Run the Intel Installation Program from the Installation Disk. 2 Choose IBM LAN Support Program from the Select Network Operating System screen. 3 Follow the prompts to complete the Intel segment of the installation.
40 CHAPTER2 13 Change to the LANMAN directory on your hard disk or boot disk. 14 Use a text editor to modify the PROTOCOL.INI file in the C:LSP directory as follows: • Under the ETHERAND section, ch.
41 Software Installation Manual Installation All network drivers provided on the Intel Network Drivers Disk can be installed manually, without the Intel Installation Program. You must copy the correct driver files to your hard disk and make appropriate changes to CONFIG.
42 CHAPTER2 6 When prompted, insert the Intel Network Drivers Disk. 7 Select “Intel EtherExpress PRO/100 Mobile CardBus 32” from the menu. 8 Continue with the installation until it is completed. 9 If installing Microsoft LAN Manager to run under Windows proceed to step 10.
43 Software Installation 13 Close the Network Drivers dialog box and click OK in the Network Setup box. 14 Complete the installation process, inserting the Intel Network Drivers Disk if required. 15 Continue with the installation until it is completed.
44 CHAPTER2 Windows for Workgroups Version 3.11 and NetWare (Using the ODI driver) 1 To configure Windows for Workgroups with NetWare, run the Intel Installation Program and choose Windows for Workgroups. 2 Choose YES to “Connect to Network Server.” 3 Choose “Novell NetWare” as your network server.
45 Software Installation 15 In the Network Setup dialog box, choose Drivers. 16 In the Network Drivers dialog box, choose Add Adapter. 17 In the Add Network Adapter box, choose Unlisted or Updated Network Adapter and click OK.
46 CHAPTER2 6 If you have not installed network support, choose Networks in the Network Setup dialog box, select Install Windows Network, and click OK. Otherwise proceed to Step 7. Click the Sharing button to share files and printers. 7 In the Network Setup dialog box, choose Drivers.
47 Software Installation 11 Delete the old Intel configuration files from the Windows system directory. 12 Restart Windows. 13 Follow the instructions for installing drivers for Windows for Workgroups alone or Windows for Workgroups and NetWare.
48 CHAPTER2 SunSoft PC-NFS (version 3.5) NDIS 2.0 Driver 1 Run the Intel Installation Program from the Installation Disk. 2 Choose SunSoft PC-NFS from the Select Network Operating System screen. 3 Follow the prompts to complete the Intel segment of the installation.
49 Software Installation No vell NetW are 32-bit ODI Drivers Installing the Client 32 Driver under Windows 3.x and DOS In order to install the Client 32 driver under Windows 3.x or DOS, the following software is needed: · PRO/100 CardBus adapter Network Drivers Disk · NetWare Client 32 for DOS/Win 3.
50 CHAPTER2 9 A screen will display the default settings for the driver. Most of the time, these settings do not need to be changed. Check the README.TXT for machine specific settings. 10 To complete installation, follow the onscreen instructions. Installing under Windows 3.
51 Software Installation Ungermann-Bass Net/One for DOS NDIS 2.0 Driver The PRO/100 CardBus adapter is supported on Ungermann-Bass Net/One LAN Manager and MS-NET networks. There are two NDIS driver packages available from UB: XNS BNS/NDIS and TCP BNS/NDIS.
52 CHAPTER2 • At the end of the file, add the following fragments: [UBLOOP] DRIVERNAME = UBLOOP$ BINDINGS = INTELNET ;INTEL ADAPTER [INTELNET] DRIVERNAME = INTEL$ 8 Reboot the PC. W ollongong P athWa y Access f or DOS NDIS and ODI Drivers Wollongong PathWay Access for DOS can be installed using Intel NDIS or ODI drivers.
53 Software Installation 6 Copy the file M32ANDIS.EXE from C:INTELM32A directory to the PATHWAY directory on your hard disk or boot disk. 7 Continue with the “custom” instructions in the PathWay Access for DOS manual. 8 Reboot the PC. Wollongong PathWay ODI Installation 1 Run the Intel Installation Program from the Installation Disk.
54 CHAPTER2.
55 Who Should Consult This Chapter? This chapter contains additional information on PRO/100 CardBus adapter features and technical information on configuration requirements, including sample configuration files.
CHAPTER3 56 For Installation without the Intel Installation Program The information in this chapter can be used to manually configure the PRO/100 CardBus adapter.
57 Configuration Reference As additional vendors add CardBus support to Card and Socket Services, new driver software from Intel may be required to use the Intel CardBus Adapter with Card and Socket Services. Review the README.TXT file and check the Intel website for the latest information.
CHAPTER3 58 HotSwap The PRO/100 CardBus adapter currently supports HotSwap during connection to a network or host computer from a CardBus computer only if you are running versions of Windows 95 or Windows NT that fully support CardBus.
59 Configuration Reference NOTE: The suspend/resume feature is not supported unless Card and Socket Services software (or its equivalent under Windows 95 or Windows NT) supports CardBus and is running on the PC Card computer.
CHAPTER3 60 Memory Exclusion When using a memory manager (under DOS and Windows 3.X), you must exclude a 4K memory range between C000 and EF00 for the use of the PRO/100 CardBus adapter.
61 Configuration Reference FILES=50 BUFFERS=30 REM INTEL PRO/100 CB — DO NOT CHANGE LINES BELOW DEVICE=C:LANTASTIPROTMAN.DOS /I:C:LANTASTI DEVICE=C:LANTASTIM32ANDIS.EXE REM INTEL PRO/100 CB — DO NOT CHANGE LINES ABOVE Sample AUTOEXEC.BAT PATH=C:UTIL;C:DOS; PROMPT $P$G CALL C:LANTASTISTARTNET.
CHAPTER3 62 REM IF LANTASTIC IS DISABLED, SKIP EVERYTHING. IF EXIST DISABLED GOTO :STARTNET_DONE @ECHO ===== BEGIN LANTASTIC CONFIGURATION ===== PATH C:LANTASTI;%PATH% SET LAN_DIR=C:LANTASTI.NET LOADHIGH AI-NDIS BIND_TO=M32ANDIS_NIF AILANBIO @STARTNET.
63 Configuration Reference @ECHO ===== END LANTASTIC CONFIGURATION ===== :STARTNET_DONE CD Bany an VINES NOTE: If you are using DOS Multi-menu CONFIG.SYS, the three VINES related lines in the CONFIG.SYS will be located at the end of your CONFIG.SYS. You will have to manually move those lines into the proper menuitem section of your CONFIG.
CHAPTER3 64 [INTELNET] DRIVERNAME = INTEL$ DEC P A THW ORKS 5.0 and 5.1 Sample CONFIG.SYS DEVICE=C:DOSHIMEM.SYS DEVICE=C:DOSEMM386.EXE NOEMS X=D200-D2FF FILES=40 BUFFERS=30 SHELL=C:DOSCOMMAND.COM /P /E:1024 LASTDRIVE=G Sample AUTOEXEC.BAT CDPW STARTNET.
65 Configuration Reference LANABASE = 0 [DATALINK] DRIVERNAME = DLL$MAC LG_BUFFERS = 14 SM_BUFFERS = 6 OUTSTANDING = 32 BINDINGS = M32ANDIS DECPARM = C:PW IRQ = 5 ;; YOUR DECNET ADDRESS IS AA0004008407 ;; [M32ANDIS] DRIVERNAME=INTEL$ Windows f or W orkgroups 3.
CHAPTER3 66 Sample AUTOEXEC.BAT C:WINDOWSNET START Sample PROTOCOL.INI [NETWORK.SETUP] VERSION=0X3110 NETCARD=M32AMAC,1,M32AMAC,1 TRANSPORT=MS$NETBEUI,NETBEUI TRANSPORT=MS$NDISHLP,MS$NDISHLP LANA0=M32.
67 Configuration Reference NETCARD=M32ANDIS.EXE TRANSPORT=*NETBEUI,NDISHLP.SYS Windows f or W orkgroups Using the ODI Driver with NetW are as Secondary Network Sample STARTNET.BAT REM INTEL PRO/100 CB — DO NOT CHANGE LINES BELOW :M32A_MENU @ECHO OFF CLS GOTO %CONFIG% :M32A_E_INTEL C: CD C:NWCLIENT IF NOT EXIST M32AODI.
CHAPTER3 68 CD REM INTEL PRO/100 CB — DO NOT CHANGE LINES ABOVE Sample CONFIG.SYS REM INTEL PRO/100 CB — DO NOT CHANGE LINES BELOW (MENU) [MENU] MENUITEM=M32A_E_INTEL,LOAD INTEL ETHEREXPRESS PRO/.
69 Configuration Reference SET TEMP=C:DOS C:DOSSMARTDRV.EXE /X C+ REM INTEL PRO/100 CB — DO NOT CHANGE LINES BELOW :M32A_MENU @ECHO OFF CLS GOTO %CONFIG% :M32A_E_INTEL C:WINDOWSNET START C: CD C:NWCLIENT IF NOT EXIST C:NWCLIENTSTARTNET.BAT GOTO M32A_ERROR CALL C:NWCLIENTSTARTNET.
CHAPTER3 70 NETCARD=M32A$ODI,1,M32A$ODI,4 TRANSPORT=MS$NWLINKNB,NWLINK TRANSPORT=MS$NETBEUI,NETBEUI LANA0=M32A$ODI,1,MS$NETBEUI LANA1=M32A$ODI,1,MS$NWLINKNB [NET.
71 Configuration Reference Driver P arameters Reference The following paragraphs present configuration guidelines for each of the driver types: NDIS2 and NDIS3, ODI, and packet. These guidelines are followed by a comprehensive “keyword” reference section.
CHAPTER3 72 Most installations will be able to use the settings implemented in the NET.CFG file by the Intel Installation Program. If any parameters need to be changed, use an ASCII text editor to open and modify the NET.
73 Configuration Reference NOPREFETCH NOT PRESENT S (COMMAND LINE ONLY: SHOW RESIDENT LAN DRIVERS) U (COMMAND LINE ONLY: UNLOAD) OS/2 ODI Driver Configuration Notes (CBEODI.OS2) The OS/2 ODI driver M32AODI.OS2 conforms to the Novell "ODI Developer's Guide for OS/2 Client Driver Hardware Specific Modules" version 2.
CHAPTER3 74 NDIS 2.0.1 DOS Driver Configuration Notes The DOS NDIS driver M32ANDIS.EXE conforms to the 3Com/Microsoft LAN Manager Network Driver Interface Specification (NDIS) version 2.0.1. It is a DOS-based executable terminate-and-stay-resident (TSR) program that will configure itself according to the options specified in the PROTOCOL.
75 Configuration Reference NDIS 2.0.1 Keywords (M32ANDIS.EXE and M32ANDIS.OS2) KEYWORD DEFAULT VALID VALUES DRIVERNAME=INTEL$ (REQUIRED FIRST ITEM IN PROTOCOL.
CHAPTER3 76 M32A.SYS (NDIS 3) Settings for Micr osoft Windows NT and Windows 95 M32A.SYS is an NDIS 3 Miniport driver. It conforms to the Microsoft Network Driver Interface Specification (NDIS). It supports both Windows NT and Windows 95. Windows NT Support The M32A.
77 Configuration Reference Parameter Default Valid Values Registry Value I/O PORT 0XF800 0X1000-0XF800 SAME MEMORY ADDRESS 0XD4000 0XC0000-0XDF000 SAME INTERRUPT 5 3, 4, 5, 7, SAME 10, 11, 15 INTERRUP.
CHAPTER3 78 The network node address can be modified by manually editing the registry and adding the parameter ‘NetworkAddress’ with a hexadecimal string value, such as ‘00A0C9112233’. If the user does NOT specify a ‘NetworkAddress’ then the M32A.
79 Configuration Reference SOCKET 0 AUTODETECT 0 11 22 33 44 The network node address can be modified by specifying a value for ‘NetworkAddress’ such as ‘00A0C9112233’.
CHAPTER3 80 ERT HIGH LOW, MEDIUM, or HIGH NOEARLYRX NOT PRESENT NOEARLYTX NOT PRESENT LINESPEED AUTO 10 or 100 LINEMODE HALF HALF or FULL LINKDISABLE NOT PRESENT NOBURST NOT PRESENT LATENCY 32 0 - 255.
81 Configuration Reference P acket Driver Settings (f or driver M32APD .COM) Packet driver parameters must be stated on the M32APD.COM command line when running the packet driver. Packet Driver Configuration Notes The Intel packet driver M32APD.COM conforms to FTP Software’s public domain packet-driver specification.
CHAPTER3 82 LINKDISABLE NOT PRESENT NOBU RST NOT PRESENT LATENCY 32 0 - 2 55 CACHE 32 0, 4, 8, 16, OR 32 NOWRITEPOST NOT PRESENT NOPREFETCH NOT PRESENT SINT 60 (60 - 80) VERB OSE NOT PRESENT Packet Driver Example A typical sequence for loading the packet driver M32APD.
83 Configuration Reference Ke ywo rd Alphabetical Reference ? displays command summary for driver CACHE sets the system cache line size on the CardBus Bridge. Valid arguments are system dependent and may include only 0 (cache disabled), 4, 8, 16, or 32.
CHAPTER3 84 I/O PORT see IOADDRESS IRQ specifies a hardware interrupt for use by the adapter. If the computer system uses PCI interrupts on the CardBus Bridge, this parameter is ignored (unless the ISAIRQ keyword is used as an override). If this parameter is not specified the driver will detect an IRQ automatically.
85 Configuration Reference For 32-bit NDIS3 Driver (M32A.SYS): LINESPEED forces operation to 10 or 100 Mbps. Valid parameters are AutoDetect, 10 Mbps, and 100 Mbps. Default keyword is AutoDetect. LINKDISABLE disables link integrity for non-IEEE 10BASE-T networks such as StarLAN 10.
CHAPTER3 86 NOLED turns off LED indicators on LAN adapter module to conserve power. NOPREFETCH disables prefetching in memory-mapped I/O mode by turning off this capability on the CardBus bridge. Using this keyword may negatively impact performance. PCIIRQ use this keyword to force the driver to use PCI IRQ routing.
87 Configuration Reference TXBUFFERSIZE sets the size of the adapter transmit packet buffer. This is the number of transmit packets in decimal in the range 1 - 10 for 16-bit drivers and 1 - 100 for the 32-bit ODI driver. Each packet adds approximately 1520 bytes to the resident size of the driver.
CHAPTER3 88.
89 This chapter contains troubleshooting information covering the most common issues encountered when installing the PRO/100 CardBus adapter, based on information developed by Intel Customer Support.
90 CHAPTER 4 Additional Sources of Information In addition to this User’s Guide , your computer and network documentation should also be consulted as needed.
91 Troubleshooting Diagnostic Self T est (MS-DOS only) Intel provides a DOS-based self test diagnostics program. This program, located on the PRO/100 CardBus adapter Network Drivers Disk, tests several PRO/100 CardBus adapter functions. It also reports test results, the serial number of the unit, and the node address.
92 CHAPTER 4 Main Screen The program consists of several function “buttons” and a view pane. Pressing or invoking a function will bring up the corresponding screen in the view pane. This view remains until another is selected. To exit M32ATEST type 'x' or push the 'Exit' button.
93 Troubleshooting SOFTWARE This function attempts to determine what software is currently loaded which will affect the operation of the card. It displays the current version of DOS and Windows, and any Card and Socket Services available. HARDWARE This function attempts to determine if a CardBus Controller exists on the machine.
94 CHAPTER 4 Error Messa g es Except as noted, these messages are specific to the Intel PRO/100 CardBus adapter. They are listed in strict numerical/alphabetical order, i.e., numbers appear before letters and messages starting with “The” are under the letter T, initial “A” or “An” under the letter A.
95 Troubleshooting No free memory segment was found The resource selection in the driver was unable to find a 4KByte block of memory available for the driver's use. Check to ensure that a 4KByte block of memory is excluded from any memory managers present.
96 CHAPTER 4 Please specify a number between 3 and 15 for the IRQ keyword The IRQ keyword only accepts decimal numbers between 3 and 15. Please specify either HALF or FULL for the LINEMODE keyword The LINEMODE keyword determines the duplex mode of the network.
97 Troubleshooting The LINESPEED keyword must be set to 10 or 100 The LINESPEED keyword is used to force the network line speed to either 10 Mbps or 100 Mbps. If the keyword is not present the line speed is automatically detected. The loopback test failed Before the driver finishes loading, it runs a loopback test.
98 CHAPTER 4 The selected memory is a ROM address The MEMORY keyword was used to force a particular memory address, but the resource checking in the driver reported a failure. To override the resource checking and load the driver anyway, use the NOCHECK keyword.
99 Troubleshooting NOTE: This section applies only if you are running MS-DOS, Microsoft Windows 3.x, or Workgroups 3.11 with Card and Socket Services that support CardBus. Upgrading to new drivers from Intel may also be required, as new Card and Socket software is released.
100 CHAPTER 4 B When the PRO/100 CardBus adapter driver is loaded it either reads a configuration file or uses command line parameters to determine which resources it should use. The following is a list of driver types, driver file names, and the configuration method used by each: Type File Name Configuration Method ODI M32AODI.
101 Troubleshooting SystemSoft The SystemSoft’s CardSoft Card and Socket Services are loaded in the CONFIG.SYS file and generally include the following lines: DEVICE=C:CARDSOFTSOCKET_SERVICES_DRIVER (This file varies by machine type) DEVICE=C:CARDSOFTCS.
102 CHAPTER 4 C Reboot the machine by turning off the power and turning it back on again (cold boot). If the driver still fails to load, the cause is generally a resource conflict. Common causes of resource conflicts include sound systems, other PC Card adapters, and built in ROMs.
103 Troubleshooting 5 CC000 11 320 6 D2000 15 320 7 CC000 15 320 8 D2000 5 340 9 CC000 5 340 10 D2000 10 340 11 CC000 10 340 12 D2000 11 340 13 CC000 11 340 14 D2000 15 340 15 D2000 15 340 The driver .
104 CHAPTER 4 E If the problem persists, and you’re on a 10BASE-T network, try patching directly into the hub. If the adapter works when plugged directly into the hub, but not when attached via a longer cable run, verify that the cable run length is within the IEEE 10BASE-T specification (100 meters).
105 Troubleshooting 86 LOADING NDIS DATA LINK... 89 PERFORMING NETBIND... 92 LOADING SCHEDULER... 93 LOADING DNP... 94 LOADING REDIRECTOR... 95 SETTING COMPUTER NAME... 98 NETWORK LOADING COMPLETED SUCCESSFULLY Use /~# parameter when you run Pathworks SETUP.
106 CHAPTER 4 3 If everything loads and you don’t connect to the network, try the following a Choose another INT setting. b Verify that you have a good cable. c Verify that you have excluded the memory being used by the Intel adapter from the EMM386.
107 Troubleshooting Put a copy of the directory for CAB files of Windows 95 from the CD- ROM on to your local hard drive. This will take up approximately 35MB of space. This will allow you to change settings on the system without using your CD-ROM. This also allows you to install Windows 95 without depending on the real mode SCSI CDROM driver.
108 CHAPTER 4 6 The dialog box “Welcome to the PC Card (PCMCIA) Wizard” will ask the following question: “Are you using a PC card (networking card, CD-ROM connected to a SCSI card, etc.
109 Troubleshooting e1 Let Windows 95 automatically find the drivers for you. This is recommended. To do this click the Next button 3 times. This lets Windows 95 automatically modify the following files: CONFIG.SYS, AUTOEXEC.BAT, and SYSTEM.INI e2 Choose the drivers yourself if none are selected.
110 CHAPTER 4 Manual Installation of the PRO/100 CardBus adapter under Windows 95 OSR2 1 Click the Start button in the lower left corner of the screen. 2 Choose the menu item: Settings. 3 Choose the menu item: Control Panel. 4 Double-click the System icon.
111 Troubleshooting Card slot). 10 After Windows 95 OSR2 comes up and all drive activity has stopped, reinsert the Adapter in the same PC Card slot it was in previously. Click the Start button, select Settings, and then Control Panel. Double-click Add New Hardware.
112 CHAPTER 4 Microsoft Windows for Workgroups This section describes general troubleshooting procedures and possible error codes you might encounter under Windows for Workgroups. Before doing anything else, check your configuration files against the sample files in Chapter 3, Configuration Reference of this document.
113 Troubleshooting When using ODI for NetWare, I get attached to server, but can’t see the F: login drive, “drive not ready” is the error message you get when trying to login.
114 CHAPTER 4 Make sure your WINDOWSPROTOCOL.INI has proper bindings. The MS$NDISHLP and NETBEUI sections should have a BINDINGS=M32AMAC. Chances are, the binding statement is wrong. See the sample PROTOCOL.INI file. WFW works the first time I boot the machine, but after a warm boot, it fails to see other machines.
115 Troubleshooting If it is already excluded, try changing memory to CC000. Make sure to make corresponding changes in the EMM386.EXE exclusion parameter in the CONFIG.SYS. For example: x=cc00-cdff 5 Try swapping cards or cables whenever possible during troubleshooting.
116 CHAPTER 4 • Read the README file on the floppy disk. It contains important information (including known incompatibilities and machine specific issues) that may solve your problem. • Obtain current versions of drivers for your adapter from the Intel BBS or http://support.
117 Troubleshooting • Make sure that the Intel adapter is not conflicting (interrupt, memory address, I/O address) with any other adapters or hardware that is installed in the computer (including sounds cards, CD-ROM drives and PEN devices). • Try loading the CardBus drivers at different memory locations (i.
118 CHAPTER 4.
119 World Wide W eb & Intel Bulletin Board Internet FTP Service (BBS) Access Intel’ s World Wide Web Use Intel’ s BBS. Dial home pages or download in by modem at 8-N-1, information using anonymous FTP .
120 Intel Web and Internet Sites Support: http://support.intel.com News: news://cs.intel.com Network Products: http://www.intel.com/network Corporate: http://www.
121 Appendix B Specifications General Specifications Model MBLA3200 Cable: 100Base-TX unshielded twisted pair for use on Category 5 (data grade) cabling; 10Base-T unshielded twisted pair (UTP) Connector: RJ-45 Operating Distance: 328 ft (100 m) Ethernet specifications Ethernet IEEE 802.
122 APPENDIX B General Specifications (continued) Temperature Range: Operating: 32°F to 131°F (0°C to 55°C) Storage: -4°F to 149°F (-20°C to 65°C) Humidity: 95% max.
123 Specifications T echnical Specifications • Supports Toshiba ToPIC 95, Texas Instruments PCI 1130 and PCI 1131, Cirrus Logic CL-PD 6832 and Ricoh. • Variable interrupts, 3 to 15. • Variable I/O window, 128 bytes needed. • Requires only a 4Kbyte memory window on a 4Kbyte bound- ary, within segment C000h to EF00h (DOS drivers only).
124 APPENDIX B.
125 Intel warrants to the original owner that the hardware product delivered in this package will be free from defects in material and workmanship. This warranty does not cover the product if it is damaged in the process of being installed or improperly used.
126 APPENDIX C Returning a defective product From North America: Before returning any product, contact Intel Customer Support and obtain a Return Material Authorization (RMA) number by calling +1-916-377-7000.
127 Limited Lifetime Hardware Warranty Some states do not allow the exclusion or limitation of incidental or consequential damages, so the above limitations may not apply to you. Software provided with the hardware product is not covered under the hardware warranty described above.
128 APPENDIX C.
129 BY USING THIS SOFTWARE, YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS AGREEMENT. DO NOT USE THIS SOFTWARE UNTIL YOU HAVE CAREFULLY READ AND AGREED TO THE FOLLOWING TERMS AND CONDITIONS. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE SOFTWARE PACKAGE AND ANY ACCOMPANYING ITEMS.
130 APPENDIX D TRANSFER: You may transfer the Software to another party if the receiving party agrees to the terms of this Agreement and you retain no copies of the Software and accompanying documentation. Transfer of the Software terminates your right to use the Software.
131 Network Software License Agreement U.S. GOVERNMENT RESTRICTED RIGHTS: The Software and documentation were developed at private expense and are provided with “RESTRICTED RIGHTS.” Use, duplication, or disclosure by the Government is subject to restrictions as set forth in FAR 52.
132 APPENDIX D.
133 Appendix E Regulatory Ag ency Notices FCC Compliance Statement This product has been tested and found to comply with the limits for a Class B computing de vice pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation.
APPENDIX E 134 NOTE This device complies with Part 15 of the FCC Rules. Operation is subject to the following tw o conditions: (1) This de vice ma y not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
135 Index Symbols 100Base-TX 1 10Base-T 1 15-pin connector 1, 4 A Ar tisoft LANtastic 26 installation 26 sample configuration files 60 troubleshooting 104 A T&T StarGR OUP installation 26 A utodet.
136 INDEX troubleshooting 104 Def ault values 25 Device driv er 25 Diagnostic T est Utility parameters 82 Diagnostics 91 Driver par ameters 71 E Equipment, required 2 Error messages 94 Exclusion, memo.
137 I N D E X manual 41 Microsoft Windows 21 Microsoft Windows f or Workgroups 21 Nov ell NetW are 21 Program, Xircom 21, 25, 44, 55 VLM shell 21 Installation, manual Windows 95 OSR2 110 Intel Web and.
138 INDEX operating system 21, 25 software installation 25 NETX shell suppor t 21 Nov ell NetW are 47 and FTP PC/TCP 36 installation 21 troubleshooting 115 O ODI driver FTP PC/TCP 33 gener ic 37 Micro.
139 I N D E X S Sample files, configuration 60 Ar tisoft LANtastic 60 Bany an VINES 63 DEC P A THW ORKS 64 Windows f or W or kgroups 65 Self test 91 slots, PC Card 2 Software updates 119 SunSoft PC-NF.
140 INDEX ODI driver 44 removing old installation 46 with NetW are 44 Windows NT 18 W ollongong PathW a y Access installation 52 W ollongong PathW a y Access for DOS 52 NDIS driver 52 ODI driver 53 W .
An important point after buying a device Intel PRO (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought Intel PRO yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data Intel PRO - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, Intel PRO you will learn all the available features of the product, as well as information on its operation. The information that you get Intel PRO will certainly help you make a decision on the purchase.
If you already are a holder of Intel PRO, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime Intel PRO.
However, one of the most important roles played by the user manual is to help in solving problems with Intel PRO. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device Intel PRO along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
