STANDARD MICROSYSTEMS CORPORATION DESKTOP NETWORKS BUSINESS UNIT Compatible Platforms and Installation Guidelines EtherEZ Plug and Play ISA Ethernet Adapter March 6, 1995 Product: EtherEZ Plug and Play Ethernet Adapter (SMC8416B, SMC8416T, SMC8416BT, and SMC8416BTA) This document is updated frequently and available from the following sources: SMC Technical Support BBS (714.707.2481): 8416CP.TXT CompuServe (Go SMC): 8416CP.TXT EliteFAX (800.SMC.8329) COMPATIBILITY TEST RESULTS SMC has conducted, and continues to conduct, extensive testing to determine the compatibility of a variety of computer systems with the EtherEZ adapter. The results of SMC Quality Assurance testing are provided in the following tables. Updates of new compatibility information will be included in the next release of this document. Many EtherEZ-compatible products are available in the market that are not yet tested or included in this document. To obtain detailed information about a particular product described in this document, contact the vendor. Unless otherwise specified, test results apply to EtherEZ Plug and Play Ethernet adapter types SMC8416B, SMC8416T, SMC8416BT, and SMC8416BTA. COMPUTER SYSTEMS TESTED Name CPU Bus Type BIOS PnP System* Test Results & Model Number ------------------------------------------------------------------------------------------------------------ ACER A1G 486-50 MHz ISA ACER 2.0 Yes Pass Advanced Logic Research 486-33 MHz ISA No Pass AMI Series 721 P-90 MHz ISA/PCI AMI, 9/25/94 Yes Pass AST Bravo MS 486-66 MHz AST 2.02.03 w/Intel Yes Pass 4/66D extensions v1.14 Power 386-33 MHz EISA No Pass Premium Power 486DX2 50 MHz EISA No Pass Premium Premia 386SX 20 MHz ISA No Pass Premia P-90 MHz EISA/PCI AST 2.02.03 w/Intel Yes Pass GX P90 extensions v1.14 AT&T Globalyst 525 486-66 MHz ISA/PCI IBM SurePath 1.2 Yes Pass Globalyst 580 Pentium-54 MHz ISA/PCI IBM SurePath 1.3 Yes Pass COMPAQ Computer Corporation DeskPro 386-33 MHz EISA No Pass DeskPro 386-33 MHz EISA No Pass DeskPro 486-66 MHz Compaq, 9/26/94 No Pass DeskPro/i 486-33 MHz ISA No Pass DeskPro/L 386-33 MHz EISA No Pass DeskPro/M 486DX2 66 MHz EISA No Pass DeskPro Pentium-60 MHz EISA 486w, 4/13/94 Yes Pass XL566 LTE 486-66 MHz Compaq, 9/26/94 No Pass Elite450ex LTE Pentium-90 MHz Compaq, 9/26/94 No Pass Elite450ex Presario 720 486-66 MHz ISA Compaq Yes Pass ProLineas/66 486-66 MHz EISA No Pass ProLinea CES 486-66 MHz Compaq, 9/26/94 Yes Pass SystemPro 486 DX2 33 MHzEISA No Pass 2585 386-33 MHz EISA No Pass Daewoo CPC-5200 Pentium 60 MHz Phoenix 4.04 Yes Pass Dell Computers 433SE 486-66 MHz EISA No Pass 486-33 486DX-33 MHz ISA No Pass Dimension Pentium-60 MHz ISA/PCI No Pass PA4221D Pentium-66 MHz EISA Phoenix No Pass XPS P90 Pentium 90 MHz ISA/PCI Pre-release Yes Pass Digital Equipment Corporation Celebris 466 486-66 MHz Phoenix 4.03 Yes Pass Celebris 590 Pentium 90 MHz Phoenix 4.04 Yes Pass DECpc 560ST Pentium-60 MHz EISA No Pass Venturis 450S2486SX2-50 MHz Phoenix 4.04 Yes Pass Fujitsu FM V-590 Pentium 90 MHz Phoenix 4.04 Yes Pass Gateway 2000 P4D-66 486DX2 66MHz ISA/PCI Phoenix 4.03 Yes Pass (Note 1A) P4D-100 486DX2 Phoenix 4.04 Yes Pass Hewlett-Packard Company NetServer 486-66MHz EISA No Pass 40/66 LE IBM Aptiva 486-66 MHz IBM SurePath 4.04 Yes Pass 62P/66P Aptiva Pentium 60 MHz IBM SurePath Yes Pass 82P/66P N1KT46AUS PS/2 386-12 386SX-12 ISA No Pass ValuePoint 486DX2 66MHz ISA No Pass ValuePoint 50 486 DX2 33MHz ISA No Pass ICL ErgPro D5/90 Pentium 90 MHz ICL 2.10 Yes Pass NEC Express II 486-66MHz EISA No Pass Image P90 Pentium 90 MHz Phoenix 4.04 Yes Pass VERSA V/50 486-50 MHz Phoenix 1.04.1011 Yes Pass w/Docking Station Olivetti M6/640 Pentium 90 MHz AMI 1.13 Yes Pass Suprema Packard Bell PB 550 Pentium 90 MHz AMI 1.00.11BBOR Yes Pass Siemens PCD-4H 486-66 MHz Phoenix 4.04 Yes Pass PCD-5H Pentium 60 MHz Phoenix 4.04 Yes Pass Tulip TC 42 Pentium 90 MHz Phoenix 4.03 Yes Pass Unisys 486-66 MHz ISA No Pass Vobis Highscreen Pentium 90 MHz AMI 1.00.10AX1 Yes Pass 500ZE-90 ZDS Z-Station 510 486-66 MHz Phoenix 4.04 Yes Pass Note 1A: Do not use IRQ2. The PnP BIOS sets the adapter at C000, creating a possible video conflict. The RAM test will fail if Zero Wait State is enabled (memory-mapped mode only). NETWORK OPERATING SYSTEMS TESTED Product Server Driver Client(s) Driver Test Results -------------------------------------------------------------------------------------------------------------------------------------- Banyan Vines Banyan Vines v5.2(5) DOS ODI: smc8000.dos v3.07 Pass DEC Pathworks DEC Pathworks v2.0 OS/2 ODI: smc8000.os2 v3.07 OS/2 ODI: smc8000.os2 v3.07 Pass DEC Pathworks v4.1 OS/2 ODI: smc8000.dos v3.07 OS/2 ODI: smc8000.dos v3.07 Pass Novell NetWare 286 v2.2 smcnw286.lan v6.01 Pass NetWare 386 v3.11 32-bit ODI: smcnw311.lan v6.01 DOS ODI: smc8000.com v5.01 Pass (Note 1B) NetWare 386 v3.12 32-bit ODI: smc8000.lan v6.01 DOS ODI: smc8000.com v5.01 Pass NetWare 386 v4.01 32-bit ODI: smc8000.lan v6.01 DOS ODI: smc8000.com v5.01 Pass OS/2 ODI: smc8000.sys v4.01 Pass Microsoft LanManager v2.2 OS/2 NDIS2: smc8000.os2 v3.07 OS/2 NDIS2: smc8000.os2 v3.07 Pass DOS NDIS2: smc8000.dos v3.07 Pass WFW v3.1 DOS NDIS2: smc8000.dos v3.07 DOS NDIS2: smc8000.dos v3.07 Pass WFW v3.11 DOS NDIS2: smc8000.dos v3.07 DOS NDIS2: smc8000.dos v3.07 Pass WIN NDIS3: smc8000w.386 v1.04 WIN NDIS3: smc8000w.386 v1.04 Pass (Note 3B) Windows NT v3.1 NT NDIS3: smc8000n.sys v1.09 NT NDIS3: smc8000n.sys v1.09 Pass (Note 3B) IBM LanServer v3.0 OS/2 NDIS2: smc8000.os2 v3.07 OS/2 NDIS2: smc8000.os2 v3.07 Pass (Note 2B) DOS NDIS2: smc8000.dos v3.07 Pass (Note 2B) UNIX SCO Rel.3.2 v4.2 DEC LLI: dce v1.22 DEC LLI: dce v1.22 Pass (Note 3B) ISC Rel.3.2 v4.0 DEC LLI: dce v1.50 DEC LLI: dce v1.50 Pass (Note 3B) Note 1B: Reports that the adapter is using thin coax cable, regardless of whether thin coax or twisted-pair cable is being used. Refer to the section titled, 'Packet Driver'. Note 2B: The current version of NTS/2 LAPS truncates the driver name SMC8000$ to SMC800$ in the PROTOCOL.INI file. Refer to the section titled, 'Using IBM NTS/2 . . .' Note 3B: The EtherEZ adapter does not support the EtherCard Elite16 Ultra adapter versions of these drivers in an NDIS3 environment. Refer to the section titled, 'Using EtherCard Elite16 Ultra Drivers . . .' WHAT IS A PLUG AND PLAY SYSTEM? Because Plug and Play is a relatively new industry specification, you may not be familiar with some of the terminology used throughout this document. A brief description of PnP and non-PnP systems is provided below. Plug and Play (PnP) System A system with Plug and Play software is considered a PnP system if it contains any of the following software components: a PnP system BIOS, a PnP operating system, or a PnP Configuration Manager device driver. A PnP system may have any combination of these components. The PnP system BIOS will configure PnP adapters with boot ROMs and optionally configure all remaining PnP adapters. A PnP operating system will configure all of the PnP adapters on the system that were not configured by the system BIOS. If there is no PnP BIOS, the PnP operating system will configure all of the adapters. A PnP Configuration Manager device driver will configure the PnP adapters similar to the way a PnP operating system does. These software components are not supplied with your EtherEZ adapter. Non-Plug and Play System A non-PnP system is a computer that does not contain any of the PnP software components described above. INSTALLATION GUIDELINES USING EZSTART WITH PLUG AND PLAY BIOS SYSTEMS The current version of EZStart (v5.31) is uniquely designed to recognize systems equipped with a Plug and Play (PnP) operating system (such as Windows 95) or a PnP Configuration Utility. If you use EZStart's Automatic configuration option to configure the adapter, and the Computer System field on the Automatic Installation screen displays Plug and Play Computer - Yes, EZStart has recognized the computer as a PnP system. Systems equipped with a PnP BIOS, but lacking a PnP operating system or PnP Configuration Utility, may not be recognized as PnP systems by EZStart. If you run EZStart's Automatic configuration option for such systems, the Computer System field on the Automatic Installation screen displays Plug and Play Computer - No. The configuration automatically assigned by EZStart will work properly, however, the BIOS may not be able to automatically reassign the adapter to a different configuration at a later time. To configure the adapter for PnP operation in a system with a PnP BIOS only, use EZStart's Custom configuration option to display the Manual Setup screen. Move to the Computer Selection field and select Yes to the question Does your computer support Plug and Play operation? Then select Save and exit EZStart. Note: EZStart v5.32 (due for release soon) will automatically detect systems equipped with a PnP BIOS, a PnP operating system, or a PnP Configuration Utility (including systems with a PnP BIOS only). PLUG AND PLAY INCOMPATIBILITIES The rapid deployment of Plug and Play systems combined with the continuing evolution of the Plug and Play specification has forced many vendors to provide systems with PnP BIOSes that do not adhere to the current Plug and Play specification. As a result, you may encounter incompatibilities between your PnP BIOS and EtherEZ adapter that prevent you from configuring the adapter or loading other device drivers. These incompatibilities occur when the system's PnP BIOS fails to detect the IRQ, I/O Base, and ROM Base addresses used by non-PnP devices and tries to assign these resources to the EtherEZ adapter. You may choose to disable Plug and Play operation as described below. Disabling PnP With EZSetup If you encounter a problem configuring the EtherEZ adapter or loading other device drivers, use SMC's EZSetup software to disable the EtherEZ's Plug and Play feature. To obtain the EZSetup software, use EZStart to extract it from the compressed file on the SuperDisk, just as you would copy a network driver. Alternatively, you can download the file GEZxxx.EXE from SMC's BBS (xxx is the software version number); then type GEZxxx.EXE at the DOS prompt of the directory where the downloaded file resides to extract the EZSetup software. After the software is extracted, you can disable the adapter's PnP feature by typing EZSetup -nopnp at the DOS prompt and pressing Enter. Note that there is a space between EZSetup and -nopnp, and that nopnp must be typed in lower-case characters. To re-enable the adapter's PnP feature, type EZSetup pnp:BASE at the DOS prompt and press Enter, where BASE is the hexadecimal I/O Base address of the EtherEZ adapter. For example, if the adapter's base address is 280, type EZSetup pnp:280 and press Enter. USING ETHERCARD ELITE16 ULTRA DRIVERS WITH THE ETHEREZ ADAPTER The NetWare Client and Server and NDIS2 drivers developed for the EtherCard Elite16 Ultra adapter (8216 board types) are forward-compatible with the EtherEZ adapter. They will function the same on an EtherEZ adapter as they do on an EtherCard Elite16 Ultra adapter provided the EtherEZ adapter is configured to operate in Memory-Mapped Addressing Mode (see directions following). However, EtherCard Elite16 Ultra drivers predating those listed below do NOT operate properly with the EtherEZ adapter (even in Memory-Mapped Addressing Mode). Drivers developed for the EtherEZ adapter DO work properly and are therefore the proper workaround for anyone wishing to use the same drivers on both EtherEZ and EtherCard Elite16 Ultra adapters. The following recent drivers DO support the EtherCard Elite16 Ultra adapter and also support the EtherEZ adapter in both Memory-Mapped and I/O-Mapped Addressing Modes: NDIS3 NT Driver v. 1.06 dated 05/17/94 NDIS3 WFW Driver v. 1.01 dated 07/17/94 SCO LLI sme v. 1.21b dated 05/27/94 SCO MDI sme v. 1.00a dated 05/06/94 ISC UNIX sme v. 1.50a dated 07/15/94 SOLARIS x86 2.4 Beta CONFIGURING THE ETHEREZ ADAPTER FOR USE WITH OLDER DRIVERS Drivers written for SMC's EtherCard Elite16 Ultra adapter (8216 board types) and other older adapters operate only in Memory-Mapped Addressing Mode, but the EtherEZ factory default configuration is I/O-Mapped Addressing Mode. Thus, the EtherEZ adapter must be configured to operate in Memory-Mapped Addressing Mode if you need to operate it with these older drivers. That configuration procedure is described below and, in more detail, in Appendix E of the EtherEZ user guide. As with any other configuration procedure using EZStart, first make sure all device drivers for other products are loaded before running EZStart. To select Memory-Mapped Addressing Mode, install the adapter into your computer, then: 1) Run EZStart. 2) Select Custom from the Main screen. 3) Select Setup from the Custom Installation screen. 4) In the Addressing Mode section, click on Memory-Mapped. 5) Click on the Save button. In a non-Plug and Play system, if you receive a resource conflict, return to the EZStart Main screen and run Automatic. Resolve any conflicts as directed by EZStart. (In a Plug and Play system, any conflicts will be resolved after rebooting your computer.) 6) Select Ok. 7) Exit EZStart and reboot your computer. At this point you can use the network driver (e.g., previously installed EtherCard Elite16 Ultra driver) of your choice. If you use an EtherCard Elite16 Ultra driver or other older driver with the EtherEZ adapter but forget to switch the EtherEZ adapter to Memory-Mapped Addressing Mode, you may receive an error message similar to the following (message for DOS ODI driver shown): SMC 8000 - DOS - 207: Other system ROM already occupies adapter RAM. SMC 8000 - DOS - 7: The adapter did not initialize. SMC 8000 did not load. USING MEMORY-MANAGEMENT UTILITIES EMM386 v4.48 or Earlier: If you use EMM386 v4.48 or earlier (provided with DOS v6.21 and earlier), upgrade to EMM386 v4.49 by obtaining DOS v6.22 or later, or change memory managers. Otherwise, incompatibilities in EMM386 may cause your computer to hang when a LAN driver tries to load. To determine your DOS version, type VER and press Enter at the DOS prompt. Memmaker and Aggressive Option: Selecting Memmaker's (DOS v6.21 or v6.22) Aggressive memory scanning option causes Memmaker to specify HIGHSCAN as an option parameter to EMM386. An incompatibility exists when using the HIGHSCAN option with EMM386 and PnP adapters. This incompatibility may cause your computer to hang or reboot. To resolve this problem, do not select the Aggressive memory scan option on Memmaker. Excluding Adapter RAM Address Space: When operating the EtherEZ adapter in Memory-Mapped Addressing mode and using a memory-management utility (such as EMM386 or QEMM), exclude an 8 KB RAM window in your CONFIG.SYS file for use by the adapter. For example: DEVICE=C:\DOS\EMM386.EXE X=D000-D1FF For adapters with Boot ROMs, you must exclude an additional 8 KB, for a total excluded memory space of 16 KB. For example: DEVICE=C:\DOS\EMM386.EXE X=D000-D3FF Reboot your computer after making these changes. ETHEREZ ADAPTERS WITH BOOT ROMs Configuration Procedure: To use a Boot ROM, you must run EZStart to modify the default settings and properly enable the Boot ROM. The configuration procedure is described below and, in more detail, in Appendix D of the EtherEZ user guide. As with any other configuration procedure using EZStart, first make sure all device drivers for other products are loaded before running EZStart. Insert the Boot ROM into the socket provided on the adapter and install the adapter into your computer, then: Plug and Play Systems 1) Run EZStart. 2) Select Custom from the Main screen. 3) Select Setup from the Custom Installation screen. 4) In the Boot ROM section, click on the ROM Enabled box. 5) Click on the Save button. You may be informed of a resource conflict. If so, the conflict will be resolved after rebooting your computer. 6) Select Ok. 7) Exit EZStart and reboot your computer. Non-Plug and Play Systems 1) Run EZStart. 2) Select Automatic from the Main screen. EZStart tests the adapter's basic functions and provides test results. 3) Select Save. 4) To install a network driver, select Yes. Otherwise, select No. 5) Exit EZStart. If EZStart fails to recognize the Boot ROM, make sure you have properly excluded a 16 KB memory space as described previously (Using Memory Management Utilities). Lanworks Technologies, Inc. v1.30 Boot ROM Known Limitations: 1) When using the v1.30 Boot ROM with the EtherEZ adapter, the BootWare Configuration Utility provided with the Boot ROM causes the system to crash during a reboot. Do not press Ctl-M during a system reboot to run the BootWare Configuration Utility; instead, use EZStart to configure the adapter. 2) A computer will not boot from a v1.30 Boot ROM installed on an EtherEZ adapter if an EtherCard Elite32 Ultra adapter (8232 board types) is installed in the same computer. The Lanworks Technologies, Inc. v1.40 Boot ROM, which is now available, incorporates fixes for these limitations. USING IBM NTS/2 AND LAN ADAPTER PROTOCOL SUPPORT (LAPS) PROGRAM The latest versions of NTS/2 and LAPS truncate the SMC driver name SMC8000$ to SMC800$ when the driver name is translated from the SMCOS2AT.NIF file to the PROTOCOL.INI file. Use a text editor or word processor to correct the driver name to SMC8000$ in the PROTOCOL.INI file. USING SMC's PC AGENT/SNMP In Windows for Workgroups v3.11, PCAgent/SNMP (all versions) is not completely supported due to memory-loading issues with Windows. Do not run PC Agent/SNMP and Windows for Workgroups simultaneously. ETHEREZ DRIVERS AND 8086/8088 (XT) PCs EtherEZ drivers will not function on 8086/8088 (XT) class PCs. PACKET DRIVER The driver PKT8000.COM v11.2 reports that the adapter is using thin coax cable, regardless of whether thin coax or twisted-pair cable is being used. This issue does not affect operation of the adapter. Information furnished by Standard Microsystems Corporation (SMC) is believed to be accurate and reliable. However, no responsibility is assumed by SMC for its use, nor for any infringements of patents or other rights of third parties which may result from its use. No license is granted by implication or otherwise under any patent or patent rights of SMC. SMC reserves the right to change specifications at any time without notice. Copyright © 1995 by Standard Microsystems Corporation. All rights reserved. SMC and Standard Microsystems are registered trademarks; and EtherEZ, EZSetup, and SuperDisk are trademarks of Standard Microsystems Corporation. Other product and company names are registered trademarks or trademarks of their respective companies. Standard Microsystems Corporation Hauppauge, New York All rights reserved. Printed in U.S.A. Compatible Platforms and Installation Guidelines Standard Microsystems Corporation