Hi Howard,
<<Howard Eisenberger:As far as I know, PPPDRC.CFG contains the arguments
to EPPPD and WATTCP.CFG contains the arguments to the stack (and
application). Idon't think that EPPPD looks at WATTCP.CFG.>
Correct. Sometimes it's hard to explain what I'm seeing to
others who are viewing from a different perspective :)
What I was saying was that using Netdial I don't
use the PPPDRC.CFG file and (separately) that the inclusion
of a COMn value for EPPPD to work is not required, except
for Arachne's MiniTerm dialer if I recall.
The Include capability I was mentioning for WATTCP was that
taking BobCat for an example, I can, in that apps config file
include 1 or more Include = c:\path\filename here lines
in the Config file to make it part of th configuration file,
something I had hoped Arachne.cfg would have so that when
we get a new version we could separate the parts that we want
to keep constant from the parts that are variable by machine,
dial in number etc.
I use the Netdial.bat file to write the session IP and other
environment variables that are in one of the include files,
much in the same way that Arachne writes PPP.LOG, I just write
it all one time and then each of the apps I switch between
during a single dial session can all use the same information
as needed.
<<my batch file uses the environment variables from IP-UP.BAT
to write to WATTCP.CFG much like Netdial and the samples
in the Dospppd documentation.>>
Yep, same thing except I don't write to a different file name and
don't use the IP-UP as a separate .bat file, just an implementation
variance :) I prefer the Netdial scripts to the Chat scripts
because I can use comments and still read the thing when I don't
change it for 6-8 months and figure out what I was doing <g>.
Bob Buckland ?:-)
