TITLE:  LANtastic for OS/2 v1.0 and IBM TCP/IP v2.x for 

OS/2 Interoperability Bulletin

UPDATED:        10.31.95

AUTHOR: JS

This bulletin presents technical information about one topic 

related to your LANtastic network.  Bulletins are available to 

help you with many aspects of managing or enhancing your network 

and with the installation of many compatible products. Bulletins 

are available:

  By fax from the Artisoft FaxReturn System at (520) 884-1397; 

request document 2 for a current list of all available 

bulletins, document 2001 for a list of compatible applications 

and other software, document 2044 for a list of compatible 

network interface cards and other hardware;

  Through the Artisoft Home Page http://www.artisoft.com on the 

World Wide Web;

  As ASCII text or Acrobat Text Enriched (PDF) files from the 

Artisoft Arti-Facts BBS at (520) 884-8648 (1200 baud - 28.8 

Kbps, 8 data bits, 1 stop bit, no parity, full duplex), the GO 

ARTISOFT forum on CompuServe, or the Artisoft anonymous FTP 

site ftp.artisoft.com; download !BLTXREF.TXT from the BULLETIN 

section for a current list of all available bulletins, 

APPCOM.TXT for a list of compatible applications and other 

software, NICCOM.TXT for a list of compatible network 

interface cards and other hardware.



Problem         

	The installation programs of LANtastic for OS/2 and IBM TCP/IP 

for OS/2 v2.x dont correctly detect a previously installed 

copy of each other. After installation, the OS/2 system files 

may not be properly configured for simultaneous operation of 

both protocol stacks.



Solution        

	Integrate the changes made by both installation programs to 

the CONFIG.SYS and PROTOCOL.INI files to produce a working 

configuration that will allow both protocol stacks to operate 

correctly.



Requirements 

  IBM OS/2 Operating System, version 2.1 or above

  LANtastic for OS/2, version 1.0

  IBM TCP/IP version 2.x for OS/2



Objectives 

  Integrate the changes made to the CONFIG.SYS file by both 

programs.

  Incorporate the sections needed by both stacks into a single 

PROTOCOL.INI file.



Procedure 

This section contains the following four subsections. Go 

directly to the one that reflects your current situation.

n       Both products are installed

n       Neither product is installed

n       LANtastic for OS/2 is installed

n       IBM TCP/IP v2.0 is installed

Both products are installed -- 

Regardless of which installation came first, LANtastic for 

OS/2 or IBM TCP/IP, the end result will be the same: both the 

CONFIG.SYS and the PROTOCOL.INI files will have to be updated 

to reflect the mixed installation. Some initial preparation 

will make the update process easier. Follow the example below 

that most closely matches your setup.

Note: In all of the following explanations and examples, the 

LANtastic for OS/2 home directory is referred to as 

C:\LANTASTI\OS2, and the LAPS home directory as C:\IBMCOM. 

Your actual drive and/or paths to these directories may be 

different. IN ALL CASES, unless otherwise noted, substitute 

your actual drive/path in place of the drive/path listed in 

this document.

Neither product is installed --

If you have installed neither package at this point, the 

preferred method is to install LANtastic for OS/2 first, 

especially if you have an AE-2, AE-3, or NodeRunner adapter, 

as the IBM package does not include drivers for these cards. 

Make sure that LANtastic for OS/2 is communicating properly on 

the network prior to installing the IBM product. Once that is 

accomplished, go to the next section.

LANtastic for OS/2 is installed --

If you already have LANtastic for OS/2 installed on your 

machine, and plan on installing IBM TCP/IP as well, 

temporarily disable LANtastic for OS/2, so that IBMs LAN 

Adapter and Protocol Support (LAPS) manager does not become 

confused by the currently running protocol manager for 

LANtastic. To accomplish this:



1. Open the LANtastic for OS/2 icon on your desktop, then 

open the LANtastic Utilities folder.

2. Choose View or Change CONFIG.SYS.

3. Locate the lines that read LASTDRIVE=Z and 

