32-Bit PCI Bus (fast) Ethernet Adapter Packet Driver Installation Overview ============================================================== The driver PCIPD.COM can be used for the following 32-bits PCI adapters: 32-Bits PCI Ethernet Adapter (ETH_32) 32-Bits PCI fast Ethernet Adapter (ETH_32 100TX) PCIPD syntax: PCIPD [-a] [-b] [-d] [-f] [-h] [-n] [-s] [-t] [-u] [-w] <PD_INT_NO> where: [-a] Automatic media detection during driver initialization. The detection sequence is: TP 10Mbps --> BNC 10Mbps for Ethernet, TP 100Mbps --> TP 10Mbps --> BNC 10Mbps for Fastnet If no physical media is attached to the adapter then BNC 10Mbps is the default media for both Ethernet & Fastnet adapters. [-b] Use Coaxial Cable(10BASE-2) as transmission media. [-d] Do not start LAN card until this driver is called by the higher layer programs first. [-f] Enable FULL_DUPLEX feature of the adapters. It makes no effect unless twisted pair is used. [-h] Display the on-line help. [-n] If your NOVELL server uses NOVELL ISO-like packets and your NOVELL workstation uses NOVELL 8137 packets, use this option to convert NOVELL 8137 packets into NOVELL ISO-like packets. [-s] Set adapter line speed 100Mbps. It is an exclusive option for Fastnet adapters. [-t] Use Twisted Pair(RJ-45 10BASE-T) as transmission media. This is a default setting. [-u] Unload the Packet Driver. [-w] Steve Wallace added a hack to let the packet drivers run under Windows. This is not to be construed with the proper solution, which is to write a TCP/IP package for Windows. Note: This hack is enabled only when you use the '-w' switch. <PD_INT_NO> This specifies the software interrupt (IRQ) where you'll load the packet driver. It must be in the range from 0x60 to 0x80. Note: The default PC/TCP kernel is loaded at interrupt 0x61. (Don't load the packet driver there!) Example: The following command line loads the 32-bit (fast) Ethernet adapters Packet Driver at software interrupt 60h, transmission media is automatically detected: PCIPD -a 0x60 or PCIPD 0x60 Note: (1) The default transmission media is automatically detected. (2) The placement of 0x prior to the parameters. Once the Packet Driver is loaded, run the PC/TCP kernel ETHDRV.EXE to start PC/TCP applications. a. Refer to PC/TCP manual, Command Reference section, Chapter 2.3. b. The following example loads the PC/TCP Kernel and allocate 8 packet buffers. Increasing the packet buffer numbers (from the default of 5) prevents dropping of packets due to buffer shortage. ETHDRV -p 8 <Enter> c. You are ready to run PC/TCP applications (e.g., 'ftp', 'telnet'). For example, ftp 192.72.24.202, 192.72.24.202 is the host address. Regard to host address, you must know its address. For more information on the "FTP's PC/TCP Network Software for DOS" software packages, please contact: FTP Software, Inc. 26 Princess Street Wakefield, MA 01880 (617) 246-0900 How to Communicate with NCSA TelNet. 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 Packet Driver (PCIPD 0x60): a. Refer to "Packet Driver Syntax" section above. b. To view the hint screen, type: PCIPD -h <Enter> c. The following example will load the packet driver using interrupt vector 60 (hex). The I/O_BASE and IRQ will be read from the adapter: PCIPD 0x60 <Enter> 4. You are now ready to run NCSA applications (e.g., 'ftp', 'telnet', etc.) For example, ftp 192.72.24.202, 192.72.24.202 is host address. For information regarding the 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 -- THE END --