CONFIGURATION PARAMETERS

                      ODI2NDI has no command line parameters but supports three
                      NET.CFG keywords and five PROTOCOL.INI keywords. NET.CFG
                      is the configuration file for the Netware Requestor envi-
                      ronment and PROTOCOL.INI is the configuration file for
                      the NDIS environment.

                          The supported NET.CFG keywords are:

                      o   NODE ADDRESS

                      o   FRAME

                      o   PROTOCOL

                          The supported PROTOCOL.INI keywords are:

                      o   DRIVERNAME

                      o   BINDINGS

                      o   NETADDRESS

                      o   TOKEN-RING

                      o   TOKEN-RING_SNAP


 Perform the following steps to manually install the ODI2NDI
 mapper for OS/2

 1) Create an ODI2NDI directory on your workstation. Copy all the
    files from the ODI2NDI\OS2 directory on the option diskette
    to the ODI2NDI directory on the workstation.

 2) The following updates must be made to config.sys:

       a) Remove the ODI MLID driver's DEVICE= statement from
          from CONFIG.SYS.

       b) Add the ODI2NDI.OS2 DEVICE= statement after the Netware
          Link Support Layer(LSL.SYS) device driver, but before
          the IPX(IPX.SYS) device driver.

                     DEVICE=*:\ODI2NDI\ODI2NDI.OS2

       c) Make sure the PROTMAN.OS2 DEVICE= statement appears
          prior to the LSL.SYS DEVICE= statement.

       d) If you are using token ring and want source routing support,
          add  Netware's ROUTE.SYS device driver after the ODI2NDI.OS2
          device driver but before IPX.SYS.

       e) If not already present, add the appropriate NDIS MAC
          driver for the LAN adapter, for example IBMTRDB.OS2.
          The NDIS MAC driver can be loaded anytime after
          PROTMAN.OS2 is loaded.

 3)  ODI2NDI.OS2 has its own section in PROTOCOL.INI.  It's section
     is like any NDIS protocol stack section, it has the following
     keywords:

           "DRIVERNAME ="  - required parameter, must be set to ODI2NDI$

           "BINDINGS ="    - required parameter, must be set to the
                             bracketed section name of the MAC ODI2NDI
                             will bind to.

           "NETADDRESS="   - required parameter, a 12 digit hex number
                             specifying the LAN adapters universal or
                             locally administered address.

           "TRACE="          optional parameter, 4 digit hex number
                             specifying trace event activation for
                             problem determination.

    In addition to the above keywords, there are two keywords that
    describe which frame header ODI2NDI will build.  The default
    frame type keyword if none is specified is "TOKEN-RING"
    regardless of actual LAN type.  The six frame type keywords
    are:
          TOKEN-RING =
          TOKEN-RING_SNAP =

   To select a particular frame type set it equal to "yes". Defaults to Token-Ring.


    Example:
     [ODI2NDI_nif]

        DriverName = ODI2NDI$
        Bindings = IBMTRDB_NIF
        NETADDRESS = "4000xxxxxxxx"    <---- This is the universal or local adapter address
        TOKEN-RING = "yes"             <---- This is the active frametype
        TOKEN-RING_SNAP = "no"
        TRACE = 0x0                    <---- This is optional keyword for activating
                                             trace events.




 4)  ODI2NDI supports three NET.CFG keywords NET.CFG is the configuration file
     for the Netware Workstation environment.

                The supported NET.CFG keywords are:

            o   NODE ADDRESS       ; must be configured

            o   FRAME              ; defaults to TOKEN-RING

            o   PROTOCOL           ; defaults to IPX


            ODI2NDI reads the NET.CFG file first, and then reads the
            PROTOCOL.INI file. The keywords in the PROTOCOL.INI will
            override the keywords in NET.CFG. The NET.CFG file and
            keywords are optional. The PROTOCOL.INI file is required.
            There must be an ODI2NDI section, a DRIVERNAME and a
            BINDINGS keyword. The instructions that follow will detail
            the necessary configuration information.


            A locally administered address must be configured for the
            ODI2NDI mapper for OS/2. This address can be configured
            through either the NODE ADDRESS keyword in the NET.CFG
            file or through the NETADDRESS keyword of the PROTOCOL.INI
            file. All NDIS Protocol Stacks that bind to the same NDIS
            MAC Driver as the mapper will also need to be configured
            for this same LAA to function properly.


       Example:

    LINK DRIVER macname            ; macname is the bracketed section name ODI2NDI will
                                     bind to.

    NODE ADDRESS 4000xxxxxxxx
    FRAME TOKEN-RING