EtherExpress™ PRO/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. It is designed to help both new and experienced network users install and configure the Intel product in the shortest time possible.
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. * Other product and corporate names may be trademarks of other companies and are used only for explanation and to the owners’ benefit, without intent to infringe.
Contents Hardware Installation .............................................. 1 Before Installing Hardware ................................................................... 1 Installing the Hardware ......................................................................... 3 What to Do Next ................................................................................... 5 Software Installation ............................................... 7 CardBus Installation Guidelines ...........................
CONTENTS 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 .................................................................... 41 Windows for Workgroups ....................................................
CONTENTS Network Operating System Troubleshooting ................................... 104 Troubleshooting Checklist ................................................................ 116 Intel Automated Customer Support ................... 119 Specifications ...................................................... 121 General Specifications ...................................................................... 121 General Specifications (continued) ...................................................
CONTENTS vi
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.
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. Contact your computer dealer for more information. 2 A local area network supporting 10 or 100 Mbps Ethernet, as required, and a network operating system supported by the PRO/100 CardBus adapter.
Hardware Installation 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. NOTE: The PRO/100 CardBus adapter will not fit in a slot that does not support CardBus technology.
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). Press the cable connector gently into the connector on the card until it clicks into place. Do not force the connection.
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. p ss da re A xp le E bi er o th M 0 lE 0 te /1 In RO P t s bi Bu 32 ard C ™ te r 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.
CHAPTER 1 6
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.
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. Cardbus built-in support is included in Windows 95 OEM Service Release #2 (also known as Windows 95 OSR2 or version 4.00.950b). Please review the README.
Software Installation Installing with Windows 95 Version 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. To use this driver, however, you must first disable support for PC Cards in Windows 95. This means you cannot simultaneously use another CardBus adapter or PC Card with the PRO/100 CardBus adapter. To install with Windows 95 Version 4.00.950 or 4.00.
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. 14 The Network window reopens. 15 Click OK. The Intel dialog box appears displaying various settings. An asterisk in any field indicates that the current setting is incorrect. Use the Up or Down arrow to adjust the setting until the asterisk disappears. 16 Click OK.
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. 6 Click OK. The System Settings Change window opens. 7 Remove the Network Drivers Disk from the floppy drive. 8 Click Yes to restart the computer.
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 another PC Card, such as a PC Card modem in your computer, you will first need to re-enable the PC Card support as described in the following steps: 1 Click Start. 2 Choose Settings. 3 Choose Control Panel. The Control Panel window opens. 4 Double-click the Network icon. The Network window opens.
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.00.950 or 4.00.
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.00.950 or 950a” at the beginning of the Installing with Windows 95 section earlier in this chapter. 12 After completing steps 1 through 17, select Yes when prompted to reboot the machine. At this point installation is complete.
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 Version 4.00.950b (OSR2) or Later Windows 95 OSR2 and later versions support CardBus. This means you can use the built-in PC Card support in Windows 95 to install, remove, and hotswap CardBus cards and PC Cards. To install the CardBus with Windows 95 Version 4.00.
CHAPTER2 Installing NetWare 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). Windows 95 installation instructions vary slightly for different versions of Windows 95. See the instructions earlier in this manual on how to determine your version of Windows 95, then follow the instructions below for your version.
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. At the last screen, DO NOT select REBOOT. Instead, click CUSTOMIZE. NOTE If prompted to insert the Windows 95 CD-ROM, click OK and type the path to the CABS directory on your hard drive (usually C:\WINDOWS\OPTIONS\CABS).
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. This means you cannot simultaneously use another CardBus or PC Card with the PRO/100 CardBus adapter. Please review the README.
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.51. To remove the PRO/100 32-bit Mobile Adapter from Windows NT 3.51: 1 Double-click the Control Panel. The Control Panel opens. 2 Double-click the Network icon. The Network Settings window opens.
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. However, consult the README.TXT file for specific settings (if necessary). 13 Click OK. The Network Settings window redisplays. 14 Click Close.
Software Installation Installing with Windows 3.x and Windows for Workgroups To install under Windows 3.x or Windows for Workgroups, use the Intel Installation Program. Insert the Installation Disk, into your disk drive, and proceed as follows (substitute the correct drive letter for your system): 1 From the Program Manager, choose File, then Run. In the Command Line box, type the following: A:SETUP 2 Press Enter or click OK. 3 Select your network operating system from the list displayed and click OK.
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 simultaneously 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. The Installation Program will modify your AUTOEXEC.BAT, CONFIG.SYS, and network configuration files to match the optimum configuration for your system.
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. 9 In the Current Configuration section, click on PRO/100 CardBus adapter and click edit to edit the driver settings. The default settings for the product will be displayed.
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. Put the Intel Network Drivers Disk in the floppy drive and click OK. 7 In the list box, enter M32AODI.OS2 as the LAN driver to install, and click Continue. 8 The Installation Message window will reappear.
Software Installation Installing Network 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.
CHAPTER2 Artisoft 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. 4 Run the Artisoft LANtastic 6.0 “install” program. Specify C:\LANTASTI as the destination directory (or the directory set with the Intel Installation Program).
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. 2 Choose Banyan VINES from the Select Network Operating System screen. 3 Follow the prompts to complete the Intel segment of the installation. The Installation Program also creates a \VINES directory on your hard disk.
CHAPTER2 DEC PATHWORKS versions 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. Prior to installing the DEC PATHWORKS client software, it is necessary to determine the Interrupt Number for the PRO/100 CardBus adapter.
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. 7a For Pathworks 5.0, choose Configure PC. 7b For Pathworks 6.0, select Yes for the “Has the Pathworks software been installed to a LAN Manager file Service.
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. 19 Under Network Adapter Information, choose other network adapter, with NDIS enabled, and enter the following information: IN THE NON-SUPPORTED NETWORK ADAPTER WINDOW DRIVER FILE: A:\M32ANDIS.EXE PROTOCOL.
Software Installation 26 Exit SETUP and reboot to start the network. (Some machines may require a cold boot at this point—power the computer down and back up again.) 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.
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. 4 Install LANWatch according to the instructions in your FTP LANWatch manual. 5 Using a text editor, add the following lines to your CONFIG.SYS file: DEVICE = C:\NDIS\PROTMAN.SYS /I:C:\NDIS DEVICE = C:\NDIS\M32ANDIS.
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. For information on which driver is appropriate for your network environment, see the FTP PC/TCP documentation. For environments using values other than those set by the Intel Installation Program, see Chapter 3, Configuration Reference in this manual. FTP PC/TCP 3.
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:\PCTCP\PCTCP.INI • Add the line C:\PCTCP\ODIPKT after the line PCTCP=C:\PCTCP\PCTCP.INI 14 Save the file and exit the text editor.
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.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:\PCTCP\PCTCP.
CHAPTER2 7 Edit the AUTOEXEC.BAT file and add the following lines: C:\PCTCP\M32APD.COM C:\PCTCP\ETHDRV.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.SYS DEVICE=[PATH]IFCUST.SYS where [path] is the drive and directory specified at the PC/TCP installation. 9 Reboot the PC. 10 Change to the directory where your PC/TCP files are stored and run M32APD.COM by typing: M32APD and pressing Enter.
Software Installation where [path] is the drive and directory specified in the PC/TCP installation. 6 Copy NET.CFG from the C:\INTEL\M32A 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. 7 To start the workstation, load the software as follows: LSL M32AODI IPXODI ODIPKT (USE THE VERSION SUPPLIED WITH PC/TCP) ETHDRV VLM 8 Change to the network drive (usually F:\LOGIN).
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. 3 Follow the prompts to complete the Intel segment of the installation. 4 Install the IBM Local Area Network Support Program according to the instructions in the IBM Local Area Network Support Program User’s Guide.
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. 4 Install the IBM Local Area Network Support Program according to the instructions in the IBM Local Area Network Support Program User’s Guide.
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, change the line that reads BINDINGS = TCMAC2 to read: BINDINGS = INTELNET • Underneath that section insert a new section that reads: [INTELNET] DRIVERNAME = INTEL$ 15 Use a text editor to edit the keyword settings in the PROTOCOL.
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.SYS, AUTOEXEC.BAT, and configuration files such as NET.CFG (for ODI) or PROTOCOL.INI (for NDIS).
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. Otherwise, skip to step 15. 10 Run Windows. 11 Choose setup from “Main” group. 12 Select Startup, and under the “Options” screen select Change System Settings. 13 Select Network then scroll to LAN Manager version 2.1.
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. 16 Click on the Control Panel in the “Main” group. 17 Select Startup from the Control Panel. 18 In the Options for Enterprise Networking window click “Log on to Windows NT or LAN Manager Domain.” 19 Save, exit, and reboot the PC. Windows for Workgroups NDIS 2.
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. 4 When the installation is complete, reboot the computer. 5 At the Intel menu, choose “Load EtherExpress PRO/100 Mobile CardBus 32 for Network Access.
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. 18 When prompted for an “unlisted, updated, or vendor-provided network driver disk,” insert the Intel Network Drivers Disk and click OK. 19 Select “Intel EtherExpress PRO/100 Mobile CardBus 32” and click OK. 20 Close the Network Drivers dialog box and click OK in the Network Setup box.
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. 8 In the Network Drivers dialog box, choose Add Adapter. 9 In the Add Network Adapter box, choose Unlisted or Updated Network Adapter and click OK.
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. 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 1 Run the Intel Installation Program from the Installation Disk.
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. 4 Install PC-NFS for Ethernet according to instructions in the PC-NFS documentation. Choose NDIS setup, and follow the instructions to complete the setup.
Software Installation DEVICE=C:\LANMAN\NFS-NDIS.SYS as follows: DEVICE=C:\LANMAN\PROTMAN.SYS DEVICE=C:\LANMAN\M32ANDIS.EXE DEVICE=C:\LANMAN\NFS-NDIS.SYS 9 Verify that your AUTOEXEC.BAT file contains a line that reads C:\LANMAN\NETBIND before the line that reads NET INIT 10 Configure PC-NFS options according to your PC-NFS documentation, and reboot the computer. Novell NetWare 32-bit ODI Drivers Installing the Client 32 Driver under Windows 3.
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.x 1 Select File, Run, and type a:\setup 2 Follow the onscreen instructions 3 When the ODI Driver Selection Dialog box appears, select User Specified Driver and click Next.
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. These packages, used with a Intel NDIS driver, provide files that support DOS workstations. They are available from UB and authorized UB representatives. Ungermann-Bass Net/One LAN Manager version 2.1 Installation 1 Begin installation of LAN Manager 2.
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. 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.
Software Installation 6 Copy the file M32ANDIS.EXE from C:\INTEL\M32A 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. 2 Choose Wollongong PathWay Access from the Select Network Operating System screen. 3 Follow the prompts to complete the Intel segment of the installation.
CHAPTER2 54
Chapter 3 Configuration Reference 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. You can use this information to modify an existing installation or perform a new installation manually without the assistance of the Intel Installation Program.
CHAPTER3 For Installation without the Intel Installation Program The information in this chapter can be used to manually configure the PRO/100 CardBus adapter. For manual installation, it is assumed that you have some experience with manual setup of network adapters, and know how to access and modify configuration files, using an ASCII text editor. Intel recommends that manual installation be performed by a system administrator or equivalent.
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. Check with the vendor who supplied your Card and Socket Services to determine if it supports CardBus. If your Card and Socket Services do not support CardBus, the remainder of this section does not apply.
CHAPTER3 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. This feature allows the CardBus to be removed from the computer, temporarily replaced with another type of card such as a modem or memory card, then reinserted without loss of network connection.
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.
CHAPTER3 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. For example: DEVICE=C:\DOS\HIMEM.SYS DEVICE=C:\DOS\EMM386.EXE NOEMS X=D200-D2FF This example excludes 4K of the D200 segment for use by the PRO/100 CardBus adapter. If the CardBus software is not configured for a specific address, it will automatically detect a free memory range.
Configuration Reference 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 ; [PROTMAN] DRIVERNAME = PROTMAN$ DYNAMIC = YES ; PROTOCOL.
CHAPTER3 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 :NOSHARE @ECHO LANTASTIC SERVER WAS INSTALLED BUT TURNED OFF. :CONTINUE REM IF CONNECT.BAT EXISTS, RUN IT TO SET UP CONNECTIONS.
Configuration Reference @ECHO ===== END LANTASTIC CONFIGURATION ===== :STARTNET_DONE CD \ Banyan 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.SYS. 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.
CHAPTER3 [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.
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 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.
CHAPTER3 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.
Configuration Reference 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 CLS GOTO %CONFIG% :M32A_E_INTEL C: CD C:\NWCLIENT IF NOT EXIST M32AODI.COM GOTO M32A_ERROR LSL M32AODI.COM IPXODI C:\WINDOWS\ODIHLP.EXE VLM IF NOT EXIST ICHECK.EXE GOTO S_M32A_INTEL CLS ICHECK.
CHAPTER3 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 FOR NETWORK ACCESS MENUITEM=M32A_END,DO NOT LOAD ANY INTEL DRIVERS MENUCOLOR=15,0 [M32A_E_INTEL] [M32A_END] [COMMON] REM INTEL PRO/100 CB — DO NOT CHANGE LINES ABOVE DEVICE=C:\WINDOWS\HIMEM.SYS /TESTMEM:OFF DEVICE=C:\DOS\EMM386.
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 CLS GOTO %CONFIG% :M32A_E_INTEL C:\WINDOWS\NET START C: 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.
CHAPTER3 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.
Configuration Reference Driver Parameters 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. All of the drivers described here automatically detect the speed of the network to which the adapter is attached (10 Mbps or 100 Mbps), unless otherwise noted. Speed can also be specified with the LINESPEED keyword.
CHAPTER3 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 Parameters can also be implemented on the command line. Command line parameters override parameters placed in the NET.CFG file. NET.CFG Example LINK DRIVER M32AODI FRAME ETHERNET_802.2 M32AODI.
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.1. It is an IBM OS/2-based device driver for use with OS/2 versions 2.0 and later. The Novell OS/2 workstation ODI stack including M32AODI.
CHAPTER3 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.INI file, which is supplied on the Network Drivers Disk. The files required for using M32ANDIS.EXE are: PROTOCOL.INI Configuration and binding information file M32ADOS.
Configuration Reference NDIS 2.0.1 Keywords (M32ANDIS.EXE and M32ANDIS.OS2) KEYWORD DEFAULT DRIVERNAME=INTEL$ (REQUIRED FIRST ITEM IN PROTOCOL.
CHAPTER3 M32A.SYS (NDIS 3) Settings for Microsoft 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.SYS driver supports the networking environment in Microsoft Windows NT versions 3.51 and greater. The files necessary for using M32A.SYS include: M32A.DLL Intel M32A installation DLL OEMSETNT.
Configuration Reference Parameter Default Valid Values Registry Value I/O PORT 0XF800 0X1000-0XF800 SAME MEMORY ADDRESS 0XD4000 0XC0000-0XDF000 SAME INTERRUPT 5 INTERRUPT STYLE 0 LINE SPEED LINE MODE PC CARD SOCKET DIRECT ENABLE EARLYTRANSMIT EARLYRECEIVE 0 1 0 0 1 1 3, 4, 5, 7, 10, 11, 15 AUTO DETECT SAME 0 PCI IRQS 1 ISA IRQS 2 AUTODETECT 0 10 MB 1 100 MB 2 AUTODETECT 0 HALF-DUPLEX 1 FULL-DUPLEX 2 AUTODETECT 0 1 1 2 2 3 3 AUTODETECT O OFF 1 ON 2 OFF
CHAPTER3 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.SYS driver uses the network node address contained in the PRO/100 CardBus adapter Card Information Structure. Windows 95 Support The M32A.SYS driver also supports the networking environment in Microsoft Windows 95. The files necessary for using M32A.
Configuration Reference SOCKET 0 AUTODETECT 0 1 1 2 2 3 3 4 4 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. Novell Client 32 Driver Settings (for driver M32A.LAN) The driver M32A.
CHAPTER3 ERT 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 CACHE 32 0, 4, 8, 16, or 32 NOWRITEPOST NOT PRESENT NOPREFETCH NOT PRESENT 80 LOW, MEDIUM, or HIGH
Configuration Reference Packet Driver Settings (for 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. It is a DOS-based terminate-and-stayresident (TSR) program. The driver file M32APD.COM is located in the \PKTDRV directory on the Network Drivers Disk.
CHAPTER3 LINKDISABLE NOT PRESENT NOBURST NOT PRESENT LATENCY 32 0 CACHE 32 0, 4, 8, 16, OR 32 NOWRITEPOST NOT PRESENT NOPREFETCH NOT PRESENT SINT 60 VERBOSE NOT PRESENT - 255 (60 - 80) Packet Driver Example A typical sequence for loading the packet driver M32APD.COM and default configuration settings is as follows: M32APD ETHDRV If no default configuration settings are used, these must be stated on the M32APD.COM command line.
Configuration Reference Keyword 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. Changing this parameter may affect network performance. DIRECTENABLE For 32-bit NDIS3 Driver (M32A.SYS) only: DIRECTENABLE forces the method used by the driver to determine if a PRO/100 CardBus adapter is present.
CHAPTER3 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. ISAIRQ use this keyword to force the driver to use ISA IRQ routing. Some CardBus bridges have the capability of supporting both PCI and ISA style IRQ routing.
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. Without this keyword in the driver command line, the driver defaults to link integrity ENABLED. MEM see MEMORY.
CHAPTER3 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. Some CardBus bridges have the capability of supporting both PCI and ISA style IRQ routing.
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. The default is 2 packets. U (ODI)(MS-DOS command line only) unloads driver from memory.
CHAPTER3 88
Chapter 4 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.
CHAPTER 4 Additional Sources of Information In addition to this User’s Guide, your computer and network documentation should also be consulted as needed. 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.
Troubleshooting 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. This utility is intended to be a diagnostic tool in troubleshooting PRO/100 CardBus adapter configuration errors.
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. When a function is active, the button appears to remain down or pushed. Once the button pops up, the function is completed and the screen is a passive results display.
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. It first checks for PCI BIOS extensions, and then it searches for any CardBus Controllers.
CHAPTER 4 Error Messages 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.
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. No network cable was detected.
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. If the network connection is half-duplex, HALF should be used. If the network connection is full-duplex, FULL should be used. Do not set the duplex mode to full unless the network connection is configured this way.
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. This tests transmits a network packet internally testing all the transmit and receive hardware before going online. This test also checks that the resources the driver is using are valid.
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. The selected memory is a RAM 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.
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. A driver failed to load, and I’m using Card and Socket Services Card and Socket Services are a set of drivers designed to support the PC Card (PCMCIA) standard. These drivers are generally supplied by the computer manufacturer.
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.COM reads NET.CFG file NDIS2 M32ANDIS.EXE reads PROTOCOL.INI file Packet M32APD.
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:\CARDSOFT\SOCKET_SERVICES_DRIVER machine type) (This file varies by 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. CSALLOC.
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. The resources required for a PRO/100 CardBus adapter include a memory window (MEM keyword), an interrupt (INT keyword), and an I/O address (IOADDRESS keyword). The default settings are indicated below.
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 loaded successfully, but I can’t get on the network A Check all connections and verify that the cable drop is good (try a cable that is known to work on another workstation). B Reboot by powering down the machine (cold boot).
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). If the cable length is correct, the adapter may be defective. Contact Intel Customer Support. Loopback failure reported when driver loads. Add the MODE IO parameter to NET.CFG or MODE=IO to PROTOCOL.INI.
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. This will allow you to see any error messages given by any driver that fails to load. 1 If you hang on error code 83%, the Intel NDIS driver failed to load.
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.EXE line of CONFIG.SYS. d Make sure you have M32ANDIS.EXE version 1.14 or above. e Always do a cold boot when troubleshooting.
Troubleshooting Put a copy of the directory for CAB files of Windows 95 from the CDROM 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.
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.) 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. Press Enter to select No.
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. This is recommended only for experienced users. e3 Override choices made by Windows 95. This is not recommended. Only experienced users should attempt this. f This is the next to last dialog box for the wizard.
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. 5 In the System Properties window, view the Device Manager tab. 6 In the Device Manager window, click PCMCIA socket. There will be two CardBus controllers listed under PCMCIA socket.
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. When asked, ‘Do you want Windows to search for your new hardware?’, select NO and click Next. Select ‘Network adapters’ and click Next. Under Manufacturers select ‘Intel’ and click the Have Disk button.
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. Drivers load but you cannot see anybody on the network. • Check that you have selected the correct workgroup. • Ensure that there are no spaces in your computer name.
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. There are several reasons that this will happen, but the most common reasons are: • DoubleSpace defaults to G or H as lastdrive, thus H: or I: will be the login drive when using DoubleSpace. The lastdrive command in CONFIG.SYS seems to be overruled by DoubleSpace lastdrive. Sample NET.
CHAPTER 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. Turn off the power to shut down the machine and do a COLD BOOT. See if this fixes the problem.
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. 6 Always do a COLD BOOT during troubleshooting. Novell NetWare Invalid network drive specified. Check the LASTDRIVE parameter in CONFIG.SYS if using NETX, or the FIRST NETWORK DRIVE statement in NET.CFG if using VLM.
CHAPTER 4 116 • 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.intel.com • Boot the computer in a clean environment (press F8 or hold down the Shift key to bypass loading of CONFIG.SYS and AUTOEXEC.
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.e.: C800, CC00, D400, D800). • Try using different interrupt locations (i.e.: 5, 10, 11). Check BIOS settings for PCI interrupts. • Try using different port addresses (i.e.: 280, 290, 310, 320).
CHAPTER 4 118
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. World Wide Web & Internet FTP Intel Bulletin Board Service (BBS) Access Intel’s World Wide Web home pages or download information using anonymous FTP. Use Intel’s BBS.
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.intel.com FTP Host: ftp.intel.com FTP Directory: /pub/support/enduser_reseller/etherexpress_lan_adapters Intel Customer Support Technicians Other support services: You can purchase a range of support services, including 24 hour support, per incident support, on-site service, and software and hardware maintenance agreements.
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: 3.37 in (86 mm) x 2.13 in (54.0 mm) x 0.20 in (5.0 mm) excluding adapter cable and network connection Weight: 0.
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.
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 boundary, within segment C000h to EF00h (DOS drivers only). • Keyword disables link integrity checking. • Suspend/resume and HotSwap support in Windows 95 OSR2 and later.
APPENDIX B 124
Appendix C Limited Lifetime Warranty 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.
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. If the Customer Support Group verifies that the product is defective, they will have the RMA department issue you an RMA number to place on the outer package of the product. Intel cannot accept any product without an RMA number on the package.
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.
APPENDIX C 128
Appendix D Network Software License Agreement 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. LICENSE: Intel Corporation (“Intel”) grants you the non-exclusive right to use the enclosed software program (the “Software”).
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. 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.
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. or its successor. EXPORT LAWS: You agree that the distribution and export/reexport of the Software is in compliance with the laws, regulations, orders or other restrictions of the U.S.
APPENDIX 132 D
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. Installed correctly, it probably will not interfere with radio or TV reception. However, we do not guarantee the absence of interference.
APPENDIX E NOTE This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (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.
Index Symbols 100Base-TX 1 10Base-T 1 15-pin connector 1, 4 A Artisoft LANtastic 26 installation 26 sample configuration files 60 troubleshooting 104 AT&T StarGROUP installation 26 Autodetection of PC Cards 2 B Banyan VINES installation 26 sample configuration files 63 Bulletin Board 119 C Cabling data grade 1 Card and Socket Services 56, 99, 101 SystemSoft 101 Category 5 cabling 1, 2 Configuration files, sample 60 Customer Support 119 D DCOMPVLM.
INDEX troubleshooting 104 Default values 25 Device driver 25 Diagnostic Test Utility parameters 82 Diagnostics 91 Driver parameters 71 E Equipment, required 2 Error messages 94 Exclusion, memory 60 F FTP LANWatch installation 31 NDIS driver 32 Packet driver 31 FTP PC/TCP 33 and NetWare 36 installation 33 Packet driver 35 Full-duplex operation 59 G Generic installation 37 H HotSwap 58 HP LAN Manager installation 37 I IBM DOS LAN Requestor 40 IBM Local Area Network Support Program 38 installation 38, 39
INDEX manual 41 Microsoft Windows 21 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 L LAN Manager Ungermann-Bass Net/One 51 LANtastic, Artisoft 26 LANWatch, FTP 31 LED indicators 90 Loopback failure 104 M Manual installation 41 Memory exclusion 60 Messages 94 N NDIS 3.
INDEX operating system 21, 25 software installation 25 NETX shell support 21 Novell NetWare 47 and FTP PC/TCP 36 installation 21 troubleshooting 115 O 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 P Packet driver FTP LANWatch 31 FTP PC/TCP 33 loading sequence 82 parameters 81 Parameters, driver 71 PATHWORKS, DEC 28 PC Card slots 2 PC-NFS 48 PC/TCP, FTP 33 Pipelining, Advanced Look-ahead
INDEX S 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 T Troubleshooting 89, 98 Artisoft LANtastic 104 checklist 116 DEC PATHWORKS 104 Microsoft Windows 95 106 Microsoft Windows for Workgroups 112 Novell NetWare 115 U Ungermann-Bass Net/One installation 51 V VINES, Banyan 26 VLM file decompression 41 V
INDEX 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 140
