zaphod%wwu.csnet@CSNET-RELAY.ARPA (11/23/85)
From: Brown@CSNET-RELAY.ARPA, David D <zaphod%wwu.csnet@CSNET-RELAY.ARPA>
Thanks to the people that responded to my request on help about getting
input from the serial port, but, as a few pointed out, I should have been
more specific...
My friend is trying to get input from the serial port using the CLI.
He has the basic (non-developer) setup, so programs in C won't work.
Does anybody know of how to send and recieve chars from the serial
port using ABasiC or the CLI?
anyway...
Dave Brown
CSNET: zaphod%wwu@csnet-relay.arpa
USPS: 2305 Douglas #9, Bellingham, Wa. 98225
(206) 647-1312
"He's just this guy, you know?"stroyan@hpfcla.UUCP (12/03/85)
I had no problem with output to the serial interface from CLI. A simple "type myfile to ser:" produces immediate output. Of course, I had to play with the cable wiring. You ALWAYS have to play with RS232 cables. :-) Input from CLI is another story. I've used "type ser: to myfile." Type seems to do reads of about 256 characters. Nothing shows up until you send that many characters into the interface, then all ~256 characters are transferred to the file. You need to pad the end of your file. When transfering files from an Apple to the Amiga, "type" always left the eighth bit set, but AbasiC didn't seem to have this problem. I used a simple program in Abasic to strip the eighth bit after using type to transfer a file. The real annoyance is that the Amiga would crash during some file transfers. Thinking about it now, this might be avoided by using "type ser: to ram:myfile." If the problem is related to using the disk drive and serial interface simultaneously, using ram: would solve it. Mike Stroyan, hpfcla!stroyan