CompuServe Thread

#AMIGA! help!!

12 messages in this thread
#102567From: Allen L. GreenbergJan 10, 1988 1:06 PM
does anyone know how to get this program to wait for a carrier signal and transmit a ^C? Wait "CONNECT" doesn't seem to work for me. I'm open to all suggestions. -Allen
#102652From: Marlene ZenkerJan 10, 1988 6:31 PM
Allen, what is AMIGA! ? Just out of curiousity – you're not using 1200 baud are you? The reason I ask is that then you would be asking it to Wait "CONNECT 1200" or 2400 whatever. Marlene
#102724From: Allen L. GreenbergJan 10, 1988 9:46 PM
I've tried it with and without '2400' and the result is the same. Do you know if anyone's gotten it to work at all? -Allen
#102732From: Marlene ZenkerJan 10, 1988 9:58 PM
Allen, I still don't know which term pgm you are using. Are you sticking in a 2 second delay before the Ctrl-C ? Marlene
#102738From: Allen L. GreenbergJan 10, 1988 10:29 PM
Sorry Marlene. I meant to put DIGA! rather than Amiga for the subject. What I've found so far is that any wait for connect command seems to blow the whole thing. If I remove that 'wait for' I'll at least get my ID and password to go through. But in either case I still can't get Diga to transmit ^C. -Allen
#102739From: Marlene ZenkerJan 10, 1988 10:36 PM
Allen, BROwse thru DL4 there are some script files for Diga! there that may help. If it doesn't – let us know. marlene
#102696From: David MastersonJan 10, 1988 8:57 PM
I'll bet this is another DIGA! problem. Are you scripting an automatic logon sequence for Compuserve? If so, the problem may be that you aren't waiting after receiving the "CONNECT" string. Simply use a sequence like: WAIT "CONNECT" DELAY 5 SEND "^C" WAIT "ID:" This may not be a strictly DIGA! problem, but this is where it was most obvious to me. David Masterson
#102725From: Allen L. GreenbergJan 10, 1988 9:47 PM
Thank you Dave, I'll try it and let you know. -Allen
#102753From: Allen L. GreenbergJan 10, 1988 11:22 PM
Sorry David. I think your idea is a good one but I think Diga has more bugs in it then any "tested" program has a right to. Thanks anyway. -Allen
#102773From: Don Curtis/SYSOPJan 11, 1988 12:10 AM
David, That particular problem (needing the delay) isn't unique to Diga! or any other terminal program. CIS doesn't recognize the ^C if typed immediately after connect, you have to wait just a moment before sending it (a second if fine) and then CIS will recognize it. Don
#102996From: David MastersonJan 12, 1988 1:22 AM
I agree Don. Its just that I ran into that first with Diga! and geared myself accordingly with other systems. However, Diga! also has bugs around this in that (under MANY circumstances) things like the output from the modem (the "CONNECT" string) and the ^C never show up. Maybe they work, maybe they don't, but the output doesn't initially show up on the Diga! screen. Is it any wonder that I dropped Diga! in favor of VT100?!? David Masterson
#103226From: Allen L. GreenbergJan 13, 1988 12:40 AM
I decided to try again David, starting from scratch and including your delay before the ^C. It works fine now. Figures. Thanks again. -Allen