IFS=C:\LANTASTI\OS2\LANTASTI.IFS. Add the letters REM and 

one space to the beginning these lines, and all lines in 

between. For example:



REM LASTDRIVE=Z

REM SET NWDBPATH=C:\LANTASTI\OS2\NW

REM DEVICE=C:\LANTASTI\OS2\LANMSGDD.OS2 

/I:C:\LANTASTI\OS2

REM DEVICE=C:\LANTASTI\OS2\PROTMAN.OS2 

/I:C:\LANTASTI\OS2

REM DEVICE=C:\LANTASTI\OS2\AEXNDIS.OS2

REM DEVICE=C:\LANTASTI\OS2\AI-NDIS.OS2

REM DEVICE=C:\LANTASTI\OS2\AILANBIO.OS2

REM DEVICE=C:\LANTASTI\OS2\NETBIOS.OS2

REM DEVICE=C:\LANTASTI\OS2\LANPDD.OS2

REM DEVICE=C:\LANTASTI\OS2\LANVDD.OS2

REM DEVICE=C:\LANTASTI\OS2\IFS2NB.OS2

REM RUN=C:\LANTASTI\OS2\NETBIND.EXE

REM RUN=C:\LANTASTI\OS2\LTDAEMON.EXE

REM IFS=C:\LANTASTI\OS2\LANTASTI.IFS



4. Save and exit the file.

5. Close all running programs, and shut down and reboot the 

machine.

6. When the desktop reloads, you may receive a pair of 

Network error (fc) messages, one from Restore LANtastic 

server, and one from Restore LANtastic Network. You can 

safely ignore these errors and click OK.

7. Now you can install the IBM TCP/IP package per 

instructions. If you have one of the previously mentioned 

Artisoft adapters, or some other adapter that isnt 

listed, choose one of the 3COM adapters from the list in 

order to complete the installation process. 

8. Once the TCP/IP install is completed, shut down and 

reboot the machine.

9. If your adapter was supported, verify TCP/IP 

communications at this point before going to the next 

step. If you did not have one of the supported adapters, 

you will receive several errors during the boot-up 

process, ignore them and proceed to the desktop.

a) Open an OS/2 window, and go to the C:\LANTASTI\OS2 

subdirectory.

b) If you have one of the Artisoft adapters mentioned, 

copy the file AEXNDIS.OS2 to the C:\IBMCOM\MACS 

subdirectory. If you have a third party adapter, copy 

its driver to the same directory as above.

c) Copy all of the *.NIF files to the C:\IBMCOM\MACS 

directory. For example:



COPY *.NIF C:\IBMCOM\MACS



d) Change directory to the C:\IBMCOM subdirectory, and run 

the LAPS program by typing LAPS at the OS/2 command 

prompt. Click Configure, confirm that the Configure LAN 

transports radio button is selected, then click 

Continue... .

e) Your adapter should now be listed in the Network 

Adapters window. Click it, then click Change to replace 

the 3COM adapter. Be sure to choose the Edit button 

under Current Configuration to set up any critical 

parameters for your adapter, such as I/O Base or IRQ. 

When youre finished, click OK, and follow the prompts 

to save the information.

f) Shut down and reboot the machine. When the desktop 

comes back up, confirm proper TCP/IP communications 

before proceeding to the next step.



10. Once proper TCP/IP communications have been established, 

you can begin combining the two installs. To accomplish 

this:



CONFIG.SYS - 

a) Follow steps 1 and 2 above for editing the CONFIG.SYS 

file.

b) Remove the remark (REM) statements from the lines 

mentioned in step 3 above.

c) Use the built-in Edit|Copy and Edit|Paste functions in 

the editor to arrange the LANtastic and TCP/IP 

statement according to the CONFIG.SYS example listed at 

the end of this bulletin.

d) Save the file and exit.



PROTOCOL.INI - 

a) Open an OS/2 window, and change directory to 

C:\LANTASTI\OS2. Then type:



EPM PROTOCOL.INI



This starts the Enhanced Editor, and loads the 

