Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site caip.RUTGERS.EDU
Path: utzoo!linus!decvax!decwrl!amdcad!lll-crg!caip!louie
From: louie@trantor.UMD.EDU
Newsgroups: net.micro.amiga
Subject: Re:  Terminal program stuff...
Message-ID: <922@caip.RUTGERS.EDU>
Date: Wed, 8-Jan-86 11:46:48 EST
Article-I.D.: caip.922
Posted: Wed Jan  8 11:46:48 1986
Date-Received: Thu, 9-Jan-86 06:11:15 EST
Sender: daemon@caip.RUTGERS.EDU
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 22

From: Louis A. Mamakos <louie@trantor.UMD.EDU>

I asked the question a few days ago about the terminal program.  It seems
that it is relativly expensive to call the console.device to do I/O to
a console window.  If you read a character from the serial.device and
write it to the console.device, you can't keep up at 1200 baud.  What you
should do, and this helped me considerably, is to read as many characters
as are present from the serial.device, and write them all to the console
device.  You can use the SDCMD_QUERY command, which will return the number
of characters in the input queue in the io_Actual field of the I/O request.

I got 80 characters by 25 lines in my terminal program.  I created my own
screen, and then a borderless, backdrop window on it.  Not having any window
bar or sizing gadgets gives you plenty of room.  All of that stuff I'll do
with menu items; or I'll just type AMIGA-N or AMIGA-M to switch back to the
workbench screen while the terminal program is running. 

I like the spoken bell;  if I can figure out how to read the sound samples
from the instruments demo disk, I'd like the Power Chord as my bell.

Louis A. Mamakos  WA3YMH    Internet: louie@TRANTOR.UMD.EDU
  University of Maryland, Computer Science Center - Systems Programming