BO> Mike the TCP/IP is initialized in the config.sys by the
 BO> following statements:

 BO> snip------- config.sys entries
 BO> -------------------------------------------rem SLIP stuff
 BO> ********************************************************
 BO> SET ETC=c:\userdir\tcpip\etc
 BO> DEVICE=c:\userdir\tcpip\bin\inet.sys
 BO> DEVICE=c:\userdir\tcpip\bin\ifndisnl.sys
 BO> RUN=c:\userdir\tcpip\bin\cntrl.exe
 BO> snip___________ en config.sys entries

TCP/IP is not started from CONFIG.SYS.  Only the NDIS stack and some other
basic stuff is started from CONFIG.SYS.

Gotcha.

 BO> The .cmd file to startup up slip is as follows:

 BO> snip---------- ccslip.cmd ------------------------
 BO> slip -nocfg -p3 -com1 -speed 38400 -hangup ath -mtu 1500
 BO> -vj -rtscts -ifconfig 0.0.0.0 199.171.196.0 +defaultroute
 BO> -connect "slattach atz OK atdt5067637 38400 \r graphics n
 BO> account: slip:bill\soconnor assword: yourpass
 BO> address\sis:\s[$IPADDR]"
 BO> snip__________ end ccslip.cmd

MB> This applies to a dial-in connection only.  I was speaking MB>
more generally about systems which run TCP/IP on a LAN.  In MB> that
case, substantial additional configuration has to take MB> place, and
this is driven from TCPSTART.CMD which is placed MB> in the WPS Startup
folder by default.  No PM, no Startup MB> folder.

That is all well and good but Alex King was originally looking for info on
running a slip connection using a dialup facility. That is what my reply
was directed at.


 BO> Mike, all I was trying to do is point out that PM is not
 BO> necessary in order to run a slip connection with OS/2 Warp.
 BO> It's no big deal, but your message seemed to indicate that
 BO> this was not the case.


For a LAN, that CMD file can be considerably more complicated. All of the
necessary TCP/IP startup can be done without PM running,but it must be done
manually through CMD files and such.

Gotcha.


regards.......................bill oconnor







--- Maximus/2 2.02