LANtastic for OS/2 PROTOCOL.INI file.

b) Click File|Open to bring up the Open dialog box. Click 

File list..., then double-click the C:\ folder. Scroll 

through the Directory: list box until you locate the 

IBMCOM folder, then double-click it. Next, scroll 

through the File: list box until you locate the 

PROTOCOL.INI file, then double-click it. This will 

start a second instance of the Enhanced Editor loaded 

with the LAPS PROTOCOL.INI.

c) Click File|Save as... and enter PROTOCOL.OLD in the 

Save as filename: field, then click Save As.

d) You can now use the Edit|Copy and Edit|Paste commands 

to copy and paste the relevant portions of the 

LANtastic PROTOCOL.INI into the LAPS PROTOCOL.INI, 

following the example provided below. Keep in mind that 

it is the LAPS PROTOCOL.INI that will be used by both 

network stacks after the modifications are complete.





e) After the LAPS PROTOCOL.INI has been modified to 

reflect the provided example, repeat step c) above, 

only enter the filename as PROTOCOL.INI this time. 

Confirm that you want to overlay the exiting file by 

clicking OK. Save the file and exit both instances of 

the Enhanced Editor. If the LANtastic copy of 

PROTOCOL.INI prompts you to save the file before 

exiting, choose no, as this file should not have been 

modified.



11. Now that both of the files have been modified to reflect 

both network stacks, shut down and reboot the machine, 

watching closely for any errors that might occur during 

the boot-up process. When the machine is fully up and 

running, test both protocols for proper connectivity.



IBM TCP/IP v2.0 is installed --

If youre adding LANtastic for OS/2 to an existing IBM TCP/IP 

version 2.0 install, verify that the TCP/IP protocol and 

drivers are functioning correctly, then perform the following 

steps for proper setup:



1. Boot up the machine as you normally would. Place the 

LANtastic for OS/2 diskette #1 into the drive.

2. Open an OS/2 window, switch to the install disk drive, 

and type SETUP <Enter>.

3. Fill in the appropriate registration information and 

follow the installation instructions until you reach the 

screen prompting for Type of Installation: Quick or 

Custom. In this case you should choose Custom.

4. Give the machine a name for your LANtastic network. The 

name you choose does not have to match the TCP/IP 

hostname, but can be the same for simplicity. You can 

also set the target drive and directory for the install, 

but in most cases it is appropriate to go with the 

defaults. Click OK.

5. The LANtastic Options dialog box will appear, allowing 

you to choose to make the machine a LANtastic server, and 

to enable SMB support. Choose the options you want and 

click OK.

6. As there is already a functioning NDIS driver in the 

system, it can be used for the LANtastic installation as 

well. When the Network Adapter Selection dialog box 

appears, notice that the lower portion of the window 

under No Adapter Settings is empty. Click the Use NDIS 

driver for non Artisoft adapter radio button. Enter 

C:\IBMCOM in the Drive and directory to search for driver 

window and click Search. A Please Wait dialog will 

appear, indicating that SETUP is searching for the 

adapter driver file. Another dialog window will appear 

indicating whether or not SETUP has located the file.

7. If the file is located and loaded, the lower section of 

the window will have information regarding the loaded 

NDIS driver, and how it is currently configured.



a) If these settings reflect the current state of your 

network card, click OK.

b) If the settings dont accurately reflect the current 

state of your network card, set them accordingly. Click 

OK to continue.

c) If SETUP failed to locate the card file, it will issue 

the error message NDIS Driver Search Error: Protocol 

file PROTOCOL.INI not found in C:\IBMCOM subdirectory 

tree. Check the drive and path string which you 

entered in that field for correctness. If you cannot 

get SETUP to find the file on the hard drive, place the 

driver diskette from your Ethernet card into the drive. 

d) Enter the path to the disk drive and click Search. 

SETUP should now locate the driver and indicate a 

successful load. Change the adapter settings to match 

your card, and click OK.



8. The install Summary screen will display information and 

choices made during SETUP. If any of these appear to be 

