Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!rutgers!faatcrl!jprad
From: jprad@faatcrl.UUCP (Jack Radigan)
Newsgroups: comp.sys.amiga.tech
Subject: Re: JRComm (Was Re: AMIGA too slow for speeds higher than 9600 Baud? HELP!)
Message-ID: <1366@faatcrl.UUCP>
Date: 6 May 90 12:46:16 GMT
References: <1490@lpami.wimsey.bc.ca>
Organization: FAA Technical Center, Atlantic City NJ
Lines: 22

lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes:

>There are probably several. If you allow the screen to be as big as possible,
>you will usually find that either the system you connect with will use it or
>it won't. If it won't, it will just use whatever portion of the screen that is
>handled by the host. To put it another way, if it thinks the cursor can't go
>beyond line 25, it will never try to put it there, and if it does, the program
>putting it there is broken.

  That part's obvious.  What happens more often than not though is that you
probably will have a few screen scrolls in there (more so with IBM ANSI than
VT100), so what you end up with is some garbage along the bottom and right
sides after a few cursor repositioning sequences have occured.  

>For the safest operation, in order to handle hosts that mess up by assuming the
>fixed size, my approach would be to allow any sized screen, but with a 'detent'
>settting at 80*25 (shouldn't that be 24?).
  
  Hmmm, hadn't thought of it that way before.  24?  You're fogetting the status
line....

  -jack-