Newsgroups: bit.listserv.novell
Date:         Tue, 8 Sep 1992 17:55:00 LCL
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "(RRAWSON)" <RRAWSON@NOVELL.COM>
Subject:      Re: ODINSUP

Chapter 6

Using the NetWare Requester with Extended Services or LAN Services

Overview

This chapter contains instructions for using NetWare Requester
with IBM Extended Services (ES) or LAN Services (LS). If you have
ES or LS, complete all the steps in this chapter.

Install all IBM software and the NetWare Requester before
completing the steps
in this section. See page 2-2.

The following topics are included.

Topic                                                 Page

Editing the CONFIG.SYS File                           6-2
Editing the NET.CFG File                              6-5
Editing the PROTOCOL.INI File                         6-8
How Can the NetWare Requester and ES/LS Coexist?      6-9
Benefits of Coexistence                               6-10


Editing the CONFIG.SYS File

You need to edit the CONFIG.SYS file for two reasons:

-    To prevent NDIS MAC drivers from loading

-    To load the ODINSUP protocol

Prerequisite

o    Are all IBM Communications products you intend to use installed
     on the workstation?

Instructions

     1.   Open the CONFIG.SYS file in a text editor.

     2.   Find the line or lines in the CONFIG.SYS which load the NDIS
          MAC driver or drivers.

See the documentation for OS/2 products to determine the
NDIS driver names.

     3.   Place an REM command or an asterisk in front of each NDIS

MAC driver line.

     4.   After the PROTMAN.OS2 line and the LSL.SYS line, add a line
          to load the ODINSUP.SYS protocol.

When you install the NetWare Requester for OS/2, the
ODSINSUP driver is copied to the directory where all Requester
files are copied (usually C:\NETWARE). Unless you've moved
the ODINSUP file, specify this Requester file location when
typing the ODINSUP line in the CONFIG.SYS file.

For example, if the ODINSUP file is in C:\NETWARE, type the
following line in your CONFIG.SYS file:

DEVICE=C:\NETWARE\ODINSUP.SYS

Figure 6-1 on page 6-4 illustrates a sample CONFIG.SYS file after
these changes have been made.

     5.   Save your changes.

     6.   Exit the CONFIG.SYS file. Do not reboot.

     7.   Go to the next section on page 6-5.

Figure 6-1
CONFIG.SYS file with ES and LS installed



Editing the NET.CFG File

You need to edit the NET.CFG file for three reasons:

-    To enable Ethernet and Token-Ring frame types (required)

ODINSUP only supports Ethernet and Token-Ring compatible ODI drivers.

-    To increase the size of the packet that can be transmitted
     through ODINSUP (required for Token-Ring boards that
     support frame sizes up to 4KB)

-    To bind the ODINSUP protocol to a particular ODI driver or
     drivers (optional)

Prerequisites

o    Are all IBM Communications products you intend to use installed
     on the workstation?

o    Have you modified the CONFIG.SYS file by following the
     instructions in the on page 6-2?

Instructions

     1.   Open the NET.CFG file in a text editor or in the NetWare
          Requester installation program.

     2.   Enable the frame types that ODINSUP requires.

2a.  If you are using Token-Ring network interface boards, type
the following lines in the NET.CFG, replacing driver-name
with the name of your ODI LAN driver:

Link Driver driver-name
    frame token-ring
    frame token-ring_snap

Indent the lines beginning with frame.

2b.  If you are using Ethernet network interface boards, type
the following lines in the NET.CFG, replacing driver-name
with the name of your ODI LAN driver:

Link Driver driver-name
    frame ethernet_802.3
    frame ethernet_ii
    frame ethernet_802.2
    frame ethernet_snap

Ethernet_802.3 is optional. Indent the lines beginning with frame.

     3.   Increase the size of the packet that can be transmitted through
          ODINSUP if necessary. Do this by increasing the buffer size of
the
          Link Support Layer.

