Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles; site hpfcdc.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!hpfcdc!hpfcdc!hpfcla!stroyan
From: stroyan@hpfcla.UUCP
Newsgroups: net.micro.amiga
Subject: Re: more on the serial port...
Message-ID: <181300004@hpfcdc.UUCP>
Date: Tue, 3-Dec-85 12:54:00 EST
Article-I.D.: hpfcdc.181300004
Posted: Tue Dec  3 12:54:00 1985
Date-Received: Sat, 7-Dec-85 05:17:14 EST
References: <532@caip.RUTGERS.EDU>
Organization: 03 Dec 85 10:54:00 MST
Lines: 20


   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