BaudBandit/BackTalk
18 messages in this thread
OK …
As it stands now, I have BackTalk 1.55a, working through
BaudBandit.device. It seems to work fine. The only problem is that it
doesn't work with my serial.device, though ser: works with all other
software.
The interesting thing was that BackTalk 1.55a worked with serial.device
the first time I used it. Then it crashed and never worked with
serial.device again, although I recopied BackTalk, serial.device and
BaudBandit.device.
BTW, BackTalk's configuration window won't accept the name
"BaudBandit.device" because it's too long. There isn't room in the
configuration file (s:BT.CFG), either. So I changed BaudBandit.device to
BBandit.device (it contains a reference to itself, which has to be changed
too).
My system is a 25 MHz A3000 with 2 Mb chip, 4 Mb fast, SCSI HD, and A2286
BridgeBoard. Enforcer is normally running, to make the Bridgeboard work.
Michael,
There is nothing in BackTalk that either modifies itself, or that
modifies serial.device. In fact, nothing that would cause it to work with
serial.device just once, and then never again. I note that you say there's
no room in the config file for a long device name…that's true (it's 15
characters long including the trailing NULL byte)…I hope you didn't try
to edit the config file, that certainly could cause some strange effects.
Don
Thanks. I have called BaudBandit.device "Bandit.device" so it's the same
length as "serial.device". Some programs are having trouble with…
serial.device. The last one I noted was TeleBase (TBASE.LZH in General
Applications). It works if I edit it to use Bandit.device instead. Some
other programs will still work with serial.device. It's weird; I don't know
whose fault it is. For the moment, everything I want to use is working.
I just downloaded BackTalk 1.55a and it doesn't work for me either. It
starts up, and I can access all the menus, except for one thing -it does
not communicate to my modem. It's the only program with this problem —
everything else I have works, including NComm 1.9, NComm 2.0, GT (ADOS 1.3
only), and even Diga!.
My system: A2000 w/5 Meg RAM, GVP Series II w/52Meg Quantum, df0:, df2:,
and df3:, ADOS 2.04 and 1.32 (via Multistart), and Anchor Automation 2400E
modem.
The system's relatively standard, but there is one possible difference.
It's one of the first U.S. 2000's, so old it had the problematic Cherry
keyboard (replaced long ago however). That's the only thing I can think of
— that BackTalk may have a problem with a very early hardware version.
Any ideas?
P.S. I got NComm 2.0, and it doesn't seem to work with Compuserve B. Did it
ever?
–apl
Andy,
I've got a very early 2000 (now a 2500) also, and it too came with
the Cherry keyboard (also replaced long ago). So that's not the problem.
What are your serial preferences set at…and are you using a 7 (or
more) wire cable for the modem?
Don
BackTalk: 2400 Full 8N1 serial.device Init Cmd=AT Prefs: Handshaking=None
2400 8N1 My cable is a simple 3-wire data cable. According to the BackTalk
docs, this requres Prefs to have the same settings, so I made sure it does.
I hope it's not the cable. Every other comm program I've used in the last
seven years has worked with it. –apl
I believe the doc for BackTalk is specific — it requires a fully
implemented serial cable (ie., 7 wire minimum).
-sja
Andy,
I have exactly same problem with BackTalk 1.55a. It just would not
communicate with modem. Don Curtis suggested few remedies but they did not
work. Everything else including BackTalk 1.51 works OK but BT 1.55a just
would not. If you find a solution please let me know.
Gopal on AutoPilot
from Beatle city Liverpool, U.K.
Andy,
Backtalk requires a 7 wire cable. You can get one at any computer
store for a few dollars.
Don
Don,
I am using BT 1.55A with a 7 wire cable. To get BT to talk to the modem,
I have to flip a switch on the bottom of the modem to force CD on. With
CD not forced (off, since offline), nothing is sent to the modem. This is
a bug, isn't it? Pretty hard to tell the modem to make a call if you
can't send anything to it.
I even went and changed modem cables to make sure the cable from my A1k
(with gender changer for A2.5k) wasn't wired wrong.
73, Kelly
Kelly,
I'm using BT with a PM14400FXSA modem and have it set for CD to
follow actual connect. Same with the Supra 2400 I was using before the
PM14400. CD is definately not required for BT to work.
What BT does though, is setup the serial port based on whether CD
is active or not. If CD is active, it doesn't change the serial port's
configuration. If CD is not active, then it changes the serial port's
configuration based on what you've chosen in your current configuration
file.
Don
Don,
That is not how BT1.55A is working on my system.
My modem is a USRobotics Courier 2400 (ancient history already!) When CD
is set to normal, BT will not send anything at all to the modem. Not even
the Modem INIT string.
When I put the switch to CD always On mode, BT will talk to the modem,
even send the Modem Exit string, but it still does not send the Modem INIT
string!
Running the release 2.04 wb/ks on an A2.5k/020.
73, Kelly
Kelly,
That's right…when CD is set, BT won't send the init string
because it presumes you're already online. Out of curiosity, what's your
serial pefrences set to?
Don
Serial preferences set at:
2400 bps, 512 byte buffer, no parity, 8 bits, 1 stop bit. Handshaking was
tried with Xon/Xoff, RTS/CTS and None. The Handshaking doesn't make any
difference.
73, Kelly
Kelly,
Oh yes, for what it's worth…I'm also on an A2500/20 under w/b
2.04.
Don
That's not what the docs say — see my message #76650 to Steve Ahlstrom.
Also, see the previous message #76590 that seems to show a difference
between verson 1.51 and 1.55, and the following message #76614 where a
7-wire cable doesn't seem to help. –apl
Andy,
I know that's not what the docs say…I didn't write the docs.
Don