Re: Terminal Emulation rates

[Alistair J Ross <mail@ataliross.co.uk>]

> Also, the unenhanced //e disables interrupts for too long to keep up 
> at 1200 bps, while the enhanced //e can generally keep up at 2400 
> bps and a IIgs can do  9600 bps. I couldn't make 19200 work.

A quick followup...

on running at 300bps (painful), all seems to work normally.

Is there nothing that can be done about this speed. To use the machine for
any practical purpose at 300bps even back in 1980 would have been unusable
to say the least.

Regards,

Alistair Ross

On Wed, 29 Sep 2004 23:50:01 +0000, John B. Matthews wrote:

> In article <%gs6d.15576$54.237216@typhoon.sonic.net>,
>  Andy McFadden <fadden@fadden.com> wrote:
> 
>> Alistair J Ross <mail@ataliross.co.uk> wrote:
>> > However - on occasion text sometimes just plain doesn't appear when typing
>> > commands in. It's mainly during operations which refresh the screen. For
>> [...]
>> > Also, issuing a 'clear' command at my linux prompt often gives me a full
>> > screen clear but with half a prompt afterwards, ie:
>> > 
>> > oss@xbolt.net]$
>> > 
>> > instead of my username in full.
>> >
>> > Is my baud rate too high, and causing errors? I'm using 19200 for my
>> > transfer rate, I've played around with 9600 bps but I don't really wanna
>> > go lower. Any ideas anyone?
>> 
>> What kind of cable are you using?  Does it have the hardware handshake
>> signals?
> 
> Also, the unenhanced //e disables interrupts for too long to keep up 
> at 1200 bps, while the enhanced //e can generally keep up at 2400 
> bps and a IIgs can do  9600 bps. I couldn't make 19200 work.

-- 
-----------------------------------------------------------[ Alistair J Ross]--
Alistair Ross
XBOLT Network 
--[ www.xbolt.net ]------------------------------------------------------------