Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!jvnca!njitsc1!argus!ken
From: ken@argus.UUCP (Kenneth Ng)
Newsgroups: comp.sources.d
Subject: Re: Using a PC for a terminal
Message-ID: <898@argus.UUCP>
Date: Tue, 9-Jun-87 10:49:11 EDT
Article-I.D.: argus.898
Posted: Tue Jun  9 10:49:11 1987
Date-Received: Thu, 25-Jun-87 02:11:27 EDT
References: <1149@carthage.swatsun.UUCP> <8601@tekecs.TEK.COM> <6828@mimsy.UUCP> <1731@ttrdc.UUCP>
Organization: NJ Instit. of Tech: TEIES Project
Lines: 26
Keywords: termcap, curses

In article <1731@ttrdc.UUCP>, levy@ttrdc.UUCP (Daniel R. Levy) writes:
> Some (all?) PC/clones cannot keep up with speeds > 4800 baud in the VT100
> terminal emulator (they lose bursts of characters, even with Xon-Xoff flow
> control).  You want a PC, you buy a PC.  You want a terminal, well, I hope
> you get an AT&T terminal (plug plug :-) ).

Don't be too sure about that.  The AT&T 4425 has a hard time keeping up
with speeds beyond 2400 baud for extended periods of time unless the
X-ON, X-OFF protocol is enabled.  BUT, that makes the terminal HANG
on one of our half duplex systems.  The only way out is a terminal
reset, which drops the line, and signs me off.  Conversely I often use
a Phillips IBM PC (believe it or not *SLOWER* than the original IBM)
with Procomm at 9600 baud with very few problems.  I guess the key is
design implementation.

< Fodder for INEWS>
<
<
<



-- 
Kenneth Ng: Post office: NJIT - CCCC, Newark New Jersey  07102
uucp !ihnp4!allegra!bellcore!argus!ken *** NOT ken@bellcore.uucp ***
bitnet(prefered) ken@orion.bitnet