incorrect, you can change them at this point by clicking 

on the appropriate button. Once youre satisfied with 

your selections, click Install to continue.

9. SETUP will now copy the LANtastic for OS/2 files to the 

hard drive.

10. Once file extraction is complete, SETUP will prompt you 

with a Modify CONFIG.SYS File? dialog box. Click the Save 

the required changes to new file: radio button, then 

Click OK. This will save the proposed LANtastic changes 

to the CONFIG.SYS file to the file C:\CONFIG.NEW instead.

11. A dialog box labeled PROTOCOL.INI Note appears, advising 

you that the changes to the PROTOCOL.INI file will be 

saved to C:\LANTASTI\OS2\PROTOCOL.NEW. Click OK to 

continue.

12. The LANtastic Installation Complete window signals 

successful completion of the installation process. You 

can click View README to read the release notes at this 

point. When youre finished, click Return to OS/2.

13. Exiting SETUP will return you to the OS/2 prompt. Change 

back to the C: drive, and type CD\ to return to the root 

directory.

14. Now that LANtastic for OS/2 is installed, you can begin 

combining the two installs. To accomplish this:



CONFIG.SYS - 

a) From the OS/2 prompt type:



EPM CONFIG.SYS



This will start the Enhanced Editor, and load the 

LANtastic for OS/2 CONFIG.SYS file.

b) Locate the line that states:



RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE



Place your cursor at the very beginning of that line, 

and press the Enter key twice, which will create two 

blank lines above this line. Press the up arrow key 

twice to move the cursor up to the first of the blank 

lines.

c) Click File|Import text file... and click again on the 

File list... . This will bring up the Import text file 

dialog box. Double-click the C:\ folder located in the 

Directory list box. Now scroll through the File: list 

box until you locate the file CONFIG.NEW. Double-click 

this file. The contents of CONFIG.NEW will be pasted 

into the CONFIG.SYS file.

d) Use the built-in Edit|Copy and Edit|Paste functions in 

the editor to arrange the LANtastic and TCP/IP 

statement according to the CONFIG.SYS example listed at 

the end of this bulletin.

e) Save the file and exit. Close the LANtastic Utilities 

and LANtastic for OS/2 folders.



PROTOCOL.INI - 

a) Open an OS/2 window, and change directory to 

C:\LANTASTI\OS2. Type:



EPM PROTOCOL.NEW



This will start the Enhanced Editor, and load the 

LANtastic for OS/2 PROTOCOL.NEW file.

b) Click File|Open to bring up the Open dialog box. Click 

File list..., then double-click C:\ folder. Scroll 

through the Directory: list box until you locate the 

IBMCOM folder, then double-click it. Next, scroll 

through the File: list box until you locate the 

PROTOCOL.INI file, then double-click it. This will 

start a second instance of the Enhanced Editor loaded 

with the LAPS PROTOCOL.INI.

c) Click File|Save as... and enter PROTOCOL.OLD in the 

Save as filename: field, then click Save As.

d) You can now use the Edit|Copy and Edit|Paste commands 

to copy and paste the relevant portions of the 

LANtastic PROTOCOL.NEW into the LAPS PROTOCOL.INI, 

following the example provided below. Keep in mind that 

it is the LAPS PROTOCOL.INI that will be used by both 

network stacks after the modifications are complete.

e) After the LAPS PROTOCOL.INI has been modified to 

reflect the provided example, repeat step c) above, 

only enter the filename as PROTOCOL.INI this time. 

Confirm that you want to overlay the exiting file by 

clicking OK . Save the file and exit both instances of 

the Enhanced Editor. If the LANtastic copy of 

PROTOCOL.NEW prompts you to save the file before 

exiting, choose no, as this file should not have been 

modified.



15. Now that both of the files have been modified to reflect 

both network stacks, shut down and reboot the machine, 

paying close attention for any errors that might occur 

during the boot-up process. When the machine is fully up 

and running, test both protocols for proper connectivity.



Note -  If, after proper setup of these files, you experience 

