Page 1: How To Use This Manual
PRO/100 CardBus adapter. It is designed to help both new and experienced network users install and configure the Intel product in the shortest time possible. Overview of the Installation Process For an overview of the installation process, see the Late Breaking News card and Chapters 1 and 2 in this User’s Guide.
Page 2 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. Other product and corporate names may be trademarks of other companies and are used only for explanation and to the owners’...
Page 3: Table Of Contents
Contents Hardware Installation ... 1 Before Installing Hardware ... 1 Installing the Hardware ... 3 What to Do Next ... 5 Software Installation ... 7 CardBus Installation Guidelines ... 7 Installing with Windows 95 ... 8 Determining Your Version of Windows 95 ... 8 Installing with Windows 95 ...
Page 4 C O N T E N T S IBM Local Area Network Support Program ... 38 IBM Local Area Network Support Program (version 1.2) ... 39 IBM PC LAN and IBM DOS LAN Requester ... 40 Manual Installation ... 41 Microsoft LAN Manager ...
Page 5 C O N T E N T S Network Operating System Troubleshooting ... 104 Troubleshooting Checklist ... 116 Intel Automated Customer Support ... 119 Specifications ... 121 General Specifications ... 121 General Specifications (continued) ... 122 Compatibility ... 122 Technical Specifications ... 123 Limited Lifetime Warranty ...
Page 6 C O N T E N T S...
Page 7: Hardware Installation
Chapter 1 Hardware Installation 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. The PRO/100 CardBus adapter provides access to both 10 Mbps and 100 Mbps networks with a single adapter cable, and auto-senses 10 Mbps or 100 Mbps network speed.
Page 8 C H A P T E R 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.
Page 9: Installing The Hardware
Installing the Hardware 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.
Page 10 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). Press the cable connector gently into the connector on the card until it clicks into place.
Page 11: What To Do Next
• 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. Software Installation. You will need the Intel Installation Disk and Network Drivers Disk.
Page 12 C H A P T E R 1...
Page 13: Software Installation
Chapter 2 Software Installation CardBus 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. In these cases you will be able to use the PRO/100 CardBus adapter, but you will not be able to use or swap PC Cards or other CardBus adapters while using the adapter.
Page 14: Installing With Windows 95
#2 (also known as Windows 95 OSR2 or version 4.00.950b). Please review the README.TXT file on the Installation Disk and visit the Intel website for the latest information on CardBus support in Windows Determining Your Version of Windows 95 Follow the steps below to determine which version of Windows 95 you are running: Click on the Start button.
Page 15: Installing With Windows 95
The Select Network Adapter window opens. Click Have Disk. The Install From Disk window opens. Insert the Intel Drivers Disk. 10 With A:\ in input box, click OK (or type in the correct path). The Select Network Adapter window reopens.
Page 16 C H A P T E R 2 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.
Page 17 In the Control Panel, double-Click the System icon. The System Properties window opens. Click the Device Manager tab. Double-click PCMCIA Socket. Click PCIC or compatible PCMCIA controller. Click Remove. A removal confirmation window opens. Click OK. The System Settings Change window opens. Remove the Network Drivers Disk from the floppy drive.
Page 18 Choose Control Panel. The Control Panel window opens. Double-click the Network icon. The Network window opens. Click the Configuration tab. Select the “Intel EtherExpress PRO/100 Mobile CardBus 32 Manual Load.” Click Remove. Click OK. Click No when prompted to restart the computer.
Page 19 Click OK. The System Properties window reopens. 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.00.950 or 4.00.950A If you are installing the PRO/100 CardBus adapter on Toshiba portables with CardBus support, including the Tecra 700 series, Tecra 500 series...
Page 20 Choose Control Panel. The Control Panel window opens. Double-click the Network icon. The Network window opens. Click the Configuration tab. Select the “Intel EtherExpress PRO/100 Mobile CardBus 32 Manual Load.” Click Remove. Click OK. Click No when prompted to restart the computer.
Page 21: Installing With Windows 95
Insert the PRO/100 CardBus adapter. Allow the Plug and Play facility to install the PRO/100 CardBus adapter. When prompted for a disk, insert the Intel Network Drivers Disk. Enabling another PCMCIA or CardBus card in Windows 95 Version 4.00.950b (OSR2) or Later...
Page 22: Installing Netware Client 32 Odi Drivers Under Windows 95
(ask your Network Administrator if you do not know which version of NetWare Client 32 you have). Follow the instructions earlier in this chapter for installing the Intel PRO/100 CardBus adapter under Windows 95 version 4.00.950b. This procedure will install the adapter with the NDIS3 (Miniport) driver.
Page 23 Adapter. Next, in the Select Network Adapters box click Have disk and insert the Intel Network Drivers Disk (Disk 2). Select OK at the Install from Disk box. In the next window highlight Intel in the manufacturers column and Intel EtherExpress PRO/100 CardBus Adapter for NetWare Client 32 V1.0.
Page 24: Installing With Windows Nt 3.51 And 4.0
CardBus adapter. Please review the README.TXT file on the Installation Disk and visit the Intel website for the latest information on CardBus support in Windows The installation steps for Windows NT 3.51 and Windows NT 4.0 are slightly different, so they are addressed separately here.
Page 25 Double-click the Control Panel. The Control Panel opens. Double-click the Network icon. The Network Settings window opens. Choose the “Intel EtherExpress PRO/100 Mobile CardBus 32.” Click Remove. Click Yes to confirm. To install with Windows NT 4.0: Insert the PRO/100 CardBus adapter.
Page 26 Card in Windows NT 4.0. To remove the PRO/100 CardBus adapter from Windows NT 4.0: Double-click the Control Panel. The Control Panel opens. Double-click the Network icon. The Network Settings window opens. Choose the “Intel EtherExpress PRO/100 Mobile CardBus 32.” Click Remove.
Page 27: Installing With Windows 3.X And Windows For Workgroups
When your system comes back up, log in to the network. NOTE: The NetWare VLM shell is used to connect to your NetWare server. The Intel Installation Program will decompress and configure the necessary files. If you do not plan to use the Installation Program, see “Manual Installation” in the alphabetical section of this chapter for instructions on how to decompress and load the NetWare VLM files.
Page 28: Installing Under Ibm Os/2 (Warp 3.0 And 4.0) Using The Ndis Or Odi Driver
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.
Page 29 1 Remove OS/2’s Card and Socket Services according to IBM’s instructions. 2 In order to install Intel’s OS/2 ODI driver, the Novell Netware Client for OS/2 installation disks are needed. Insert disk 1 of the OS/2 client installation disks (the WSOS2_1 disk) in the floppy drive and run INSTALL.
Page 30 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. Put the Intel Network Drivers Disk in the floppy drive and click OK.
Page 31: Installing Network Software
The section is organized in alphabetical order by network operating system vendor. Unless otherwise indicated, these instructions are designed to be used with the Intel Installation Program. They assume a first-time installation of client software on a workstation, using the configuration...
Page 32: Artisoft Lantastic Version 6.0
Run the Intel Installation Program from the Installation Disk. Choose Artisoft LANtastic from the Select Network Operating System screen. Follow the prompts to complete the Intel segment of the installation. Run the Artisoft LANtastic 6.0 “install” program. Specify C:\LANTASTI as the destination directory (or the directory set with the Intel Installation Program).
Page 33 Run the Intel Installation Program from the Installation Disk. Choose Banyan VINES from the Select Network Operating System screen. Follow the prompts to complete the Intel segment of the installation. The Installation Program also creates a \VINES directory on your hard disk.
Page 34: Dec Pathworks Versions 5.X Or 6.X
Choose DEC PATHWORKS from the Select Network Operating System screen. Follow the prompts to complete the Intel segment of the installation. Check the README file on your PATHWORKS SETUP disk for requirements such as lastdrive, setver, etc. You will need 500 K of free conventional memory and about 1 MB of extended memory to run PATHWORKS SETUP.
Page 35 DRIVER FILE: A:\M32ANDIS.EXE PROTOCOL.INI STUB: A:\DEC\PROTOCOL.INI Skip the Additional Files section. 12 Insert the Intel Network Drivers Disk when prompted. 13 Enter your node information when prompted. 14 Save the PROTOCOL.INI file with the default settings. At this point, the SETUP program will try to connect to the DECnet server.
Page 36 NI_IRQ = [IRQ VALUE FROM STEP 5 OF THE FIRST PROCEDURE ABOVE] The ni_irq value must be the same as the interrupt value used for the Intel adapter. Verify that the [m32andis] section has the following lines and...
Page 37: Ftp Software Lanwatch
FTP Software LANWatch 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.
Page 38 Run the Intel Installation Program from the Installation Disk. Choose FTP LANWatch from the Select Network Operating System screen. Follow the prompts to complete the Intel segment of the installation. Install LANWatch according to the instructions in your FTP LANWatch manual.
Page 39: 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. For information on which driver is appropriate for your network environment, see the FTP PC/TCP documentation.
Page 40 16 Reboot the PC.FTP PC/TCP 3.X with OnNet 1.1 with Windows 3.1 FTP PC/TCP 3.X with OnNet 1.1 with Windows 3.1 Run the Intel Installation Program from the Installation Disk. From the Select Network Operating System screen, choose FTP PC/ TCP.
Page 41 Run the Intel Installation Program from the Installation Disk. Choose FTP PC/TCP from the Select Network Operating System screen. Follow the prompts to complete the Intel segment of the installation. Exit to DOS, switch to the C:\INTEL\M32A directory and run M32APD.COM.
Page 42 Run the Intel Installation Program from the Installation Disk. Choose FTP PC/TCP from the Select Network Operating System screen. Follow the prompts to complete the Intel segment of the installation. Install PC/TCP according to the instructions in your FTP PC/TCP manual.
Page 43: Generic Installation
Log in to the network. Generic Installation If your NOS is not listed in the Intel Installation Program, you can try selecting “Generic NDIS Driver” or “Generic ODI Driver” in the Intel Installation Program and clicking the Install button. A sample configuration file containing parameters optimized for your system will be created in the \INTEL\M32A directory on your hard disk.
Page 44: Ibm Local Area Network Support Program
Under Environment Information, respond “no” to the question “Do you have adapter option disks?” Choose the Intel CardBus adapter from the list provided. If prompted to do so, insert the Intel Network Drivers Disk when prompted and type the path A:\NDIS Press Esc twice to bypass error messages.
Page 45: Ibm Local Area Network Support Program (Version 1.2)
Choose IBM LAN Support Program from the Select Network Operating System screen. Follow the prompts to complete the Intel segment of the installation. Install the IBM Local Area Network Support Program according to the instructions in the IBM Local Area Network Support Program User’s Guide.
Page 46: Ibm Pc Lan And Ibm Dos Lan Requester
15 Use a text editor to edit the keyword settings in the PROTOCOL.INI file in the C:\LSP directory to match the keywords contained in the sample PROTOCOL.INI file located at C:\INTEL\M32A as required (unless you are using PRO/100 CardBus adapter default settings).
Page 47: Manual 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.SYS, AUTOEXEC.BAT, and configuration files such as NET.CFG (for ODI) or PROTOCOL.INI (for NDIS).
Page 48 System screen. Select “Yes” on the Attached to Network File Server screen. Select Microsoft LAN Manager. Follow the prompts to complete the Intel segment of the installation. Start Windows and, in the Network program group, double-click on the Network Setup icon.
Page 49: Windows For Workgroups
Windows for Workgroups version 3.11 alone or with NetWare. These instructions assume that Windows for Workgroups has already been installed. Remove any earlier version of the Intel drivers before installing the new version. No NDIS 3 driver is supplied for Windows for Workgroups.
Page 50 C H A P T E R 2 Windows for Workgroups Version 3.11 and NetWare (Using the ODI driver) To configure Windows for Workgroups with NetWare, run the Intel Installation Program and choose Windows for Workgroups. Choose YES to “Connect to Network Server.”...
Page 51 Network Adapter and click OK. 18 When prompted for an “unlisted, updated, or vendor-provided network driver disk,” insert the Intel Network Drivers Disk and click 19 Select “Intel EtherExpress PRO/100 Mobile CardBus 32” and click 20 Close the Network Drivers dialog box and click OK in the Network Setup box.
Page 52 10 When prompted for an “unlisted, updated, or vendor-provided network driver disk,” insert the Intel Network Drivers Disk. 11 Select “Intel M32A NDIS 2.01 Real Mode” and click OK. 12 Close the Network Drivers dialog box and click OK in the Network Setup box.
Page 53: Novell Netware
13 Follow the instructions for installing drivers for Windows for Workgroups alone or Windows for Workgroups and NetWare. Novell NetWare ODI Driver The Intel ODI driver allows for the concurrent use of Novell NetWare and other protocols that support Novell’s Open Data-Link Interface (ODI) specification. NetWare Run the Intel Installation Program from the Installation Disk.
Page 54: Sunsoft Pc-Nfs (Version 3.5)
Choose SunSoft PC-NFS from the Select Network Operating System screen. Follow the prompts to complete the Intel segment of the installation. Install PC-NFS for Ethernet according to instructions in the PC-NFS documentation. Choose NDIS setup, and follow the instructions to complete the setup.
Page 55: Novell Netware 32-Bit Odi Drivers
4 Follow the onscreen instructions 5 At the Select a LAN Driver screen, select User Specified LAN Driver 6 Insert the Intel Network Drivers Disk in drive A 7 Type A: and press enter. 8 Select Intel EtherExpress PRO/100 CardBus Adapter...
Page 56: Installing Under Windows 95
3 When the ODI Driver Selection Dialog box appears, select User Specified Driver and click Next. 4 When prompted, insert the Intel Network Drivers Disk in drive A: 5 Select the driver a:\m32a.lan 6 To complete installation, follow the onscreen instructions.
Page 57: Ungermann-Bass Net/One For Dos
LAN Manager and MS-NET networks. There are two NDIS driver packages available from UB: XNS BNS/NDIS and TCP BNS/NDIS. These packages, used with a Intel NDIS driver, provide files that support DOS workstations. They are available from UB and authorized UB representatives.
Page 58: Wollongong Pathway Access For Dos
Wollongong PathWay Access for DOS NDIS and ODI Drivers Wollongong PathWay Access for DOS can be installed using Intel NDIS or ODI drivers. Installation instructions for both types of driver are provided below. For information on which driver is appropriate for your network environment, refer to the Wollongong PathWay Access for DOS documentation.
Page 59 Choose Wollongong PathWay Access from the Select Network Operating System screen. Follow the prompts to complete the Intel segment of the installation. Install PathWay Access for DOS Kernel and Drivers programs according to the instructions in the PathWay Access for DOS manual.
Page 60 C H A P T E R 2...
Page 61: Configuration Reference
Intel Installation Program. You can modify configuration settings by re-running the Intel Installation Program or by running IEDIT, the Intel System File Editor installed in the Intel Mobile Windows program group.
Page 62: Special Features
To use Card and Socket Services with the PRO/100 CardBus adapter, the Card and Socket Services must support CardBus. At press time, Intel had tested the following Card and Socket Services with the PRO/100 adapter: Product/Operating System CardWizard v.
Page 63 NOTE: For DOS and Windows 3.1 systems, the Intel PRO/100 CardBus driver may be able to co-exist with older Card and Socket Services, even though the Card and Socket Services do not directly support CardBus. Consult the installation instructions in...
Page 64 The HotSwap 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. Upgrading to new drivers from Intel may also be re- quired, as new Card and Socket software is released.
Page 65 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. Power Management Guidelines HotSwap and suspend/resume operations are subject to limitations dictated by the network operating system.
Page 66: Sample Configuration Files For Selected Network Operating Systems
CONFIG.SYS. The same is true for the line call c:\lantasti\startnet.bat in your AUTOEXEC.BAT file. Sample CONFIG.SYS device=c:\dos\himem.sys REM INTEL PRO/100 CB — DO NOT CHANGE LINES BELOW DEVICE=C:\DOS\EMM386.EXE NOEMS X=D200-D2FF REM DEVICE=C:\DOS\EMM386.EXE NOEMS REM INTEL PRO/100 CB — DO NOT CHANGE LINES ABOVE...
Page 67 FILES=50 BUFFERS=30 REM INTEL PRO/100 CB — DO NOT CHANGE LINES BELOW DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI DEVICE=C:\LANTASTI\M32ANDIS.EXE REM INTEL PRO/100 CB — DO NOT CHANGE LINES ABOVE Sample AUTOEXEC.BAT PATH=C:\UTIL;C:\DOS; PROMPT $P$G CALL C:\LANTASTI\STARTNET.BAT Sample PROTOCOL.INI ;PROTOCOL.INI FOR LANTASTIC VERSION 6.00 ;—————— USING INTEL ETHEREXPRESS PRO/100 32-BIT ;MOBILE ADAPTER...
Page 68 C H A P T E R 3 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.CFG REDIR T4700 @STARTNET.CFG IF EXIST NOSHARE GOTO :NOSHARE SERVER C:\LANTASTI.NET @STARTNET.CFG NET LOGIN \\T4700 GOTO :CONTINUE...
Page 69: Banyan Vines
If you are getting Banyan VINES Error codes 10xx, check your C:\VINES\NDISBAN.DOC for explanations of error codes. Sample CONFIG.SYS DEVICE=C:\DOS\HIMEM.SYS REM INTEL PRO/100 CB — DO NOT CHANGE LINES BELOW (EMM) DEVICE=C:\DOS\EMM386.EXE NOEMS X=D200-D2FF REM DEVICE=C:\DOS\EMM386.EXE NOEMS REM INTEL PRO/100 CB — DO NOT CHANGE LINES ABOVE...
Page 70: Dec Pathworks 5.0 And 5.1
C H A P T E R 3 [INTELNET] DRIVERNAME = INTEL$ DEC PATHWORKS 5.0 and 5.1 Sample CONFIG.SYS DEVICE=C:\DOS\HIMEM.SYS DEVICE=C:\DOS\EMM386.EXE NOEMS X=D200-D2FF FILES=40 BUFFERS=30 SHELL=C:\DOS\COMMAND.COM /P /E:1024 LASTDRIVE=G Sample AUTOEXEC.BAT CD\PW STARTNET.BAT Sample PROTOCOL.INI (after completion of install process)
Page 71: Windows For Workgroups 3.11
;; YOUR DECNET ADDRESS IS AA0004008407 [M32ANDIS] DRIVERNAME=INTEL$ Windows for Workgroups 3.11 Sample CONFIG.SYS DEVICE=C:\DOS\HIMEM.SYS REM INTEL PRO/100 CB — DO NOT CHANGE LINES BELOW (EMM) DEVICE=C:\DOS\EMM386.EXE NOEMS X=D200-D2FF REM DEVICE=C:\DOS\EMM386.EXE NOEMS REM INTEL PRO/100 CB — DO NOT CHANGE LINES ABOVE FILES=40 BUFFERS=30 DEVICE=C:\WINDOWS\IFSHLP.SYS...
Page 72 C H A P T E R 3 Sample AUTOEXEC.BAT C:\WINDOWS\NET START Sample PROTOCOL.INI [NETWORK.SETUP] VERSION=0X3110 NETCARD=M32AMAC,1,M32AMAC,1 TRANSPORT=MS$NETBEUI,NETBEUI TRANSPORT=MS$NDISHLP,MS$NDISHLP LANA0=M32AMAC,1,MS$NETBEUI LANA1=M32AMAC,1,MS$NDISHLP [NETBEUI] BINDINGS=M32AMAC,ASYMAC LANABASE=0 DRIVERNAME=NETBEUI$ SESSIONS=10 NCBS=12 [PROTMAN] DRIVERNAME=PROTMAN$ PRIORITY=MS$NDISHLP [M32AMAC] DRIVERNAME=INTEL$ [MS$NDISHLP] DRIVERNAME=NDISHLP$ BINDINGS=M32AMAC Sample [NETWORK DRIVERS] SECTION IN SYSTEM.INI [NETWORK DRIVERS] DEVDIR=C:\WINDOWS LOADRMDRIVERS=YES...
Page 73: Windows For Workgroups Using The Odi Driver With Netware As Secondary Network
NETCARD=M32ANDIS.EXE TRANSPORT=*NETBEUI,NDISHLP.SYS Windows for Workgroups Using the ODI Driver with NetWare as Secondary Network Sample STARTNET.BAT REM INTEL PRO/100 CB — DO NOT CHANGE LINES BELOW :M32A_MENU @ECHO OFF GOTO %CONFIG% :M32A_E_INTEL CD C:\NWCLIENT IF NOT EXIST M32AODI.COM GOTO M32A_ERROR M32AODI.COM...
Page 74 C H A P T E R 3 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/100 32-BIT MOBILE ADAPTER...
Page 75 Configuration Reference SET TEMP=C:\DOS C:\DOS\SMARTDRV.EXE /X C+ REM INTEL PRO/100 CB — DO NOT CHANGE LINES BELOW :M32A_MENU @ECHO OFF GOTO %CONFIG% :M32A_E_INTEL C:\WINDOWS\NET START CD C:\NWCLIENT IF NOT EXIST C:\NWCLIENT\STARTNET.BAT GOTO M32A_ERROR CALL C:\NWCLIENT\STARTNET.BAT GOTO M32A_END :M32A_ERROR ECHO ERROR: UNABLE TO LOCATE DRIVER FILE.
Page 76 C H A P T E R 3 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.CFG] PATH=C:\NWCLIENT\NET.CFG [M32A$ODI] [LINK DRIVER M32AODI] DATA=FRAME ETHERNET_802.2 [NWLINK] BINDINGS=M32AODI [NETBEUI] BINDINGS=M32AODI LANABASE=0 SESSIONS=10 NCBS=12 Sample [network drivers] section in SYSTEM.INI [NETWORK DRIVERS] DEVDIR=C:\WINDOWS LOADRMDRIVERS=NO Sample NET.CFG file (located C:\NWCLIENT) LINK DRIVER M32AODI FRAME ETHERNET_802.3 FRAME ETHERNET_802.2...
Page 77: Driver Parameters Reference
NET.CFG file. This file is supplied on the Network Drivers Disk and must be present in the same directory as the ODI driver. Files required for using M32AODI.COM are M32AODI.INS NET.CFG M32AODI.COM Configuration Reference Intel installation information file Network configuration file Intel ODI driver...
Page 78 C H A P T E R 3 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.CFG file...
Page 79: Ndis 2.0.1 Settings (For Drivers M32Andis.exe And M32Andis.os2)
M32AODI.OS2 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.CFG file and insert the appropriate keywords and values after the line LINK DRIVER M32AODI NDIS 2.0.1 Settings (for drivers M32ANDIS.EXE...
Page 80 Keyword Alphabetical Reference follows the keyword listings. Most installations will be able to use the settings implemented in the PROTOCOL.INI file by the Intel Installation Program. If any parameters need to be changed, use an ASCII text editor to modify the PROTOCOL.INI file with the appropriate keywords and values.
Page 81 NDIS 2.0.1 Keywords (M32ANDIS.EXE and M32ANDIS.OS2) KEYWORD DRIVERNAME=INTEL$ MEMORY IOADDRESS SOCKET MODE NOCHECK NOLED TXBUFFERSIZE RXBUFFERSIZE NOEARLYRX NOEARLYTX LINESPEED LINEMODE LINKDISABLE NOBURST LATENCY CACHE NOWRITEPOST NOPREFETCH VERBOSE Configuration Reference DEFAULT (REQUIRED FIRST ITEM IN PROTOCOL.INI) AUTO AUTO AUTO AUTO NOT PRESENT...
Page 82: M32A.sys (Ndis 3) Settings For Microsoft Windows Nt And Windows 95
Network Control Panel built into Windows NT. This applet uses the OEMSETNT.INF file to set the corresponding parameters in the registry. The user-configurable parameters are as follows: Intel M32A installation DLL Intel installation file for Microsoft Windows NT Intel NDIS 3 driver for Microsoft Windows NT...
Page 83 Parameter I/O PORT MEMORY ADDRESS INTERRUPT INTERRUPT STYLE LINE SPEED LINE MODE PC CARD SOCKET DIRECT ENABLE EARLYTRANSMIT EARLYRECEIVE Configuration Reference Default Valid Values 0XF800 0X1000-0XF800 0XD4000 0XC0000-0XDF000 SAME 3, 4, 5, 7, 10, 11, 15 AUTO DETECT PCI IRQS ISA IRQS AUTODETECT 10 MB...
Page 84: Windows 95 Support
The user-configurable parameters are as follows: Parameter Value DIRECTENABLE EARLYTRANSMIT LINESPEED LINEMODE INTERRUPTSYTLE Intel installation file for Windows 95 Intel NDIS 3 driver for Windows 95 Default Valid Values AUTODETECT OFF, ON, AUTODETCT AUTO AUTO DETECT 0 10 MBPS 100 MBPS...
Page 85: Novell Client 32 Driver Settings (For Driver M32A.lan)
SOCKET The network node address can be modified by specifying a value for ‘NetworkAddress’ such as ‘00A0C9112233’. If the user does NOT specify a ‘NetworkAddress’ then the M32A.SYS driver uses the network node address contained in the PRO/100 CardBus adapter Card Information Structure.
Page 86 C H A P T E R 3 NOEARLYRX NOEARLYTX LINESPEED LINEMODE LINKDISABLE NOBURST LATENCY CACHE NOWRITEPOST NOPREFETCH HIGH NOT PRESENT NOT PRESENT AUTO HALF NOT PRESENT NOT PRESENT NOT PRESENT NOT PRESENT LOW, MEDIUM, or HIGH 10 or 100 HALF or FULL 0 - 255 0, 4, 8, 16, or 32...
Page 87: Packet Driver Settings
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. It is a DOS-based terminate-and-stay- resident (TSR) program. The driver file M32APD.COM is located in the \PKTDRV directory on the Network Drivers Disk.
Page 88: Diagnostic Test Utility Settings (M32Atest.exe)
M32APD IOADDRESS=320 INT=7 ETHDRV Diagnostic Test Utility Settings (M32ATEST.EXE) The M32ATEST.EXE utility is a Intel utility for testing Intel adapter hardware. It is an MS-DOS executable file. M32ATEST.EXE tests the adapter hardware functionality, including the PC Card interface, the serial EEPROM, the Ethernet controller, and the PHY interface (adapter modules).
Page 89: Keyword Alphabetical Reference
Keyword Alphabetical Reference CACHE DIRECTENABLE DRIVERNAME=INTEL$ required as first item in the INTEL section of the INTERRUPT INTERRUPTSTYLE IOADDRESS and IOBASEADDRESS Configuration Reference displays command summary for driver 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.
Page 90 C H A P T E R 3 I/O PORT ISAIRQ LATENCY LINEMODE LINESPEED see IOADDRESS 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).
Page 91 ENABLED. see MEMORY. specifies the host PC memory location for the Intel adapter in hexadecimal notation, when MODE MEMORY (memory-mapped I/O) is being used (see MODE). The memory block occupies 4 Kbytes of host memory.
Page 92 PC Card slot or socket into which the PRO/100 CardBus adapter is inserted. If a socket number is specified, only the specified socket is checked for the Intel adapter. If no socket is specified, all sockets are searched until the Intel adapter is found.
Page 93 TXBUFFERSIZE Configuration Reference 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.
Page 94 C H A P T E R 3...
Page 95: Troubleshooting
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. This information is intended for users or network administrators who are already familiar with the PRO/100 CardBus adapter and its user documentation, and...
Page 96: Led Indicators
For the latest information on the PRO/ 100 CardBus adapter, see the README file on the Intel Network Drivers Disk, call the Intel BBS (see attached Support Page File), or visit the Intel World Wide Web site at http://support.intel.com. See Appendix A in this User’s Guide for Intel support services access information.
Page 97: Diagnostic Self Test (Ms-Dos Only)
Diagnostic Self Test (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. M32ATEST can only be run from an MS-DOS command line.
Page 98: Main Screen
Write down the PRO/100 CardBus adapter model and serial numbers for reference Customer Support will ask you to supply the model and serial numbers when requesting technical assistance or warranty service from Intel. CONFIGURE This function allows the user to set the parameters used for testing. The address mode can be set to Auto, Memory, or I/O.
Page 99 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.
Page 100: Error Messages
IRQ resources, or the available IRQ resources could not be configured for the CardBus Bridge. A PRO/100 CardBus adapter could not be found The driver was able to detect a CardBus Bridge, but there was no Intel PRO/100 CardBus adapter inserted into a slot.
Page 101 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. If the error persists, use the MEMORY keyword to force a known address that's available, and use the NOCHECK keyword to disable resource verification.
Page 102 C H A P T E R 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.
Page 103 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.
Page 104: General Troubleshooting
C H A P T E R 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.
Page 105 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.
Page 106 C H A P T E R 4 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...
Page 107 SystemSoft The SystemSoft’s CardSoft Card and Socket Services are loaded in the CONFIG.SYS file and generally include the following lines: DEVICE=C:\CARDSOFT\SOCKET_SERVICES_DRIVER machine type) DEVICE=C:\CARDSOFT\CS.EXE DEVICE=C:\CARDSOFT\CSALLOC.EXE C:\CARDSOFT\CSALLOC.INI DEVICE=C:\CARDSOFT\CARDID.EXE (Called a ‘generic’ card driver) Resources assigned by CardSoft Card and Socket Services are controlled by the files CSALLOC.INI and CARDID.INI.
Page 108 C H A P T E R 4 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.
Page 109 The driver loaded successfully, but I can’t get on the network Check all connections and verify that the cable drop is good (try a cable that is known to work on another workstation). Reboot by powering down the machine (cold boot). On some machines the PC Card controller chipset is not properly reset on a warm boot, and this can cause network errors.
Page 110: Network Operating System Troubleshooting
Remove Card and Socket Services. DEC PATHWORKS This section only discusses the problems that might be related to configuration of the Intel adapter. For non-Intel related issues, consult your PATHWORKS user’s manual. These are the PATHWORKS error codes (indicated by “percentage done”):...
Page 111 Use /~# parameter when you run Pathworks SETUP. This will allow you to see any error messages given by any driver that fails to load. If you hang on error code 83%, the Intel NDIS driver failed to load. Here are some possible reasons for the failure: a Interrupt conflict - some machines use INT 5 for a sound card.
Page 112 Microsoft Windows installed on their system and are upgrading to Windows 95. It may also be helpful to new users of Windows 95 who were unable to successfully install the Intel driver using the instructions provided in Chapter 2, Software Installation.
Page 113 NOTE: If you do not have Windows 95 version 4.00.950b (OSR2) or later, the following instructions do not apply. The Intel PRO/100 CardBus adapter will be loaded using its own driver, and not by using Windows 95 PC Card support.
Page 114 (networking card, CD-ROM connected to a SCSI card, etc.) to install windows?” The default answer is No. If you did use a PC Card SCSI adapter or a network card to install Windows 95, it is recommended that you keep a copy of the Windows 95 directory on your hard disk and not load any real mode PC Card or network drivers.
Page 115 8 Insert your Intel CardBus adapter. Windows 95 should now detect the Intel card, and put up a dialog box. It should automatically load the drivers from the Windows 95 directory. If it asks you to supply a manufacturer’s disk, insert the Intel Network Drivers...
Page 116 C H A P T E R 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.
Page 117 Windows to search for your new hardware?’, select NO and click Next. Select ‘Network adapters’ and click Next. Under Manufac- turers select ‘Intel’ and click the Have Disk button. Insert the Intel Network Drivers diskette in the floppy drive and make sure A: is selected in the ‘Copy Manufacturer’s files from’...
Page 118: Microsoft Windows For Workgroups
Drivers do not load or errors are reported when NET START is executed. Ensure you are excluding the memory range used by the Intel adapter from the memory manager in CONFIG.SYS. Drivers do not load or errors are reported when NET START is executed for Windows For Workgroups.
Page 119 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. There are several reasons that this will happen, but the most common reasons are: •...
Page 120 C H A P T E R 4 Make sure your \WINDOWS\PROTOCOL.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.
Page 121: Troubleshooting Checklist
LASTDRIVE=H or FIRST NETWORK DRIVE=I). File Server not found. • Run the Intel test utility to see if any network traffic is visible. • Check the frame types in the NET.CFG file. Your frame type must match the frame type used by the file server. Remember that the adapter binds to the first frame type listed in the NET.CFG.
Page 122 (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.intel.com • Boot the computer in a clean environment (press F8 or hold down the Shift key to bypass loading of CONFIG.SYS and...
Page 123 Disable all power management features in the CMOS settings on the computer. • Disable all shadow RAM features in the CMOS settings on the computer. • Ensure that you are excluding the memory range used by the Intel adapter from your memory manager (EMM386.EXE, QEMM.EXE, etc.). Troubleshooting...
Page 124 C H A P T E R 4...
Page 125: Intel Automated Customer Support
Appendix A Intel Automated Customer Support You can reach Intel’s automated support services 24 hours a day, every day at no charge. The services contain the most up-to-date information about Intel products. You can access installation instructions, troubleshooting information, and general product information.
Page 126 Worldwide access: Intel has technical support centers worldwide. Many of the centers are staffed by technicians who speak the local languages. For a list of all Intel support centers, the telephone numbers, and the times they are open, download document 9089 from one of the automated services.
Page 127: Specifications
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.3 for 10 Mbps, 802.3u for 100 Mbps Type II CardBus PC Card Full or half duplex at 10 or 100 Mpbs Size:...
Page 128: General Specifications (Continued)
Card and Socket Services Supports CardBus compliant PC Card support in Windows 95 version 4.00.950b (OSR2 ) and later. Contact Intel for an updated list of Card and Socket Services supporting CardBus and information on using the PRO/100 CardBus 32 adapter with that software.
Page 129: Technical Specifications
Technical 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).
Page 130 A P P E N D I X B...
Page 131: Limited Lifetime Warranty
If the product is found to be otherwise defective, Intel, at its option, will replace or repair the product at no charge except as set forth below, or refund your purchase price provided that you...
Page 132 Intel wants you to be completely satisfied with the Intel adapter product that you have purchased. Any time within ninety (90) days of purchase, you may return your Intel adapter to the original place of purchase for a full refund of the purchase price from your dealer. Resellers and Distributors, respectively, accepting returns and refunding money back to their customers may return Intel adapters to their original place of purchase.
Page 133 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. See the applicable software license agreement which shipped with the adapter product for details on any software warranty.
Page 134 A P P E N D I X C...
Page 135: Network Software License Agreement
PROMPTLY RETURN THE SOFTWARE PACKAGE AND ANY ACCOMPANYING ITEMS. LICENSE: Intel Corporation (“Intel”) grants you the non-exclusive right to use the enclosed software program (the “Software”). You will not use, copy, modify, rent, sell or transfer the Software or any portion thereof except as provided in this Agreement.
Page 136 Software terminates your right to use the Software. OWNERSHIP AND COPYRIGHT OF SOFTWARE: Title to the Software and all copies thereof remain with Intel or its vendors. The Software is copyrighted and is protected by United States and international copyright laws.
Page 137 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.227-14 and DFAR 252.227-7013 et seq.
Page 138 A P P E N D I X...
Page 139: Regulatory Agency Notices
Appendix E Regulatory Agency Notices FCC Compliance Statement This product has been tested and found to comply with the limits for a Class B computing device pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation.
Page 140 (2) this device must accept any interference received, including interference that may cause undesired operation. CAUTION If the device is changed or modified without permission from Intel, the user may void his or her authority to operate the equipment. Canadian compliance (Industry Canada)
Page 141: Index
Index Symbols 100Base-TX 1 10Base-T 1 15-pin connector 1, 4 Artisoft LANtastic 26 installation 26 sample configuration files 60 troubleshooting 104 AT&T StarGROUP installation 26 Autodetection of PC Cards 2 Banyan VINES installation 26 sample configuration files 63 Bulletin Board 119 Cabling data grade 1 Card and Socket Services 56, 99, 101...
Page 142 I N D E X troubleshooting 104 Default values 25 Device driver 25 Diagnostic Test Utility parameters 82 Diagnostics 91 Driver parameters 71 Equipment, required 2 Error messages 94 Exclusion, memory 60 FTP LANWatch installation 31 NDIS driver 32 Packet driver 31 FTP PC/TCP 33 and NetWare 36 installation 33...
Page 143 Microsoft Windows for Workgroups 21 Novell NetWare 21 Program, Xircom 21, 25, 44, 55 VLM shell 21 Installation, manual Windows 95 OSR2 110 Intel Web and Internet Sites 120 LAN Manager Ungermann-Bass Net/One 51 LANtastic, Artisoft 26 LANWatch, FTP 31 LED indicators 90...
Page 144 I N D E X operating system 21, 25 software installation 25 NETX shell support 21 Novell NetWare 47 and FTP PC/TCP 36 installation 21 troubleshooting 115 ODI driver FTP PC/TCP 33 generic 37 Microsoft Windows for Workgroups 43 parameters 71 Wollongong PathWay Access for DOS 52 OnNet with FTP PC/TCP 33, 34 OSR2 109, 110...
Page 145 Sample files, configuration 60 Artisoft LANtastic 60 Banyan VINES 63 DEC PATHWORKS 64 Windows for Workgroups 65 Self test 91 slots, PC Card 2 Software updates 119 SunSoft PC-NFS installation 48 Suspend/resume 58 SystemSoft Card and Socket Services 101 Troubleshooting 89, 98 Artisoft LANtastic 104 checklist 116 DEC PATHWORKS 104...
Page 146 I N D E X ODI driver 44 removing old installation 46 with NetWare 44 Windows NT 18 Wollongong PathWay Access installation 52 Wollongong PathWay Access for DOS 52 NDIS driver 52 ODI driver 53 World Wide Web 119...

Intel NetportExpress PRO User Manual

Hardware Installation

Software Installation

Configuration Reference

Intel Automated Customer Support

Specifications

Limited Lifetime Warranty

Network Software License Agreement

Regulatory Agency Notices

Index

Quick Links

How to Use This Manual

Overview of the Installation Process

How to Find More Information

Troubleshooting

Related Manuals for Intel NetportExpress PRO

Summary of Contents for Intel NetportExpress PRO

Table of Contents