Packet Driver
Make Sure you have this Driver or Later:
EXP16.COM V10.4
PDIPX.COM V1.02EC
FTP Software developed the spec for Packet Drivers just like Novell
developed the spec for ODI.
Earlier versions of this driver did not work reliably on on PC/XT style
computers.
EXP16.COM:
This is an auto sense-packet driver. That means it will scan I/O
addresses until it finds the EtherExpress 16 and download the IRQ
from the EEPROM. The software interrupt will still need to be in the
command line when invoking the packet driver.
usage: EXP16 [-n] [-d] [-w] w_int> {io_addr}
-n | For use with the BYU IPX stack |
-d | Delay intialization for boot roms |
-w | For use with windows* (this insures that the driver does not make a
call to the wrong V86 box in 386-e Windows) |
<sw_int> Software interrupt 60-80 hex, example 0x7c
{io_addr} I/O address (optional)
Example: EXP16 0x7C
Where EXP16: is name of the packet driver
0x7C: is the software interrupt 7C
NOTE: The I/O address is not needed because this packet driver scans
for the I/O address!!! If the I/O address is included and is
not the same as the I/O address set in SOFTSET, errors will
occur.
NOTE: If you need to use other software interrupts with the PDIPX,
run dconfig or use the override option PDIPX -o#.
PDIPX:
This Driver is an IPX interface that talks to the Packet Driver. Use
this driver if you want to load the Packet Driver at boot time and still
use Novell services.
NOTE: We recommend you use the PDIPX included in this archive with
the EtherExpress 16 packet driver and not the BYU PDIPX.
Intel has made this driver freely copyable by all parties for all
purposes. Intel does not warrant the fitness of PDIPX for any
particular task. Intel will not be liable for any damage caused by the
use or misuse of PDIPX. Intel will not support PDIPX in the event that
it does not function.
Configuration Notes:
PDIPX is a econfigurable driver.
In 802.3 (default) mode it requests Class 11 Type FFFF packets.
In econfig mode it requests Class 1 Type ???? (defined by the ECONFIG
program) packets.
Clarkson Drivers starting at version 9 will accept requests for both
class 1 and 11 packets. (1 = DIX ethernet, type at byte 12. 11 = 802.3
ethernet, type at byte 14 [Ssap Dsap])
If you are using the Clarkson Drivers you must have version 9 or above
to use 802.3 mode (do not use the -n option).
If you are using econfig mode and your network is using 802.3 you must
use the -n option on the Clarkson Drivers.