Bill Oconnor wrote in a message to Mike Bilow:

 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.

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

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

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

 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.  If what you were implying is that
 BO> you must run the above ccslip.cmd in order to make a slip
 BO> connection, then I would say you are absolutely right, as
 BO> that is all one need do.

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.  This can involve interface
configuration, IP routing, starting services, and so on.  All of the
standard TCP/IP management tools assume that PM is running, so you are
reduced to a text editor and intimate knowledge about obscure files if you
want to run TCP/IP without PM.
 
-- Mike


---