Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!pogo!guillaum
From: a.guillaume@trl.oz.au (andrew guillaume)
Newsgroups: comp.sys.apple2
Subject: Re: //c serial ports.
Keywords: Apple//c,serial port, communication, Applesoft, basic.
Message-ID: <7175@munnari.oz.au>
Date: 26 Mar 91 22:19:21 GMT
References: <1991Mar26.043509.24160@sserve.cc.adfa.oz.au>
Sender: news@cs.mu.oz.au
Reply-To: a.guillaume@trl.oz.au (andrew guillaume)
Followup-To: comp.sys.apple2
Organization: Telecom Research Laboratories, Melbourne, Australia
Lines: 31


In article <1991Mar26.043509.24160@sserve.cc.adfa.oz.au>,
pgc@csadfa.cs.adfa.oz.au (Phil Clark) writes:
> I seem to remember reading somewhere, possibly in this newsgroup, that
> Applesoft basic has problems keeping up with data via the serial ports of
> a //c at greater than about 1200 baud. 

> Has anyone else experienced this problem and if so, is there a simple
> answer?

> The data format is 8 data bits, no parity, 2 stop bits, 4800 baud.

G'day !

I have had similar problems, at 1200 baud. Data format : 8 bits, no parity,
1 stop bit, 1200 baud. I was using Visiterm (a comms program), hooked up
directly to my unix box, to download text. At 1200 baud, I would loose a
character ot two every time the Apple //c would send a stop character to
write to disk. No problems at 300 baud. I was wondering whether this was 
a software problem or whether that was linked to the serial port. 
Theoretically, the //c port can go up to 19.2k baud. So says the tech
manual.

I would also appreciate if someone could shed light on this, and give
an indication as to whether the problem disappears with an upgrade (I have
to upgrade my //c from a "boat anchor" :-) to a unidisk in order to be able
to buy a Chinook HD). Thanks in advance.

Andrew Guillaume

Internet : a.guillaume@trl.oz.au