Ethernet Adapter
Packet Driver Installation
==========================
The packet driver NWPD.COM can be used for the NE2000 Ethernet Adapter.
To load the packet driver, type NWPD 0X60.
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 adapter type automatically.
You can use this option to run the Packet Driver on
any third party network adapter. Before using this
option, you must ensure that your adapter is
is compatible with NE1000, NE2000, NE2.
[-d] The "-d" option does not start the adapter,
until this driver is first called by the higher
layer programs.
[-n] The Novell server uses NOVELL ISO-like packets, while
the Novell workstation uses NOVELL 8137 packets.
You can use this option to convert NOVELL 8137
packets into NOVELL ISO-like packets. In your
workstation, these packets communicate with each
other regardless of packet type.
[-w] Windows interface
[-u] Unloads the Packet Driver
[-h] Loads 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. Take not to use this software
interrupt.
[IRQ] Specifies the adapter's hardware interrupt (IRQ)
[IO_BASE] This specifies the I/O address
Note
----
1. If you want to use the adapter's default IRQ and IO_BASE values,
you do not have to indicate them in the Packet Driver syntax;
they are automatically detected for you.
If your IRQ and IO_BASE uses other values, you should indicate the
appropriate values when you run the Packet Driver.
2. Sample entries for the [cTYPE] switch include the following:
NE1000, NE2000, NE2.
Examples
========
The following command line loads the Packet Driver for the
NE1000 & NE2000 compatible adapter series at software interrupt
60h, I/O address 300 and hardware interrupt (IRQ) 3.
NWPD 0x60 3 0x300, or
NWPD 0x60, or
NWPD -cne2000 0x60 3 0x300
In the preceding examples, note that:
1. The default I/O address is 300.
2. The default hardware interrupt is 3.
3. The placement of 0x prior to the parameters.
Packet Driver Application: Using adapter on PC/TCP Environment
--------------------------------------------------------------
1. Load your Packet Driver.
2. Load the PC/TCP kernel ETHDRV.EXE. See following
example:
To load the PC/TCP kernel and allocate 8 packet buffers,
type the following:
ETHDRV -p 8 <Enter>
This will increase the number of packet buffers from
5 (default) to 8.
3. You are now ready to run any PC/TCP application, like
FTP's telnet.
Packet Driver Application: Communicating with NCSA Telnet
---------------------------------------------------------
1. Make sure that 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. Refer
to the NCSA documentation for detailed instructions.
3. Load the Packet Driver (NWPD 0x60). Refer to the
corresponding section for details.
4. Get help or view the Packet Driver's syntax
by typing the following command:
NWPD -h <Enter>
5. Run the NCSA application that you need. To
do this, you need to know the host's
IP address. For example, ftp 192.72.24.202.
TRADEMARKS
==========
All trademarks or brand names mentioned are properties
of their respective companies.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.