Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!think!ames!ucbcad!ucbvax!hoser.berkeley.edu!bryce From: bryce@hoser.berkeley.edu (Bryce Nesbitt) Newsgroups: comp.sys.amiga Subject: Re: Amiga serial questions Message-ID: <22073@ucbvax.BERKELEY.EDU> Date: Sat, 5-Dec-87 23:05:14 EST Article-I.D.: ucbvax.22073 Posted: Sat Dec 5 23:05:14 1987 Date-Received: Thu, 10-Dec-87 22:47:43 EST References: <4558@pyr.gatech.EDU> <1303@saturn.ucsc.edu> <2893@cbmvax.UUCP> <5171@fmsrl7.UUCP> Sender: usenet@ucbvax.BERKELEY.EDU Distribution: na Organization: University of California at Berkeley Lines: 32 Keywords: Serial speeds, terminal emulation In article <5171@fmsrl7.UUCP> wayne@fmsrl7.UUCP (/\/\ichael R. \/\/ayne) writes: > >Does anyone know of a >terminal emulator for the (stock, 512K, 1000) Amiga that will run at 19.2K >SUSTAINED?... >Scrolling is mandatory... To start off, no I don't know of a program that will meet your needs, however I can pass on some tips that allow a micro to operate a much higher speeds. (These techniques were used on a program for "another computer") Scrolling once per line adds significant overhead (though extra true- fast ram and the blitter compensate quite a bit on the Amiga). A slick way to reduce this is to add a 6 or more speed manual transmission: You look at the size of your buffer, depending on how far behind you are, scroll up multiple lines. *All* the data makes it on the screen. In general screen output takes much longer than just collecting bytes in a buffer. It would be very possible to have a lower priority sub-task updating the screen. (The two above suggestions apply mostly to a plain text system...) In any case some the of communications programs for the Amiga still request serial.device data a byte at a time. This is *wrong*. Allways to a query and read the number of pending bytes. |\ /| . Ack! (NAK, SOH, EOT) {o O} . bryce@hoser.berkeley.EDU -or- ucbvax!hoser!bryce (") U WARNING: hoser's spool directory eats a *lot* of mail. :-(