home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
alltips.zip
/
NWCOEX.FAX
< prev
next >
Wrap
Text File
|
1994-11-26
|
29KB
|
858 lines
Three Methods of Coexistence (replaces F 7/14/94
COEXISTENCE OF THE NETWARE CLIENT FOR OS/2 WITH EITHER
IBM LAN SERVER OR COMMUNICATIONS MANAGER/2
Purpose of this document:
To explain coexistence and describe the steps necessary to install
IBM and NetWare Client for OS/2 software.
These configurations are discussed:
-OS/2 2.1, LAN Requester 3.0, NetWare Client for OS/2
or
-OS/2 2.1, Communications Manager/2, NetWare Client for
OS/2
or
-OS/2 2.1, LAN Requester 3.0, Communications Manager/2,
NetWare Client for OS/2
The configurations presented here also work in an environment
with Extended Services 1.0.
What is Coexistence?
The term coexistence means that IBM and Novell NetWare
Client for OS/2 and other IBM communications software
like LAN Server, CM/2, IBM's TCP/IP for OS/2, or DB2/2 share
the same network hardware. For example, the Novell NetWare
Client for OS/2 sharing a LAN adapter with different
protocols like IEEE 802.2, NetBIOS or TCP/IP.
Three Methods of Coexistence
In order to share a network interface card between two or more
network communication packages, you must choose a method to make
the coexistence possible. There are three methods available
to allow the coexistence of the NetWare Client for OS/2
with LAN Server, CM/2, IBM's TCP/IP for OS/2, or DB2/2. The
methods that allow coexistence are: ODINSUP, LANSUP, and, ODI2NDI.
The ODINSUP method translates NDIS transmissions to Open Data-Link
Interface (ODI). ODINSUP receives requests from the Link Support
Layer (LSL) and passes them on to the NDIS protocol stack.
The LANSUP method uses the NDIS drivers.
The ODI2NDI method translates ODI transmissions from the NetWare
environment to the NDIS environment. Because ODI2NDI.OS2 comes
as a part of Network Transport Services/2, you must have NTS/2
installed (or the LAPS diskette with the ODI2NDI driver) in order
to use this third method.
Document Index
Section One. Assumptions and important information for all
configurations.
Section Two. Installation section for IBM OS/2 LAN Requester 3.0.
This section presents an overview of the steps necessary to install
the LAN Requester and its default components. For more details
on installation of the various components, please refer to the
IBM OS/2 LAN Server Version 3.0 Network Administrator Reference
Volume 1: Planning and Installation.
Section Three. Installation section for the NetWare Client
for OS/2 2.10. This is a basic list of instructions on how to use
the NetWare Client for OS/2 installation utility. For more
information on the NetWare Client for OS/2 2.10, please refer
to the Workstation for OS/2 or the Workstation Basics and
Installation manuals.
Section Four. Workstation configuration using ODINSUP.SYS.
Section Five. Workstation configuration using LANSUP.SYS.
Section Six. Workstation configuration using ODI2NDI.OS2.
For more information on the installation of ODI2NDI.OS2,
refer to Appendix I of the LAN Adapter and Protocol Support
Configuration Guide.
Section One
Assumptions and Important Information
Insure the coexisting software is working properly BEFORE NetWare
is loaded. In the particular configuration examples that follow,
Network Transport Services/2 (NTS/2) and Communication Manager/2
(CM/2) were installed and operating prior to installation of all
of the requester code. This is not necessary but was done to
demonstrate that not only is coexistence of IBM LAN Requester
and the NetWare Client for OS/2 possible, but that CM/2 can
also be installed in this scenario.
You may use the Communications Manager portion of Extended Services
1.0 instead of CM/2. Please note that if you are using Communications
Manager from Extended Services and have not installed Network
Transport Services ,you cannot use the ODI2NDI.OS2 method.
The sample configurations that follow were created using an
IBM 16/4 Token Ring network interface card.
Please be sure to choose only one method of coexistence and configure
for that method. Do not try to configure for more than one method
of coexistence on the same workstation. Of course, different
workstations on the same LAN may use different methods of
coexistence if desired.
It is a good idea to install one product and get that one product
working before continuing with the installation. You may wish to
write down the order that you will install your software packages in
before you begin the installation process.
Section Two
OS/2 LAN Requester Installation and Configuration
Boot OS/2 v2.1 on a workstation. Install the IBM OS/2 LAN Requester.
What follows is a list of the basic steps that you may use if
you are unfamiliar with the installation of IBM LAN Requester.
1) Insert Requester Diskette 1.
2) Open an OS/2 session and type the installation command:
A&colon.LANINST
3) Select Advanced on the Installation/Configuration Window.
4) Select OK to install or configure this workstation.
5) Choose the disk drive to install the LAN Requester on.
6) Select OK to accept the default of Install or Remove a component.
7) Browse through the list of components. Note the ones that are
selected by default and the ones that are required. Select
OK to continue and accept the default components.
8) Choose Configure a Component and select OK to continue.
9) Select the first component (Requester) and then click the
Configure button to continue.
A) Enter your machine name. Example: TESTER
B) Enter the domain name. Example: DOMAIN20
C) Click on OK to Start the Requester Automatically.
D) Select the various components you want to start.
The default components are all that are necessary.
10) Select to configure LAN Adapter and Protocol Support next.
A) Add support for your network interface card. This is
necessary only if CM/2 has not been previously installed.
B) Add IEEE 802.2 support. This is not need by either
LAN Requester or the NetWare Requester for OS/2.
It is necessary only to load drivers that
are required by Communications Manager/2.
C) Add NETBIOS support. This is required for LAN Requester.
D) Edit the Token-Ring profile. Configure this for use with
a LAA. For example, LAA: 400001234567
E) Select OK to continue.
11) When you have completed configuring components, you are ready
to complete the installation. On the configuration window,
select OK.
12) On the Installation and Configuration window, select "Apply the
Changes."
Select OK and begin shuffling diskettes.
After the installation is complete, the system will automatically
backup the CONFIG.SYS file as CONFIG.001. You should now perform a
shutdown of the system, reboot, and verify that the requester
functions properly. Make a backup copy of the CONFIG.SYS and
PROTOCOL.INI files for future reference.
Section Three
NetWare Client for OS/2 Installation
Your PC should be booted to OS/2 before you begin installing the
NetWare Client for OS/2.
1) Open an OS/2 session. Insert the WSOS2_1 diskette into drive A&colon..
2) Type the installation command:
A&colon.INSTALL
3) Select Installation from the menu bar.
4) Select Requester on Workstation...
5) Choose the target directory to install files to and click on
the OK button.
6) Select to Edit the CONFIG.SYS and Copy All Files.
7) Select the appropriate Network Interface Card driver.
A) Click on the arrow on the right side of the yellow box.
B) Insert either the WSDRV_1 diskette or diskette containing
the ODI drivers for your network interface card.
C) Highlight the appropriate driver from the list of choices
and click on the Continue button.
If you use ODINSUP.SYS, choose the ODI driver for your card.
If you use LANSUP.SYS, choose LANSUP.SYS from the list.
If you use ODI2NDI.OS2, choose an ODI driver.
Click on the Continue button.
8) Select IPX support for DOS and Windows Applications only if
needed. Choose the type of shell support that you want: private,
global, or none. In this case, global is preferable since private
sessions can be set up later. Click on the Continue button.
9) Select SPX for OS/2 session only if needed.
10) Select Remote Named Pipes support only if needed.
11) Select NetBIOS emulation only if needed.
12) Click on the Save button.
13) Click on the OK button to save changes to the CONFIG.SYS.
14) Choose Copy Default Driver and select OK.
15) Click Copy to begin install. Insert the NetWare installation
diskettes WSOS2_1 and WSOS2_2 when prompted.
This completes the installation of the NetWare Client for
OS/2 2.1. Do not close the NetWare Install utility yet. It
will be used in the following section to create/edit
the NET.CFG file.
Now it is time to configure the workstation for proper operation.
As previously mentioned, this can be done in one of three ways:
ODINSUP.SYS, LANSUP.SYS, or ODI2NDI.OS2. Perform one of the
following sections to complete workstation configuration.
Section Four
Workstation Configuration using ODINSUP.SYS
1) Create the NET.CFG file. This is the NetWare requester
configuration file that holds the NetWare parameters.
A) Select Configuration from the NetWare Install utility menu bar.
B) Select This Workstation.
C) Click on the Edit button to edit the NET.CFG file.
D) Place the following as a minimum in the NET.CFG file:
Netware Requester
preferred server server_name
directory services off
Protocol ODINSUP
bind token
Link Driver TOKEN
frame token-ring
frame token-ring_snap
node address 400001234567
NOTE: If you have a NetWare 4.0 or 4.01 server, do not put the
"directory services off" line in the NET.CFG.
2) Edit the PROTOCOL.INI file in the IBMCOM subdirectory. You
should change the Bindings statements so that they are equal to
your ODI driver. Below is a sample PROTOCOL.INI:
PROT_MANU
DRIVERNAME = PROTMAN$
IBMLXCFGU
IBMTOK_nif = IBMTOK.nif
LANDD_nif = LANDD.nif
NETBEUI_nif = NETBEUI.nif
LANDD_nifU
DriverName = LANDD$
Bindings = token
NETADDRESS = "400005d5a359"
NETBEUI_nifU
DriverName = netbeui$
Bindings = token
IBMTOK_nifU
DriverName = IBMTOK$
ADAPTER = "PRIMARY"
NETADDRESS = "400005d5a359"
MAXTRANSMITS = 6
RECVBUFS = 2
RECVBUFSIZE = 256
XMITBUFS = 1
TOKENU
DriverName = TOKEN$
4) Edit the CONFIG.SYS file. You will need to do extensive work on
this file. There are a number of device driver statements that must
be moved for this coexistence to work properly.
Be sure that you REMark out or remove entirely the NDIS device driver
for your network interface card. For example, if you have an IBM
Token Ring 16/4 card, you will REMark out the IBMTOK.OS2 driver.
Below is a complete CONFIG.SYS file. Make sure that all of the
network device drivers at the bottom of the file are in the order
shown.
PROTSHELL=D&colon.\OS2\PMSHELL.EXE
SET USER_INI=D&colon.\OS2\OS2.INI
SET SYSTEM_INI=D&colon.\OS2\OS2SYS.INI
SET OS2_SHELL=D&colon.\OS2\CMD.EXE
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS
SET RUNWORKPLACE=D&colon.\OS2\PMSHELL.EXE
SET COMSPEC=D&colon.\OS2\CMD.EXE
LIBPATH=E&colon.\IBMLAN\NETLIB;D&colon.\MUGLIB\DLL;D&colon.\IBMCOM\DLL;.;D&colon
.\OS2\DLL;
E&colon.\CMLIB\DLL;D&colon.\OS2\MDOS;D&colon.\;D&colon.\OS2\APPS\DLL;D&colon.\NE
TWARE;E&colon.\WPCOS2;
SETPATH=E&colon.\IBMLAN\NETPROG;D&colon.\OS2;E&colon.\CMLIB;D&colon.\MUGLIB;D&co
lon.\OS2\SYSTEM;
D&colon.\OS2\MDOS\WINOS2;D&colon.\OS2\INSTALL;D&colon.\;D&colon.\OS2\MDOS;D&colo
n.\OS2\APPS;
D&colon.\NETWARE;L&colon.\OS2;P&colon.\OS2;E&colon.\WPOS2;
SETDPATH=E&colon.\IBMLAN\NETPROG;E&colon.\IBMLAN;D&colon.\IBMCOM;D&colon.\OS2;E&
colon.\CMLIB;
D&colon.\MUGLIB\DLL;D&colon.\OS2\SYSTEM;D&colon.\OS2\MDOS\WINOS2;D&colon.\OS2\IN
STALL;D&colon.\;
D&colon.\OS2\BITMAP;D&colon.\OS2\MDOS;D&colon.\OS2\APPS;D&colon.\NETWARE;L&colon
.\OS2;P&colon.\OS2;
SET PROMPT=$i$pU
SET HELP=D&colon.\OS2\HELP;D&colon.\OS2\HELP\TUTORIAL;E&colon.\CMLIB;
SET GLOSSARY=D&colon.\OS2\HELP\GLOSS;
SET IPF_KEYS=SBCS
PRIORITY_DISK_IO=YES
FILES=20
DEVICE=D&colon.\OS2\TESTCFG.SYS
DEVICE=D&colon.\OS2\DOS.SYS
DEVICE=D&colon.\OS2\PMDD.SYS
BUFFERS=30
IOPL=YES
DISKCACHE=1024,LW,AC&colon.D
MAXWAIT=3
MEMMAN=SWAP,PROTECT
SWAPPATH=E&colon.\swap 4096 6144
BREAK=OFF
THREADS=128
PRINTMONBUFSIZE=134,134,134
COUNTRY=001,D&colon.\OS2\SYSTEM\COUNTRY.SYS
SET KEYS=ON
REM SET DELDIR=C&colon.\DELETE,512;D&colon.\DELETE,512;E&colon.\DELETE,512;
BASEDEV=PRINT02.SYS
BASEDEV=IBM2FLPY.ADD
BASEDEV=IBM2ADSK.ADD
BASEDEV=OS2DASD.DMD
SET BOOKSHELF=E&colon.\IBMLAN\BOOK;D&colon.\OS2\BOOK;E&colon.\CMLIB\BOOK;
SET EPMPATH=D&colon.\OS2\APPS;
REM DEVICE=D&colon.\OS2\APPS\SASYNCDB.SYS
PROTECTONLY=NO
SHELL=D&colon.\OS2\MDOS\COMMAND.COM D&colon.\OS2\MDOS
FCBS=16,8
RMSIZE=640
DEVICE=D&colon.\OS2\MDOS\VEMM.SYS
DOS=LOW,NOUMB
DEVICE=D&colon.\OS2\MDOS\VDPX.SYS
DEVICE=D&colon.\OS2\MDOS\VXMS.SYS /UMB
DEVICE=D&colon.\OS2\MDOS\VDPMI.SYS
DEVICE=D&colon.\OS2\MDOS\VCDROM.SYS
DEVICE=D&colon.\OS2\MDOS\VWIN.SYS
REM DEVICE=D&colon.\OS2\PCMCIA.SYS
REM DEVICE=D&colon.\OS2\MDOS\VPCMCIA.SYS
DEVICE=D&colon.\OS2\MDOS\VMOUSE.SYS
DEVICE=D&colon.\OS2\POINTDD.SYS
DEVICE=D&colon.\OS2\MOUSE.SYS
DEVICE=D&colon.\OS2\COM.SYS
DEVICE=D&colon.\OS2\MDOS\VCOM.SYS
CODEPAGE=437,850
DEVINFO=KBD,US,D&colon.\OS2\KEYBOARD.DCP
BASEDEV=XGA.SYS
DEVICE=D&colon.\OS2\XGARING0.SYS
DEVINFO=SCR,VGA,D&colon.\OS2\VIOTBL.DCP
SET VIDEO_DEVICES=VIO_XGA
SET VIO_XGA=DEVICE(BVHVGA,BVHXGA)
DEVICE=D&colon.\OS2\MDOS\VVGA.SYS
DEVICE=D&colon.\OS2\MDOS\VXGA.SYS
DEVICE=E&colon.\CMLIB\ACSLANDD.SYS
DEVICE=E&colon.\CMLIB\CMKFMDE.SYS
DEVICE=D&colon.\OS2\LOG.SYS
RUN=D&colon.\OS2\SYSTEM\LOGDAEM.EXE
RUN=D&colon.\OS2\EPWROUT.EXE 1
RUN=D&colon.\OS2\EPW.EXE
REM --- Netware Requester statements BEGIN ---
SET NWLANGUAGE=ENGLISH
DEVICE=D&colon.\NETWARE\LSL.SYS
RUN=D&colon.\NETWARE\DDAEMON.EXE
DEVICE=D&colon.\NETWARE\TOKEN.SYS
DEVICE=D&colon.\NETWARE\ROUTE.SYS
DEVICE=D&colon.\NETWARE\IPX.SYS
rem DEVICE=D&colon.\NETWARE\SPX.SYS
rem RUN=D&colon.\NETWARE\SPDAEMON.EXE
rem DEVICE=D&colon.\NETWARE\NMPIPE.SYS
rem DEVICE=D&colon.\NETWARE\NPSERVER.SYS
rem RUN=D&colon.\NETWARE\NPDAEMON.EXE
DEVICE=D&colon.\NETWARE\NWREQ.SYS
IFS=D&colon.\NETWARE\NWIFS.IFS
RUN=D&colon.\NETWARE\NWDAEMON.EXE
rem DEVICE=D&colon.\NETWARE\NETBIOS.SYS
rem RUN=D&colon.\NETWARE\NBDAEMON.EXE
DEVICE=D&colon.\NETWARE\VIPX.SYS
DEVICE=D&colon.\NETWARE\VSHELL.SYS GLOBAL
REM ----- Netware Requester statements END ---
DEVICE=D&colon.\IBMCOM\LANMSGDD.OS2 /I&colon.D&colon.\IBMCOM
DEVICE=D&colon.\IBMCOM\PROTMAN.OS2 /I&colon.D&colon.\IBMCOM
DEVICE=D&colon.\IBMCOM\PROTOCOL\LANDD.OS2
DEVICE=D&colon.\IBMCOM\PROTOCOL\LANDLLDD.OS2
REM ----- Be sure to REMark out your NDIS driver ---
rem DEVICE=D&colon.\IBMCOM\MACS\IBMTOK.OS2
DEVICE=D&colon.\IBMCOM\PROTOCOL\NETBEUI.OS2
REM ----- You must add this line yourself ---
device=d&colon.\netware\odinsup.sys
RUN=D&colon.\IBMCOM\PROTOCOL\LANDLL.EXE
RUN=D&colon.\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=D&colon.\IBMCOM\LANMSGEX.EXE
REM -----These lines are for LAN Requester ---
DEVICE=E&colon.\IBMLAN\NETPROG\RDRHELP.200
IFS=E&colon.\IBMLAN\NETPROG\NETWKSTA.200 /I&colon.E&colon.\IBMLAN /N
RUN=E&colon.\IBMLAN\NETPROG\LSDAEMON.EXE
DEVICE=D&colon.\IBMCOM\PROTOCOL\NETBIOS.OS2
The installation and configuration of a dual requester workstation
with ODINSUP.SYS is now complete. Shut down the system and reboot.
Section Five
Workstation Configuration using LANSUP.SYS
1) Create a NET.CFG file.
A) Select Configuration from the NetWare Install utility menu bar.
B) Select This Workstation.
C) Click on the Edit button to edit the NET.CFG file.
D) Place the following as a minimum in the NET.CFG file&colon.
Netware Requester
Preferred Server server_name
Directory Services Off
Link Driver LANSUP
frame token-ring
frame token-ring_snap
node address 400001234567
NOTE: If you wish to login to a NetWare 4.0 or 4.01 file server,
do not put "DIRECTORY SERVICES OFF" in the NET.CFG.
NOTE: On Ethernet, LANSUP.SYS only supports the Ethernet_802.2
and Ethernet_II frame types.
When using LANSUP.SYS, you must specify a node address.
2) Edit your CONFIG.SYS file so that is similar to the following.
Below is a sample working CONFIG.SYS.
PROTSHELL=C&colon.\OS2\PMSHELL.EXE
SET USER_INI=C&colon.\OS2\OS2.INI
SET SYSTEM_INI=C&colon.\OS2\OS2SYS.INI
SET OS2_SHELL=C&colon.\OS2\CMD.EXE
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS
SET RUNWORKPLACE=C&colon.\OS2\PMSHELL.EXE
SET COMSPEC=C&colon.\OS2\CMD.EXE
LIBPATH=C&colon.\IBMLAN\NETLIB;C&colon.\MUGLIB\DLL;C&colon.\IBMCOM\DLL;.;C&colon
.\OS2\DLL;
C&colon.\CMLIB\DLL;C&colon.\OS2\MDOS;C&colon.\;C&colon.\OS2\APPS\DLL;C&colon.\NE
TWARE;
SETPATH=C&colon.\IBMLAN\NETPROG;C&colon.\MUGLIB;C&colon.\OS2;C&colon.\CMLIB;C&co
lon.\OS2\SYSTEM;
C&colon.\OS2\MDOS\WINOS2;C&colon.\OS2\INSTALL;C&colon.\;C&colon.\OS2\MDOS;C&colo
n.\OS2\APPS;
C&colon.\NETWARE;L&colon.\OS2;P&colon.\OS2;
SETDPATH=C&colon.\IBMLAN\NETPROG;C&colon.\IBMLAN;C&colon.\MUGLIB;C&colon.\IBMCOM
;C&colon.\OS2;
C&colon.\CMLIB;C&colon.\OS2\SYSTEM;C&colon.\OS2\MDOS\WINOS2;C&colon.\OS2\INSTALL
;C&colon.\;
C&colon.\OS2\BITMAP;C&colon.\OS2\MDOS;C&colon.\OS2\APPS;C&colon.\NETWARE;L&colon
.\OS2;P&colon.\OS2;
SET PROMPT=$i$pU
SET HELP=C&colon.\OS2\HELP;C&colon.\OS2\HELP\TUTORIAL;C&colon.\CMLIB;
SET GLOSSARY=C&colon.\OS2\HELP\GLOSS;
SET IPF_KEYS=SBCS
PRIORITY_DISK_IO=YES
FILES=20
DEVICE=C&colon.\IBMCOM\PROTOCOL\LANPDD.OS2
DEVICE=C&colon.\IBMCOM\PROTOCOL\LANVDD.OS2
DEVICE=C&colon.\IBMCOM\LANMSGDD.OS2 /I&colon.C&colon.\IBMCOM
DEVICE=C&colon.\IBMCOM\PROTMAN.OS2 /I&colon.C&colon.\IBMCOM
DEVICE=C&colon.\IBMCOM\PROTOCOL\LANDD.OS2
DEVICE=C&colon.\IBMCOM\PROTOCOL\LANDLLDD.OS2
DEVICE=C&colon.\OS2\TESTCFG.SYS
DEVICE=C&colon.\OS2\DOS.SYS
DEVICE=C&colon.\OS2\PMDD.SYS
BUFFERS=30
IOPL=YES
DISKCACHE=1024,LW,AC&colon.C
MAXWAIT=3
MEMMAN=SWAP,PROTECT
SWAPPATH=C&colon.\OS2\SYSTEM 2048 2048
BREAK=OFF
THREADS=256
PRINTMONBUFSIZE=134,134,134
COUNTRY=001,C&colon.\OS2\SYSTEM\COUNTRY.SYS
SET KEYS=ON
REM SET DELDIR=C&colon.\DELETE,512;
BASEDEV=PRINT02.SYS
BASEDEV=IBM2FLPY.ADD
BASEDEV=IBM2ADSK.ADD
BASEDEV=OS2DASD.DMD
SET EPMPATH=C&colon.\OS2\APPS;
PROTECTONLY=NO
SHELL=C&colon.\OS2\MDOS\COMMAND.COM C&colon.\OS2\MDOS
FCBS=16,8
RMSIZE=640
DEVICE=C&colon.\OS2\MDOS\VEMM.SYS
DOS=LOW,NOUMB
DEVICE=C&colon.\OS2\MDOS\VDPX.SYS
DEVICE=C&colon.\OS2\MDOS\VXMS.SYS /UMB
DEVICE=C&colon.\OS2\MDOS\VDPMI.SYS
DEVICE=C&colon.\OS2\MDOS\VCDROM.SYS
DEVICE=C&colon.\OS2\MDOS\VWIN.SYS
DEVICE=C&colon.\OS2\MDOS\VMOUSE.SYS
DEVICE=C&colon.\OS2\POINTDD.SYS
DEVICE=C&colon.\OS2\MOUSE.SYS
DEVICE=C&colon.\OS2\COM.SYS
DEVICE=C&colon.\OS2\MDOS\VCOM.SYS
CODEPAGE=437,850
DEVINFO=KBD,US,C&colon.\OS2\KEYBOARD.DCP
DEVINFO=SCR,VGA,C&colon.\OS2\VIOTBL.DCP
SET VIDEO_DEVICES=VIO_VGA
SET VIO_VGA=DEVICE(BVHVGA)
DEVICE=C&colon.\OS2\MDOS\VVGA.SYS
DEVICE=C&colon.\CMLIB\ACSLANDD.SYS
DEVICE=C&colon.\IBMCOM\MACS\IBMTOK.OS2
DEVICE=C&colon.\CMLIB\CMKFMDE.SYS
SET CMPATH=C&colon.\CMLIB
RUN=C&colon.\OS2\EPWROUT.EXE 1
RUN=C&colon.\OS2\EPW.EXE
SET BOOKSHELF=C&colon.\IBMLAN\BOOK;C&colon.\CMLIB\BOOK;
DEVICE=C&colon.\IBMCOM\PROTOCOL\NETBEUI.OS2
DEVICE=C&colon.\IBMLAN\NETPROG\RDRHELP.200
REM ----- Netware Requester statements BEGIN ---
SET NWLANGUAGE=ENGLISH
DEVICE=C&colon.\NETWARE\LSL.SYS
RUN=C&colon.\NETWARE\DDAEMON.EXE
DEVICE=C&colon.\NETWARE\LANSUP.SYS
DEVICE=C&colon.\NETWARE\ROUTE.SYS
DEVICE=C&colon.\NETWARE\IPX.SYS
DEVICE=C&colon.\NETWARE\SPX.SYS
RUN=C&colon.\NETWARE\SPDAEMON.EXE
rem DEVICE=C&colon.\NETWARE\NMPIPE.SYS
rem DEVICE=C&colon.\NETWARE\NPSERVER.SYS
rem RUN=C&colon.\NETWARE\NPDAEMON.EXE
DEVICE=C&colon.\NETWARE\NWREQ.SYS
IFS=C&colon.\NETWARE\NWIFS.IFS
RUN=C&colon.\NETWARE\NWDAEMON.EXE
rem DEVICE=C&colon.\NETWARE\NETBIOS.SYS
rem RUN=C&colon.\NETWARE\NBDAEMON.EXE
DEVICE=C&colon.\NETWARE\VIPX.SYS
DEVICE=C&colon.\NETWARE\VSHELL.SYS GLOBAL
REM ----- Netware Requester statements END ---
IFS=C&colon.\IBMLAN\NETPROG\NETWKSTA.200 /I&colon.C&colon.\IBMLAN /N
DEVICE=C&colon.\IBMCOM\PROTOCOL\NETBIOS.OS2
RUN=C&colon.\IBMLAN\NETPROG\LSDAEMON.EXE
RUN=C&colon.\IBMCOM\PROTOCOL\LANDLL.EXE
RUN=C&colon.\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=C&colon.\IBMCOM\LANMSGEX.EXE
3) You do NOT need to edit your PROTOCOL.INI file.
Below is a sample working PROTOCOL.INI file.
PROT_MANU
DRIVERNAME = PROTMAN$
IBMLXCFGU
LANDD_nif = LANDD.nif
NETBEUI_nif = NETBEUI.nif
IBMTOK_nif = IBMTOK.nif
LANDD_nifU
DriverName = LANDD$
Bindings = IBMTOK_nif
NETBEUI_nifU
DriverName = netbeui$
Bindings = IBMTOK_nif
IBMTOK_nifU
DriverName = IBMTOK$
ADAPTER = "PRIMARY"
NETADDRESS = "400005d01234"
MAXTRANSMITS = 6
RECVBUFS = 2
RECVBUFSIZE = 512
XMITBUFS = 1
XMITBUFSIZE = 2040
The installation and configuration using ODINSUP.SYS is now
complete. Shut down the system and reboot.
Section Six
Workstation Configuration with ODI2NDI.OS2
1) Create a NET.CFG file.
A) Select Configuration from the NetWare Install utility menu bar.
B) Select This Workstation.
C) Click on the Edit button to edit the NET.CFG file.
D) Place the following as a minimum in the NET.CFG file&colon.
NETWARE REQUESTER
PREFERRED SERVER SERVER_NAME
DIRECTORY SERVICES OFF
NOTE: If you wish to login to a NetWare 4.0 or 4.01 file server,
do not put "DIRECTORY SERVICES OFF" in the NET.CFG.
2) Run LAPS from the IBMCOM subdirectory.
A) Open an OS/2 session. CD to the IBMCOM subdirectory.
Type: LAPS
B) Click on the Configure button.
C) Choose Configure LAN Transports and click on the
Continue button.
D) Add IBM NetWare Requester Support to your network adapter.
E) Edit IBM NetWare Requester Support and add a network adapter
address.
Set the frame types that you need on your network to Yes.
F) Select the OK button when you are finished.
G) Select the OK button on the Configure Workstation screen.
H) Choose the Exit button.
I) Select the drive to update and click on the Continue button.
J) You should get a message that your CONFIG.SYS file was
successfully updated. Click on the OK button.
K) Exit the LAPS Installation and Configuration by clicking on
the Exit button.
L) Close the OS/2 session.
2) You do NOT need to edit your CONFIG.SYS. Below is a sample
working CONFIG.SYS file.
PROTSHELL=C&colon.\OS2\PMSHELL.EXE
SET USER_INI=C&colon.\OS2\OS2.INI
SET SYSTEM_INI=C&colon.\OS2\OS2SYS.INI
SET OS2_SHELL=C&colon.\OS2\CMD.EXE
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS
SET RUNWORKPLACE=C&colon.\OS2\PMSHELL.EXE
SET COMSPEC=C&colon.\OS2\CMD.EXE
LIBPATH=C&colon.\IBMCOM\DLL;C&colon.\IBMLAN\NETLIB;C&colon.\MUGLIB\DLL;.;C&colon
.\OS2\DLL;
C&colon.\CMLIB\DLL;C&colon.\OS2\MDOS;C&colon.\;C&colon.\OS2\APPS\DLL;C&colon.\NE
TWARE;
SETPATH=C&colon.\IBMLAN\NETPROG;C&colon.\MUGLIB;C&colon.\OS2;C&colon.\CMLIB;C&co
lon.\OS2\SYSTEM;
C&colon.\OS2\MDOS\WINOS2;C&colon.\OS2\INSTALL;C&colon.\;C&colon.\OS2\MDOS;C&colo
n.\OS2\APPS;
C&colon.\NETWARE;L&colon.\OS2;P&colon.\OS2;
SETDPATH=C&colon.\IBMCOM;C&colon.\IBMLAN\NETPROG;C&colon.\IBMLAN;C&colon.\MUGLIB
;C&colon.\OS2;
C&colon.\CMLIB;C&colon.\OS2\SYSTEM;C&colon.\OS2\MDOS\WINOS2;C&colon.\OS2\INSTALL
;C&colon.\;
C&colon.\OS2\BITMAP;C&colon.\OS2\MDOS;C&colon.\OS2\APPS;C&colon.\NETWARE;L&colon
.\OS2;P&colon.\OS2;
SET PROMPT=$i$pU
SET HELP=C&colon.\OS2\HELP;C&colon.\OS2\HELP\TUTORIAL;C&colon.\CMLIB;
SET GLOSSARY=C&colon.\OS2\HELP\GLOSS;
SET IPF_KEYS=SBCS
PRIORITY_DISK_IO=YES
FILES=20
DEVICE=C&colon.\IBMCOM\PROTOCOL\LANPDD.OS2
DEVICE=C&colon.\IBMCOM\PROTOCOL\LANVDD.OS2
DEVICE=C&colon.\IBMCOM\LANMSGDD.OS2 /I&colon.C&colon.\IBMCOM
DEVICE=C&colon.\IBMCOM\PROTMAN.OS2 /I&colon.C&colon.\IBMCOM
DEVICE=C&colon.\IBMCOM\PROTOCOL\LANDD.OS2
DEVICE=C&colon.\IBMCOM\PROTOCOL\LANDLLDD.OS2
DEVICE=C&colon.\OS2\TESTCFG.SYS
DEVICE=C&colon.\OS2\DOS.SYS
DEVICE=C&colon.\OS2\PMDD.SYS
BUFFERS=30
IOPL=YES
DISKCACHE=1024,LW,AC&colon.C
MAXWAIT=3
MEMMAN=SWAP,PROTECT
SWAPPATH=C&colon.\OS2\SYSTEM 2048 2048
BREAK=OFF
THREADS=256
PRINTMONBUFSIZE=134,134,134
COUNTRY=001,C&colon.\OS2\SYSTEM\COUNTRY.SYS
SET KEYS=ON
REM SET DELDIR=C&colon.\DELETE,512;
BASEDEV=PRINT02.SYS
BASEDEV=IBM2FLPY.ADD
BASEDEV=IBM2ADSK.ADD
BASEDEV=OS2DASD.DMD
SET EPMPATH=C&colon.\OS2\APPS;
PROTECTONLY=NO
SHELL=C&colon.\OS2\MDOS\COMMAND.COM C&colon.\OS2\MDOS
FCBS=16,8
RMSIZE=640
DEVICE=C&colon.\OS2\MDOS\VEMM.SYS
DOS=LOW,NOUMB
DEVICE=C&colon.\OS2\MDOS\VDPX.SYS
DEVICE=C&colon.\OS2\MDOS\VXMS.SYS /UMB
DEVICE=C&colon.\OS2\MDOS\VDPMI.SYS
DEVICE=C&colon.\OS2\MDOS\VCDROM.SYS
DEVICE=C&colon.\OS2\MDOS\VWIN.SYS
DEVICE=C&colon.\OS2\MDOS\VMOUSE.SYS
DEVICE=C&colon.\OS2\POINTDD.SYS
DEVICE=C&colon.\OS2\MOUSE.SYS
DEVICE=C&colon.\OS2\COM.SYS
DEVICE=C&colon.\OS2\MDOS\VCOM.SYS
CODEPAGE=437,850
DEVINFO=KBD,US,C&colon.\OS2\KEYBOARD.DCP
DEVINFO=SCR,VGA,C&colon.\OS2\VIOTBL.DCP
SET VIDEO_DEVICES=VIO_VGA
SET VIO_VGA=DEVICE(BVHVGA)
DEVICE=C&colon.\OS2\MDOS\VVGA.SYS
DEVICE=C&colon.\CMLIB\ACSLANDD.SYS
DEVICE=C&colon.\IBMCOM\MACS\IBMTOK.OS2
DEVICE=C&colon.\CMLIB\CMKFMDE.SYS
SET CMPATH=C&colon.\CMLIB
RUN=C&colon.\OS2\EPWROUT.EXE 1
RUN=C&colon.\OS2\EPW.EXE
SET BOOKSHELF=C&colon.\IBMLAN\BOOK;C&colon.\CMLIB\BOOK;
DEVICE=C&colon.\IBMCOM\PROTOCOL\NETBEUI.OS2
DEVICE=C&colon.\IBMLAN\NETPROG\RDRHELP.200
REM ----- Netware Requester statements BEGIN ---
SET NWLANGUAGE=ENGLISH
DEVICE=C&colon.\NETWARE\LSL.SYS
RUN=C&colon.\NETWARE\DDAEMON.EXE
device = C&colon.\ibmcom\protocol\odi2ndi.os2
REM DEVICE=C&colon.\NETWARE\LANSUP.SYS
DEVICE=C&colon.\NETWARE\ROUTE.SYS
DEVICE=C&colon.\NETWARE\IPX.SYS
DEVICE=C&colon.\NETWARE\SPX.SYS
RUN=C&colon.\NETWARE\SPDAEMON.EXE
rem DEVICE=C&colon.\NETWARE\NMPIPE.SYS
rem DEVICE=C&colon.\NETWARE\NPSERVER.SYS
rem RUN=C&colon.\NETWARE\NPDAEMON.EXE
DEVICE=C&colon.\NETWARE\NWREQ.SYS
IFS=C&colon.\NETWARE\NWIFS.IFS
RUN=C&colon.\NETWARE\NWDAEMON.EXE
rem DEVICE=C&colon.\NETWARE\NETBIOS.SYS
rem RUN=C&colon.\NETWARE\NBDAEMON.EXE
DEVICE=C&colon.\NETWARE\VIPX.SYS
DEVICE=C&colon.\NETWARE\VSHELL.SYS GLOBAL
REM ----- Netware Requester statements END ---
IFS=C&colon.\IBMLAN\NETPROG\NETWKSTA.200 /I&colon.C&colon.\IBMLAN /N
DEVICE=C&colon.\IBMCOM\PROTOCOL\NETBIOS.OS2
RUN=C&colon.\IBMLAN\NETPROG\LSDAEMON.EXE
RUN=C&colon.\IBMCOM\PROTOCOL\LANDLL.EXE
RUN=C&colon.\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=C&colon.\IBMCOM\LANMSGEX.EXE
4). You do NOT need to edit your PROTOCOL.INI file.
Below is a sample working PROTOCOL.INI.
PROT_MANU
DRIVERNAME = PROTMAN$
IBMLXCFGU
LANDD_nif = LANDD.NIF
NETBEUI_nif = NETBEUI.NIF
ODI2NDI_nif = ODI2NDI.nif
IBMTOK_nif = IBMTOK.nif
LANDD_nifU
DriverName = LANDD$
Bindings = IBMTOK_nif
NETBEUI_nifU
DriverName = netbeui$
Bindings = IBMTOK_nif
ODI2NDI_nifU
DriverName = odi2ndi$
Bindings = IBMTOK_nif
NETADDRESS = "400005d01234"
TOKEN-RING = "yes"
TOKEN-RING_SNAP = "yes"
ETHERNET_802.3 = "no"
ETHERNET_802.2 = "no"
ETHERNET_II = "no"
ETHERNET_SNAP = "no"
TRACE = 0x0
IBMTOK_nifU
DriverName = IBMTOK$
ADAPTER = "PRIMARY"
NETADDRESS = "400005d01234"
MAXTRANSMITS = 6
RECVBUFS = 2
RECVBUFSIZE = 512
XMITBUFS = 1
XMITBUFSIZE = 2040
5) You are now finished with the install and configure for
coexistence with ODI2NDI.OS2. Shut down and reboot your
system.
--------------------------------------------------------------
NetWare, NetWare Client for OS/2, and NetWare Requester for OS/2
are trademarks of Novell, Inc.
Thank you for calling Software Solution Services. Regarding the
problem reported to the support line, we feel that this information
may assist you in resolving your problem. If you still require
assistance, please call 1-800-992-4777 again, and you will be
connected to the appropriate support personnel.
IBM disclaims all warranties, whether expressed or implied, including
without limitation, warranties of fitness and merchantability with
respect to the information in this document. By furnishing this
document, IBM grants no licenses to any related patents or copyrights.
If you identify errors or have comments about this document, please let
us know. We will make every effort to correct errors and improve the
quality of this document.
Please FAX your comments to&colon.
(512) 823-9495
IBM
Attn: CBR Express Team
Thanks!
*****
LAST UPDATED 6/08/94
(END)
12/31/99