INSTANT-LINK 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 Instant-Link includes the following models: -ND5000: SELF-INSTALLING NE2000/NE2000plus compatible, Ethernet adapter with AUI, BNC and RJ-45 connectors. -ND5010: SELF-INSTALLING NE2000/NE2000plus compatible, Ethernet adapter with BNC connector. -ND5020: SELF-INSTALLING NE2000/NE2000plus compatible, Ethernet adapter with RJ45 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. - Banyan Vines is a registered trademarks of Banyan Systems Inc. - Wollongong and Pathwat Access are registered trademark of Wollongong Group 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. NDC is 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 Instant-Link Ethernet Adapter Default Settings 3-2 Installing The Instant-Link 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 Installation Program 4-1-1 NDCGO.BAT Installation Program 4-1-2 NDCONF.EXE Configuration Program 4-2 Installing Novell NetWare 4-2-1 NetWare DOS Client 4-2-2 NetWare 2.15 / 2.2 Server 4-2-3 NetWare 3.10 / 3.11 Server 4-2-4 NetWare 3.12 / 4.0X Server 4-2-5 NetWare Lite 4-3 Installing Microsoft LAN Manager 4-3-1 LAN Manager V2.0 4-3-2 LAN Manager V2.1 (or later) 4-4 Installing Microsoft Windows for Workgroups and Windows 95 4-4-1 Windows For Workgroups 3.10 4-4-2 Windows For Workgroups 3.11 4-4-3 Windows 95 4-5 Installing IBM OS/2 LAN Server 4-6 Installing IBM PC LAN Program 4-6-1 Workstation 4-6-2 Server 4-7 Installing FTP PC/TCP 4-7-1 NDIS Driver for FTP PC/TCP 4-7-2 Packet Driver for FTP PC/TCP 4-8 Installing SUN PC-NFS 4-9 Installing Wollongong Pathway Access 4-10 Installing NCSA TCP/IP 4-11 Installing Banyan VINES 4-11-1 Banyan VINES Client 4-11-2 Banyan VINES Server 4-12 Installing ARTISOFT LANtastic 4-12-1 ARTISOFT LANtastic/AI 4.1 4-12-2 ARTISOFT LANtastic 6.0 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 [1] PREFACE This document describes the features and operation of the Instant-Link 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 Instant-Link 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 Instant-Link adapter to them. The Instant-Link adapters 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 Instant-Link adapters and gives some basic knowledge of Ethernet cabling and PC/AT, ISA bus, system architecture. 3. Hardware Installation...describes how to install an Instant-Link adapter. 4. Software Installation...describes how to install the various network operating system software drivers for the Instant-Link adapters. 5. Troubleshooting...provides basic troubleshooting procedures should you encounter problems with your installation of an Instant-Link adapter. This document covers all of the Instant-Link adapters. They are Novell NE2000/NE2000plus compatible Ethernet adapters. The only difference in the models is the 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 Instant-Link 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. INSTANT-LINK MODEL FEATURES MODEL JUMPER SOFTWARE ----------CONNECTORS------------- NUMBER LESS CONFIGURABLE Thin Net Thick Net Twisted Pair ND5000 XX XX XX XX XX ND5010 XX XX XX ND5020 XX XX XX The Instant-Link 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 Instant-Link 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 ND5000 and ND5020 feature 2 LED Indicators. The red LED will dim and flash when it is transmitting and it will become brighter and flash when a collision occurs. The green LED will flash when it is receiving data. When using the Twisted-Pair cabling, the green LED will become brighter if the connection is good. [2-3] Unpacking The Product The following items are included in the Instant-Link Ethernet adapter package: * An Ethernet adapter * A Quick Installation Guide * A "Setup Program" Diskette * A BNC "T" Connector (ND5000 and ND5010) [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 adapters 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 an 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 Instant-Link 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 Instant-Link Ethernet Adapter Default Settings [2] Installing the Instant-Link 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 Instant-Link Ethernet Adapter Default Settings The Default settings for the Instant-Link Ethernet boards are: IRQ : 3 Base I/O : 300h - 31Fh Remote Boot PROM : Disable Bus Timing : Standard Connector : BNC (ND5000 only) The current configuration of the Instant-Link adapter can be checked with the NDCONF.EXE program contained on the diskette shipped with the adapter. [3-2] Installing the Instant-Link Ethernet Adapter 1. Make sure that the power to the computer is turned off and that the power cord is disconnected. 2. After the Instant-Link 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 NDCONF.EXE program to configure the adapter. When you have completed all the setup operations and saved them, the Instant-Link is ready for operation. If more than one Instant-Link is to be installed into the same computer, you must install and run NDCONF.EXE to automatically separate the I/O base addresses. [3-3] Selecting the IRQ, I/O Port Address, ROM Address and Connector All of the above options are configured by running the NDCONF.EXE program. -- The main menu of the NDCONF.EXE program looks like: : View Configuration : Change Configuration : Load Defaults : Execute Diagnostics : Update NET.CFG : Load (Configuration) from a File : Save (Configuration) to a File Note: (When more than one Instant-Link adapters are installed, only items 1,2 and 4 are shown.) 1. Choosing the second option, "Change 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 accommodates 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 NDCONF.EXE program. 2. Enable the Boot ROM with the NDCONF.EXE program. 3. Power off the computer. 4. Remove the Instant-Link 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 Instant-Link 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 protocol 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: Use the NDCONF.EXE Configuration Program's Self-Installation Feature to resolve the conflict. RPL-ROM_ERR:1002 Card RAM failure; RPL Halted. Cause: The adapter may be defective. 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 NDET07 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 defective. Action: Contact your network card dealer. ERR03: Hardware Fails to Respond. Cause: The I/O base address setting may be in conflicting with another device in the PC. Action: Use the NDCONF.EXE Configuration Program's Self-Installation Feature to resolve the conflict. ERR05: IRQ not Found Cause: The Interrupt level may conflict with another card. Action: Use the NDCONF.EXE Configuration Program's Self-Installation Feature to resolve the conflict. [3-5] Bus Timing Compatibility The default setting for the Instant-Link 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 Instant-Link adapters be changed to accommodate the different bus speed. Some of the machines with which the Instant-Link 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] Installation Program [2] Installing Novell NetWare [3] Installing Microsoft LAN Manager [4] Installing Microsoft Windows for Workgroups [5] Installing IBM OS/2 LAN Server [6] Installing IBM PC LAN Program [7] Installing FTP PC/TCP [8] Installing SUN PC-NFS [9] Installing Wollongong Pathway Access [10] Installing NCSA TCP/IP [11] Installing Banyan VINES [12] Installing ARTISOFT LANtastic [4-1] Installation Program [1] NDCGO.BAT Installation Program [2] NDCONF.EXE Configuration Program [4-1-1] NDCGO.BAT Installation Program The NDCGO.BAT Installation Program provides an easy way to install a Instant-Link Adapter as a NetWare Workstation or Microsoft Windows For Workgroups Workstation. It will automatically set the I/O Address, Interrupt Level (IRQ), and detect the cable connector in use. After this, it will display the card configurations and it will run a series of diagnostic tests. If there are no errors; then, it will access Novell NetWare or install Windows For Workgroups. There are two ways to use this program. The first way is to type the command NDCGO /N and press Enter key. This provides step-by-step instructions for the first-time users. The second way is to type the command NDCGO and Enter. This is a faster way of using the program for experienced users. After NDCGO program is executed, a batch file STARTNW.BAT will be created in the directory you specify. You can type STARTNW command for daily login NetWare server. [4-1-2] NDCONF.EXE Configuration Program The NDCONF.EXE Configuration Program provides an Self-Installtion Function that will search for an available, non-conflicting I/O Address and IRQ Level. It will also detect the cable type. The NDCONF.EXE Configuration Program also allows you to change the settings manually or to restore the default settings. To use the NDCONF.EXE Configuration Program type the command NDCONF and Enter. The configuration parameters and their default settings are list on the Quick Installation Guide. [4-2] Installing Novell NetWare [1] NetWare DOS Client [2] NetWare 2.15 / 2.2 Server [3] NetWare 3.10 / 3.11 Server [4] NetWare 3.12 / 4.0X Server [5] NetWare Lite [4-2-1] NetWare DOS Client The Card comes with a NDCGO program which provide a fast way to install your PC as a NetWare workstation. It is recommended to run the NDCGO program for the NetWare DOS client installation. Otherwise, follow the procedure below to complete the installation. INSTALLATION PROCEDURE 1) Insert the "Instant-Link ND50XX Setup Diskette" into a floppy drive (A: or B:). 2) Make a directory (usually \NETWARE) on your hard disk (usually C: drive) to hold the Novell NetWare utilities. MD C:\NETWARE 3) Copy these files from the "\NETWARE" directory of the "Instant-Link ND51XX Setup Diskette" to the "\NETWARE" directory of your hard disk: LSL.COM NE2000.COM IPXODI.COM NETX.EXE NET.CFG NWSTART.BAT To copy these files, type: COPY A:\NETWARE\LSL.COM C:\NETWARE COPY A:\NETWARE\NE2000.COM C:\NETWARE COPY A:\NETWARE\IPXODI.COM C:\NETWARE COPY A:\NETWARE\NETX.COM C:\NETWARE COPY A:\NETWARE\NET.CFG C:\NETWARE COPY A:\NETWARE\NWSTART.BAT C:\NETWARE (You may use your versions of these programs from Novell instead) 4) Edit "NET.CFG" to specify the values of "INT" and "PORT" match what you specified by NDCONF. 5) Check with your network administrator to make sure that the protocol stack (IPX protocol bound with Ethernet Frame type) defined in the NET.CFG file matches your network. The default protocol stack is: PROTOCOL IPX E0 ETHERNET_802.3 If you are running NetWare 3.12 or 4.0X, you may have to change this line to: PROTOCOL IPX E0 ETHERNET_802.2 6) Make sure the MAM (Media Access Module) is physically connected to the network. From the "\NETWARE" directory of your hard disk, you may use "STARTNW.BAT" or just type: LSL NE2000 IPXODI NETX to connect to NetWare server. If you are running NetWare 3.12 or 4.0X, you should change the last line from "NETX" to "VLM". (Note: You may have to install the VLM files by applying the "NetWare Client for DOS" diskettes.) [4-2-2] NetWare 2.15 / 2.2 IPX Server You must run the NetWare program NETGEN or INSTALL and choose the NE2000/NE2000plus driver. The NET$OS.EXE file is created, which is the executable server driver. Follow these steps to generate the server: INSTALLATION PROCEDURE 1) Run NETGEN or INSTALL. 2) Choose the NE2000/NE2000plus 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-2-3] NetWare 3.10 or 3.11 ODI Server The following steps illustrate the driver installation for NE2000 (I/O Mode): INSTALLATION PROCEDURE 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. The following steps illustrate the driver installation for NE2000plus (Share Memory Mode): INSTALLATION PROCEDURE 1) After booting to DOS, load the SERVER. 2) Type "LOAD PATCHMAN.NLM". 3) Type "LOAD LSLENH.NLM". 4) Type "LOAD MSM31X.NLM". 5) Type "LOAD ETHERTSM.NLM". 6) Type "LOAD NE2000.LAN". 7) Choose the share Memory address, and IRQ chosen during configuration. Make sure that these choices match the hardware settings. 8) After the server driver is loaded, type "BIND IPX TO NE2000". 9) You will be prompted for a network number. This number should be the number of the network that this server will be on. Note: You can get "PATCHMAN.NLM", "LSLENH.NLM", "MSM31X.NLM", "ETHERTSM.NLM", and "NE2000.LAN" from Your Novell dealer or Novell BBS. [4-2-4] NetWare 3.12 or 4.0X ODI Server The following steps illustrate the driver installation for NE2000 (I/O Mode) and NE2000plus (Share Memory Mode): INSTALLATION PROCEDURE 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. [4-2-5] NetWare Lite NetWare Lite uses the same drivers as the DOS ODI workstation. The following steps detail the installation process: INSTALLATION PROCEDURE --- If NetWare Lite is being installed for the first time --- 1) Insert NetWare Lite Program Diskette into a floppy drive (A: or B:). 2) Make this floppy drive(A: or B:) the current driver. Type: "INSTALL" and press key to install NetWare Lite. 3) Select "NOVELL/Eagle NE2000" in "Network Interface Card" menu. 4) Specify the values of "INT" and "PORT" in "NET.CFG Setting for ODI Driver NE2000" menu to match what you specified by NDCONF. 5) Continue to finish the installation. --- 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 3) Specify the values of "INT" and "PORT" in "NET.CFG Setting for ODI Driver NE2000" menu to match what you specified by NDCONF. Refer to your NetWare manuals for the further details of the NET.CFG file. [4-3] Installing Microsoft LAN Manager [1] LAN Manager V2.0 [2] LAN Manager V2.1 (or above) [4-3-1] LAN Manager V2.0 INSTALLATION PROCEDURE 1) Type "Setup" In Lan Manager Directory (usually C:\LANMAN.DOS for DOS requester and C:\LANMAN for OS/2 Requester/Server). Press . 2) Press . 3) Choose "Select Network Drivers" in "Action". Press . 4) Select "Novell NE2000 Ethernet Adapter", then press button, and press , press . Workstation Primary parameters appear, press . 5) Press three times. 6) Choose "Save" in "Action". 7) Press to Exit. 8) Edit PROTOCOL.INI in C:\LANMAN.DOS or C:\LANMAN to set the values of "INTERRUPT" and "IOBASE" in [NE2000_NIF] to match what you specified by NDCONF. 9) Reboot your computer. This completes the installation procedure. [4-3-2] LAN Manager V2.1 (or later) INSTALLATION PROCEDURE 1) Type "LMSETUP" In Lan Manager Directory (usually C:\LANMAN.DOS for DOS requester and C:\LANMAN for OS/2 Requester/Server). Press . Microsoft LAN Manger Setup appear. 2) Choose "Network Drivers..." in " Configuration ". Press Enter. 3) Choose ,press Enter. Network Adapter Driver appears. 4) Select "Novell NE2000 Ethernet Adapter". Push button. 5) Press the SPACEBAR to select the protocol what you want. 6) Push button. Configuration Complete appear. 7) Push button. 8) Press "F3" to exit. 9) Press Enter. 10) Edit PROTOCOL.INI in C:\LANMAN.DOS to set the values of "INTERRUPT" and "IOBASE" in [NE2000_NIF] to match what you specified by NDCONF. 11) Reboot your computer. This completes the installation procedure. [4-4] Installing Windows for Workgroups [1] Windows For Workgroups 3.10 [2] Windows For Workgroups 3.11 The Card comes with a NDCGO program which provide a fast way to install Windows for Workgroups for you. It is recommended to run the NDCGO program for the Windows for Workgroups installation. Otherwise, follow the procedure below to complete the installation. [4-4-1] Windows For Workgroups 3.10 INSTALLATION PROCEDURE 1) Select "Control Panel" icon in Main group in Windows environment. 2) Select "Network" icon. 3) Select "Adapters" item in "Option" dialog. 4) Push button. 5) Select "NE2000 Compatible". 6) WFWG may ask you to insert a floppy disk. Insert the specified Driver Disk in the specified drive, then press . You should then see the "NE2000 Compatible" screen. 7) Set the values of "Interrupt (IRQ)" and "Base I/O Port (hex)" to match those you specified by NDCONF. 8) Press . 9) Press . 10) Press twice. 11) Restart computer. [4-4-2] Windows For Workgroups 3.11 INSTALLATION PROCEDURE 1) Select "Network Setup" icon in "Network Program" group in Windows environment. 2) Select "Drivers" item. 3) Select "Add Adapter" item. 4) Select "NE2000 Compatible" from "Add Network Adapter" window and click "OK". 5) Select "Setup" item and set the values of "Interrupt (IRQ)" and "Base I/O Port (hex)" to match those you specified by NDCONF. 6) Select the protocol used by the rest of your network and make sure it is set as the "Default Protocol". 7) Press . 8) Press . 9) WFWG may ask you to insert a few WFWG disks. Insert the specified WFWG disks in the specified drive to copy some new files. 10) Restart computer. [4-4-3] Windows 95 INSTALLATION PROCEDURE 1) Plug the adapter ND50XX into an ISA slot of your PC. 2) Connect the network cable to the adapter. 3) Turn on the power of your PC to bring up Windows 95. 4) On the main Windows screen, click "Start" (on the left bottom corner of the main Windows screen) ==> select "Programs" ==> click "MS-DOS Prompt". 5) Under "MS-DOS Prompt", run "NDCONF" to configure ND50XX and remember the "Interrupt (IRQ#)" and "I/O port address range" settings. 6) On the main Windows screen, click "Start" ==> select "Settings" ==> click "Control Panel". 7) On "Control Panel" screen, select "Network" icon. 8) Select "Add" option ==> highlight "Adapter" ==> click "Add". 9) On "Select Network adapters" screen, highlight "Novell/Anthem" and "NE2000 Compatible" ==> click "OK". 10) Windows 95 will automatically set up necessary network components for networking. 11) Press "OK" to go to "NE2000 Compatible Properties" screen ==> adjust the "Interrupt (IRQ)" and "I/O address range" to match the hardware settings configured in "step 5" ==> Press OK. 12) Follow the instructions on the screen to finish installing the software if necessary. (Insert Windows 95 diskettes or CD ROM as requested ==> press "OK".) 13) You must restart your computer before the new settings will take effect. Press "Yes" to restart your computer. [4-5] Installing IBM OS/2 LAN Server Following is the installation procedure for the DOS Requester of IBM OS/2 LAN Server. INSTALLATION PROCEDURE 1) At the DOS prompt, insert the IBM LAN Support Program (LSP) Version 1.30 (or later) diskette. 2) Type: DXMAID 3) Press the Enter key three times. The Environment Information screen appears. 4) Specify the following values for the fields on this screen: Configuration for this computer? Yes Use existing configuration information? No Do you have adapter option diskettes? Yes Are you configuring for two adapters? No Source for LSP A:\ Target for new configuration C:\lsp 5) Press Enter to store your choices. The program prompts you to install the option diskette. 6) Insert the NDC Setup diskette in your source drive and specify the path: A:\NDIS. 7) Press Enter. The necessary files are copied from the NDC Setup diskette to your target directory on your computer's hard disk. 8) Press Enter three times. 9) Insert the LSP diskette and press Enter. The Current Configuration screen appears with the NE2000 Ethernet adapter and protocols already selected ("IBM IEEE 802.2" and "IBM OS/2 NETBIOS"). 10) Press F4. LSP is installed. 11) Use any text editor to edit the CONFIG.SYS file. Specify at least 20 files in the FILES= line; for example: files=20 Edit PROTOCOL.INI in C:\LSP to set the values of "INTERRUPT" and "IOBASE" in [NE2000_NIF] to match what you specified by NDCONF. Once you save your CONFIG.SYS and PROTOCOL.INI files, reset your computer. 12) Insert the DOS LAN Requester Install Diskette. 13) Type: INSTALL 14) Press Enter three times. The program prompts you for the pathname of the DOS LAN Requester directory. 15) Specify the pathname for the DOS LAN Requester directory (C:\DOSLAN is the default). Press Enter. The program asks which services you require. 16) Highlight either the "Send messages" or "Send, View, Edit, and Log messages" option. (Normally, you select the second option.) 17) Press Enter to confirm your choice. 18) Specify the workstation's ID and the domain ID. The domain ID must be the domain server ID and must be the same for all workstations on the network. 19) Follow the screen prompts to complete the installation. [4-6] Installing IBM PC LAN Program [1] Workstation [2] Server [4-6-1] Workstation Following is the Installation Procedure for the workstation of IBM PC LAN Program. INSTALLATION PROCEDURE 1) At the DOS prompt, insert the IBM LAN Support Program (LSP) Version 1.30 (or later) diskette. 2) Type: DXMAID 3) Press the Enter key three times. The Environment Information screen appears. 4) Specify the following values for the fields on this screen: Configuration for this computer? Yes Use existing configuration information? No Do you have adapter option diskettes? Yes Are you configuring for two adapters? No Source for LSP A:\ Target for new configuration C:\lsp 5) Press Enter to store your choices. The program prompts you to install the option diskette. 6) Insert the NDC Setup Diskette in your source drive and specify the path: A:\NDIS. 7) Press Enter. The necessary files are copied from the "Instant-Link ND51XX Setup Diskette" to your target directory on your computer's hard disk. 8) Press Enter three times. 9) Insert the LSP diskette and press Enter. The Current Configuration screen appears with the NE2000 Ethernet adapter and protocols already selected. 10) Press F4. LSP is installed. 11) Use any text editor to edit the CONFIG.SYS file. Specify at least 20 files in the FILES= line; for example: files=20 Edit PROTOCOL.INI in C:\LSP to set the values of "INTERRUPT" and "IOBASE" in [NE2000_NIF] to match what you specified by NDCONF. Once you save your CONFIG.SYS and PROTOCOL.INI files, reset your computer. 12) Insert the PC LAN Program Install Diskette in your computer's diskette drive. 13) Type: INSTALL 14) Press Enter. 15) Press Enter three more times. 16) Select the level of function for this workstation, either "Basic Services" or "Extended Services". Most of the time, select the second option. 17) Specify "Workstation". 18) Specify either "Send messages" or "Send, receive, and log messages" options. Most of the time, select the second option. 19) Specify the target path for the PC LAN files. The default pathname is C:\DOS. 20) Specify the machine's ID and the domain ID. The domain ID must be the domain server ID and must be the same for all workstations on the network. 21) Follow the prompts to complete the installation until you reach the Change System Configuration File screen. Usually, you should accept the default for the system configuration file. The Change System Batch File screen appears. Usually you should accept the default. [4-6-2] Server Following is the Installation Procedure for the server of IBM PC LAN Program. INSTALLATION PROCEDURE 1) At the DOS prompt, insert the IBM LAN Support Program (LSP) Version 1.30 (or later) diskette. 2) Type: DXMAID 3) Press the Enter key three times. The Environment Information screen appears. 4) Specify the following values for the fields on this screen: Configuration for this computer? Yes Use existing configuration information? No Do you have adapter option diskettes? Yes Are you configuring for two adapters? No Source for LSP A:\ Target for new configuration C:\lsp 5) Press Enter to store your choices. The program prompts you to install the option diskette. 6) Insert the NDC Setup Diskette in your source drive and specify the path: A:\NDIS. 7) Press Enter. The necessary files are copied from the "Instant-Link ND51XX Setup Diskette" to your target directory on your computer's hard disk. 8) Press Enter three times. 9) Insert the LSP diskette and press Enter. The Current Configuration screen appears with the NE2000 Ethernet adapter and protocols already selected. 10) Press F4. LSP is installed. 11) Use any text editor to edit the CONFIG.SYS file. Specify at least 20 files in the FILES= line; for example: files=20 Edit PROTOCOL.INI in C:\LSP to set the values of "INTERRUPT" and "IOBASE" in [NE2000_NIF] to match what you specified by NDCONF. Once you save your CONFIG.SYS and PROTOCOL.INI files, reset your computer. 12) Insert the PC LAN Program Install Diskette in your computer's diskette drive. 13) Type: INSTALL 14) Press Enter. 15) Press Enter three more times. 16) Select the level of function for this workstation, either "Basic Services" or "Extended Services". Most of the time, select the second option. 17) Specify "Workstation". 18) Specify either "Send messages" or "Send, receive, and log messages" options. Most of the time, select the second option. 19) Specify the target path for the PC LAN files. The default pathname is C:\DOS. 20) Specify the machine's ID and the domain ID. The domain ID must be the domain server ID and must be the same for all workstations on the network. 21) Follow the prompts to complete the installation until you reach the Change System Configuration File screen. Usually, you should accept the default for the system configuration file. The Change System Batch File screen appears. Usually you should accept the default. [4-7] Installing FTP PC/TCP [1] NDIS Driver for FTP PC/TCP [2] Packet Driver for FTP PC/TCP [4-7-1] NDIS Driver for FTP PC/TCP INSTALLATION PROCEDURE 1) Insert NDC Setup diskette to drive A: and copy NE2000 NDIS driver to the destination subdirectory of your PC (the recommended Destination Subdirectory is C:\PCTCP). A:\> Copy A:\NDIS\NE2000.DOS C:\PCTCP 2) Refer to Chapter 5 of the PC/TCP Installation and Configuration Guide, entitled "Using an NDIS Driver with the Generic Kernel". 3) Copy the netbind files from the \NDIS subdirectory on FTP Disk A, labeled "Unsupported Network Software". 4) Using any text editor, add the following lines to your workstation's CONFIG.SYS file: DEVICE=C:\PCTCP\PROTMAN.SYS /I:C:\PCTCP DEVICE=C:\PCTCP\NE2000.DOS DEVICE=C:\PCTCP\DIS_PKT.GRP Adjust the drive and path specifications to match your installation. 5) Use any text editor to make the PROTOCOL.FTP file in the \PCTCP subdirectory on your PC's hard drive to look as follows: [Protocol Manager]: Drivername = protman$ [PKTDRV] Drivername = pktdrv$ Bindings = NE2000_NIF Intvec = 0x60 Chainvec = 0x65 [NE2000_NIF] DriverName = MS2000$ INTERRUPT = 3 IOBASE = 0x300 where the values for "INTERRUPT" and "IOBASE" must match what you specified by NDCONF. 6) Rename the PROTOCOL.FTP file to PROTOCOL.INI. Refer to your DOS manual if you need assistance. 7) Proceed with the rest of the instructions in the PC/TCP Installation and Configuration Guide. [4-7-2] Installing Packet Driver for FTP PC/TCP INSTALLATION PROCEDURE 1) Insert PC/TCP Netware Software for DOS "Disk 1" into a drive (A:\or B:\) 2) Make this disk drive (A:\ or B:\) the current drive. Type : "INSTALL" nd press the key. 3) When you are installing the PC/TCP generic kernel, the Operating Environment menu lists 12 environments. Please select a IEEE 802.3 packet driver, answer "Y" in the "Pkt Drv" field. When you have selected the type of driver appropriate to network configuration , press F10 and continue to finish the installation. 4) Edit the AUTOEXEC.FTP. - Replace: echo Run packet driver here. with: NE2000PK 0x60 3 0x300 ETHDRV where the NE2000 packet driver (NE2000PK.COM) will use software interrupt vector 0x60 for NE2000 compatible adapter with IRQ=3, IO_BASE=0x300. Note: NE2000 Packet Driver Basic Syntax: NE2000PK [IRQ] [IO_BASE] where: This specifies the software interrupt (IRQ) where you'll load the packet driver. It must be in the range 0x60 to 0x80. The PC/TCP kernel, by default, is loaded at interrupt 0x61 (so don't load the packet driver there!) [IRQ] This specifies the hardware interrupt (IRQ) of your card. [IO_BASE] This specifies the I/O address of your card. 5) Copy ETHDRV.EXE file from "PC/TCP Network Software for DOS disk 2" to your PC/TCP directory (usually C:\PCTCP). 6) Insert NDC Setup diskette to drive A: and copy NE2000 Packet driver to the destination subdirectory of your PC (the recommended Destination Subdirectory is C:\PCTCP). A:\> Copy A:\PACKET\NE2000PK.COM C:\PCTCP (Note: You may also replace NE2000PK.COM with the NE2000 packet driver "NE2000.COM" from "PC/TCP Netware Software for DOS, Unsupported Network Software disk B:".) 7) TO preserve your current AUTOEXEC.BAT file, rename it to AUTOEXEC.BAT. REN C:\AUTOEXEC.BAT C:\AUTOEXEC.OLD Copy AUTOEXEC.FTP to AUTOEXEC.BAT COPY C:\AUTOEXEC.FTP C:\AUTOEXEC.BAT This complete the installation of FTP PC/TCP. For further information see the FTP PC/TCP manuals. [4-8] Installing SUN PC-NFS INSTALLATION PROCEDURE 1) Insert NDC Setup diskette to drive A: and copy NE2000 NDIS driver to the destination subdirectory of your PC (the recommended Destination Subdirectory is C:\LANMAN). A:\> Copy A:\NDIS\NE2000.DOS C:\LANMAN 2) Insert the "Installation and Connections" diskette into a disk drive (A:\ or B:\). 3) Make this disk drive (A:\ or B:\) the current drive. Type: INSTALL and press the Enter key. 4) Specify the destination drive letter (usually C) and press Enter. 5) Specify "Ethernet" and press Enter. 6) Select the "NDIS" option. 7) Follow the screen prompts to copy the PCNFS files to your destination drive. 8) When prompted, press Enter to configure PCNFS. 9) Specify the PC name, IP address, server name, and server IP address. If you need assistance, refer to the "Configuring PC-NFS" section of your Sun PC-NFS Installation Guide. 10) Follow the screen prompts to complete the installation. 11) When the installation is complete, select Quit to exit the configuration program, defer the boot, and return to DOS. 12) Using any text editor, add the following line above the NFS_NDIS.SYS driver specification in your CONFIG.SYS file: device=c:\lanman\NE2000.DOS Note: The 'c:' shown in the line above indicates the destination drive you selected during the PCNFS installation. 13) Use any text editor to edit the PROTOCOL.NFS file in the \LANMAN subdirectory in your Destination Directory: - Replace: [YOUR-MAC-MODULE] with: [NE2000_NIF] - Replace: drivername = yourmac$ with: drivername = MS2000$ - Replace: option1 = value1 etc. with: IOBASE = 0x300 INTERRUPT = 3 where the values for "INTERRUPT" and "IOBASE" must match what you specified by NDCONF. - Replace: bindings = YOUR-MAC-MODULE with: bindings = NE2000_NIF - Locate the file PROTOCOL.NFS in the \LANMAN subdirectory on your destination drive and rename it to PROTOCOL.INI. Refer to your DOS manual if you need assistance. - Add the following NETBIND statement just before the NFS RUN statement in your AUTOEXEC.BAT file: C:\LANMAN\NETBIND NFSRUN Note: The 'C:' shown in the line above indicates the destination drive you selected during the PCNFS installation. 14) Reboot the computer. 15) Execute NFSCONF.EXE to configure system (i.e. Mount a virtual driver E:). Execute TELNET.EXE to do terminal emulation. Following are the sample configuration files: CONFIG.SYS: SHELL=C:\COMMAND.COM /P /E:526 DOS=HIGH, UMB rem ----pcnfs install DEVICE=C:\DOS\ANSI.SYS DEVICE=C:\NFS\PCNFS.SYS /m DEVICE=C:\NFS\SOCKDRV.SYS DEVICE=C:\LANMAN\PROTMAN.SYS /i:C:\LANMAN DEVICE=C:\LANMAN\NE2000.DOS DEVICE=C:\LANMAN\NFS-NDIS.SYS FILES=50 BUFFERS=50 LASTDRIVE=v STACKS=9,256 PROTOCOL.INI at \LANMAN directory: [PROTOCOL MANAGER] DRIVERNAME = PROTMAN$ [NE2000_NIF] DRIVERNAME = MS2000$ INTERRUPT = 3 IOBASE = 0x300 [NFS-NDIS] DRIVERNAME = NFSLINK1 BINDING = NE2000_NIF AUTOEXEC.BAT: ... SET TZ=PST8 SET PATH=C:\;C:\NFS;C:\LANMAN SET NFSDRIVE=D C:\LANMAN\NETBIND PRT * NFSRUN [4-9] Installing Wollongong Pathway Access INSTALLATION PROCEDURE A. NDIS driver Installation Procedure 1) Insert your copy of Pathway Drivers diskette into drive A. Enter as follow : C:\>A: 2) To copy the software onto the system, enter : A:\>PWINSTAL C: where C: is the disk drive ( you could also use D:, E:, and so on ) that you intend to use for the installation of your Pathway software on a hard drive system. The PWINSTAL program automatically installs the driver software in a new directory named \PATHWAY on the drive you specified. The diskette is finished copying when you receive the following message: "The Pathway Drivers have been copied successfully. Refer to documentation to complete driver installation." 3) Insert NDC Setup diskette to drive A: and copy NDIS driver to the subdirectory where you install the Pathway software : A:\> Copy A:\NDIS\NE2000.DOS C:\PATHWAY 4) Edit the C:\CONFIG.SYS file to contains the following three entries : DEVICE=C:\PATHWAY\PWTCP.SYS DEVICE=C:\PATHWAY\PROTMAN.EXE/I:C:\PATHWAY DEVICE=C:\PATHWAY\NE2000.DOS 5) Use any text editor to generate a PROTOCOL.INI file in C:\PATHWAY which must have the following section [NE2000_NIF] DriverName = MS2000$ INTERRUPT = 3 IOBASE = 0x300 where the values for "INTERRUPT" and "IOBASE" must match what you specified by NDCONF. 6) The startup batch file - AUTOEXEC.BAT should have the following entries in the order shown : path=c:\pathway ndis [-d:#] pwbind where the -d option is used when accessing a specific module number within PROTOCOL.INI. In your PROTOCOL.INI file, a line enclosed by square brackets designates the beginning of a new module. Each module is referred to by a hexadecimal number. The first module is module number one. The second module is module two, and so on. B. Pathway Kernel Installation Procedure 1) Insert your copy of Pathway Kernel diskette into drive A. Enter as follow : C:\>A: 2) To copy the software onto the system, enter : A:\> pwinstal C: where C: is the disk drive ( you could also use D:, E:, and so on ) that you intend to use for the installation of your Pathway software on a hard drive system. The PWINSTAL program automatically installs the driver software in a new directory named \PATHWAY on the drive you specified. Diskette copying is complete when you see the following message : "Pathway Kernel files have been copied successfully. Reboot and refer to the documentation to complete kernel installation." 3) Remove the diskette from drive A: and reboot your PC by pressing , , and at the same time. 4) Change current directory to PATHWAY. 5) Run the CUSTOM program in order to set or change the following settings: * The Internet address * The subnet bits (if your network includes subnetworks) * The gateway address (if you are communicating with hosts outside your local network) 6) Remove the diskette from drive A: and reboot your PC by pressing , , and at the same time. 7) Enter the following command to load the Kernel : C:\PATHWAY> PWTCP 8) Test your PC Using PING program C:\PATHWAY> PING hostname where hostname is the official name, alias, or Internet address of a host on your network that you expect to be able to communicate with. [4-10] Installing NCSA PC/TCP INSTALLATION PROCEDURE 1) Make sure you have the correct version of NCSA Telnet for the PC. You need version 2.3 or later to support the packet driver interface. 2) Install the NCSA software onto your system. Please refer to the NCSA documentation for detailed instructions. 3) Load the NE2000 Packet Driver "NE2000PK.COM" in the \PACKET directory of Instant-Link Setup diskette: NE2000 Packet Driver Basic Syntax: NE2000PK [IRQ] [IO_BASE] where: This specifies the software interrupt (IRQ) where you'll load the packet driver. It must be in the range 0x60 to 0x80. The PC/TCP kernel, by default, is loaded at interrupt 0x61 (so don't load the packet driver there!) [IRQ] This specifies the hardware interrupt (IRQ) of your card. [IO_BASE] This specifies the I/O address of your card. Following is an example to load the NE2000 packet driver using software interrupt vector 0x60 for NE2000 compatible adapter with IRQ=3, IO_BASE=0x300. NE2000PK 0x60 3 0x300 4) At this point you are ready to run NCSA applications (e.g., 'ftp', 'telnet', etc.). For information regarding NCSA's products please contact: National Center for Supercomputing Applications 264 Computing Applications Building 605 E. Springfield Ave. Champaign, Ill. 61820 (217) 244-0638 telbug@ncsa.uiuc.edu [4-11] Installing Banyan VINES [1] Banyan VINES Client [2] Banyan VINES Server [4-11-1] Banyan VINES Client A. Installation Procedure for Banyan VINES Client (DOS/OS2) ----------------------------------------------------------- INSTALLATION PROCEDURE 1) On your hard disk, make a directory called BANYAN (C:\BANYAN) 2) Insert the "VINES (R) LAN S/W (DOS/OS2) INSTALL" diskette into drive A: and copy all files to your BANYAN directory: COPY A:\*.* C:\BANYAN 3) Locate the "VINES(R) LAN S/W (DOS/OS2)" diskette that has a subdirectory named NOVELL. Copy the "NEBAN.EXE" file from this diskette to your BANYAN directory: COPY A:\NOVELL\NEBAN.EXE C:\BANYAN 4) Form the BANYAN directory of your hard disk, run the PCCONFIG program (a VINES utility) by typing: PCCONFIG 5) From the "Configuring a PC for the Network" menu, select: "1-Network Card Settings" From the selection of network cards, choose: "Novell NE1000/NE2000" Select the appropriate values of "I/O Address (300, 320, 340, 360) " and "Interrupt Level (2-5)" to match what you specified by NDCONF. 6) Save your changes by enter the (F10) key. 7) Return to the main menu of PCCONFIG. This time, select: "2-Login Environment Settings" From the next menu, select: "Novell NE1000/NE2000" 8) Save your changes by entering the (F10) key. This completes the installation of BANYAN VINES (DOS/OS2) Client. B. Installation Procedure for Banyan VINES Client (DOS) with NDIS Driver ------------------------------------------------------------------------ INSTALLATION PROCEDURE 1) On your hard disk, make a directory called BANYAN (C:\BANYAN) 2) Insert the "VINES (R) LAN S/W (DOS) INSTALL" diskette into drive A: and copy all files to your BANYAN directory: COPY A:\*.* C:\BANYAN 3) Form the BANYAN directory of your hard disk, run the PCCONFIG program (a VINES utility) by typing: PCCNOFIG 4) From the "Configuring a PC for the Network" menu, select: "1-Network Card Settings" From the selection of network cards, choose: "NDIS Ethernet" Key in specified interrupt number, and "NE2000_NIF" to the "PROTOCOL bindings =". 5) Save your changes by enter the (F10) key. 6) Return to the main menu of PCCONFIG. This time, select: "2-Login Environment Settings" From the next menu, select: "NDIS Ethernet" 7) Save your changes by entering the (F10) key. 8) Modify the CONFIG.SYS and PROTOCOL.INI files, see the example. Sample configuration files: CONFIG.SYS : DEVICE=C:\BANYAN\PROTMAN.DOS /I:C:\BANYAN DEVICE=C:\BANYAN\NE2000.DOS : PROTOCOL.INI [PROTOCOL MANAGER] DRIVERNAME = PROTMAN$ [VINES_XIF] DRIVERNAME = NDISBAN$ BINDINGS = "NE2000_NIF" [NE2000_NIF] DRIVERNAME = MS2000$ IOBASE = 0x300 INTERRUPT = 3 where the values of "IOBASE" and "INTERRUPT" must match what you specified by NDCONF. 9) Copy the NE2000 DOS NDIS driver to your Banyan directory COPY A:\NDIS\NE2000.DOS C:\BANYAN This completes the installation of BANYAN VINES (DOS) Client with NDIS driver. [4-11-2] Banyan VINES Server INSTALLATION PROCEDURE 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 Instant-Link done by "NDCONF.EXE" . 7) Select "SAVE configuration and exit" to build a device driver for Instant-Link. 8) Shut down and reboot the system to make the installed driver take effect. [4-12] Installing ARTISOFT LANtastic [1] ARTISOFT LANtastic/AI 4.1 [2] ARTISOFT LANtastic 6.0 [4-12-1] ARTISOFT LANtastic/AI 4.1 INSTALLATION PROCEDURE 1) Run the LANtastic Installation program. A:install 2) Select "Novell NE2000 16-bit ISA bus or Compatible" for "Network Adapter Installed:" on the installation menu. 3) Follow the instructions guided by the Installation program to finish the installation process. 4) Edit "STARTNET.BAT" (usually in C:\LANTASTI) to make the values of "IRQ" and "IOBASE" in statement "NEX000 IRQ=3 IOBASE=300 16-BIT VERBOSE" match what you specified by NDCONF. This complete the installation of LANtastic/AI 4.1. [4-12-2] ARTISOFT LANtastic 6.0 INSTALLATION PROCEDURE 1) Run the LANtastic Installation program. A:install 2) Select "NEX016 Novell NE2000 16-bit ISA bus or Compatible" from the installation menu. Note: If you select "Support Novell NetWare", you neither have to nor have chance to select driver for your adapter in this step. In such condition, you have to skip step 4 and continue step 5. 3) Follow the instructions guided by the Installation program to finish the installation process. 4) Edit "STARTNET.BAT" (usually in C:\LANTASTI) to make the values of "IRQ" and "IOBASE" in statement "NEX000 IRQ=3 IOBASE=300 16-BIT VERBOSE" match what you specified by NDCONF. This complete the installation of LANtastic 6.0. 5) Copy Novell NE2000 ODI driver "NE2000.COM" to your LANtastic directory (usually C:\LANTASTI). COPY A:\NETWARE\NE2000.COM C:\LANTASTI 6) Edit "STARTNET.BAT" in our LANtastic directory (usually in C:\LANTASTI). - Replace: : LOADHI LSL NRODI : with: : LOADHI LSL NE2000 : 7) Edit "NET.CFG" in your LANtastic directory (usually in C:\LANTASTI). - Replace: : LINK DRIVER NRODI FRAME ETHERNET_802.3 FRAME ETHERNET_802.2 FRAME ETHERNET_II FRAME ETHERNET_SNAP : with: : LINK DRIVER NE2000 INT 3 PORT 300 FRAME ETHERNET_802.3 FRAME ETHERNET_802.2 FRAME ETHERNET_II FRAME ETHERNET_SNAP : where the values of "INT" and "PORT" must match what you specified by NDCONF. This complete the installation of LANtastic 6.0 with "Support Novell NetWare". [5] Troubleshooting [1] Basic Troubleshooting [2] Troubleshooting Tips [3] Diskless Boot (Remote Boot or RIPL) Problems [5-1] Basic Troubleshooting If the Instant-Link 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 Instant-Link 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 Instant-Link 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. When using the Shared Memory Mode and if there has a memory conflict. Some PC/XT/AT system have video shadowing features and ESDI disk controller cards or EMS drivers which may conflict with the card's default memory setting. e. If you are using NE2000, only I/O Mode is allowed. If NE2000plus driver is used, either I/O or Shared Memory Mode can be allowed. 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 with proper termination. - 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 each 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 NDCONF.EXE program to determine if the card is functioning properly in the computer. 6. Technical Support. a. If, after completing the above steps, your Instant-Link 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 Instant-Link 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 IRQ conflicts, 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. Determine if another workstation that is known to connect to the server will 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 Instant-Link 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 or Shared Memory 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