See below ...
Joe.
> -----Original Message-----
> From: Michael Polak [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, 22 February 2001 9:40
> To: [EMAIL PROTECTED]
> Subject: Re: DOS command line redirection for TSRs
>
>
>
> > You CAN elect to not send anything to STDOUT, which is probably what
> happens
> > when you close the file handle, but this is not the only (or original)
> way
> > to access STDOUT.
> > Or you can use another output method and do an end run around DOS, but
> > I don't see why you would want to.
> >
> > IMHO, _if_ it WAS possible to kill STDOUT, the "cure" would be much
> > worse than the perceived problem.
>
> Redirection of stdout is very old solution, from times,
> when the only way to find which IP address we were assigned
> was to redirect output of PPP.EXE (EtherPPP - 125 KB !!!)
> to file and then parse the file for output address.
>
> As both EPPPD and LSPPP support BOOTP emulation, this method
> is now obsolete, and driver's output won't be redirected to
> PPP.LOG in future releases.
>
[da Silva, Joe]
You are quite correct, Michael. I have always preferred
the BOOTP method, and initially didn't even support the
PPP.LOG method in my LSPPPCFG package. I added
support for this, by popular request, for two reasons :
1. People wanted to put LSPPP's output into PPP.LOG
for diagnostics reasons. This is still a valid reason,
even if you use the BOOTP method ...
2. Current versions of Arachne do not show the
"connect time", unless you select the PPP.LOG
method. No doubt, this will change ... <g>
> I will also give user and option to choose from two PPP
> drivers, because it is always better if users can experiment
> before they complain.
>
