USING THE SETUP PROGRAM TO INSTALL A PROTOCOL DRIVER

This directory, \LANMAN\DRIVERS\XIF, contains protocol information
files (XIFs).  The XIFs contain information used by the Setup program to
install individual protocol drivers.

Protocol drivers and media access control drivers are considered NDIS
drivers because they conform to the "Microsoft(R)/3Com(R) Network Driver
Interface Specification (NDIS)."  Media access control drivers
manipulate network adapter cards, while protocol drivers handle protocol
concerns.  The Setup program uses network information files (NIFs) to
install media access control drivers.

Besides XIFs, the Setup program also needs PROTOCOL.INI fragments to
successfully install protocol drivers.  PROTOCOL.INI fragments must be
saved in the directory described by the PATH entry of the driver's XIF
file, under the filename PROTOCOL.INI.  A PROTOCOL.INI fragment must
contain all the entries needed to run the device driver except the
[section name] entry, which will be provided by the Setup program (for a
complete description of PROTOCOL.INI entries see the "LAN Manager
Network Device Driver Guide").

XIF files have entries of the following form:

  MODEL =
  PATH =
  DEVICEDRIVER =
  DEVICENAME =
  TYPE =
  CLASS =

where

Entry           Explanation
------------------------------------------------------------------------
MODEL           Is a descriptive remark about the protocol driver.  The
                Setup program displays the first 20 characters of the
                entry in the "Transports" list box during installation
                or modification.

PATH            Is the location of the device driver and its
                PROTOCOL.INI fragment file.  This directory might also
                contain a README.TXT file.  The Setup program will
                append PATH to the end of @LANROOT\DRIVERS, where
                @LANROOT is the LANMAN root directory (usually
                C:\LANMAN).

DEVICEDRIVER    Is the name of the driver with appropriate options as
                listed in the CONFIG.SYS file.  If more than one line
                needs to be added, lines should be entered using the
                following form:

                 DEVICEDRIVER = name1 [options]
                 DEVICEDRIVER = name2 [options]
                 DEVICEDRIVER = name3 [options]

                If the device driver is in the path listed in PATH, use
                its drivername.  If the file is not in the PATH
                directory, use @LANROOT and the relative path of the
                file.  The Setup program expands the string @LANROOT to
                the path of the LANMAN root directory (usually
                C:\LANMAN).

DEVICENAME      Use for MS OS/2 drivers only.  The Setup program ignores
                this field for MS-DOS drivers.  The Setup program places
                this field's contents after the "netx=" keyword in the
                [networks] section of the LANMAN.INI file.

TYPE            Specifies the type of device driver.  The Setup program
                allows the following values:

                  NDIS_XPORT for transport protocol drivers.
                  NDIS       for generic protocol drivers.
		  NDIS_TSR   for terminate-and-stay-resident programs
                             that function as protocol drivers.

                NDIS_XPORT designates transport protocol drivers.

                NDIS tells the installer to bind the protocol driver
                to the associated media access control driver, but not
                list the protocol driver on the "netx=" line in the
                [networks] section of LANMAN.INI.

                NDIS_TSR designates terminate-and-stay-resident programs
                that function as protocol drivers.

CLASS           Defines the "group of like protocol drivers" to which
                the protocol driver belongs.  A media access control
                driver is allowed to have only one protocol driver of a
                particular class attached to it at one time.