This document attempts to explain how to configure the Netware Requester and IBM' TCP/IP product. It uses the ndis drivers as the base drivers. (This explanation courtesy of Dave Scott at the University of Cambridge) Regarding: RE>[Netware and TCP/IP] I grabbed your document and found it good. I have included an alternative way to setup which rigs ODI on top of NDIS to give (I think) an easier alternative. Feel free to use, edit or discard as you see fit ------------------------------------------------------------------------------- Making TCP/IP and Netware coexist - The Alternative Most people use the ODINSUP method to get Netware and TCP/IP to work on the same network adapter. This method basically gives control of the network card to the network driver that is written to the ODI specification that is required for Netware (and is championed by Novell). The ODINSUP program is what is commonly called a 'shim' in that it provides the glue for programs that write to the NDIS spec (like IBM TCP/IP for OS/2). This approach is fine in the main but there is an alternative that has the opposite arrangement. I find this alternative poorly documented (as in not mentioned anywhere I know about) but much easier to setup. This method uses a file ODI2NDI.OS2 as the 'shim' and allows the NDIS driver to control the card with ODI supported on top of that. This is often necessary because some network card manufacturers may only support NDIS drivers (like IBM) or the NDIS driver may be better written or more up-to-date. It also has to do with how you view your network (as a Netware or TCP/IP network primarily). IBM in their wisdom (?) when they supplied the LAPS (Lan Adapter Protocol Support) program disk with the TCP/IP package chose not to include any protocol support other than for TCP/IP. This is the main stumbling block for anyone trying to install via the ODI2NDI method. There are a couple of ways around this. 1) If you have Lan Server use the LAPS disk from there. 2) You can buy something called NTS/2 (This is the way IBM recommends) :-( 3) You can ask IBM or your dealer for the WR7020 CSD for LAPS (available from ftp.informatik.tu-muenchen.de pub/comp/os/os2/lanserver/csds/wr07020.zip) 4) You can get a copy of one of the option disk that comes with an IBM network card (like the etherstreamer) from the IBM BBS. Which of these options you use depend very much on what is available on your site and whatever licencing restrictions are in force. Okay, assuming now your LAPS version is at least to the WR7020 level (use SYSLEVEL to check) you will have support for the Netware requester. The first thing to do is install TCP/IP as per the excellent install procedure. Reboot the machine and make sure that your setup is working fine. Once you are sure everything is okay you are ready to install the Netware Requester. Make a backup of your CONFIG.SYS and PROTOCOL.INI and have a boot floppy ready just in case. During the installation of Netware you will be prompted to name the driver being used DONOT select any of the drivers listed but type C:\IBMCOM\PROTOCOL\ODI2NDI.OS2 (change C: to point to the correct drive for your system). After you have completed the installation go ahead and create your NET.CFG file using the example I have included. When you quit from the intall procedure you are prompted to reboot the system - DONOT do this. Start up LAPS (OS/2 System - System Setup - LAPS icons) select the Netware Requester from the Protocol table and add it so it shows up in the current configuration box. Here is the good bit - double click on the Netware Requester line in the current configuration box to open the option screen for it (or highlight it and press the edit button). Go ahead and enter the various options in there. The defaults are for token ring, if you use ethernet change the token ring stuff to no and the ethernet stuff to yes. That's it, go ahead and save then exit LAPS. Go ahead and reboot your system keeping your fingers crossed. Bootup will now take much longer so don't panic. When I first did this I was presented with a Trap D which turned out to be a know problem on ethernet cards. The solution is to get an older copy of ODI2NDI.OS2 and install that. You can get this from IBM or some FTP site (I used ftp.informatik.tu-muenchen.de pub/comp/os/os2/lanserver/ntsod2nd.zip). The boot floppy I had came into its own here :-) One final thing - I had to rename the TCP/IP LOGIN.EXE file to avoid confusion with the Novell LOGIN.EXE. That as they say is that. Enjoy !!