3a.  If you are using Token-Ring network interface boards that
support frame sizes up to 4 KB, type the following lines in
the NET.CFG file:

Link Support
    buffers 15 4210

Indent the line beginning with buffers.

3b.  If you are using Ethernet network boards or Token-Ring
boards that support only frame sizes up to 2 KB, the
default size of the Link Support buffers is adequate.

The default size is:

Link Support
    buffers 20 1514

     4.   Bind ODINSUP to one or more ODI drivers by using the
          Protocol option with the name of the ODI driver that is used
          with your network interface board.

For example, if you have one NE2000 network interface board
in your workstation, type:

Protocol ODINSUP
    bind ne2000

If you do not use the Protocol option to bind ODINSUP to an
ODI driver, ODINSUP searches for any Ethernet or Token-Ring
drivers that are loaded. ODINSUP binds to and uses the first
driver that it locates. When ODINSUP has bound to a driver, the
network interface board for that driver is the board used for
transmissions to and from the network.

If you have two or more network interface boards of the same
type in your workstation, ODINSUP binds to only the driver for
the first board unless you specify differently. You can specify
exactly which driver to bind to, or you can bind ODINSUP to
multiple drivers with the same name, by typing an *instance:
number with the Protocol option.

For example, if you had two NE2000 network interface boards
in your workstation, you could bind ODINSUP to each board by
typing a 2 for the second board:

Protocol ODINSUP
    bind ne2000
    bind ne2000 2

ODINSUP can be bound to a maximum of four ODI drivers.

     5.   Save your changes and exit the NET.CFG file. Do not reboot.

     6.   Go to the next section.

Editing the PROTOCOL.INI File

You need to edit the PROTOCOL.INI file for two reasons:

-    To bind the NDIS protocol stack to the ODI drivers (required)

-    To remove NDIS-related information (optional)

Prerequisites

o    Are all IBM Communications products you intend to use installed
     on the workstation?

o    Have you modified the CONFIG.SYS file as described on page 6-2?

o    Have you modified the NET.CFG file as described on page 6-5?

Instructions

     1.   Open the PROTOCOL.INI file.

     2.   Find each place where the file says Bindings= followed by a
          NDIS MAC driver name.

For example, you might see the following lines:

[NETBEUI_nif]
.
.
Bindings=ELNKII_NIF

     3.   Replace each NDIS MAC driver name with the ODI driver name
          that goes with the type of network board.

For example, you might replace ELNKII_NIF with NE2000.

To bind an NDIS protocol to more than one ODI driver, type in
both driver names on the same line, separated by a comma. For
example, to bind the Etherand protocol to both an NE2000
driver and an NE1000 driver, type:

Bindings=ne2000,ne1000

Since driver names in the PROTOCOL.INI file cannot start with
a number, place an X before 3Com drivers and other drivers
that start with a number (for example, X3C503).

To bind an NDIS driver to an instance of an ODI driver other
than the first instance, type the instance number at the end of
the driver name (for example, NE20004). Do not put a space
between the driver name and the instance number.

If you do not know the name of the ODI driver you are using, reboot your
machine and read the start-up messages carefully. The driver name you
should use will be displayed.

     4.   At the bottom of the PROTOCOL.INI file, add a driver section
          heading followed by a blank line for each ODI driver you typed
          in Step 3.

The driver section does not need to contain any parameters. For
example, if you typed NE2000 in Step 3, you would type the
following at the bottom of the file:

[NE2000]

Leave a blank line after each driver section heading. If the driver
name starts with a number, you do not need an X in front of the number.

     5.   Make sure transmit buffers are 6 bytes larger than the buffer
          value set with Link Support option in the NET.CFG file.

     6.   Remove all NDIS driver-specific information from the
          PROTOCOL.INI file (optional).

This NDIS information is not required by ODINSUP.

     7.   Save your changes.

     8.   Exit the PROTOCOL.INI file.

     9.   Reboot your machine for changes to CONFIG.SYS, NET.CFG,
          and PROTOCOL.INI to take effect.

