BackTalk Problem
9 messages in this thread
I loaded BackTalk 1.46 today, printed the many docs files, and followed —
I believe — all of the installation instructions. The problem is that
program comes up as advertised and I can even see the pull-down menu
selections. Only problem is none of the selections (whether by mouse or
Amiga-key) work. I cannot even exit but must do a reset to exit the
program. My computer is an Amiga 2000 with 9Mb of RAM, 20 meg Supradrive,
etc. What am I doing wrong? Any ideas?
Did you place kd_freq.library and xprquickb.library in libs: ?
Yes, I placed those files as directed in the documentation. That is what
puzzles me. Other software works OK. I used CLI-Mate so I know that I
didn't make a typo — I transfered the files by clicking on them in that
program. I use version 1.3 of AmigaDos. This isn't for version 2.0
exclusively is it (I note the comments associated with FR Bypass 3.0
indicate that it is designed for the 2.0 AmigaDos. Any help you can offer
will be appreciated. Thanks.
Eric,
No, BT is not 2.0 specific — neither is fr_bypass. BT does require a 7
wire modem cable, is that what you have?
Yes I use a full 25 wire ribbon cable. But program hangs long before
trying modem. No pulldown menu works. I can pull down the list of
selections, but nothing happens after selecting one with the mouse. The
same with Right-Amiga commands. Typing the command results in no action.
Even trying to exit fails. (I have to reboot.) I have not had this problem
before with ANY other software. I do not have the dreaded 6.0 or 6.1
revision of the A2000 motherboard, but have the older but "safe" version
4.3. I am running V1.3 of AmigaDos complete with fat Agnus etc. My curent
modem program is the very first release of Online! I downloaded Backtalk
with hopes of getting a first class up-to-date Rexx supported modem program
without paying the $69 dollars for the latest "Platinum" version of Online!
It appears that there is an obscure bug in Backtalk that affects only
certain configurations (such as mine) since other message in this SIG
attest to user satisfaction. I have double-checked the presence of the
required librarys in my libs: directory and they are all present. I am not
a computer novice but have been a Professor of Computer Science (as well as
of Fine Arts as I am now). Alas, if I can't get BT working in a couple of
weeks I will have to buy a newer copy of Online! But perhaps you will
figure out what is wrong either with my copy or my configuration. It is
strange that I don't get any error messages. But then, since I did not
write BT I do not know what error handling routines are included in the
software. Having specialized in developing public access hyper-media
kiosks I am grateful that the original v1.0 Online! has served me well for
five years and two Amigas. Regards — Eric Somers
Eric,
I'm also using an A2000 with a rev4.3 motherboard and a 1.2 ROM.
And as one of the developers of BackTalk…I can assure you it does work.
So…a few questions:
1. Does you modem have status LED's…if so, what LED's are lit
before you boot BT and what LED's are lit after you boot it?
2. What's your stack size? If low (as in the default 4000) you
might try to bump it up to 10000 and see if that helps (doubt it will…but
it's worth a try).
3. From a CLI, type AVAIL before you attempt to run BT. How much
memory of which type (fast…chip) do you have available.
4. Look at your serial preferences (via preferences) and what's the
default set at? If not already set that way, try setting it to 2400 baud,
2048 byte buffer, 8 bit read, 8 bit write, 1 stop, no parity and NONE on
handshake. See if that helps. You don't need to save them to try
them…select the USE option when comming out of preferences.
If none of that works…let me know and we'll try some more things.
Don
I have the same problem with my amiga at work. At home, no problem. The
main difference between the two machines is that the one at home
has AREXX 1.10 and the one at work 1.05. That is most likely the problem.
(Symptoms are at work that BACKTALK will allow you to pick one
menu item and then there is no response after that item executes [i.e.
changing the screen or saving parameters]
Michael,
That is very likely the problem. You might consider updating ARexx on your
office machine.
Thanks for the suggestions. I'll try them this weekend and let you know
the results. It surprises me that no menu functions work even when modem
commands are not accessed. That is, merely entering the program prevents
me from quitting even if that is the only command I give it. Or does it
check modem status on entry? Perhaps then it is waiting for some
handshaking my Promethius ProModem 2400 (cheap!) is not pro-perly
providing. But I'll run down your check list above. Thanks.