ATalk III?
5 messages in this thread
Betty,
Thanks for the info Betty. AtalkIII not working with Whap! may
disqualify it for my purposes. Unfortuanately, I have not received any
other suggestions for commercial comm programs other than yours. I find
this disappointing (not that I don't charish your opinion). Maybe I can
dig into my old AmigaWorld's. I seem to remember an article on comm
programs was in one of them.
<<< Michael Shea >>>>
<<< 76665,3360 >>>>
I think the problem is that most of the commercial programs are not as good
as (or at least no better than) the shareware ones. Our shareware in
communications is excellent – most of it of commercial quality.
Betty
I have been happy with Sharware comm programs (JRComm and Access), but
unfortunately I need KERMIT, and would rather deal with one telecomm
program vice two or three.
<<< Michael Shea >>>>
<<< 76665,3360 >>>>
I have AtalkIII and I am not sure why it doesn't work. It does open the
modem in Shared mode (a command line switch) but when I open Whap! and then
ATalkIII both at the same time chaos results. They both start asking for
characters from the serial port and they each get half of them. Maybe I
don't understand how it's supposed to work, though.
—–> Brian Simmons, Denver, Colorado.
SHARED MODE!!!!
Now I know how to get ATalk3 to work with WHAP!.
Normally WHAP! must invoke the terminal program when it is has finished
it's job of logging on and possibly accessing forums. You have to tell
WHAP! where the terminal program is by filling tin the box labeled
"Terminal" in the parameters screen (same screen where you tell WHAP! the
phone numbers and baud rates to use). If you try to run WHAP! and a
terminal program independently the operating system will give each program
every other character, like you described. Trouble with WHAP! running
ATalk3 is WHAP! dosen't have a way to pass CLI arguments to a terminal
program, it just uses the entire string in the Terminal field of the
parameters screen as one long command name.
When I first got my modem (a Supramodem 2400 internal moden) WHAP! would
access it when I told it to use the device driver modem0.device that came
with the modem. ATalk3 also had to be set up to use modem0.device in the
icon tools field. BUT when WHAP! invoked ATalk3, Atalk3 did not know about
the modem0.device and was trying to use serial.device ! My cure for this
was to write a short C program that WHAP! would run and which would run
ATalk3 with the command line options to tell it about modem0.device. BUT I
DID NOT KNOW THERE WAS ALSO A SHARED KEYWORD. I did not see SHARED
mentioned in the manual so I just thought there was none. Now I have run
ATalk3 from the CLI with a "?" and I see I do have a SHARED mode. In fact I
quickly added it to my ATalk3 loader program and IT WORKED. In a few days I
can clean it up and generalized it and upload it here if anyone is
interested? Might do it anyway even if no one is interested, just for
pratice at uploading.
Herbert L. Crowder