Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!spool.mu.edu!sdd.hp.com!usc!bbn.com!ulowell!oneill
From: oneill@ulowell.ulowell.edu (Brian 'Doc' O'Neill)
Newsgroups: comp.sys.next
Subject: Re: Problem with telnet session to NeXTstation (answer summary)
Message-ID: <1991Jun19.131353.17074@ulowell.ulowell.edu>
Date: 19 Jun 91 13:13:53 GMT
References: <1991Jun18.141839.25360@ulowell.ulowell.edu>
Organization: University of Lowell Computer Science, Lowell MA
Lines: 71

In article <1991Jun18.141839.25360@ulowell.ulowell.edu> oneill@ulowell.ulowell.edu (Brian 'Doc' O'Neill) writes:
>I am having a problem with telnet sessions to a NeXTstation Color running
>2.1. Whenever I display some information, it may work fine for a few lines,
>but then it begins to drop the carriage returns, and only gives line feeds,
>wrapping the output around the screen, making it mostly unreadable. Is there
>any quick solution to this?
>

Thanks to all who responded. A couple of people had the same response, which
worked. It was to add 'stty -extproc' to my .cshrc, and it worked
beatifully. Those who sent this reponse:

smithw@hamblin.math.byu.edu (Dr. William V. Smith)
Claude William Saunders <saunders@cs.uoregon.edu>

There were some other responses as well, included below.

#Date: Tue, 18 Jun 91 17:08:05 -0500
#From: Rob Francis <francisr@silver.ucs.indiana.edu>
#Subject: Re: Problem with telnet session to NeXTstation
#Organization: Indiana University, Bloomington
#
#I don't know why or if it is the reason, but I sure don't have these
#problems that a lot of people are having with telnet sessions.  Here's
#the relative part of my .login:
#
#if ($TERM != xterm) then
#        stty dec new cr0 -tabs
#        setenv TERM `tset - -Q '?vt100'`
#endif
#
#I don't think this is any differant than anyone elses, but I thought
#I'd at least let you know about it.
#
#Rob

#Date: Tue, 18 Jun 91 19:12:16 -0400
#From: Will Raymond <raymond@cs.unc.edu>
#Subject: Re: Problem with telnet session to NeXTstation
#Organization: University of North Carolina, Chapel Hill
#
#Hope this helps.
#This is a weell-known problem with , supposedly, csh for the NeXT. If you
#rlogin/telnet etc. to the cube from a system that isn't running the
#same version o the shell ( ie. non-Next machine) this problem appears. 
#I've been told that telnet/rlogin doesnt exhibit this behavoir when you
#log in from another machine.
#
#I log into my cube at home from my PC running unix. When I rlogin
#I run sh ( bourne shell). This shell doesnt exhibit the prob.
#
#Hope this helps.
#
#Will
#

#Date: Tue, 18 Jun 91 19:28:59 -0400
#From: Bob Sutterfield <bob@morningstar.com>
#Subject: Problem with telnet session to NeXTstation
#
#I find that NeXT's telnetd wants to negotiate a lot more Telnet
#options and suboptions than does Sun's, and then it doesn't seem to be
#as smart with the options it gets.  I eventually gave up and just use
#`rlogin -8'.


-- 
=======================================================================
Brian O'Neill - Systems Manager, Computer Science, University of Lowell
Internet: oneill@ulowell.edu				 (508) 934-3645 
UUCP: harvard!ulowell!oneill