NDC 4100 SERIES ON-LINE INSTALLATION GUIDE NOTE: To Print this document, README.TXT, use the DOS command PRINT d:\README.TXT (d: = A: or B: depending on drive used) or import it into your word processor (use Courier 10 font and set all margins at .5 inch) and then print it. This document is in ASCII format. "EDIT" (DOS 5.0+) can also be used to view this document. The 4100 Series includes the following models: -ND4113-E: NE2000 compatible, software configurable, Ethernet adapter with AUI, BNC and RJ-45 connectors. -ND4112-E: NE2000 compatible, software configurable, Ethernet adapter with BNC connector. -ND4102-E: NE2000 compatible, software configurable, Ethernet adapter with RJ-45 connector. TRADEMARKS - IBM is a registered trademark of International Business Machines Inc. - Apple and Macintosh are registered trademarks of Apple Computer Inc. - NetWare, NetWare Lite and Novell are registered trademarks of Novell Inc. - Personal Computer AT is a trademark of International Business Machines Inc. - Sun Microsystems is a registered trademark of Sun Microsystems Inc. - Windows and Windows For Workgroups are registered trademarks of Microsoft Inc. - LANtastic and AI-LANBIOS are registered trademarks of Artisoft Inc. - Sound Blaster is the registered trademark of Creative Labs,Inc. RADIO FREQUENCY INTERFERENCE STATEMENT This product has been verified to comply with the limits for a Class A computing device pursuant to subpart B of Part 15 of the FCC rules. This does not guarantee that interference will not occur in individual installations. We are not responsible for any television, radio, or other interference caused by unauthorized modifications of this product. If interference problems do occur, please consult the system hardware manual for suggestions. Some of these suggestions include relocation of the computer system away from the television or radio and placing the computer on a different electrical circuit from the television or radio. NDC makes no warranties regarding the information contained in this file. Additionally, NDC is not responsible or liable for any loss or damage of any kind resulting from the use of this product. TABLE OF CONTENTS SECTION 1 PREFACE SECTION 2 INTRODUCTION 2-1 Product Description 2-2 LED Indicators 2-3 Unpacking The Product 2-4 PC/AT ISA Bus Adapter Installation Basics SECTION 3 HARDWARE INSTALLATION 3-1 The 4100 Series Ethernet Adapter Default Settings 3-2 Installing The 4100 Series Ethernet Adapter 3-3 Configuring The I/O Port, IRQ, ROM Address And Connector Type 3-4 Installing The Boot ROM 3-4-1 NDET06 Installation 3-4-2 NDET07 Installation 3-5 Bus Timing Compatibility SECTION 4 SOFTWARE INSTALLATION 4-1 Installing Drivers For NetWare 4-1-1 IPX Shell Drivers 4-1-2 NetWare 2.15/2.2 IPX Server Drivers 4-1-3 DOS ODI Drivers 4-1-4 NetWare 3.10/3.11 ODI Server Drivers 4-1-5 NetWare Lite Drivers 4-2 Installing FTP PC/TCP Drivers 4-2-1 FTP PC/TCP Drivers 2.0x 4-2-2 FTP PC/TCP Drivers 2.1x 4-3 Installing NDIS Drivers 4-3-1 LAN Manager 1.x Drivers 4-3-2 LAN Manager 2.0, 2.1 Drivers 4-3-3 Windows Or Windows For Workgroups Drivers 4-4 Installing Drivers For Banyan VINES 4-4-1 Banyan VINES Workstation Drivers 4-4-2 Banyan VINES Server Drivers SECTION 5 TROUBLESHOOTING 5-1 Basic Troubleshooting 5-2 Troubleshooting Tips 5-3 Diskless Boot (Remote Boot or RIPL) Problems APPENDIX A 1 Ethernet Cabling 1-1 Thin Ethernet 1-2 Thick Ethernet 1-3 UTP Ethernet 2 Product Specifications PREFACE This document describes the features and operation of the 4100 Series Ethernet Adapters. You should have some basic knowledge of PC/AT hardware and DOS before attempting to install the network hardware. This document explains how to install the 4100 Series network adapters in a standard PC/AT, ISA bus, computer. A working knowledge of Ethernet networks is required if you intend to install the cable and the entire network yourself. This document describes some of the cable options and how to connect the 4100 Series adapter to them. The 4100 Series are plug-and-play hardware-only adapters that use the native software drivers provided by the respective LAN operating system vendors. Installing and configuring these drivers require some knowledge of the network operating system you are using. This document describes some of the drivers supported, and gives a brief explanation of the installation procedures. For complete installation instructions, please consult the installation manual for your specific network operating system. The five major sections of this document are: 1. Preface.....describes this document and what information is contained herein. 2. Introduction...describes the 4100 Series adapters and gives some basic knowledge of Ethernet cabling and PC/AT, ISA bus, system architecture. 3. Hardware Installation...describes how to install a 4100 Series adapter. 4. Software Installation...describes how to install the various network operating system software drivers for the 4100 Series adapters. 5. Troubleshooting...provides basic troubleshooting procedures should you encounter problems with your installation of a 4100 Series adapter. This document covers all of the 4100 Series adapters. They are NE2000 compatible Ethernet adapters. The only difference in the models is media connector configuration. [2] INTRODUCTION [1] Product Description [2] LED Indicators [3] Unpacking The Product [4] PC/AT ISA Bus Adapter Installation [2-1] Product Description The 4100 Series adapters are designed for standard PC/AT ISA bus, IBM compatible computers. They provide LAN (local area network) connectivity allowing communication with other PC/AT, PS/2, Macintosh, etc. computers that are connected to the same cable. The cable can be unshielded twisted-pair (UTP), thin (coax) or thick Ethernet that complies with the IEEE 802.3, 10Base5, 10Base2, or 10BaseT standards. 1. [Thin Ethernet:] uses economical RG58 A/U (50 Ohm) coaxial cable for network interconnection. The connectors used are BNC. 2. [Thick Ethernet:] uses thick, heavily insulated coaxial cable. The connectors used are AUI. 3. [Unshielded twisted-pair (UTP) Ethernet:] uses economical unshielded twisted-pair, 22, 24, or 26 AWG, interior wire. The connectors used are RJ-45. 4100 SERIES MODEL FEATURES MODEL JUMPER SOFTWARE ----------CONNECTORS------------- NUMBER LESS CONFIGURABLE Thin Net Thick Net Twisted Pair ND4113-E XX XX XX XX XX ND4112-E XX XX XX ND4102-E XX XX XX The 4100 Series Ethernet adapter has a high performance LAN controller and a 16Kb RAM buffer that is used to transfer data between the network and the computer's memory. No DMA channels are used, eliminating any DMA conflict with other devices in the computer. A socket is provided on the 4100 Series Ethernet adapters for an optional Boot ROM. When the Boot ROM is installed on the adapter and a boot image file is installed on a file server, the workstation can load the operating system from the file server over the network. This capability makes it possible to install diskless workstations. [2-2] LED Indicators The ND4113-E and the ND4102-E feature 2 LED indicators. Both the red and green LED's will light up when the power is on. When using Twisted-Pair cabling: the green LED will become brighter, if connection is good; or, it will flash, if it is receiving. The red LED will flash when it is transmitting or when a collision occurs. [2-3] Unpacking The Product The following items are included in the 4100 Series Ethernet adapter package: * An Ethernet adapter * A Quick Installation Guide * A Diskette that contains the SOFTSET program * A BNC "T" Connector (ND4112-E and ND4113-E) [2-4] PC/AT ISA Bus Adapter Installation Basics and Definitions - Slot: The PC/AT architecture supports slots located on the system (mother) board into which can be placed additional adapter cards which expand the computer's power or capabilities. - I/O Port: I/O Ports are communication channels through which the computer communicates with the added devices and gets a response, or status from these devices. Valid I/O Port addresses for ISA bus (PC/AT) machines are from 0x0000h to 0xFFFFh. The address range from 0x0000h to 0x00FFh is reserved for the system (mother) board. Each I/O Port can be used by only one device. If two devices attempt to use the same I/O Port, one, or both of the devices will fail to operate properly. Most devices use a group of I/O Port Address like 300h-31Fh. This address runs from 300h thru 31Fh. Even if the base address is 300h, putting another device at 310h would conflict with the upper half of the address range of device at 300h. Be sure to check the total address of a device. - IRQ (Interrupt ReQuest): Devices "Interrupt" the CPU (processor) on the mother board and "Request" some specific service. This is a hardware signal that causes the CPU to execute a routine called "Interrupt Service Routine". Valid IRQs for the PC/AT are 0 - 15. Some IRQs on the PC/XT/AT may be shared between devices, but in most cases the IRQ is dedicated for some specific device and problems may arise if two devices are set for the same IRQ. - Software Interrupt: This is a method used to execute part of a software program, or a software routine. The difference between the software and the hardware interrupt is that the software interrupt is caused by an "INT xx" instruction (where xx is the software interrupt number) from another program and the hardware interrupt is caused by an actual electrical signal. - Memory Address: Memory is where the computer keeps data and programs that are running. The CPU keeps track of data and programs in memory by their address, or location in memory. Each piece of data or each program occupies a unique address in the computer's memory. Some adapter cards support shared memory. These cards share a block of memory addresses with the CPU and use this memory area to transfer data. No two devices may share the same block of memory addresses. When there are two devices attempting to use the same block of memory addresses, one or both of the devices will fail to operate properly. - DMA (Direct Memory Access) Channel: Devices using DMA access system memory directly, and not via the system CPU. Eight DMA channels are supported in the PC/AT. Each DMA channel can be used for one device only. They can not be shared by two or more devices. [The Adapters:] Some common devices in a computer and the memory addresses, IRQs and DMA channels they might use are: - VGA Display Adapter: some use memory addresses from B8000h through C3FFFh, and I/O Ports 3C2, 3C3, 3C5, 3C7 ... - LPT1 Printer Port: I/O Port addresses 3BC, 3BD and 3BE, and IRQ 7. - The Floppy Disk Controller: I/O Port 372 through 377, and IRQ 6. - The 4100 Series Ethernet Adapter: uses I/O Port 300 through 31F, and IRQ 3 (default settings). Some devices have fixed settings and others are configurable for a range of settings. Be certain that no devices in the computer are set for the same shared memory addresses, I/O Ports, IRQs or DMA channels. If some adapter does conflict, one must be changed so that there are no conflicting addresses or settings. The network card needs to use a unique I/O address range. The following table shows possible address conflicts. ____________________________________________________ | I/O | | | ADDRESS| POTENTIAL CONFLICT DEVICES | |________|__________________________________________| | 1F0 | AT disk controller (1F0-1F8) | | 200 | game controller/joystick (200-20F) | | 220 | SoundBlaster/ Novell network keycard | | 240 | | | 260 | LPT2: (278-27F) | | 280 | LCD display on Wyse 2108 PC | | 2A0 | | | 2C0 | | | 2E0 | COM4:, GPIB-Adapter 0 (2E1) | | | COM2:, Data acquisition (300-31F) | | 300 | CD-ROM Interface card (300-31F) | | | Ethernet card Default (300-31F) | | 320 | XT hard disk interface (320-32F) | | 330 | SoundBlaster MIDI Interface | | 340 | | | 360 | LPT1:(378-37F) | | 380 | SLDC/Sec Bi-Sync interface (380-38C) | | 3A0 | Primary Bi-Sync interface (3A0-3A9) | | 3B0 | Monochrome display (3B0-3BB) | | 3C0 | EGA display control (3C0-3CF) | | | CGA display control (3D0-3DF) | | 3E0 | COM3: (3E8-3EF) | | | floppy disk controller (3F0-3F7) | | | COM1: (3F8-3FF) | |_______ |__________________________________________| Note: The range of an address for one device can be long enough to overlap that of another device. An example is a CD-Rom interface at 310-32F would overlap the Ethernet card at 300-31F. Use an interrupt (IRQ) for your network card. The following table shows what the IRQ levels are used for in XT and AT computers. __________________________________________ |IRQ | XT | AT (286, 386, 486) | |___ |______________|____________________| | 0 | | timer output 0 | | 1 | | keyboard | | 2 | EGA/VGA | EGA/VGA | | 3 | COM2 | COM2/Ethernet | | 4 | COM1 | COM1 | | 5 | hard disk | LPT2 | | 6 | | floppy disk | | 7 | LPT1 | LPT1 | | 8 |Not Available | real time clock | | 9 |Not Available | | | 10 |Not Available | | | 11 |Not Available | | | 12 |Not Available | | | 13 |Not Available | co-processor | | 14 |Not Available | hard disk | | 15 |Not Available | | |_____|______________|____________________| [The Software Drivers:] Some adapters require software, or drivers in order to operate properly. These drivers must know what I/O Port address and IRQ the adapter is set for in order to function properly. If the drivers have been passed the wrong information (parameters) regarding the I/O Port address and IRQ, the adapter will not function properly. Some drivers require that the hardware settings to be passed to them as parameters when they are loaded. Other drivers are self-configuring and they interrogate the hardware directly to determine the proper settings. [3] HARDWARE INSTALLATION [1] The 4100 Series Ethernet Adapter Default Settings [2] Installing the 4100 Series Ethernet Adapter [3] Selecting IRQ, I/O Port and Media Connector [4] Installing the Boot ROM [5] Bus Timing and Wait States [3-1] The 4100 Series Ethernet Adapter Default Settings The Default settings for the 4100 Series Ethernet boards are: IRQ : 3 Base I/O : 300h - 31Fh Remote Boot PROM : Disable Bus Timing : Standard Connector : BNC (4113 only) The current configuration of the 4100 Series adapter can be checked with the SOFTSET.EXE program contained on the diskette shipped with the adapter. [3-2] Installing the 4100 Series Ethernet Adapter 1. Be sure that no other adapter in the computer is using I/O address 300h - 31Fh or IRQ 3. If there is another adapter in the computer using this I/O address or IRQ, installing the 4100 Series into the computer without first changing the I/O address of the other adapter will cause the other adapter to fail due to the conflicting I/O addresses or IRQs. An alternative is to remove the other adapter from the machine until after the 4100 Series has been configured so that the I/O address or IRQ will no longer conflict. Once the 4100 Series adapter has been properly configured, the other adapter can be reinstalled into the computer. You should determine the I/O Port address and IRQ's of existing devices before you power the computer off. Utility Programs like "system information" (SI) that come with PC Tools and Norton Utilities and MSD that is supplied with MS-DOS 6.0 will help you establish this information. Also the test program QAplus can provide this information. Beware that none of these programs are 100% accurate. 2. Make sure that the power to the computer is turned off and that the power cord is disconnected. 3. After the 4100 Series has been installed into an open 16 bit slot (will work in an 8 bit slot at slower speed) on the mother board, power on the computer and run the SOFTSET.EXE program to configure the adapter. When you have completed all the setup operations and saved them, the 4100 Series is ready for operation. If more than one 4100 Series is to be installed into the same computer, you must install and configure to different address and IRQ's one at a time because the default settings are all the same. 4. If you removed any adapter as recommended in step one above, power off the computer and reinstall that adapter. [3-3] Selecting the IRQ, I/O Port Address, ROM Address and Connector All of the above options are configured by running the SOFTSET.EXE program. -- The main menu of the SOFTSET.EXE program looks like: : View current configuration : Change current configuration : Load default configuration : Run on-board diagnostics : Load configuration from file : Save configuration to file : Exit to DOS 1. Choosing the second option, "Change current configuration" results in the following menu being displayed: : I/O Base:_____________________ : Interrupt Level:______________ : Boot ROM Address:_____________ : Connector:____________________ : Hardware compatibility setting All of the configuration options can be changed from the above menu. The hardware compatibility setting can overcome problems stemming from non-standard bus timing. CHRDY (Channel Ready) Control, and I/O 16 (Input/Output) Control are the two available options for Hardware compatibility setting. CHRDY(Channel Ready) Control: Normal is the setting for most computers. This sets the board for standard PC/AT compatible timing. "Early" is an optional setting that makes the board compatible with the following computers: Compaq portable, IBM 286/30, IBM PS/VP, and computers using the Chips and Technologies chip set. I/O 16 (Input/Output) Control: Normal is the default setting for most computers. This sets the board for standard 16 bit PC/AT compatible bus timing. "Special" is an optional setting that makes the board timing compatible with computers using the VLSI chip set, such as the IBM PS/2 Model 30 computer. 2. Any changes you made in the previous step must be saved to the board or they will not take effect. Note: There is a memory chip on the board called an EEPROM where the configuration is stored. This EEPROM will hold the settings saved to it even when there is no power supplied to the board. 3. Once the changes have been saved to the adapter, running the on-board diagnostics will insure that the configuration is good and that the board is functioning properly. [3-4] Installing the Boot ROM [1] NDET06 Installation [2] NDET07 Installation SKIP THIS SECTION IF YOU ARE NOT USING A BOOT ROM The Remote Boot option allows the workstation to load the operating system from a file server located on the network. The adapter accomodates two optional NetWare Boot ROM Modules. Please contact your local dealer and order model number: NDET06 or NDET07. NDET06 uses the Find/Found protocol with the Ethernet_802.2 frame type. NDET07 uses the Netware IPX protocol with the Ethernet_802.3 frame type. To install the Remote Boot ROM, you must: 1. Select a Boot ROM address and range with the SOFTSET.EXE program. 2. Enable the Boot ROM with the SOFTSET.EXE program. 3. Power off the computer. 4. Remove the 4100 Series adapter and install the PROM into the empty socket on the adapter. Make sure that the notch on the PROM matches the notch on the socket before installing the PROM. 5. Reinstall the 4100 Series into the computer. 6. Power on the computer and the Boot ROM will then request the loading of the operating system from a file server on the network. [3-4-1] NDET06 Installation: To meet Novell's new approach, the NDET06 Boot ROM Module uses the Ethernet_802.2 frame type. Therefore, you must configure the server to do the following: 1. Load the NE2000 with the Ethernet_802.2 frame type. 2. Load the RPL.NLM and bind it to the NE2000. The RPL.NLM must be version V4.01 or newer. NDET06 Error Messages: RPL-ROM-ERR:1001 Card I/O port failed to respond; RPL Halted. Cause: The I/O base address setting may be conflicting with another device in the PC. Action: Select a new I/O base address. RPL-ROM_ERR:1002 Card RAM failure; RPL Halted. Cause: The adapter may be out of order. Action: Contact your network card dealer. RPL-ROM-ERR:1003 The bus width data in the PROM is invalid; RPL Halted. Cause: The EEPROM failed. Action: Contact your network card dealer. [3-4-2] NDET07 Installation: If you use the NDEY07 Boot ROM Module, please make sure the Ethernet_802.3 frame type has been loaded on the NetWare Server. NDET07 Error Messages: ERR02: Memory Failure. Cause: The adapter may be out of order. Action: Contact your network card dealer. ERR03: Hardware Fails to Respond. Cause: The I/O base address setting may be confliction with another device in the PC. Action: Select a new I/O base address. ERR05: IRQ not Found Cause: The Interrupt level may conflict with another card. Ation: Run the SOFTSET program to change the IRQ number. [3-5] Bus Timing Compatibility The default setting for the 4100 Series Ethernet adapter is for standard bus timing. The standard, as defined by IBM for the PC/AT, is 8 MHz. Computers that have a bus running at a faster speed, as do some of the machines with the Chips and Technologies chip set, require that the compatibility setting on the 4100 Series adapters be changed to accommodate the different bus speed. Some of the machines with which the 4100 Series adapters require that the compatibility settings be changed are: COMPAQ 286 Portable IBM PS/2 Model 30-286 IBM PS/VP [4] SOFTWARE INSTALLATION [1] Installing Drivers For NetWare / NetWare Lite [2] Installing FTP PC/TCP Drivers [3] Installing NDIS Drivers for LAN Manager or Windows for Workgroups [4] Installing Drivers For Banyan VINES [4-1] Installing Drivers For NetWare [1] IPX Shell Drivers [2] NetWare 2.15 / 2.2 IPX Server Drivers [3] DOS ODI Drivers [4] NetWare 3.10 / 3.11 Server Drivers [5] NetWare Lite [4-1-1] Installing The IPX Shell Drivers The IPX Shell Driver, IPX.COM, is generated by running the NetWare programs SHGEN or WSGEN, and is a combination of the NetWare IPX and a driver file. To generate the IPX.COM, you must: 1. Run SHGEN or WSGEN. 2. Select the NE2000 driver. 3. Choose the Configuration from the NetWare menu that matches the hardware settings for your adapter. 4. After SHGEN or WSGEN has completed, the appropriate IPX.COM will have been written to the SHGEN_2 OR WSGEN diskette. If you need to change the configuration of the IPX.COM, you can do so by running the NetWare DCONFIG.EXE or ECONFIG.EXE programs. For further details, please consult your NetWare manuals. [4-1-2] Installing the NetWare 2.15 / 2.2 IPX Server Driver You must run the NetWare program NETGEN or INSTALL and choose the NE2000 driver. The NET$OS.EXE file is created, which is the executable server driver. Follow these steps to generate the server: 1. Run NETGEN or INSTALL. 2. Choose the NE2000 driver. 3. Choose the configuration that matches the hardware setting of the adapter. 4. After the NETGEN or INSTALL is complete, the NET$OS.EXE will be generated and written to the OSEXE diskette. If you have Macintoshes on your network, you must choose the correct drivers required to support either Appletalk Phase I or II depending on which your Macintoshes are running. For further information consult your NetWare manuals. [4-1-3] Installing the DOS ODI Drivers Follow these steps to load the ODI workstation drivers: 1. Run LSL.COM (comes with NetWare). 2. Run NE2000.COM (comes with NetWare). 3. Run IPXODI.COM (comes with NetWare). 4. Run NETX.COM (comes with NetWare). If you have changed the configuration of your adapter from the defaults, you can change the default ODI workstation by creating a NET.CFG file. A sample NET.CFG file follows: LINK DRIVER NE2000 Int 3 Port 300 For more detailed information consult your NetWare manuals. [4-1-4] Installing NetWare 3.10 or 3.11 ODI Server Drivers The following steps illustrate the driver installation: 1. After booting to DOS, load the SERVER. 2. Type "LOAD NE2000". 3. Choose the I/O Port address, and IRQ chosen during configuration. Make sure that these choices match the hardware settings. 4. After the server driver is loaded, type "BIND IPX TO NE2000". 5. You will be prompted for a network number. This number should be the number of the network that this server will be on. For further information consult your NetWare manuals. [4-1-5] Installing NetWare Lite Drivers NetWare Lite uses the same drivers as the DOS ODI workstation. The following steps detail the installation process: -- If NetWare Lite is already installed on the station -- 1. Copy NE2000.COM from the NetWare driver diskette to the directory where the NetWare Lite programs are. 2. Edit the NetWare Lite startup batch file, usually named "STARTNET.BAT" so that it reads as follows: LSL NE2000 IPXODI A 3. Edit the NET.CFG file (if it exists or is needed) so that it reads as follows: LINK DRIVER NE2000 Refer to your NetWare manuals for the further details of the NET.CFG file. If NetWare Lite is being installed for the first time: 1. Follow the instructions in the NetWare Lite Installation Manual. 2. When prompted for the name of the network adapter, select NE2000. 3. Choose the NE2000.COM driver and select the configuration that matches the hardware settings of your adapter. 4. Complete the installation instructions as prompted on your screen. Refer to your NetWare Lite manuals for further information. [4-2] Installing FTP PC/TCP Drivers [1] FTP PC/TCP Drivers 2.0x [2] FTP PC/TCP Drivers 2.1x [4-2-1] FTP PC/TCP Drivers 2.0x The PC/TCP Drivers for the NE2000 are distributed with FTP PC/TCP. Before installing these drivers, you must have first installed FTP PC/TCP. The CONFIG.SYS file must include the following lines: DEVICE=(drive letter)\(directory name)\IFCUST.SYS DEVICE=(drive letter)\(directory name)\IPCUST.SYS Both of the above drivers are distributed with the FTP PC/TCP. Reboot your computer after the above two drivers have been installed and the CONFIG.SYS has been edited to contain those drivers. The following steps detail installing the drivers for your 4100 Series adapter. 1. Locate the NE2000 driver on the FTP diskettes. Type "NE2000PD *0X60 0X3 0X300" and press "ENTER". 2. Run "ETHDRV" (the FTP driver). 3. Run FTP xxx.xxx.xxx.xxx to connect to another resource on the TCP/IP network, where xxx.xxx.xxx.xxx is the IP address of the other resource. *0X60 is the software interrupt number, 0X3 is the default IRQ number, and 0X300 is the default I/O Port address. If your adapter is configured differently, the above parameters must be altered so that they match the hardware settings of your adapter. [4-2-2] FTP PC/TCP Version 2.1X For FTP PC/TCP Version 2.1X, you can run the install program to install PC/TCP automatically. When the install program finishes. It creates a configuration file called PCTCP.INI. It does this by combining the following elements: . Information in current in-memory PC/TCP system files. such as ifcust and ipcust, These files are used by the previous release of PC/TCP. . The configuration files used by the previous release of PC/TCP. . Your responses to the questions asked by the install program. This process is documented in the section that follows. There are three stages you must follow to install PC/TCP automatically. 1.Run the install program Insert Disk1 in drive A: , then enter c:\>a:install 2.You will be asked to define the PC/TCP environment variable based on your responses to it's promts. 3.Run the PC/TCP Kernel. Following is an example of autoexec.bat after the PC/TCP is installed: SET PATH=C:\PATH;%PATH% SET PATH=C:\PCTCP SET PCTCP=C:\PCTCP\PCTCP.INI NE2000 0x60 0x3 0x300 ;Packet Driver ETHDRV ;Ethernet generic Kernel TN 128.127.50.100 ;TELNET to Host, the ID address is ;128.127.50.100 For further information see the FTP PC/TCP manuals. [4-3] Installing NDIS Drivers [1] NDIS with LAN Manager 1.x [2] NDIS with LAN Manager 2.0, 2.1 [3] NDIS with Windows for Workgroups [4-3-1] NDIS with LAN Manager 1.x DOS and OS/2 workstations and OS/2 servers are generated with the NetSetup program under LAN Manager. The NetSetup program allows you to choose the LAN adapter from a list of supplied drivers. Assuming that you have installed your LAN Manager files in the directory called MSLAN, the following steps detail installing the drivers for your 4100 Series adapter. DOS Workstation Installation: 1. Edit the CONFIG.SYS file to add the NE2000 driver. DEVICE=(drive letter)\MSLAN\DOSWKSTA\LANMAN\DRIVERS\NE2000.DOS 2. Modify the PROTOCOL.INI file by adding the following lines: [NE2000_NIF] DRIVERNAME = NE2000$ IOBASE = 0X300 INTERRUPT = 3 3. If the NBP protocol was chosen during installation, modify the following lines located under the [NBP] label in the PROTOCOL.INI file: BINDINGS = NE2000_NIF 4. Copy the file NE2000.DOS to the drivers directory as referenced above. OS/2 Workstation or Server Installation The installation steps are almost identical those for a DOS workstation, only the driver is named "NE2000.OS2. 1. Edit the CONFIG.SYS file to add the NE2000 driver. DEVICE=(drive letter)\MSLAN\SERVER\LANMAN\DRIVERS\NE2000.OS2 2. Modify the PROTOCOL.INI file by adding the following lines: [NE2000_NIF] DRIVERNAME = NE2000$ IOBASE = 0X300 INTERRUPT = 3 3. If the NBP protocol was chosen during installation, modify the following lines located under the [NBP] label in the PROTOCOL.INI file: BINDINGS = NE2000_NIF or 4. Copy the file NE2000.OS2 to the drivers directory as referenced above. For further information refer to your LAN Manager documentation. [4-3-2] NDIS With LAN Manager 2.0, 2.1 DOS Workstation Installation 1. Run the SETUP.EXE in the \LANMAN.DOS directory and select "View/Modify" in the Action Menu to delete the current LAN adapter and change it to NE2000 your new adapter. 2. After running SETUP.EXE add the following parameters in the DEVICE driver line of the CONFIG.SYS file: DEVICE = (drive letter)\LANMAN.DOS\...\NE2000.DOS [X] [Y] OS/2 Workstation or Server Installation 1. Run the SETUP.EXE in the \LANMAN directory and select "View/Modify" in the Action Menu to delete the current LAN adapter and change it to NE2000 your new adapter. 2. After running SETUP.EXE add the following parameters in the DEVICE driver line of the CONFIG.SYS file: DEVICE = (drive letter)\LANMAN\...\NE2000.OS2 [X] [Y] For further details please refer to your LAN Manager documentation. [4-3-3] NDIS With Windows for Workgroups NDIS drivers are also be used with Windows for Workgroups. The following steps detail the installation of NDIS with Windows for Workgroups. If Windows for Workgroups has not been previously installed: 1. Follow the installation instructions for Windows for Workgroups. 2. When prompted for the type of network adapter, choose NE2000. 3. Complete the installation according to the directions provided. If Windows for Workgroups has previously been installed: 1. Enter Windows. 2. Double click on the group "Main". 3. Double click on the item "Control Panel". 4. Double click on the item "Network". 5. Double click on the item "Adapter". 6. Choose NE2000 when prompted for the type of LAN adapter installed. 7. Complete the installation according to the directions provided. For further information please refer to your Windows for Workgroups documentation. [4-4] Installing Drivers For Banyan VINES [1] Banyan VINES Workstation Drivers [2] Banyan VINES Server Drivers [4-4-1] Banyan VINES Workstation Drivers DOS and OS/2 Workstation Installation 1. Run the PCCONFIG.EXE in the directory where VINES workstation is installed. 2. Select " 1 - Network Card Settings ", and then select "Novell NE1000/NE2000" to set the "I/O address" and "Interrupt Level" to match what you configured for 4100 Series. 3. Select " 2 - Login Environment Settings", and then select "Novell NE1000/NE2000". [4-4-2] Banyan VINES Server Drivers Banyan VINES Server Installation 1. Boot up Banyan VINES server and then select "4-EXIT" under "SERVICE MONITOR" to go into "OPERATOR MENU". 2. Select "10. System Maintenance" under "OPERATOR MENU". 3. Select "6. Configure/Diagnose Server" under "SYSTEM MAINTENANCE". 4. Select "1. Add Cards/Change Card Configuration" under "VINES Server Configuration". 5. Select "ADD a card" and then select "Novell NE1000/NE2000". 6. Select "CHANGE card settings" to make "CARD INT" and "I/O ADDR" to match those settings of 4100 Series done by "SOFTSET.EXE" . 7. Select "SAVE configuration and exit" to build device driver for 4100 Series. 8. Shut down and reboot the system to make the installed driver take effect. [5] Troubleshooting [1] Basic Troubleshooting [2] Troubleshooting Tips [3] Diskless Boot (Remote Boot or RIPL) Problems [5-1] Basic Troubleshooting If the 4100 Series Ethernet Adapter does not function properly, please check the following before calling for Technical Support: 1. Check the adapter. a. Is there an IRQ conflict? Is another board also set for the same IRQ that the 4100 Series is set for? b. Is there an I/O Port address conflict? Is another board also set for the same I/O Port address that the 4100 Series is set for? c. Did you disable the Boot ROM? If you do not have a Boot PROM installed be sure that the ROM is disabled. d. Is there a memory conflict? Some PC/XT/AT systems have video shadowing features and ESDI disk controller cards or EMS drivers which may conflict with the card's default memory setting. e. Did you choose the correct driver for the operational mode of the card? Did you configure the card for NE2000 compatible mode and then choose the WD drivers? 2. Check the software. a. Is the workstation network driver configured and generated properly? For the NetWare IPX driver, issue the command: IPX I The response from the IPX.COM will indicate the driver, software version, and the hardware configuration. b. Does the driver's configuration match that of the hardware? Are the IRQ, and I/O Port base address identical to that of the hardware. 3. Check the network cable. a. Are the cables within specification? - Thin Ethernet should be RG-58, 50 Ohm impedance coaxial cable. - UTP should be a two-pair wire cable, minimum 24 gauge, with a minimum of two twists per foot. b. Are the RJ-45 connectors wired correctly? - The color of the wire connected to pin one of both ends of the cable should be the same. The Ethernet twisted-pair workstation drop cable is a "straight through" cable. c. Is the cable good? - The cable connections may be suspect, in which they should be tested with a multimeter for continuity. d. Are all ports properly terminated? - With Thin Ethernet, a 50-Ohm terminator must be used to close the "T" connector at the end of the cable run. 4. Check the computer. a. There may be other devices or peripherals installed in the computer that conflict with the network adapter. Remove all unnecessary devices, such as tape drives, modems, FAX cards, etc. and see if the problem still persists. If the problem does not, reinstall the previously removed devices, one at a time, to determine where the conflict exists. 5. Run the Adapter Diagnostics. a. After completing the above basic troubleshooting steps and the adapter still fails to connect to the network, run the DIAGNOSTICS option of the SOFTSET.EXE program to determine if the card is functioning properly in the computer. 6. Technical Support. a. If, after completing the above steps, your 4100 Series Ethernet Adapter still fails, contact Technical Support at (408) 428-9108. [5-2] Troubleshooting Tips > Symptom: Workstation hangs after IPX.COM or IPXODI displays the hardware configuration information. Check: Check the 4100 Series adapter settings to make sure that they are identical to those of the workstation shell. > Symptom: When the system is powered on the screen is blank and it will not boot. Check: Check to see that there are no conflicted IRQ, or I/O Port address settings. > Symptom: After NETX is executed, the error message "File Server Not Found" is displayed at the workstation. Check: Be sure that the Thin Ethernet coax is properly terminated with 50 Ohm terminators. Check the cable for other breaks or opens. Will another workstation that is known to connect to the server still connect to the server when moved to this location and connected to the network at this location. Make sure that the settings for IRQ, I/O Port addresses and frame type of the software agree with the settings of the hardware. [5-3] Diskless Boot (Remote Boot or RIPL) Problems > Symptom: "Error Opening Boot File" is displayed when attempting to boot from a server. Check: Refer to the workstation remote boot instructions in your NetWare Installation Manual. > Symptom: "File Server Could Not Be Found" is displayed and the workstation hangs. Check: Make sure that the Boot PROM address, the IRQ, and I/O Port addresses and frame type are set properly. > Symptom: The workstation hangs when booting from the network. Check: Make sure that you ran the NetWare utility RPLFIX against the workstation boot image file if it was generated with DOS 5 or DOS 6. Appendix A A-1 Ethernet Cabling A-1-1 Thin Ethernet A-1-2 Thick Ethernet A-1-3 UTP Ethernet A-2 Product Specifications [A-1-1] Thin Ethernet A Thin Ethernet network has the following characteristics and limitations: . Maximum cable segment length (between repeaters) is 185 meters. . Total cable length (with repeaters) is 925 meters. . The maximum number of stations (nodes) supported is 256. . The maximum number of stations supported per segment is 30. . Cable used is RG58 A/U coax. . Connects to Thick Ethernet or UTP segments through a repeater or bridge. Thin Ethernet network connections are made from the adapter's coaxial port with a BNC "T"-type coaxial cable connector and the RG58 A/U coaxial cable in a daisy chain manner. Thin Ethernet Cabling * Uses a bus topology * The maximum cable length between repeaters (or terminators) is 185 meters. * The minimum cable length between computers is 0.5 meters. * The default 185 meter segment length complies with the IEEE 802.3 10Base2 standard. * A maximum of five 185 meter segments may be connected together, using commercially available signal repeaters, for a total maximum cable length of 925 meters. * A BNC "T" connector is needed at each computer. * A 50 Ohm cable terminator must be installed at each end of the cable. * One of the two terminators should be the grounded type and connected to ground. [A-1-2] Thick Ethernet A Thick Ethernet network has the following characteristics and limitations: . Maximum cable segment length (between repeaters) is 500 meters. . Total cable length (with repeaters) is 2500 meters. . The maximum number of stations (nodes) supported is 1,024. . The maximum number of stations (nodes) supported per segment is 100. . Cable used is heavily insulated (thick) coax. . Connects to Thin Ethernet or UTP segments through a repeater or bridge. Thick Ethernet Cabling * A Thick Ethernet network is composed of a main cable segment, or "backbone", with additional segments, or "ribs" radiating from the main cable segment or backbone. Workstations are generally attached to the rib segments and repeaters and/or bridges are generally attached to the backbone. * Thick Ethernet network connections are made through commercially available AUI drop cables which are connected to transceivers which are tapped into the thick coax. * The AUI drop cable can be up to 50 meters long. One end of the drop cable is attached to the AUI connector on the Ethernet adapter and the other end is attached to the Ethernet segment through a medium attachment unit (MAU) transceiver/cable connector. MAU connectors may be installed on the thick coax cable every 2.5 meters and the cable is marked at these intervals. A 50 Ohm cable terminator must be installed at each end of every cable segment. * Signal repeaters are used to connect 500-meter segments for larger networks. Repeaters amplify and retime the network signals and are available with single or multiple output connections. Repeater links that use fiber optic cables can be used to extend the total network length to 2500 meters. [A-1-3] UTP Ethernet An Unshielded Twisted Pair Ethernet network has the following characteristics and limitations: . Maximum cable segment length from the adapter to a 10BaseT hub is 100 meters. . Utilizes standard unshielded 22, 24, or 26 AWG twisted-pair wire. . Uses standard RJ-45 connectors. . Sustains 10 Mbps transmission rate and is compatible with the coax cable based Ethernet systems. . Connects to standard Thick or Thin Ethernet segments through a repeater, bridge or 10BaseT hub. . Uses a star topology. Each network station connects directly to a 10BaseT hub. . The maximum distance between two hubs is 100 meters. The maximum number of cable segments between any two stations (going through hubs only) on the network is five. [A-2] Product Specifications The 4100 Series Ethernet Adapters are 16-bit boards that are designed to provide connectivity to a Ethernet network with Thin/UTP/Thick Ethernet cable. - The [AUI] (15-pin "D" connector) uses thick Ethernet cable with an external transceiver. - The [BNC] connector uses thin Ethernet cable with an internal, built-in transceiver. - The [RJ-45] connector uses unshielded twisted-pair Ethernet cable with an internal, built-in 10BaseT transceiver. <> [AUI] connector pin-outs: (DB-15 connector to Thick Net Adapter) Pin Description 1 Control In Circuit Shield 2 Control In Circuit A 3 Data Out Circuit A 4 Data In Circuit Shield 5 Data In Circuit A 6 Voltage Common 7 Control Out Circuit A 8 Control Out Circuit Shield 9 Control In Circuit B 10 Data Out Circuit B 11 Data Out Circuit Shield 12 Data In Circuit B 13 Voltage Plus 14 Voltage Shield 15 Control Out Circuit B Shell Protective Ground <> [RJ-45] pin-outs: (Twisted Pair Connector) Pin Description 1 Data Out + 2 Data Out - 3 Data In + 4 NC 5 NC 6 Data In - 7 NC 8 NC General Specifications * Hardware compatibility: IBM PC/XT/AT, PS/2 (with AT bus) and compatibles * Software compatibility: Novell NetWare, Microsoft LAN Manager, Microsoft Windows for Workgroups, Microsoft Windows NT, Banyan Vines, FTP PC/TCP, Artisoft LANtastic/AI * Standards supported: Thick Ethernet IEEE 802.3 10Base5, or Thin Ethernet IEEE 802.3 10Base2, or UTP Ethernet IEEE 802.3 10BaseT and 10 Mbps baseband * Packet buffer size: 16K bytes * Packet buffer access: I/O mapping * Interrupt level: IRQ 2/9, 3, 4, 5, 10, 11, 12, 15 * I/O base address: 240, 280, 2C0, 300, 320, 340, 360 hex * Boot ROM size 16K bytes * Boot ROM address: C0000 to DC000 hex in 16K byte segments * REV C.0.