Packet Driver installation with NE2000 Compatible NDIS driver
-------------------------------------------------------------
for
NIC-2002/UK series LAN Adapter
1. Installation Introductions for the Packet Driver
---------------------------------------------------
a. Copy NWPD.COM from the \PKTDRV subdir on the driver disk to the
subdirectory where you want to load the driver.
NWPD syntax:
To load the packet driver use the following syntax:
NWPD [-cTYPE] [-d] [-n] [-w] [-u] [-h] <PD_INT_NO> [IRQ] [IO_BASE]
where:
[-cTYPE] The Packet Driver will detect card type automatically.
Options are: NE1000, NE2000, NE2.
[-d] The "-d" option does not start the LAN card until this driver
is called by the higher layer programs first.
[-n] Your NOVELL server uses NOVELL ISO-like packets. Your NOVELL
workstation uses NOVELL 8137 packets. You can use this option
to convert NOVELL 8137 packets into NOVELL ISO-like packets.
In your workstation, whatever the packets are, they can com-
mmunicate with each other.
[-w] Using this option will allow the packet driver to run under
Windows.
[-u] Using this option will unload the Packet Driver.
[-h] Using this option can display the on-line help.
<PD_INT_NO> This specifies the software interrupt (IRQ) where you will
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 the NIC-2002.
[IO_BASE] This specifies the Base I/O address of the NIC-2002.
Example:
The following command line loads the NE1000 & NE2000 series Packet Driver
at software interrupt 60h, at I/O address 300, at hardware interrupt 3:
NWPD 0x60 3 0x300
Note: The default I/O address is 300.
Note: The default hardware interrupt is 3
Note: You must place '0x' prior to I/O address and interrupt parameters.
The following command line loads the NE1000 & NE2000 series Packet Driver
at software interrupt 63h, at I/O address 320, at hardware interrupt 5,
running under windows:
NWPD 0x63 5 0x320 -w
After the Packet Driver is loaded, you can run the PC/TCP kernel ETHDRV.EXE.
The PC is then ready for PC/TCP communications.
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 <ret>
c) At this point, you are ready to run PC/TCP applications
Example: ftp 192.72.24.202
where '192.72.24.202' is the host address.
Note: You must know the host address.
For information regarding the "FTP's PC/TCP Network
Software for DOS" 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 NCSA Telnet V2.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. Load Packet Driver (nwpd 0x60):
a) Refer to "Packet Driver Syntax" section above.
b) To view the hint screen, type
nwpd -h <ret>
c) The following example will load the packet driver
using interrupt vector 60 (hex). The iobase
and irq will be read from the software
configured adapter:
nwpd 0x60 <ret>
4. At this point you are ready to run NCSA applications
Example: ftp 192.72.24.202
where '192.72.24.202' is host address.
Note: You must know the host address.
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
