STANDARD MICROSYSTEMS CORPORATION
Packet Driver
For SMC Ethernet 10/100 EISA LAN Adapters
INSTALLATION GUIDE
This software is licensed by SMC for use by its customers only.
Copyright (c) 1995 Standard Microsystems Corporation.
All rights reserved.
This installation guide describes:
o Basic packet driver use.
o Software interrupts.
o Driver support.
o Running NetWare and another protocol stack at the same time.
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.
DRIVER SUPPORT
The PKT8000 driver supports all 8216 (Ultra), 80xx (Elite), 80xx
(PLUS), and 8416 (EtherEZ) Series ISA and Micro Channel Ethernet
adapters.
The PKT8232 driver supports the 32-bit 82M32 EISA Ethernet adapter.
The PKT8016 driver supports the 8016/PC (PCMCIA) adapter, both on
laptop PCMCIA sockets, and desktop PCMCIA sockets hosted on the ISA,
EISA, or Micro Channel buses.
The PKT9232 driver supports the Fast Ethernet 10/100 EISA adapter.
RUNNING NetWare WITH ANOTHER PROTOCOL STACK
Note: The following examples use the PKT8000 driver; however, they
also apply to the PKT8232 and PKT8016 drivers.
The standard IPX used with NetWare will NOT WORK with the packet
driver. This is because the standard IPX driver tries to control the
adapter at the same time the packet driver tries to control the adapter.
To resolve this problem, run either the BYUIPX or the Intel PDIPX
driver. Both of these IPX drivers have been designed to be used with
packet drivers. The following sections provide examples of using
these drivers.
Connecting to a NetWare 2.2 Server Using the BYU Packet Driver Shell
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.
The use of this driver is deprecated in favor of the PDIPX driver.
PKT8000 -n 0x7e
BYUIPX
NETX
In this command line:
o PKT8000 denotes the packet driver.
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
To connect to a NetWare server using the Intel packet driver shell,
pdipx103, use the following command line:
PKT8000 0x7e
PDIPX
NETX
In this command line:
o PKT8000 denotes the packet driver.
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 Jumper-Configured Adapters
You can use the packet driver with Western Digital jumper-configured
adapters. However, you must include the following adapter information
in a batch file or on a command line:
o Software interrupt setting
o Interrupt (IRQ) setting
o Input/output (I/O) address
o RAM address
If you use 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 use a jumper-configured adapter and the
Intel PDIPX driver, and want to connect to a NetWare 3.11 server,
refer to "Using SMC Adapters with the Intel Packet Driver NetWare
Shell."
Using SMC 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> <IRQ> <0xI/O> <0xRAM Address>
BYUIPX
NETX
In this command line:
o PKT8000 denotes the Packet Driver.
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 <IRQ> is the adapter's interrupt setting.
o <0xI/O> is the I/O base address of the adapter, and is prefaced
by "0x" to indicate a hexadecimal number.
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 10 0x280 0xCC00
BYUIPX
NETX
Using SMC 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> <IRQ> <0xI/O> <0xRAM Address>
PDIPX
NETX
In this command line:
o PKT8000 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 <IRQ> is the adapter's interrupt setting.
o <0xI/O> is the adapter's I/O base address, and is prefaced
by "0x" to indicate a hexadecimal number.
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 10 0x280 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
EliteCard, Elite Series, EZStart, SuperDisk, UltraChip, and UMAC/LMAC
are trademarks of Standard Microsystems Corporation. Other products
and company names are registered trademarks or trademarks of their
respective companies.
