Hi John:

JZ>  -=> Quoting Mike Bilow to Bill Oconnor <=-
JZ> 
JZ>  MB> driven from TCPSTART.CMD which is placed in the WPS Startup folder by
JZ>  MB> default.  No PM, no Startup folder.
JZ> 
JZ> When I installed WARP Connect over here, a call to 
JZ> TCPSTART.CMD was placed in the CONFIG.SYS by the install 
JZ> program.  The startup folder was empty after the install.
JZ> 
JZ> Perhaps certain install options determine where 
JZ> TCPSTART.CMD is invoked from, like wether the peer services 
JZ> were installed, etc.
JZ> 
JZ> John

Could you possibly be thinking of MPTSTART.CMD???

CALL=C:\OS2\CMD.EXE /Q /C C:\MPTN\BIN\MPTSTART.CMD

I've installed WARP Connect on dozens of machines with differing
configurations and I've never seen a call to TCPSTART.CMD in the
CONFIG.SYS.  Of course, I'm sure that there are more configurations
options, which I haven't tried, than I could imagine.


Best wishes,

Tom

 * KWQ/2 1.2g * Polaroids: what polar bears get from sitting on icecaps

--- GEcho/2 1.20/Pro