------------------------------------------------------------------------------- PowerNIC(TM) CN40BC PC Card Type II Ethernet Adapter Setup & Driver Diskette Copyright (C) 1995 by CNet Technology Inc. All rights reserved. All trademarks and trade names are the property of their respective owners. ------------------------------------------------------------------------------- CONTENTS OF THIS FILE 1. INTRODUCTION 2. USING SETUP.EXE WITH THE CN40BC PC CARD ADAPTER 3. COPEN.EXE FOR THE DOS ENVIRONMENT 4. COPEN.OS2 FOR THE OS2 ENVIRONMENT 5. NETWORK ACCESS 6. DISKETTE STRUCTURE AND CONTENTS ********************************************** * * * 0. DISKETTE VERSION UPDATE HISTORY * * * ********************************************** Version Release Date Change Description V1.00 25/Sep/1995 First Release V1.10 20/Oct/1995 Windows 95 driver added V1.20 25/Apr/1996 Windows NT 3.5, 3.51 driver added V1.30 11/Nov/1996 1. PCI-PCMCIA bridge (Cirrus Logic) solved in SETUP and COPEN programs. 2. Windows NT 4.0 driver added 3. Access Windows95 version B (OSR2) *************************** * * * 1. INTRODUCTION * * * *************************** Thank you for purchasing this CNet product. This file includes late-breaking information not included in the User's Manual. Also included is a description of how SETUP.EXE works and a list of other files on this diskette. ** "PC Card" is the same as "PCMCIA" ** In early 1995 the Personal Computer Memory Card International Association (PCMCIA) decided to change the name of its specification to "PC Card", effective immediately. Both terms are used interchangeably in this file and other product documentation. Since the PowerNIC PC Card Ethernet adapter is designed for portability, we assume that it will usually be used with portable computers (laptops, notebooks, and palmtops). There are also desktop computers with PC Card slots. References to "notebook," "PC" or "computer" are generic terms used here for any machine in which you wish to install this PC Card Ethernet adapter. ************************************************************* * * * 2. USING SETUP.EXE WITH THE CN40BC PC CARD ADAPTER * * * ************************************************************* When the SETUP.EXE program is run, it will automatically detect the PC's configuration and assign free I/O address and IRQ (interrupt request line) settings for the PC Card adapter. From the SETUP.EXE Main Menu, you can select the "View Configuration" item to see the current card settings. The "Change Configuration" item lets you manually change the I/O and IRQ. You can also choose "Run Diagnostics" to verify the card's functions. *********************************************** * * * 3. COPEN.EXE FOR THE DOS ENVIRONMENT * * * *********************************************** Another executable file in this directory is COPEN.EXE. It is called an "Enabler." Do NOT delete COPEN.EXE. The COPEN.EXE program must be executed before the computer can access the network. SETUP.EXE calls the COPEN.EXE program automatically to open the hardware settings (I/O base address and IRQ). This enables the adapter to access the network. While the user does not need to invoke COPEN.EXE, it must exist in the same directory as SETUP.EXE. The PowerNIC PC Card Ethernet adapter must first be "enabled" by COPEN.EXE (through SETUP.EXE) before the loaded LAN drivers can function properly. The enabler program opens the I/O address and IRQ for the card. After these are open, then the LAN drivers can operate correctly. So remember: a) that the enabling program and LAN drivers must use the same I/O address and interrupt line, and b) COPEN.EXE must be loaded AFTER Card & Socket Services, and BEFORE the LAN drivers. COPEN.EXE can enable many versions of the PCMCIA chip set: Intel 365, Vadem, Cirrus, Databook, Toshiba 3300SL ICCNT, Texas CCU, Motorola, IBM ThinkPad, Sharp PHIC, and others are all supported. The card works well under all popular Socket Services 1.x & 2.x, and with all Card Services version 2.xx vendors: SystemSoft (CardSoft), Phoenix (PCM), Award (CardWare), AMI, Databook (CardTalk), and so on. Normally your notebook PC comes with Card Services software. Commands to invoke the software are in your C:\CONFIG.SYS file. The correct order for loading the required files is 1) Socket Services, 2) Card Services, 3) COPEN.EXE Enabler program, and 4) LAN Drivers. An example of a valid CONFIG.SYS file is shown below: [DEVICE=Socket Services command] [DEVICE=Card Services command] [DEVICE=Card Services resource manager command] DEVICE=COPEN.EXE [/IO=xxx] [/IRQ=yy] [/MEM=mmmm] [/O] ; PC Card Enabler Program DEVICE=E200P.DOS ; If NDIS 2 driver is selected where, xxx is a 3-digit hexadecimal number representing the I/O port base address. Supported values are: 300, 320, 340, & 360. Default is 300. (NOTE: CN40 series version C, "PCMCIA CARD (C)" wording on the back side of the card, supports additional 200, 220, 240, 260 ports). yy is a one- or two-digit number representing the number of the interrupt request line. Values supported are: 3, 4, 5, 9, 10, 11, 12, & 15. Default is 5. mmmm is a 4-digit hexadecimal number representing PC upper memory base address. The address should not conflict with an upper memory manager like EMM386.EXE. Supported values are: C000, C400, C800, CC00, D000, D400, D800, & DC00. Default is D800. /O is an override option. It allows to force the specified IO and IRQ selections for the adapter. Remember that COPEN.EXE must be executed before the network drivers are loaded. ************************************************* * * * 4. COPEN.OS2 FOR THE OS/2 ENVIRONMENT * * * ************************************************* COPEN.OS2 is an enabler program to enable the card for the OS/2 environment. COPEN.OS2 must run before any network drivers. To enable the adapter, put the following command sequence into your C:\CONFIG.SYS file: : : : DEVICE=C:\path\COPEN.OS2 [/IO=xxx] [/IRQ=yy] [/MEM=mmmm] [/O] : : : [DEVICE=C:\path\E200P.OS2] ; for NDIS 2 LAN driver : : : where, xxx is a 3-digit hexadecimal number representing the I/O port base address. Supported values are: 300, 320, 340, & 360. Default is 300. yy is a one- or two-digit number representing the number of the interrupt request line. Values supported are: 3, 4, 5, 9, 10, 12, & 15. Default is 5. mmmm is a 4-digit hexadecimal number representing PC upper memory base address. The address should not conflict with upper memory managers like EMM386.EXE. Supported values are: C000, C400, C800, CC00, D000, D400, D800, & DC00. Default is D800. /O is an override option. It allows to force the specified IO and IRQ selections for the adapter. **************************** * * * 5. NETWORK ACCESS * * * **************************** To install the correct driver for your network operating system (NOS), please follow the instructions below: 1. Determine which NOS is used by the network to which you wish to connect your PC. 2. Search the directories listed below for the one which has the driver for your NOS. 3. Change to that directory. Read the file "INSTALL.DOC" in the directory and follow the instructions to install the driver. The system information files "NET.CFG" and "PROTOCOL.INI" can be modified if necessary. ********************************************* * * * 6. DISKETTE STRUCTURE AND CONTENTS * * * ********************************************* The files included in this diskette are: \ ³ README.1ST ; This file ³ ³ SETUP.EXE ; Setup program ³ COPEN.EXE ; PC Card Enabler Program under DOS ³ COPEN.OS2 ; PC Card Enabler Program under OS/2 ³ DISK1 ; Diskette file for NDIS 3.0 driver ³ ÃÄÄÄDOS_ODI ; Subdirectory for NetWare DOS ODI driver ³ ³ LSL.COM ; NetWare DOS ODI workstation driver ³ ³ E200P.COM ; NetWare DOS ODI workstation driver ³ ³ IPXODI.COM ; NetWare DOS ODI workstation driver ³ ³ NETX.COM ; NetWare DOS ODI workstation driver ³ ³ E200P.INS ; Personal NetWare installation file ³ ³ NET.CFG ; NetWare ODI configuration file ³ ³ VERSION.DOC ; Version list ³ ³ INSTALL.DOC ; Installation documemt for NetWare DOS ODI ³ ³ STARTNET.BAT ; Batch file to access NetWare ³ ³ ³ ÃÄÄÄLANWP4.DOS ; Subdirectory for Novell LAN WorkPlace ³ ³ for DOS ³ ³ INSTALL.DOC ; Installation documemt for Novell LAN ³ ³ WorkPlace for DOS ³ ³ NET.CFG ; NetWare ODI configuration file ³ ³ ³ ÀÄÄÄPNW ; Subdirectory for Personal NetWare ³ INSTALL.DOC ; Installation documemt for Personal NetWare ³ ÃÄÄÄOS2_ODI ; Subdirectory for NetWare OS/2 ODI driver ³ E200P.SYS ; NetWare OS/2 ODI workstation driver ³ NET.CFG ; NetWare ODI configuration file ³ VERSION.DOC ; Version list ³ INSTALL.DOC ; Installation documemt for NetWare OS/2 ODI ³ ÃÄÄÄNW_311 ; Subdirectory for NetWare v3.11 server driver ³ E200P.LAN ; NetWare v3.11 server driver ³ VERSION.DOC ; Version list ³ INSTALL.DOC ; Installation documemt for NetWare v3.11 ³ server driver ³ ÃÄÄÄNW_4 ; Subdirectory for NetWare v4.x or v3.12 ³ ; server driver ³ E200P.LAN ; NetWare v4.x or v3.12 server driver ³ VERSION.DOC ; Version list ³ INSTALL.DOC ; Installation documemt for NetWare v4.x ³ server driver ³ ÃÄÄÄPCTCP ; Subdirectory for PC/TCP ³ 200EPD.COM ; PC/TCP packet driver ³ VERSION.DOC ; Version list ³ INSTALL.DOC ; Installation documemt for packet driver ³ ÃÄÄÄNDIS_20 ; Subdirectory for NDIS 2.0 driver ³ ³ E200P.DOS ; NDIS 2.0.1 driver for DOS ³ ³ E200P.OS2 ; NDIS 2.0.1 driver for OS/2 ³ ³ E200P.NIF ; Information for DOS LAN Manager installation ³ ³ PROTOCOL.INI ; LAN Manager Sample PROTOCOL initialization ³ ³ ; file segment ³ ³ OEMSETUP.INF ; Information for installation WFW 3.1 ³ ³ VERSION.DOC ; Version list ³ ³ ³ ÃÄÄÄMSLANMAN ³ ³ INSTALL.DOC ; Installation documemt ³ ³ ³ ÃÄÄÄIBMLANSE ³ ³ E200P.NIF ; Information for OS2 LAN Server installation ³ ³ INSTALL.DOC ; Installation documemt ³ ³ ³ ÃÄÄÄWFW31 ; Windows For Workgroups version 3.1 ³ ³ INSTALL.DOC ; Installation documemt ³ ³ ³ ÃÄÄÄPATHWORK ³ ³ INSTALL.DOC ; Installation documemt ³ ³ ³ ÃÄÄÄPCNFS ³ ³ INSTALL.DOC ; Installation documemt ³ ³ ³ ÃÄÄÄBANYAN ³ ³ INSTALL.DOC ; Installation documemt ³ ³ ³ ÃÄÄÄWOLLONG ³ ³ INSTALL.DOC ; Installation documemt ³ ³ ³ ÃÄÄÄPCTCP ³ ³ INSTALL.DOC ; Installation documemt ³ ³ ³ ÀÄÄÄLSP ³ E200P.DOS ; NDIS 2.0.1 driver for DOS ³ E200P.NIF ; Information for LAN Support Program ³ installation ³ INSTALL.DOC ; Installation document ³ ÃÄÄÄMSLANMAN.DOS ; Subdirectory for MS LAN Manager for DOS ³ ÀÄÄÄDRIVERS ³ ÃÄÄÄETHERNET ³ ³ ÀÄÄÄE200P ³ ³ E200P.DOS ; NDIS 2.0.1 driver for DOS ³ ³ PROTOCOL.INI ; LAN Manager Sample PROTOCOL initialization ³ ³ file segment ³ ÀÄÄÄNIF ³ E200P.NIF ; Information for DOS LAN Manager installation ³ ÃÄÄÄMSLANMAN.OS2 ; Subdirectory for MS LAN Manager for DOS ³ ÀÄÄÄDRIVERS ³ ÃÄÄÄETHERNET ³ ³ ÀÄÄÄE200P ³ ³ E200P.OS2 ; NDIS 2.0.1 driver for OS/2 ³ ³ PROTOCOL.INI ; LAN Manager Sample PROTOCOL initialization ³ ³ file segment ³ ÀÄÄÄNIF ³ E200P.NIF ; Information for OS2 LAN Manager installation ³ ÃÄÄÄWFW311 ; Subdirectory for MS Windows for Workgroups ³ E200P.DOS ; NDIS 2.0.1 driver for real mode ³ E200P.386 ; NDIS 3.0 driver for enchanced mode ³ OEMSETUP.INF ; Information for installing WFW 3.11 ³ VERSION.DOC ; Version list ³ INSTALL.DOC ; Installation document ³ ³ÄÄÄWIN95 ; Subdirectory for MS Windows 95 ³ INSTALL.DOC ; Installation document ³ E200P.VXD ; NDIS 3.1 driver for Windows 95 ³ NET40BC.INF ; Required scripts for installing Windows 95 ÀÄÄÄWINNT ; Subdirectory for MS Windows NT ³ ÃÄÄÄ35 ; Subdirectory for MS Windows NT 3.5 ³ E200P SYS ; NDIS 3.1 driver for Windows NT 3.5 ³ OEMSETUP INF ; Required scripts for installing WIN NT 3.5 ³ INSTALL DOC ; Installation document ³ ÃÄÄÄ351 ; Subdirectory for MS Windows NT 3.51 ³ E200P SYS ; NDIS 3.1 driver for Windows NT 3.51 ³ OEMSETUP INF ; Required scripts for installing WIN NT 3.51 ³ INSTALL DOC ; Installation document ³ ÀÄÄÄ40 ; Subdirectory for MS Windows NT 4.0 E200P SYS ; NDIS 3.1 driver for Windows NT 4.0 OEMSETUP INF ; Required scripts for installing WIN NT 4.0 INSTALL DOC ; Installation document