Trap D errors during operation, obtain the patch file 

OS2P10.EXE from the ArtiFacts BBS at (520) 884-9675.





Examples



This section contains examples of the system files that require 

modification for proper operation of both network protocols. Your 

actual files should follow these examples as closely as possible 

regarding the network drivers.



CONFIG.SYS - This example shows only the lines to be verified or 

modified. Those lines marked with the Adapter Driver 

flag are specific to the network adapter being used in 

your machine, and therefore may vary from the example.

.

.

.

SET 

LIBPATH=D:\LANTASTI\OS2;D:\LANTASTI\OS2\NW;D:\IBMCOM\DLL;.;D:\OS2

\DLL;D:\OS2\MDOS;D:\;D:\OS2\APPS\DLL;D:\MMOS2\DLL;D:\TCPIP\DLL;D:

\CBOS2;

SET 

PATH=D:\LANTASTI\OS2;D:\LANTASTI\OS2\NW;D:\OS2;D:\OS2\SYSTEM;D:\O

S2\INSTALL;D:\;D:\OS2\MDOS;D:\OS2\APPS;D:\MMOS2;D:\TCPIP\BIN;D:\C

BOS2;

SET 

DPATH=D:\LANTASTI\OS2;D:\IBMCOM;D:\OS2;D:\OS2\SYSTEM;D:\OS2\INSTA

LL;D:\;D:\OS2\BITMAP;D:\OS2\MDOS;D:\OS2\APPS;D:\MMOS2;D:\MMOS2\IN

STALL

SET PROMPT=$i[$p]

SET 

HELP=D:\LANTASTI\OS2;D:\OS2\HELP;D:\OS2\HELP\TUTORIAL;D:\MMOS2\HE

LP;D:\TCPIP\HELP

SET BOOKSHELF=D:\LANTASTI\OS2;D:\OS2\BOOK;D:\MMOS2;D:\TCPIP\DOC

.

.

.

DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM 

DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM

.

.

.

LASTDRIVE=Z

SET NWDBPATH=C:\LANTASTI\OS2\NW

rem DEVICE=C:\LANTASTI\OS2\LANMSGDD.OS2 /I:C:\LANTASTI\OS2

rem DEVICE=C:\LANTASTI\OS2\PROTMAN.OS2 /I:C:\LANTASTI\OS2

rem DEVICE=C:\LANTASTI\OS2\AEXNDIS.OS2

DEVICE=C:\LANTASTI\OS2\AI-NDIS.OS2

DEVICE=C:\LANTASTI\OS2\AILANBIO.OS2

DEVICE=C:\LANTASTI\OS2\NETBEUI.OS2

DEVICE=C:\LANTASTI\OS2\NETBIOS.OS2

DEVICE=C:\LANTASTI\OS2\LANPDD.OS2

DEVICE=C:\LANTASTI\OS2\LANVDD.OS2

DEVICE=C:\LANTASTI\OS2\IFS2NB.OS2 /USEDD

rem RUN=C:\LANTASTI\OS2\NETBIND.EXE

RUN=C:\LANTASTI\OS2\LTDAEMON.EXE

IFS=C:\LANTASTI\OS2\LANTASTI.IFS



RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE

RUN=C:\IBMCOM\LANMSGEX.EXE

DEVICE=C:\IBMCOM\PROTOCOL\INET.SYS

DEVICE=C:\IBMCOM\PROTOCOL\IFNDIS.SYS

SET ETC=C:\TCPIP\ETC

SET TMP=C:\TCPIP\TMP

SET READIBM=C:\TCPIP\DOC

SET HOSTNAME=server

RUN=C:\TCPIP\BIN\CNTRL.EXE

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

.

.

.



PROTOCOL.INI - This example shows all of the lines to be included 

in this file. The sections in bold type are those 

that are added from the LANtastic PROTOCOL.INI.



[PROT_MAN]



   DRIVERNAME = PROTMAN$



