--- How to make Netware and TCP/IP Coexist ---

NOTE: Remember to make a backup of your config.sys before you start. It would
also be wise to put this on a floppy along with these instructions in case
something goes wrong (and it will). You also might want to make a hardcopy
of the instructions, and sample files for reference during installation.


This file attempts to explain how to install both the Netware Requester
for OS/2 and IBM's TCP/IP for OS/2 on a typical machine. In this case
a typical machine is defined as an ISA bus machine with a standard
ethernet card.

This explanation also assumes you will be using the odi drivers as the
base drivers. See the "tcpnet.txt" file for using ndis drivers as the base
drivers.

1.  Netware Requester

First obtain the Netware Requester for OS/2. The current version
as of this writing is 2.1. The two main sources for this are:

  ftp-os2.cdrom.com
  ->pub/os2/2_x/network

  ftp.novell.com
  ->pub/novfiles/client.kit/os2/files

The files are:

  wsos21.zip
  wsos22.zip
  wsdrv1.zip
  os2ut1.zip
  os2dc1.zip

(Note that on the novell ftp site, these files will be self-extracting zip files with
a .exe extension.)

Install the Netware Requester following the install program on disk 1 of the requester.
If you're installing on a 3.11 or 3.12 Netware network, you'll want to add this line
to your net.cfg under the Netware Requester section:

directory services off

(Note: If you connect to a 4.01 server, don't include this line.)

My personal suggestion is also to include the following in your config.sys to
log you in to the Novell server. Add this line where you have substituted your
netware path, server name, and user name:

CALL=c:\lan\netware\login.exe utk_apac/hethmon

This will log you in to the server before your startup folder starts. This allows you
to put your network apps in the startup folder and have the drive mappings available
when they look for them. In my case, I use the windows version of QuickMail which
has to have the drive mappings available before it will start correctly.

At this point, you should reboot and verify that the Netware Requester works. It
might also be a good idea to make a backup of your config.sys in case the tcp/ip
installation breaks it.


2. TCP/IP

Now the harder part. Using the tcp/ip install program, go ahead and go through it
all. The question here is whether you should use laps. In my situation, I don't think it
helped at all. If you have some of the hardware listed in the tcp/ip manual, it might
help to use it. What it appears to do is write your protocol.ini file. I would suggest
running it as part of the tcp/ip install and not prior to.

Anyway, follow the instructions and get through the install. Don't reboot at the end!!!!

REMEMBER, DON'T REBOOT WHEN YOU FINISH!!!!!!!!!

3. Coexistence

Now the fun part. What we're going to do is configure things where Novell's odi
drivers control the physical card and tcp/ip talks to them. The first part is to
edit the config.sys file. Open the config.sys file with your favorite text editor.
Find where the tcp/ip statements have been inserted. Take the group of tcp/ip
statements and put them BEFORE the netware statements. Next find where
the IBM mac driver is located in the config.sys file. It will look something
like this:

        DEVICE=C:\IBMCOM\MACS\MACWD.OS2

The driver name may be different, but the directories should be the same, the install
program doesn't give an option to change them. Comment out this line with rem. 

Now go to the requester section and locate your device statement for your card. It
should be similiar to this:

        DEVICE=C:\LAN\NETWARE\SMC8000.SYS

Your driver name may be different. Just under this line, add the following:

        DEVICE=C:\LAN\NETWARE\ODINSUP.SYS

This line loads the odi drivers which allow sharing of your ethernet card. This
completes modifying the config.sys file.

Next find the net.cfg file. There are several things to add in here. First find your
Link Driver section. It should look something like this:

Link Driver SMC8000
        Port 280 10
        Mem d000 2000/10
        Int 5
        Frame Ethernet_II
        Frame Ethernet_802.3
        Frame Ethernet_802.2
        Frame Ethernet_SNAP
        Protocol  IPX 0 Ethernet_802.3
        Protocol   IP 800 Ethernet_II
        Protocol  ARP 806 Ethernet_II
        Protocol RARP 8035 Ethernet_II

The important thing to do to this section is to enable ALL FOUR frame types.
The odinsup driver needs them all. Put what you actually need first, though I
don't think it matters. In my case, I use Ethernet_II and Ethernet_802.3.

Next, we need some protocol sections:

Protocol ODINSUP
        Bind SMC8000
Protocol Stack IPX
        Bind SMC8000
        Sockets 128
Protocol TCPIP
        Bind SMC8000
        ip_address 128.169.15.22
        ip_router 128.169.12.1
        tcp_sockets 8
        udp_sockets 8
        raw_sockets 1

These need to be added/modified as necessary. The general idea here is to bind
your driver to all of the protocols you will be running.

Finally, we're going to modify the protocol.ini file found in the \ibmcom directory.
Here's mine in entirety:

[PROT_MAN]

   DRIVERNAME = PROTMAN$

[IBMLXCFG]

   TCPIP_nif = TCPIP.nif

[TCPIP_nif]

   DriverName = TCPIP$
   Bindings = SMC8000

The main point here is to bind the TCPIP_nif to your card. In my case the
SMC8000.

At this point, you should be ready to reboot and enjoy. 

4. After the Reboot

The thing to do now is to configure your tcp/ip settings. Make sure that your ip address,
subnet, default router, and broadcast address are correct.

If you have suggestions or additions to this file, please mail them to me. All will
be welcome.

Paul Hethmon
hethmon@apac.ag.utk.edu
Agricultural Policy Analysis Center
The University of Tennessee at Knoxville
615-974-3666