Packet
drivers provide a simple, common programming
interface that allows multiple applications
to share a network interface at the data
link layer. Packet drivers
demultiplex incoming packets among the
applications by using the network media's
standard packet type or service access
point field(s).
The
packet driver provides calls to initiate
access to a specific packet type, to
end access to it, to send a packet, to
get statistics on the network interface
and to get
information about the interface.
Protocol
implementations that use the packet driver
can coexist and can make use
of one another's services, whereas multiple
applications which do not use the driver
do not coexist on one machine properly.
Through use of the packet driver, a user
could run TCP/IP, XNS and a proprietary
protocol implementation such as DECnet,
Banyan's, LifeNet's, Novell's or 3Com's
without the difficulties associated with
pre-empting the network interface.
Applications
which use the packet driver can also
run on new network hardware of
the same class without being modified;
only a new packet driver need be supplied.
Usage
/ Requirements
Server
Requirements:
Client
Requirements:
emBoot
Universal Packet Driver uses the PXE-compliant
boot ROM present on a
client PC. The upper side of the Universal
Packet Driver interfaces with a protocol
driver such as TCP/IP. The lower side
interfaces with the boot ROM and calls
functions in the UNDI driver to perform
the network operations.
It
should work with any brand of NIC that
includes a PXE-compliant boot ROM -
you no longer need to create multiple
image files to accommodate NIC specific
packet drivers.
UNDI_PKT.COM
must be used within a PXE network boot
image. There are no command line options.
Sample
Configuration File for Use within a DOS
Boot Image:
AUTOEXEC.BAT:
UNDI_PKT.COM
rem loads DOSRDP XP client
G2