[IBMLXCFG]



   tcpip_nif = tcpip.nif

   AEXNDIS_nif = AEXNDIS.nif

   NETBEUI_nif    = NETBEUI.nif

   AILANBIO_nif   = AILANBIO.nif

   AILANBIO_nif2  = AILANBIO.nif

   AI-NDIS_nif    = AI-NDIS.nif

   AI-NDIS_nif2   = AI-NDIS.nif 





[NETBIOS]

 DriverName = NETBIOS$

 Adapter0 = ailanb$,0   

 Adapter1 = netbeui$,1

; Adapter0 = ailanb$,0

; Adapter1 = netbeui$,1

; Adapter2 = ailanb2$,2

; Adapter3 = netbeui$,3



[NETBEUI_nif]

 DriverName = netbeui$

 Bindings = ,AEXNDIS_NIF

 ETHERAND_TYPE = "I"

 USEADDRREV = "YES"

 SESSIONS = 128

 NCBS = 128

 NAMES = 32

 SELECTORS = 5

 USEMAXDATAGRAM = "NO"

 ADAPTRATE = 1000

 WINDOWERRORS = 0

 TI = 30000

 T1 = 500

 T2 = 200

 MAXIN = 1

 MAXOUT = 1

 NETBIOSTIMEOUT = 500

 NETBIOSRETRIES = 8

 NAMECACHE = 0

 PIGGYBACKACKS = 1

 DATAGRAMPACKETS = 2

 PACKETS = 350

 PIPELINE = 5

 MAXTRANSMITS = 6

 MINTRANSMITS = 2

 DLCRETRIES = 5



[tcpip_nif]



   DriverName = TCPIP$

   Bindings = AEXNDIS_nif



[AILANBIO_nif]

 DriverName = ailanb$

 Bindings = AI-NDIS_nif

 ACK_TIMEOUT = 2

 ADAPTER = 0

 BUFFERS = 5

 INITIAL_SEND = 570

 IPX_SIZE = 1024

 MAX_NAMES = 32

 MAX_NCBS = 128

 MAX_SESSIONS = 128

 SESSIONS = 128

 NCBS = 128

 RETRY_PERIOD = 2

 RUN_BURST=10

 SIZE = 570

 TIMEOUT = 8

; NO_MULTICAST

; VERBOSE



[AI-NDIS_nif]

 DriverName = AINDIS$

 Bindings = AEXNDIS_NIF

 PROTOCOL_ID = 0

 RECEIVE_BUFFERS = 10

; NO_RECEIVE_HOLDOFF

; ROUTE_ENTRIES = 8



[AEXNDIS_nif]



   DriverName = AEXNDS$    







ARTISOFT TECHNICAL SUPPORT:

Artisoft offers a wide selection of technical support options. 

For information regarding technical support services, please 

refer to our Directory of Support Services, available where you 

obtained this bulletin (request fax document 4, check Support & 

Services at our Home Page, or download file DIRLIST.TXT).  You 

can also obtain this information by calling Artisoft at (520) 

670-7000.

Artisoft makes no warranties as to the completeness or accuracy 

of this document.  Artisoft is not responsible for lost profit or 

revenue, loss of software use, loss of data, cost of re-creating 

data, cost of any substitute equipment or program, or any other 

claim.  Artisoft makes no warranty that complying products will 

operate under any other conditions, or that products will satisfy 

requirements, or that products will be without defect or error, 

or that product operation will be uninterrupted.  Artisofts 

aggregate liability is limited to the total of payments made by 

the customer for the Artisoft product and Artisoft shall not in 

any case be liable for any special, incidental, consequential, 

indirect, or punitive damages, even if it has been advised of the 

possibility of those damages.  LANtastic is a trademark of 

Artisoft, Inc.  Brand names, company names, and product names are 

trademarks or registered trademarks of their respective 

companies.



	LANtastic Technical Bulletin    Page 11 of 11



Artisoft Inc.



Sales: Phone 800-846-9728 Fax: 520-870-7359



2202 Forbes Blvd



Technical Support: Phone 520-670-7000



Tucson, Arizona 85745

