Howard,
>
As far as I know, PPPDRC.CFG contains the arguments to EPPPD and
WATTCP.CFG contains the arguments to the stack (and application).
I don't think that EPPPD looks at WATTCP.CFG.
Using EPPPD with CHAT and fake BOOTP, PPPDRC.CFG and WATTCP.CFG
never change. Without fake BOOTP (for KA9Q), 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.
>
EPPPD, used with CHAT, can be used to write WATTCP.CFG. EPPPD does not depend
on WATTCP.CFG but does depend on PPPDRC.CFG or other file used in place of
PPPDRC.CFG.
Netdial, as it came with DOSLYNX, creates a file PATH.CFG; actually a .BAT file
rather than Netdial creates PATH.CFG. It would be possible then to have a
WATTCP.CFG with an include line pointing to this PATH.CFG.
Now what is real or fake BOOTP, and how does it work, or does it work? I think
I know what it's supposed to do.
UKA_PPP has its own weird WATTCP.CFG format and seems not to recognize the
include statement. Apparently UKA_PPP decides it's online when it sees an
IP-UP.BAT file, and that works even if IP-UP.BAT has the wrong stuff, as long as
WATTCP.CFG in the UKA_PPP directory is correct. WATTCP.CFG environment variable
must either be undefined or point to UKA_PPP version.
Apparently Arachne looks at WATTCP.CFG environment variable to get the directory
where the appropriate WATTCP.CFG file is located.
