Text 106, 60 rader
Skriven 2005-05-26 22:40:34 av Mike Luther (1:117/3001.0)
    Kommentar till text 105 av Peter Knapper (3:772/1.10)
Ärende: What makes SETUP.CMD in MPTN?
=====================================
Thanks Peter for taking time to help me ..

 PK> For Warp 4, TCPCFG.EXE, or the equivalent for the 
 PK> other versions of OS/2. Thats why its so easy to end 
 PK> up with issues if you mix and match different version 
 PK> of MPTS and TCP/IP and get them out of step.

Aha.  Now I'm seeing why things can get messed up.

 PK> TCPCFG is forced to run...

 PK> If you upgrade from Base Warp 4 and go to MPTS 4.21 or 
 PK> later, then many things change that REQUIRES a new 
 PK> TCPCFG.EXE (TCPCFG2.EXE???), but you only get the new 
 PK> version of TCPCFG if you apply the TCP/IP applications 
 PK> upgrade as well.

Yes .. and in all my cases locally here I've moved to the later versions here
as far as I know.

 PK> Oliver Ricks site is a good source of the ins and outs 
 PK> of these relationships, he can explain it heaps better 
 PK> than I can...

I'll study it again in respect to this focus..

 PK> get your head around that you are fine. Also, TCPCFG 
 PK> has an annoying bug when lines in Config.Sys get 
 PK> longer than about 256 bytes (or something close to 
 PK> that).

Uhhhh..  I thought that was restricted to issues with PEER installs. I've got
such line lengths in most all of my CONFIG.SYS files.  That's why I wound up
installing PEER under Warp 5.2 via the CID technique. The version of things in
the CID install got around that limitation. Then onward into MCP1/2 there
wasn't, as far as I know, any such problem until you got to greater than 512
byte CONFIG.SYS lines.  Which was fixed in I think the third fixpack for PEER
if I recall right.

Now .. after looking at Herbert's tutorial about what all files are involved in
all this, I wonder.

Supposed I 'fix' things by hand editing the SETUP.CMD file.  Then suppose I run
it to do what is 'needed'.  Does the TCPCFG or TCPCFG2 tool then know what I
have added in there for LAN0 and 127.0.0.1 and all that?  Thus when I go in to
look at things with TCPCFG(2) will it be displaying what has been hand edited
in that SETUP.CMD file?  Then, in that the SETUP.CMD file only contains NIC and
certain route information,including hop counts and MTU sizes and so on, I
guess; what about lots of other things that are 'set up' in the TCPCFG(2) tool?
 Such as what is started, Ultimail if you are to use it, and so on?

Thanks..


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001

--- Maximus/2 3.01
 * Origin: Ziplog Public Port (1:117/3001)