#sending text
3 messages in this thread
the problem with uploading text files to CIS using no protocol is not entirely
AMiga's fault. It is CIS's problem as well. I'm only sending at 300 baud, but
believe it or not, CIS would not accept my sending of 15K basic program at the
speed the AMiga was sending. The solution is to put some delay loops in your
send routine and an extra delay at line end. I successfully upl the file
Sunday, so this may help some who have have their files truncated after so many
lines had been accepted. Just slow it down, until something better comes
along. Ed Martie
Ed, delays are one way to do it, but a poor way. CIS uses full XON/XOFF flow
control. Your program can send at full speed until it recieves an XOFF (^S).
Then it must wait until it receives an XON (^Q) before continuing. I regularly
do all-out text uploads at 1200 baud — my modem program (CrossTalk XVI –
EyeBeeEm PeeSea) honors flow control.
– Bela Lubkin
Bela,
I agree about xon/xoff. I'm using my Amiga with the EZ-term prog. from DL7.
Looking at it the other nite, (morning?) there is a way to detect those ctrl
chars and cause a pause, so I may try implementing it. Another thing we need
is a filter for received CTRL chars. Someone sent me a CTRL-G last nite to wake
me up. Naturally no sound was emitted from the Amiga, but it got my attention
anyway, it turned my screen background color from the brown-tan I usually use
to a light blue ! Weird, I could hardly read the text anymore. Another bug?
(oh nooooo). Later, Ed