How Can the NetWare Requester and ES/LS Coexist?

The NetWare Requester and ES/LS can coexist because, with
Novell's new ODINSUP protocol, the IBM products can use the
same ODI drivers as the Requester uses.

ODINSUP translates NDIS transmissions from ES or LS into a form
that complies with the ODI drivers. ODINSUP also translates
transmissions received from the network into a form readable by ES
and LS.

ODINSUP functions like a default protocol stack, meaning that it
accepts requests from the Link Support Layer (LSL) that are not
specifically marked for another registered protocol (such as IPX or
TCP/IP). When it receives requests, ODINSUP passes them on to the
NDIS protocol stack.

ODINSUP allows IBM's Protocol Manager (found in ES and LS) to
communicate with a network interface board without having to be
aware of the details of transmission on that board (such as frame
type).

Instead, the details are handled at the ODI driver level and then
transmissions are passed on to the Link Support Layer, which in
turn passes them on to the correct protocol stack or to ODINSUP.
ODINSUP translates the request to a form understood by Protocol
Manager.

For a diagram of how IBM and Novell components work together,
see page B-9.

Benefits of Coexistence

You benefit three ways when using ODINSUP:

-    Easier switching between LAN Services networks and NetWare networks.

When ODINSUP is loaded, you do not have to reconfigure or
reboot your workstation to switch from one type of network to
another. You can use both networks from your workstation as if
they were a single network.

-    Easier switching from Communications Manager connections to NetWare
     connections.

When ODINSUP is loaded, you do not have to reconfigure or
reboot your workstation to switch between a Communications
Manager connection and a NetWare network.

-    Compatibility between applications written to use the NDIS
     specification and driver written to use the ODI specification.

When ODINSUP is loaded, you can use a wider variety of
programs without having to worry about compatibility.

End of Chapter
.
.
rem ** Paths to Requester files and utilities are included.

LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;C:\NETWARE;
SET PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;
 C:\;C:\OS2\MDOS;C:\OS2\APPS;C:\NETWARE;L:\OS2;P:\OS2
SET DPATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;
 C:\;C:\OS2\BITMAP;C:\OS2\MDOS;C:\OS2\APPS;C:\NETWARE;P:\OS2

.
.

DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
DEVICE=C:\IBMCOM\PROTOCOL\LANDD.OS2
DEVICE=C:IBMCOM\PROTOCOL\NETBEUI.OS2

rem ** The NDIS drivers are commented out.

rem DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2
rem DEVICE=C:\IBMCOM\MACS\ELNKMC.OS2

RUN=C:\IBMCOM\PROTOCOL\LANDLL.EXE
RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=C:\IBMCOM\LANMSGEX.EXE
DEVICE=C:\IBMLAN\NETPROG\RDHELP.200
IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN
DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2

REM --- NetWare Requester statements BEGIN ---
DEVICE=C:\NETWARE\LSL.SYS
RUN=C:\NETWARE\DDAEMON.EXE

rem ** The ODINSUP driver is loaded.

DEVICE=C:\NETWARE\ODINSUP.SYS

rem ** The ODI driver you selected is loaded.

DEVICE=C:\NETWARE\NE2000.SYS

rem ** The Requester components are loaded.

DEVICE=C:\NETWARE\IPX.SYS
DEVICE=C:\NETWARE\SPX.SYS
RUN=C:\NETWARE\SPDAEMON.EXE
DEVICE=C:\NETWARE\NWREQ.SYS
IFS=C:\NETWARE\NWIFS.IFS
RUN=C:\NETWARE\NWDAEMON.EXE
DEVICE=C:\NETWARE\VIPX.SYS
DEVICE=C:\NETWARE\VSHELL.SYS
RUN=C:\NETWARE\NWSPOOL.EXE
REM --- NetWare Requester statements END ---
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU