I know, but there is no way, to see what it sends to the modem/TA in
ifcico.. :(
But imho bt is simply the best.
BinkleyTerm XE keeps the
comport for it's exclusive use, and wioth only two comports available
for use, well that is not a good, use of resources from my point of view. :-)
Each unto his own, preferances that is. <BG>
I know, but there is no way, to see what it sends to the
modem/TA in ifcico.. :(
But imho bt is simply the best.
BinkleyTerm XE keeps the
comport for it's exclusive use, and wioth only two comports
available for use, well that is not a good, use of resources
from my point of view. :-)
Yeah we talked about that, but there should be somekind of suspend
option in BTXE. But binkleyterm is the only mailer i'm feeling safe
about, so i'll use it :-)
And i shutdown the mailer if i shall use somekind of other problem.
Each unto his own, preferances that is. <BG>
:-)
I know, but there is no way, to see what it sends to the
modem/TA in ifcico.. :(
tail -f /opt/mbse/log/system.log gives me a similar indication of
what is
being done during a connection, as happens while Binkley term does,
with
"mbcico" which is a ifcico derivative work.
Yeah we talked about that, but there should be somekind of suspend
option in BTXE. But binkleyterm is the only mailer i'm feeling safe
about, so i'll use it :-)
Well, it seems that it is the only one that will work with Maximus
for
Linux/FreeBSD, so on my Maximus system, I will also use it. <grin>
And i shutdown the mailer if i shall use somekind of other problem.
Can live with that, ...
BinkleyTerm XE keeps the comport for it's exclusive use, and wioth
only two comports available for use, well that is not a good, use
of resources from my point of view. :-)
Yeah we talked about that, but there should be somekind of
suspend option in BTXE. But binkleyterm is the only mailer i'm
feeling safe about, so i'll use it :-)
Well, it seems that it is the only one that will work with Maximus for Linux/FreeBSD, so on my Maximus system, I will also use it. <grin>
BinkleyTerm XE keeps the comport for it's exclusive use, and
wioth only two comports available for use, well that is not a
good, use of resources from my point of view. :-)
Yeah we talked about that, but there should be somekind of
suspend option in BTXE. But binkleyterm is the only mailer i'm
feeling safe about, so i'll use it :-)
Well, it seems that it is the only one that will work with
Maximus for Linux/FreeBSD, so on my Maximus system, I will also
use it. <grin>
Not sure what your problem is based on the above but,... Binkleyterm
will pass to the bbs the comport used and thereafter the bbs takes
over the com port until finished when it is passed back to binkley.
If you need to use the com port for other purposes such as Fax then
you need to set that up within the binkley config file.
I know, but there is no way, to see what it sends to the
modem/TA in ifcico.. :(
tail -f /opt/mbse/log/system.log gives me a similar indication of
what is being done during a connection, as happens whileBinkley term does, with "mbcico" which is a ifcico derivative
work.
Still the thing i'm missing is the Alt-V feature in Binkleyterm
neither mgetty or mb/ifcico can provide that.
Yeah we talked about that, but there should be somekind of
suspend option in BTXE. But binkleyterm is the only mailer i'm
feeling safe about, so i'll use it :-)
Well, it seems that it is the only one that will work with
Maximus for Linux/FreeBSD, so on my Maximus system, I will also
use it. <grin>
:-)
And i shutdown the mailer if i shall use somekind of other
problem.
Can live with that, ...
i meant 'program whitch should use the modem' :)
No problem, as such, just that Binkley Term controling the "Com Port"
is not as flexable or convient to use as mgetty/getty_ps and mbcico/ifcico. For the most part, call it personal preferance if you
must. :-)
If you need to use the com port for other purposes such as Fax
then you need to set that up within the binkley config file.
Fax, I seldom use, but PPP is something I use a lot.
Hmm, PPP might be a problem but, if you can call the PPP dialer (etc)
from within Binkley then as above it will release the com port.
If you need to use the com port for other purposes such as Fax
then you need to set that up within the binkley config file.
Fax, I seldom use, but PPP is something I use a lot.
Hmm, PPP might be a problem but, if you can call the PPP dialer (etc)
from within Binkley then as above it will release the com port.
Hmm, PPP might be a problem but, if you can call the PPP dialer
(etc) from within Binkley then as above it will release the com
port.
It _should_ be possible to start pppd from binkley, afaik in the documentation (if you can start a fax utility, you should could start
a pppd)..
If you need to use the com port for other purposes such as Fax
then you need to set that up within the binkley config file.
Fax, I seldom use, but PPP is something I use a lot.
Hmm, PPP might be a problem but, if you can call the PPP dialer (etc)
from within Binkley then as above it will release the com port.
No idea, if it can be done from within Binkley, but I
doudt it as I have seen
no reference to Binkly being able to reconise a
incoming PPP call, nor a way
for it to release the port for a outgoing PPP call.
Fax, I seldom use, but PPP is something I use a lot.
Hmm, PPP might be a problem but, if you can call the PPP dialer
(etc) from within Binkley then as above it will release the com
port.
No idea, if it can be done from within Binkley, but I doudt it as I
have seen no reference to Binkly being able to reconise a incoming PPP call, nor a way for it to release the port for a outgoing PPP call.
It _should_ be possible to start pppd from binkley, afaik in the
documentation (if you can start a fax utility, you should could
start a pppd)..
Starting PPPD from Binkley should not be a problem, but getting
Binkley to reconise a incoming PPP call, and then start PPPD, I
believe is.
Hmm, PPP might be a problem but, if you can call the PPP dialer
(etc) from within Binkley then as above it will release the com
port.
No idea, if it can be done from within Binkley, but I
doudt it as I have seen
no reference to Binkly being able to reconise a
incoming PPP call, nor a way
for it to release the port for a outgoing PPP call.
I have been tracking having Binkley run PPP as an external protocol
for use under OS/2.... I've seen some comments, that in theory, it is possible to do. One catch is knowing the first characters to see from
the remote end to determine the call is PPP (instead of FIDO or
something else). This is needed to hook in an extern (like FAX)
protocol. I have seen reference to running UUCP code under Binkley in
an OS/2 environment....
So, just as mgetty(?) can answer and hand off a PPP call, Binkley
should be able to perform the exact same function. I might have to
dig into the mgetty (or other appropriate software) to figure out what
the initial characters of the PPP handshake are, but once you know
those, the external protocol options in Binkley should be usable to
spawn a program to start up a needed PPP connection....
So, it should be do-able.... It may take some effort to figure
everything out.
Fax, I seldom use, but PPP is something I use a lot.
Hmm, PPP might be a problem but, if you can call the PPP dialer
(etc) from within Binkley then as above it will release the com
port.
No idea, if it can be done from within Binkley, but I doudt it as
I have seen no reference to Binkly being able to reconise a
incoming PPP call, nor a way for it to release the port for a
outgoing PPP call.
Ahh, sorry I thought you was referring to an outgoing call.
It _should_ be possible to start pppd from binkley, afaik in the
documentation (if you can start a fax utility, you should could
start a pppd)..
Starting PPPD from Binkley should not be a problem, but getting
Binkley to reconise a incoming PPP call, and then start PPPD, I
believe is.
Yeah! That's kinda tricky.. That's quite easy with mgetty, but i
suppose it would be a problem with bt :(
Starting PPPD from Binkley should not be a problem, but getting
Binkley to reconise a incoming PPP call, and then start PPPD, I
believe is.
Yeah! That's kinda tricky.. That's quite easy with
mgetty, but i suppose it would be a problem with bt :(
Yeah! That's kinda tricky.. That's quite easy with
mgetty, but i suppose it would be a problem with bt :(
Ok....
(1) Look up the initial characters sent to mgetty so that mgetty
knows that a PPP handshake is requested....
(2) Look up how to insert an external protocol for use with Binkley.
I believe this is one way fax reception can be handled.....
(3) Hook the PPPD daemon up to be called from binkley as an external protocol based on reception of the first (few) characters of the
initial PPP hand shake sequence.....
Starting PPPD from Binkley should not be a problem, but getting
Binkley to reconise a incoming PPP call, and then start PPPD, I
believe is.
Yeah! That's kinda tricky.. That's quite easy with mgetty, but i
suppose it would be a problem with bt :(
Hmmm ... yes, in it's current form, I think it is a problem, but I
also have no idea, what it will take to solve it, tho in a
previous post Bob Jones seems to have a reasonably good understanding/appreciation for the problem and a possible
solution.
So there is still hope fpr Binkley, yet. :-))
Ofcause there is, it's still the best :-)
Ofcause there is, it's still the best :-)
then there is not much hope for the rest :-)
but why is BTXE not using the connect strings ?
so it can deliver the incomming call to the right program like pppd
:)
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,044 |
| Nodes: | 15 (0 / 15) |
| Uptime: | 28:43:16 |
| Calls: | 236,098 |
| Files: | 60,370 |
| D/L today: |
43 files (38,067K bytes) |
| Messages: | 289,236 |