home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 14 Text
/
14-Text.zip
/
NWIBM.ZIP
/
NWIBM.TXT
Wrap
Text File
|
1993-02-21
|
8KB
|
214 lines
Define the rules:
1) ODINSUP.SYS is RED and uses the MLID\ODI drivers. It will translate
IBM NDIS packets.
2) LANSUP.SYS is BLUE and is used when the network card is NOT ODI
compliant. It replaces the old OS/2 v1.3 TOKENEE andCMGRLAN Netware
drivers.
3) ODI2NDI.OS2 is Blue and "emulates" an ODI driver although you use
NDIS drivers. Red doesn't even know Blue is around and doing the
work.
We've found it best to install OS/2, ES before installing the Netware
requester. Each product affects the config.sys, NET.CFG, and protocol.ini in
its own way; by installing them one at a time, then checking the various files,
its' easier to troubleshoot.
*******************************************************************************
* ODINSUP *
*******************************************************************************
ODINSUP with ES 1.0 and OS/2 Netware Requester:
CONFIG.SYS
1. Make sure your Netware drive and directory are referenced in LIBPATH
,PATH and DPATH statements
2. REM out the NDIS IBM DD path:ibmcom\macs\ndisdd.OS2
******************* Next is positional*****************************
3. Add the Netware section starting with Device=path\LSL.SYS
Put the ODI driver name in this section NE2000.SYS or TOKEN.SYS.
These are supplied by Novell and are on the NW diskettesbut may be
more up to date thru Netwire or the adapter(NIC) OEM.
4. Add the IBM section starting with DD path\IBMCOM\LANMSGDD.SYS
_AND_ the PROTMAN.OS2 driver. Must be before the ODINSUP dd.
5. Add the path\NETWARE\ODINUP.SYS. Must be after the Protman.os2 *BUT* before
any LS statements if thats a consideration.
6. Finish off with remaining protocol DDs. Rem any other DDs from an
IBM supplied path refering to LSDAEMON.EXE, ndis.OS2. Don't forget
to REM there RUN= statements.
Summary:The Netware requester is loaded first, followed by the IBMCOM
devices. ODINSUP follows these drivers, then RUN statements.
NET.CFG
LINK SUPPORT
Anything you or the ODI supplied driver may need. Token-Ring/Enet
really vary here. Buffers are usually here # and size
PROTOCOL ODINSUP
BIND odi driver name
LINK DRIVER odi driver name
FRAME ethernet_802.3
FRAME ethernet_ii
FRAME ethernet_802.2
FRAME ethernet_snap
PROTOCOL STACK IPX
Sockets=xx(35-64) <---- 3 per session
PROTOCOL.INI File:
This file is for the IBM Protocol Manager-PROTMAN$. ";" in front on a
line is used to comment out stuff you don't want or to document.
[PROT_MAN]
DrivrName = PROTMAN$
[IBMLXCFG]
; These tell Protman$ what sections to process
LANDD-nif = LANDD.NIF
NETBEUI_nif = NETBEUI.NIF <----- for netbios/802.2(ES uses lots of
802.2
[LANDD_NIF]
DriverName = LANDD$ <---802.2 support
BINDINGS = odi driver name
LINKS = ## <--- you supply
NOTE: Any_reference to an IBM MAC driver xx.OS2, xx_nif, bindings=xx
in the PROTOCOL and/or MAC sections of the Protocol.ini file
must be changed to the odi driver name. There are a geat deal of
other settings that can/must be included but, your Device Driver
and/ adapter(NIC) OEM documentation should cover all these.
******************************************************************************
* LANSUP *
******************************************************************************
LANSUP.SYS
The LANSUP coexistence driver is a Network Protocol Driver written to
the IBM Communications Manager IEEE 802.2 interface. Protocol drivers
written to the NW ODI spec.(IPX/SPX) sit on top of LANSUP and LANSUP
translate ODI requests into 802.2 format and the IBM LAPS 802.2 sub-
system(LANDD.OS2) then passes the request to the NDIS MAC driver. It
is somewhat easier to configure.
Again, recommended install sequence is OS/2, ES and NW requester.
CONFIG.SYS
1.You should have the IBMCOM DD statements for ES first.
path\IBMCOM\MACS\ndis driver name must be used(IBMTOK.OS2 or NE2000.OS2 ).
The protman.os2 statement must be in this group also.
2.Rem out any reference to \NETWARE\odi driver name and add the following
statement path\NETWARE\LANSUP.SYS.
3.Next group of statements should be for NETWARE(route.sys,ipx.sys,
spx.sys etc.)
4.Any additional DDs go last like IBM Lan Requester(NETWKSTA.XXX)
The general ordering criterion must be met: LANSUP.SYS must be placed after
LSL.SYS, PROTMAN.OS2, the LANDD.OS2, and the LANDLLDD.SYS DD statements.
The 802.2 NDIS support must also be active in the PROTOCOL.INI
file(the LANDD_nif section must be present).If you use Token-Ring source
routing must include the \NETWARE\ROUTE.SYS statement.
NET.CFG
;Sample NET.CFG Note link support section may specify # and size of
; buffers and interupt your card is using
NETWARE REQUESTER
preferred xxxxx <- perferred server name if wanted
PROTOCOL ODINSUP
bind lansup
LINK DRIVER LANSUP
frame ethernet_802.2
frame ethernet_snap <- use which ones that apply to you. Note: NW
frame ethernet_ii 2.1x & 2.2 servers can not be seen if they
frame ethernet_802.3 only use _ii and 802.3
node address xxxxxxxxxxxx
The node address defined in net.cfg must match the NETADDRESS= coded in
the LANDD_NIF section of PROTOCOL.INI.
If you code a Transmit Buffer Size(XMITBUFSIZE)in PROTOCOL.INI, it must
be at least 32 bytes larger than the buffer size coded in the Link
Support Section of the NET.CFG. If you do not code an XMITBUFSIZE, LAPS
will use 25% of the available memory on the adapter as the transmit buffer
size,which is usually 2k or 4k. LANSUP.SYS uses an IEEE802.2
"User" so you should define USERS= to be 4 or higher in the PROTOCOL.INI.
;PROTOCOL.INI SAMPLE for LANSUP. Substitute your NDIS driver name for
; ndis in this example
[PROT_MAN]
DriverName = PROTMAN$
[IBMLXCFG]
ndis_nif = ndis.nif
LANDD_nif = LANDD_nif <--- 802.2 support
NETBEUI_nif = NETBEUI.nif <--- if netbios is needed for CM
;-------------------Protocol Section------------------------------------
[LANDD_nif]
DriverName = LANDD$
Bindings = ndis_nif
; adapter specifics for ES Comm. Mgr here
[NETBEUI_nif] <--- if netbios is needed
DriverName = netbeui$
Bindings = ndis_nif
; adapter specifics for netbios LS here if needed
;-------------------MAC Section-----------------------------------------
[ndis_nif]
DriverName = ndis$ (IBMTOK$, NE2000$ etc)
Primary
NETADDRESS = xxxxxxxxxxxx
MAXTRANSMITS = 12
RECVBUFS = 2
RECBUFSIZE = 256
XMITBUFS = 1
Note: All from Primary to XMITBUFS is adapter/driver specific.
*************************************************************************
* O D I 2 N D I *
*************************************************************************
ODI2NDI
Unlike LANSUP, ODI2NDI does not use the IBM IEEE 802.2 interface. AS the
result ODI2NDI does not have any coexistence problems with apps. written
to the IBM IEEE 802.2 interface.
The ES Communications Manager product is not needed for ODI/NDIS support.
ODI2NDI has better performance for NDIS apps. while not degrading ODI
IPX/SPX protocols.
Connectivity to pre-v311 NW servers is not limited to Ethernet and 802.2
ethernet frame support does not have to loaded on all file servers.
ODI2NDI supports all Ethernet and Token-Ring frame types.
The ODI2NDI driver does not require and definitions to be made to the
NW NET.CFG file(although your configuration may require other additions
to the NET.CFG for protocols etc.).
ODI2NDI can be installed and configured using LAPS(LAN Adapter and Protocol
Support) configuration program. NO_manual_configuration_of_ config.sys_ or
_PROTOCOL.INI_is_required.
***************************************************************************
Now you can pick which is best suited for you and your environment.....
ODINSUP.SYS or LANSUP.SYS or ODI2NDI.OS2.
***********************END***********************************************