Can BinkleyTerm be passed a hot com port ? eg. BGFax answers a call and then passes data calls to BinkleyTerm.

I know that BinkleyTerm can use the ExtrnMail fax handling method, but this is not what I want.


--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

Can BinkleyTerm be passed a hot com port ? eg. BGFax
answers a call and then passes data calls to
BinkleyTerm.

I know that BinkleyTerm can use the ExtrnMail fax
handling method, but this is not what I want.

Depends on how you are starting up the program.

In batch files, under the WIN32 version of DOS command.com, the problem with using batch files to start a second program (such as Binkley to a BBS) is that command.com drops DTR, which for most setups will hang up on the caller. So, it depends on methods used.

As to Binkley, I believe it was designed to call the fax software and not have the fax software call it. At a minimum you will need to tweak the init strings
in binkley. And you would need to find a setup that lets you properly terminate binkley after each call.... Probably doable, but the reverse logic that I've seen most systems running Binkley use.....

I think there is a way to have binkley call BGFax for fax handling. There is definately a way to have Binkley handle the fax calls along with the data calls..... Why reverse the process?

Bob Jones, 1:343/41


--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

I know that BinkleyTerm can use the ExtrnMail fax
handling method, but this is not what I want.

Depends on how you are starting up the program.

In batch files, under the WIN32 version of DOS
command.com, the problem with using batch files to
start a second program (such as Binkley to a BBS) is
that command.com drops DTR, which for most setups will
hang up on the caller. So, it depends on methods used.

So you're basically saying that the DOS version of BinkleyTerm can't run spawnbbs.bat under Windows 2000 ?

I'd have to use thw Win32 BinkleyTerm or WinFOSSIL to get it to work ?

As to Binkley, I believe it was designed to call the
fax software and not have the fax software call it. At
a minimum you will need to tweak the init strings in
binkley. And you would need to find a setup that lets
you properly terminate binkley after each call....
Probably doable, but the reverse logic that I've seen
most systems running Binkley use.....

Somewhere in Bt-ref.txt mentions leaving DTR high, but that might have been related to terminal mode.

Even if I left DTR high when calling "bt unattended", BinkleyTerm would need to
know that a connection had been made ie. "CONNECT" needs to be sent. Otherwise I doin't see BinkleyTerm doing anything with the live line after it enters unattended mode ... it would just sit there until the remote end hangs up.

I think there is a way to have binkley call BGFax for
fax handling. There is definately a way to have
Binkley handle the fax calls along with the data
calls..... Why reverse the process?

I want to see if I can pass telnet callers to BinkleyTerm without using virtual
modem or virtual com port methods.

FrontDoor can do it, so I want to see if BinkleyTerm could.

--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

In batch files, under the WIN32 version of DOS
command.com, the problem with using batch files to
start a second program (such as Binkley to a BBS) is
that command.com drops DTR, which for most setups will
hang up on the caller. So, it depends on methods used.

So you're basically saying that the DOS version of
BinkleyTerm can't run spawnbbs.bat under Windows 2000 ?

I believe any program using DTR to control the modem can't use the batch method
under a Win32 system (such as windows 2000). Doesn't matter if it is a Win32 program or a DOS based program. If the program starts command.com to run a batch file to start the next program, I believe it will drop DTR.

I'd have to use thw Win32 BinkleyTerm or WinFOSSIL to get it to work ?

I believe Win32 version of binkley using a batch file would also fail. Using the Win32 version of binkley with the internal spawning method should work. I would expect the winfossil option to also fail.

As to Binkley, I believe it was designed to call the
fax software and not have the fax software call it. At
a minimum you will need to tweak the init strings in
binkley. And you would need to find a setup that lets
you properly terminate binkley after each call....
Probably doable, but the reverse logic that I've seen
most systems running Binkley use.....

Somewhere in Bt-ref.txt mentions leaving DTR high, but
that might have been related to terminal mode.

Most BBS software uses DTR for controlling the modem to hang up. If DTR is dropped (to low), the call is hung up on. This requires the modem to be configured to use DTR....

Even if I left DTR high when calling "bt unattended",
BinkleyTerm would need to know that a connection had
been made ie. "CONNECT" needs to be sent. Otherwise I
doin't see BinkleyTerm doing anything with the live
line after it enters unattended mode ... it would just
sit there until the remote end hangs up.

Ah, yes. Bink does look for the connect string to start things, at least the normal way it is run. Well, you have source code available to you if you want to change something.... Just make sure the modified version is properly renamed / documented per what the licensing documentation calls for.

I think there is a way to have binkley call BGFax for
fax handling. There is definately a way to have
Binkley handle the fax calls along with the data
calls..... Why reverse the process?

I want to see if I can pass telnet callers to
BinkleyTerm without using virtual modem or virtual com port methods.

Ah.... I don't know of folks using binkley without such. But I'm also not using the versions after 2.60 of Binkley. You may need to look at the later development to see if there are options to do what you want. I don't think most BBS software has been converted to properly use TCP/IP signals for session
hang up versus simulated modem controls.

FrontDoor can do it, so I want to see if BinkleyTerm could.

Ok..... Then look for BinkleyTerm after 2.60, which is strictly third part development.

Remember Binkley was developed for modem controlled communications, not IP based communications.....

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

Hello, Mvan...

I spent some time on this, and eventually gave up. If I remember correctly, the
problem had to do with ownership of the port. When BinkleyTerm exits, the port becomes owned by the shell and it won't give it back, or something like that. You might try it using CMD.com, rather than the 16-bit shell, but I think it would have occurred to me to try that.


Regards,

Jerry Schwartz

mailto:jerryschwartz@comfortable.com
http://www.writebynight.com

--- Msged/NT 6.0.1
* Origin: Write by Night (1:142/928)