da Silva, Joe wrote:
> OK, David has sent me a copy of LSPPP 0.71, which
> closes STDOUT before "going resident" ...
Are you sure it is compatible with all DOS flavours ?
I vote rather for modifying Arachne scripting to not require
redirection of PPP log to file. I think logging option is
best solution, and Arachne will just type lsppp.log>>ppp.log,
and we are done.
I would also appreciate some API for detection of modem line
status - currently, Arachne is not able to detect whether PPP
conenction was lost, or not. Arachne should be able to detect it,
so termin.com 0x60 can be called, and connection automaticaly
re-initiated. In Linux, it is easy to see whether PPP inteface
is up or down...
> You will be pleased to know, this solves all the "file
> sharing violation" problems when LSPPP's output is
> redirected to PPP.LOG and, contrary to Clarence's
> fears, does not make STDOUT disappear (for other
> applications or COMMAND.COM) when the output
> is either not redirected, or is redirected to NUL. :-)
Well, if it work for all DOSes...
> BTW, David has also fixed the "packet driver statistics"
> (aka "TCP/IP statistics") ... :-)
And what about connectivity statistics ? I don't know much
about it, all this DTR up/down stuff, but I would like to
be able to check whether remote party hung up the connection...
> One minor problem has been introduced, which David
> will no doubt rectify shortly, in that LSPPP 0.71 does
> not return a zero "errorlevel", even when everything
> is fine ... Oh, well! :-/
I think I will stuck with 0.7 for Arachne 1.71. I am sorry
I haven't started testing yet...
