Subj : Ezycom & OS/2
To   : Leonard Erickson
From : Mike Tripp
Date : Wed May 14 2003 07:57 am

Hello Leonard!

13 May 03 22:56, Leonard Erickson wrote to Mike Tripp:

 LE> Working Config.sys:
 LE> DEVICE=C:\IBMCOM\LANMSGDD.OSS2 /I:C:\IBMCOM /S
 LE> DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM

 LE> Non-working:
 LE> DEVICE=C:\IBMCOM\PROTOCOL\LAANPDD.OS2
 LE> DEVICE=C:\IBMCOM\PROTOCOL\LANVDD.OS2
 LE> DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S
 LE> DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM


Check your inbound for CONFIG.MJT...if a sample without Peer Services will do 
you any good.  If you need all 3, then I would suggest trying 2 protocol combos 
first, considering order added unique, and then test both protocols.  Then do 
the same by adding the third protocol to the two-protocol combos that passed.

Consider TCP/IP to be the "no brainer" since you actually feed it settings 
later, elsewhere.  Peer and Netware can fail to talk, even though they are 
correctly installed and loaded, due simply to bad settings that are stored 
externally from CONFIG.SYS.

..\\ike

--- GoldED 2.50+
 * Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

.