STANDARD MICROSYSTEMS CORPORATION
Packet Driver
For Ethernet LAN Adapters
INSTALLATION GUIDE
This software is licensed by SMC for use by its customers only.
Copyright (c) 1994-1995 Standard Microsystems Corporation.
All rights reserved.
This installation guide describes:
o Basic packet driver use.
o Software interrupts.
o How to use the packet driver to connect to a NetWare 2.2 server
using the BYU packet driver shell.
o How to use the packet driver to connect to a NetWare server
using the Intel packet driver shell.
o Using the packet driver with SMC/WD adapters.
Note: This driver supports all 8416, 8216 (Ultra), 80xx (Elite),
80xx (PLUS), and 8416 (EtherEZ) Series ISA, EISA, and Micro
Channel Ethernet adapters.
BASIC PACKET DRIVER USE
The following section describes basic packet driver use. Since
different networks have different requirements, you can include the
following switches in your command lines as needed.
-d This switch delays the adapter's initialization until the first
time the packet driver is accessed. Use this switch if your
workstation loads the operating system over the network using a
Boot ROM on the SMC adapter.
-n This switch configures the driver to change 8137-formatted
packets seen by the client into IEEE802.3 packets. Unless you
use the BYU's NetWare packet driver shell, you can omit this
switch. If you want to use 8137 packets, use "econfig" to
configure Intel's PDIPX103 packet driver shell.
-p This switch disables promiscuous mode. A small level of security
can be achieved by disabling promiscuous mode; however,
disabling promiscuous mode should not be mistaken for real
security.
-w This switch is used with Microsoft Windows for nonresident DOS
TCP stacks, such as NCSA Telnet and PC-Gopher. Alternatively,
you can use the Windows public domain utility, winpkt.
-i The SMC packet driver can be used with both Ethernet_II and
IEEE 802.3 frame types. The packet driver specification, however,
only allows a driver to report one class which, by default, is
Ethernet_II. If you use the packet driver with client software
that expects to find an IEEE 802.3 packet driver instead of an
Ethernet_II packet driver, use this switch to configure the
driver to use IEEE 802.3-formatted packets.
SOFTWARE INTERRUPTS
A packet driver provides services for client programs. These programs
access the packet driver by issuing software interrupts.
Any software interrupt between the hexadecimal addresses of 0x60
through 0x80 can be used with the packet driver, with the following
exceptions:
o 0x67 is reserved for the EMS specification.
o 0x70 through 0x77 are reserved for hardware IRQ lines 8 through 15.
After you choose a software interrupt, assign that interrupt to the
packet driver, and install the packet driver. The client programs
will then automatically locate the packet driver by searching for
the packet driver's signature at software interrupts from 0x60
through 0x80.
CONNECTING TO A NetWare 2.2 SERVER USING THE BYU PACKET DRIVER SHELL
If you want to connect to a NetWare 2.2 server that, by default, is
configured to use IEEE 802.3-type packets, use the following command
line examples.
PKT8000 -n 0x7e
BYUIPX
NETX
In this command line:
o PKT8000 denotes the SMC/Western Digital adapter.
o -n configures the driver to change 8137-formatted packets seen by
the client into IEEE802.3 packets.
o Software interrupt setting 0x7e is the hexadecimal address 7E,
which allows packet driver clients to use interrupt 7E to
communicate with the packet driver.
CONNECTING TO A NetWare SERVER USING THE INTEL PACKET DRIVER SHELL
If you want to connect to a NetWare server using the Intel packet
driver shell, pdipx103, use the following command line:
PKT8000 0x7e
PDIPX
NETX
In this line:
o PKT8000 denotes the SMC/Western Digital adapter.
o 0x7e is the hexadecimal address 7E, which allows packet driver
clients to use interrupt 7E to communicate with the packet driver.
USING THE PACKET DRIVER WITH WD JUMPER-CONFIGURED ADAPTERS
You can use the packet driver with Western Digital (WD) adapters. If
you use the packet driver with jumper-configured WD adapters, you
must include the following adapter information in a batch file or on
a command line:
o Software interrupt setting
o Input/output (I/O) address
o Interrupt (IRQ) setting
o RAM address
If you are using a jumper-configured adapter and want to connect to
a NetWare 2.2 server using the BYU packet driver shell, refer to the
next section. If you are using a jumper-configured adapter and the
Intel PDIPX driver and want to connect to a NetWare 3.11 server,
refer to "Using Older Adapters with the Intel Packet Driver NetWare
Shell."
Using SMC/WD Adapters with NetWare 2.2
and the BYU Packet Driver Shell
The following command line can be used to connect SMC and Western
Digital adapters to a NetWare 2.2 server when the server has not
been configured using "econfig" and you are using the BYU packet
driver shell.
PKT8000 -n <0xSoftware Interrupt> <0xI/O> <IRQ> <0xRAM Address>
BYUIPX
NETX
In this command line:
o PKT8000 denotes the SMC/Western Digital adapter.
o -n configures the driver to use 8137-formatted packets. This
switch is necessary to connect to a Novell NetWare 2.2 server.
However, if you are using Ethernet II frame types, you must
omit this switch.
o <0xSoftware Interrupt> is the adapter's software interrupt setting,
and is prefaced by "0x" to indicate a hexadecimal number.
o <0xI/O> is the I/O base address of the adapter, and is prefaced
by "0x" to indicate a hexadecimal number.
o <IRQ> is the adapter's interrupt setting.
o <0xRAM Address> is the RAM base address of the adapter, and is
prefaced by "0x" to indicate a hexadecimal number.
A typical command line might resemble:
PKT8000 -n 0x7e 0x280 10 0xCC00
BYUIPX
NETX
Using SMC/WD Adapters with the Intel Packet Driver NetWare Shell
The following command line can be used to connect SMC and Western
Digital adapters to a NetWare NetWare 3.11, 3.12, 4.0, 4.01, or
4.10 server:
PKT8000 -i <0xSoftware Interrupt> <0xI/O> <IRQ> <0xRAM Address>
PDIPX
NETX
In this line:
In this command line:
o PKT8000 denotes the denotes the SMC/Western Digital adapter.
o -i configures the driver to use IEEE 802.3-formatted packets,
which the PDIPX protocol expects to receive.
o <0xSoftware Interrupt> is the adapter's software interrupt setting,
and is prefaced by "0x" to indicate a hexadecimal number.
o <0xI/O> is the adapter's I/O base address, and is prefaced
by "0x" to indicate a hexadecimal number.
o <IRQ> is the adapter's interrupt setting.
o <0xRAM Address> is the RAM base address of the adapter, and is
prefaced by "0x" to indicate a hexadecimal number.
A typical command line might resemble:
PKT8000 -i 0x7e 0x280 10 0xCC00
PDIPX
NETX
Note: If you are using Ethernet II frame types, you must use
"econfig" to configure the PDIPX driver before loading it.
"econfig" is a step you use to configure a shell. For more
information, refer to your Novell NetWare documentation.
This commercial computer software and documentation is provided with
RESTRICTED RIGHTS. Use, duplication, or disclosure by the
Government is subject to restrictions set forth in subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer Software
clause at DFARS 252.227-7013, or subparagraphs (c) (1) and (2) of the
Commercial Computer Software -- Restricted Rights clause at
FAR 52.227-19, or Alternate III of the Rights in Data -- General
clause at FAR 52.227-14, as applicable. The manufacturer /
subcontractor is Standard Microsystems Corporation, 80 Arkay Drive,
Hauppauge, NY 11788.
SMC and Standard Microsystems are registered trademarks; and EtherEZ,
EtherCard Elite 16 Ultra, EtherCard Elite 16T Ultra, EtherCard Elite
16C Ultra, EliteSeries, EZStart, and SuperDisk are trademarks of
Standard Microsystems Corporation. Other product and company names
are registered trademarks or trademarks of their respective holders.
