Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!linus!necntc!ames!oliveb!pyramid!decwrl!labrea!Shasta!kaufman From: kaufman@Shasta.UUCP Newsgroups: comp.sources.d Subject: Re: Using a PC for a terminal Message-ID: <1790@Shasta.STANFORD.EDU> Date: Sat, 20-Jun-87 13:42:25 EDT Article-I.D.: Shasta.1790 Posted: Sat Jun 20 13:42:25 1987 Date-Received: Sun, 21-Jun-87 12:02:28 EDT References: <1149@carthage.swatsun.UUCP> <8601@tekecs.TEK.COM> <6828@mimsy.UUCP> <1075@laidbak.UUCP> <94@spked.UUCP> <1017@watmum.UUCP> Reply-To: kaufman@Shasta.stanford.edu (Marc Kaufman) Organization: Stanford University Lines: 16 In article <1017@watmum.UUCP> smvorkoetter@watmum.UUCP (Stefan M. Vorkoetter) writes: >I am using an AT Clone, running a VT102 emulation package (Terminal Emulator >and File Transfer 2.40a), and it is having no trouble at 19200 baud, using >only XON/XOFF (no hardware flow control)... My teeth itch when I read this. Let's get it straight. The ability to read individual characters at a speed of 19200 bits per second is NOT THE SAME as the ability to asimilate characters at the rate of 1920 Characters per second. Got that? If you need/use XON/XOFF protocol, you are NOT keeping up at the speed in question. We are talking about the ability to process characters WITHOUT flow control at a given speed. BTW: just because your VAX, etc., is set to send characters at a (bit) speed of 19200 bits per second, is no reason to assume that is is sending 1920 Characters per second... you have to do some timing studies to determine what is really happening.