home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Path: sparky!uunet!eco.twg.com!twg.com!twg.com!sk
- From: sk@twg.com (Shantanu Kothavale)
- Subject: Re: TELNET Terminal types
- Message-ID: <1993Jan11.204251.8227@twg.com>
- Sender: news@twg.com (USENET News System)
- Organization: The Wollongong Group, Palo Alto, CA
- Date: Mon, 11 Jan 1993 20:42:51 GMT
- Lines: 45
-
-
- ** Joe Morris <jcmorris@mwunix.mitre.org> writes: **
-
- >> (Stuff deleted)...
- >> In particular, in the terminal-type options negotiation (per RFC 1091)
- >> the Wollongong product is delivering the text string:
-
- >> DEC-VT100
-
- ** Frank McConnell <frank@twg.com> writes: **
-
- >> I find the following workaround helpful in dealing with mismatches
- >> between the terminal types listed in the Assigned Numbers RFC and
- >> those that appear in termcap or terminfo databases:
-
- >> eval `tset -s -m 'dec-vt100:vt100' -m 'network:?vt100'`
-
- >> This appears in my .login on most of the Suns that I work with.
-
- ** trier@odin.ins.cwru.edu (Stephen C. Trier) writes: **
-
- >> The solution used by NCSA Telnet (or was it CUTCP?) was to make the
- >> terminal name user-configurable.
-
-
- The PathWay Access for (Microsoft) Windows product includes also makes
- the terminal name configurable. When creating a new Terminal session,
- the Options dialog box can be used to customize the session. One of its
- options allows you to edit the string "DEC-VT100", and replace it with
- the terminal type of your choice. Replacing DEC-VT100 with VT100 should
- do the trick in this case.
-
-
- For products that don't have this sort of workaround, I recommend Frank's
- suggestion of using *tset*.
-
-
-
- Enjoy,
-
-
- Shantanu R. Kothavale
- The Wollongong Group, Inc.
- <sk@twg.com>
- --
-