Hello Bob.

18 Jul 03 22:03, you wrote to me:

 VC>> Hmm, PPP might be a problem but, if you can call the PPP dialer
 VC>> (etc) from within Binkley then as above it will release the com
 VC>> port.

 RT>> No idea, if it can be done from within Binkley, but I
 RT>> doudt it as I have seen
 RT>> no reference to Binkly being able to reconise a
 RT>> incoming PPP call, nor a way
 RT>> for it to release the port for a outgoing PPP call.

 BJ> I have been tracking having Binkley run PPP as an external protocol
 BJ> for use under OS/2....  I've seen some comments, that in theory, it is
 BJ> possible to do.  One catch is knowing the first characters to see from
 BJ> the remote end to determine the call is PPP (instead of FIDO or
 BJ> something else).  This is needed to hook in an extern (like FAX)
 BJ> protocol.  I have seen reference to running UUCP code under Binkley in
 BJ> an OS/2 environment....

 BJ> So, just as mgetty(?) can answer and hand off a PPP call, Binkley
 BJ> should be able to perform the exact same function.  I might have to
 BJ> dig into the mgetty (or other appropriate software) to figure out what
 BJ> the initial characters of the PPP handshake are, but once you know
 BJ> those, the external protocol options in Binkley should be usable to
 BJ> spawn a program to start up a needed PPP connection....

 BJ> So, it should be do-able....  It may take some effort to figure
 BJ> everything out.

My thoughts too, I don't think that, until recently, much thought has been 
directed to how Binkley would re-act/inter-act on a system needing 
incoming/outgoing PPP connections, on it's tradional operating systems such a 
requirement did not exist.

Thanks for your reply,

Russell

--- GoldED+/LNX 1.1.4.7