STANDARD MICROSYSTEMS CORPORATION FTP Packet Driver For EtherCard PLUS Family LAN Adapters INSTALLATION GUIDE This software is licensed by SMC for use by its customers only. Copyright (c) 1992 Standard Microsystems Corporation. All rights reserved. General Information ------------------- 1. This packet driver conforms to the "Packet Driver Specification v1.09" developed by FTP Software, Inc. This Packet Driver Specification is supported by several software vendors, whose software packages interface to this driver specification. This document describes the installation of this driver with three of these vendor's software packages (FTP's PC/TCP, Wollongong Group's WIN/TCP, and NCSA's TelNet) all of which have been tested with this driver. 2. The driver will operate with all EtherCard PLUS Family LAN Adapters. 3. The driver supports Class 1 ("bluebook") and/or Class 11 (802.3) Ethernet packets. 4. The driver will operate under two different environments: a) NetWare Co-Exist Mode: If NetWare IPX.COM (driver version v3.07 or later) is present when this driver is installed, this driver will hook into the IPX driver to allow shared usage of the hardware. In this mode, Extended functions as defined in the Packet Driver Specification will not be supported. This is done to prevent the packet driver from disturbing the IPX driver's operation mode. b) Stand-Alone Mode: The driver will install itself as a "Stand-Alone" driver after determining that NetWare IPX.COM is NOT present. In this mode, it will support all (basic, high performance, extended) functions according to the specification. See Note below about one exception. Note: The function "as send pkt ()" was not implemented at this time due to the anticipated change of this function's specification on the next revision (v1.10) of the Packet Driver Specification. FTP Software PC/TCP Installation -------------------------------- 1. Make sure you have the correct version of FTP Software. You need the "generic" Ethernet version of PC/TCP or LANWatch software modules (I-210, PC-210, K-210, LW-110) to run this driver. The OEM versions will not function with this driver. 2. Install the PC/TCP files onto your system. Please refer to the PC/TCP manual, Installation Guide section. 3. Copy the packet driver (8003PKDR.EXE) file onto your system. 4. Configure PC/TCP network parameters: a) Use IPCONFIG.EXE program to customize file IPCUST.SYS. b) Use IFCONFIG.EXE program to customize file IFCUST.SYS. c) Refer to PC/TCP manual, Command Reference section, Chapter 3. 5. Edit your CONFIG.SYS file to include the two configuration files: a) Add the following two statements: DEVICE = pathname\IFCUST.SYS DEVICE = pathname\IPCUST.SYS (where pathname is the correct directory path into the PC/TCP file directory) 6. Re-boot the system to load these configuration files. 7. For NetWare Co-Exist Mode load NetWare IPX Shell driver : a) Load IPX.COM and NET3.COM. Make sure the 8003/8013 driver file used to generate (using SHGEN) the IPX.COM is version 3.07 or later. b) Login to the NetWare File Server. 8. Load Packet Driver (8003PKDR.EXE): a) Refer to "Packet Driver Parameters" section below. b) To view the hint screen, type 8003pkdr /? c) The following example will load the packet driver using interrupt vector 60 (hex). The iobase, RAM segment, and irq will be read from the software configured adapter: 8003PKDR 9a. To run PC/TCP applications, load PC/TCP Kernel ("ETHDRV.EXE"). a) Refer to PC/TCP manual, Command Reference section, Chapter 2.3. b) The following example will load the Kernel and allocate 8 packet buffers. Increasing the # of packet buffers (from the default of 5) prevents dropping packets due to a buffer shortage. ETHDRV -p 8 c) At this point, you are ready to run PC/TCP applications (e.g., 'ftp', 'telnet'). 9b. To run LANWatch (supported only in Stand-Alone mode), load and run the program ("LW.EXE"). a) Refer to the LANWatch manual for details. b) The following example will load LANWatch using no more than 300k bytes of memory. This leaves enough memory for DOS. Command Processor in case you need to us the "escape to DOS Shell" command (i.e., ! command). LW -m 300 10. To Unload Drivers: a) Unload PC/TCP Kernel ("ETHDRV.EXE") using INET.EXE program: INET unload b) Unload packet driver ("8003PKDR.EXE") using /U option: 8003PKDR /U For information regarding the "FTP's PC/TCP Network Software for DOS" or LANWatch packages, please contact: FTP Software, Inc. 26 Princess Street Wakefield, MA 01880 (617) 246-0900 ------------------------------------------------------------------------------- Wollongong Group's WIN/TPC Installation --------------------------------------- 1. Make sure you have the correct version of Wollongong software. The following software from The Wollongong Group supports the Packet Driver: WIN/TCP for DOS, version 4.1.1 and above. WIN/ROUTE for DOS, version 2.1 and above. 2. Install the WIN/TCP files onto your system. Please refer to the WIN/TCP manual, Installation Guide section. 3. Copy the packet driver (8003PKDR.EXE) file (from the release diskette) onto your system. 4. Configure WIN/TCP network parameters: Use CUSTOM.EXE program to customize file WINTCP.SYS. 5. Re-boot the system to load this configuration file. 6. For NetWare Co-Exist Mode load NetWare IPX Shell driver : a) Load IPX.COM and NET3.COM. Make sure the 8003/8013 driver file used to generate (using SHGEN) the IPX.COM is version 3.07 or later. b) Login to the NetWare File Server. 7. Load Packet Driver (8003PKDR.EXE): a) Refer to "Packet Driver Parameters" section below. b) To view the hint screen, type 8003pkdr /? c) The following example will load the packet driver using interrupt vector 60 (hex). The iobase, RAM segment, and irq will be read from the software configured adapter: 8003PKDR 8. Load WIN/TCP Packet Driver Interface (PKTDRV.EXE): The following is an example of how the packet driver interface is loaded: PKTDRV -N:61 -I:3 Make sure of the following: a) The software interrupt number specified by the 8003/8013 packet driver (8003pkdr.exe) MUST be different from that specified by PKTDRV. For the 8003pkdr.exe program, this is specified by the /E 0r /8 argument; in the PKTDRV.EXE, it is specified with the -N: argument. b) The hardware interrupt setting (specified with "-I:number") MUST match the hardware interrupt setting of the interface card (and the packet driver 8003pkdr.exe). 9. At this point, you are ready to run WIN/TCP applications (e.g., 'ftp', 'telnet') and/or access a NetWare file server. For information regarding the "WIN/TCP Network Software for DOS" package, please contact: The Wollongong Group 1129 San Antonio Road Palo Alto, CA 94303-3674 ------------------------------------------------------------------------------- NCSA TelNet Installation ------------------------ 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 documention for detailed instructions. 3. Copy the packet driver (8003pkdr.exe) file onto your system. 4. Edit your config.tel file to include the line: hardware=packet There should be no other hardware= lines in your config.tel file. 5. Re-boot the system to load this configuration file. 6. For NetWare Co-Exist Mode, load NetWare IPX Shell driver : a) Load IPX.COM and NET3.COM. Make sure the 8003/8013 driver file used to generate (using SHGEN) the IPX.COM is version 3.07 or later. b) Login to the NetWare File Server. 7. Load Packet Driver (8003PKDR.EXE): a) Refer to "Packet Driver Parameters" section below. b) To view the hint screen, type 8003pkdr /? c) The following example will load the packet driver using interrupt vector 60 (hex). The iobase, RAM segment, and irq will be read from the software configured adapter: 8003PKDR 8. At this point you are ready to run NCSA applications (e.g., 'ftp', 'telnet', 'lpr', etc.) 9. To unload drivers: a) Unload packet driver (8003pkdr.exe) using /U option: 8003pkdr /U 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 ------------------------------------------------------------------------------- Packet Driver Parameter Specification ------------------------------------- 1. Program defaults: In the absence of user's parameter specification, the following default values will be used for each of the options: /S: (slot #): 0 (none) /R: (rambase): D000 /B: (iobase): 0 (none) /I: (irq): 3 /E: (class 1 int): 60 (hex) /8: (class 11 int): 00 (none) /M: (mx multicast adrs): 8 2. DOS "SET" environment string: You may use DOS "SET" command to specify parameters. This method is useful to set parameters semi-permanently (e.g., in "autoexec.bat" file). The parameters will be in effect until another "SET" command is given. The parameter values may be temporarily overridden by command line parameters. syntax: SET 8003PKDR= [options] 3. Command Line parameters: This method is temporary in that you need to specify them each time you run (load) the packet driver. The values given will override previously set (via either program default or the environment string) values. syntax: 8003PKDR [options] 4. [Options]: [Options] are any combination of options described below separated by one of the valid delimiters. Valid delimiters include a slash (/), a dash (-), and a space. Options and parameter values may be specified in either upper or lower cases. Some options are not applicable to DOS "SET" environment string method. Some options will only be valid for intelligent and/or Micro Channel adapters. Hardware related options are not applicable to "NetWare Co-Exist Mode". Any inapplicable options will be ignored. A colon (':') may be placed to separate the option keyword and the parameter value. a) /? Display the Hint Screen. N/A to "SET" method. b) /U Unload Packet Driver. N/A to "SET" method. c) /S:n Micro Channel Slot #. N/A to ISA bus machines. n = slot # - 1 hex digit - range: 1-8 d) /B:yyy I/O Base Address of adapter. Required only for adapters that are configured by jumpers. If not specified, the driver will search for a software configured adapter. If found, all other adapter parameters will be read from the adapter, ignoring any adapter parameters supplied on the command line. If not found, an error message will be generated. yyy = i/o base address - 3 hex digits - range: 200 - 3e0 e) /R:xxxx Ram Base Address. Required only for adapters that are configured by jumpers. xxxx = ram base address - 4 hex digits - range: C000 - EE00 f) /I:zz IRQ Number. Required only for adapters that are configured by jumpers. zz = irq #' - 1 or 2 DECIMAL digit - choices: {2,3,4,5,7,10,11,15} g) /E:vv Pkt driver Interrupt Vector # (Class 1 - "bluebook") vv = interrupt vector # - 2 hex digits - range: 60 - 80 - to disable: specify 00 h) /8:vv Pkt driver Interrupt Vector # (Class 11 - "802.3/802.2") vv = interrupt vector # - 2 hex digits - range: 60 - 80 - to disable: specify 00 i) /M:kk Max # of Multicast Addresses. kk = max multicast address count - 1 or 2 hex digits - range: 00 - 40 5. Notes: a) If any device in your (AT) computer uses irq 8 or above, you MAY NOT use certain interrupt vectors between 70 and 77. It is best to stay away from these vectors on AT machines since Real Time Clock, Mouse, Math Coprocessor, or Fixed Disk typically use irq's 8 or above. b) You need to specify at least one of the packet driver interrupt vectors (i.e., Class 1 or Class 11). If both vectors are disabled, an error will be generated. c) Until a new version (v2.05) of FTP's PC/TCP is available (10/90), there is a restriction in specifying the packet driver interrupt vectors. You must put the Class 1 vector # below that of Class 11. ------------------------------------------------------------------------------- The following describes the Packet Driver Error Messages: Packet Driver Error Messages ============================ a) *** ERROR: Bad "/E:" or "/8:" parameter value "xx"... *** Option /E: or /8: parameter xx is not valid. The Packet Driver interrupt vector # (range hex 60 - 80) is expected. b) *** ERROR: Bad "/M:" parameter value "xx"... *** Option /M: parameter xx is not valid. The maximum multicast address count (range hex 00 - 40) is expected. c) *** ERROR: Bad Option "xx"... *** The option xx is not a valid option. Type "8003PKDR /?" for a list of valid options. d) *** ERROR: "8003PKDR" Not Loaded; Can't Unload! *** The /U (unload driver) option was specified, but the driver is not loaded. e) *** ERROR: "8003PKDR" already Loaded! *** The driver is already in the system; it cannot be loaded twice. f) *** ERROR: At least one of the pkt driver int vectors must be enabled! *** Option /E:00 was given without specifying the /8: option. At least one of the two class (1 and 11) interrupt vectors are required to install the packet driver. g) *** ERROR: IPX Driver in this system does not support this program! *** The IPX driver running in the system does not support this (8003PKDR.EXE) packet driver. It must be version 3.07 or after. h) *** ERROR: "Novell/AT&T StarLAN" is not compatible with TCP/IP! *** The packet driver is not compatible with the "Novell/AT&T StarLAN" packets. Therefore, it can not hook into such an IPX driver. Hardware Related Error Messages (stand-alone version only) ========================================================== a) *** ERROR: No active MCA card in the system... *** The system is a Micro Channel system, but no 8003 family LAN adapter is present in the system. b) *** ERROR: MCA card - you must specify slot # (/S:n)... *** The system is a Micro Channel system. You must specify the slot # where the adapter for the packet driver is plugged in. c) *** ERROR: No MCA card in slot "x"... *** The system is a Micro Channel system. There is no 8003 family LAN adapter in the specified slot x. d) *** ERROR: Bad "/S:" parameter value "xxx"... *** Option /S: parameter xxx is not valid. The Micro Channel slot number is expected. Type "8003PKDR /?" for the correct format information. e) *** ERROR: Bad "/B:" parameter value "xxx"... *** Option /B: parameter xxx is not valid. The I/O base address is expected. Type "8003PKDR /?" for the correct format information. f) *** ERROR: Bad "/R:" parameter value "xxxx"... *** Option /R: parameter value xxxx is not valid. The ram segment address is expected. Type "8003PKDR /?" for the correct format information. g) *** ERROR: Bad "/I:" parameter value "xx"... *** Option /I: parameter xx is not valid. The IRQ number is expected. Type "8003PKDR /?" for the correct format information. h) *** ERROR: I/O base address must be specified. *** No I/O base was specified, and there is no software configured adapter in the system. You need to specify the I/O base value (use /B: option). i) *** ERROR: No adapter at I/O port "xxx"... *** No adapter is present at I/O address xxx. Specify the correct I/O base address. j) *** ERROR: Adapter in 8-bit slot, invalid irq "xx"... *** The adapter is in an 8-bit slot, and an irq above 7 is specified. You need to specify an irq ranging from 2 to 7. k) *** ERROR: Adapter RAM error - check RAM base. *** The ram segment could not be accessed properly. Check the jumper and re-specify the correct ram segment base address. l) *** ERROR: Adapter RAM must be configured below 1M. The adapter was configured to use memory above its 1 megabyte address limit. Re-configure the adapter to use conventional memory below 1M. EtherCard PLUS, TokenCard, and SuperDisk are trademarks, and SMC and Standard Microsystems are registered trademarks of Standard Microsystems Corporation. Other trademarks mentioned herein belong to their respective companies.