Subj : Ezycom & OS/2
To   : Mike Tripp
From : Leonard Erickson
Date : Thu May 15 2003 03:57 am

-=> Quoting Mike Tripp to Leonard Erickson <=-

MT> Hello Leonard!

MT> 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


MT> Check your inbound for CONFIG.MJT...if a sample without Peer Services
MT> will do you any good.

Well, for starters, I want Netware access to the server. And TCP/IP
connectivity to the Internet. After that, trying to get peering to the
Windows boxes working would be nice.

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

Want me to zip up some config files so you can check them for dumb mistakes?

I can email them to you, or I can use Irex from a Windows box.

--- FMailX 1.60
* Origin: Shadowgard (1:105/50)