Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!PURDUE.EDU!sbm From: sbm@PURDUE.EDU Newsgroups: comp.protocols.appletalk Subject: Re: Troubles with NCSA Telnet 2.1 Message-ID: <8807111819.AA07246@merlin.cs.purdue.edu> Date: 11 Jul 88 18:19:26 GMT References: <4085@saturn.ucsc.edu> Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 21 What you have described is a common problem with remote login across networks. The process on the remote machine produces output which is buffered and sent in packets across a slow network to a process on the local machine which buffers the output until the even slower output device can print it. Remember that CPUs are very fast in relation to I/O; by the time you see the output on the local machine (the Mac), it is possible that the process on the remote machine has finished its output and exited. The reason for the "mushy" ^S, ^Q, and ^C is that they are not interpreted locally, but sent to the remote machine, where the output you are seeing is ancient history. I don't know the particulars of AppleTalk, except that, at 230 Kbaud, it is extremely slow as networks go, but the solution is considered messy, because it requires treating ^S and ^Q as special cases instead of just sending all characters verbatim to the remote machine. Steve Munson sbm@Purdue.EDU sbm@Purdue.CSNET ----------