Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!uunet!mcsun!sunic!chalmers!tekno.chalmers.se!cth_co
From: cth_co@tekno.chalmers.se (CHRISTER OLSSON)
Newsgroups: comp.dcom.modems
Subject: Re: US Robotics HST doing strange things to ^S
Message-ID: <964@tekno.chalmers.se>
Date: 23 Aug 89 21:07:50 GMT
References: <663@lakart.UUCP> <218@conch.UUCP>
Organization: Chalmers Univ. of Technology, Gothenburg, Sweden
Lines: 12

In article <218@conch.UUCP>, steve@conch.UUCP (Steve Froeschke) writes:
> cause problems with 'hot keys' not responding, etc.  The fix that I used
> was to limit the transmit buffer down to 128 bytes vice the normal (default)
> of 1024 bytes (1K).  This helped quite a bit, but still, there was a
> little delay in response.  (But considering you can interrupt it every
> 128 bytes vice 1K, it worked much much better).  What I would recommend
> is letting the Sysop of the system know about the transmit buffer size,
> and see if he/she is agreeable to reducing it.
The transmitt buffer is 3.5K in ARQ-mode and 1.5K, not 1K in non-ARQ-mode.

ATS15=8 reducing the non-ARQ-buffer from 1.5K to 128 bytes.