home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!ohstpy!kenyon.edu!oursler
- Newsgroups: vmsnet.networks.tcp-ip.ucx
- Subject: Terminal type problems
- Message-ID: <1992Oct15.113401.128@kenyon.edu>
- From: oursler@kenyon.edu
- Date: 15 Oct 92 11:34:01 -0500
- Organization: Kenyon College
- Lines: 32
-
- Hullo,
-
- This is a stab in the dark, but I'm having a problem
- with UCX and QVTNET (telnet for windows package).
-
- Whenever, I connect to a VAX running UCX (1.3 or 2.0) the
- terminal type negotiation results in setting the terminal
- to a VT102 rather than a VT220. This does not occur when I
- connect to VAX hosts running Multinet or Unix hosts of
- various flavors.
-
- The problem is either with UCX or QVTNET, but the QVTNET folks
- don't seem to recognize there's a problem with their product.
- So I'm trying to attack the problem from the UCX end. If
- Multinet can manage it, why can't UCX?
-
- Is there anything I can do about this? It so happens that the
- host I connect to most often is a VAX running UCX and I am
- tired of changing the term type and then doing a SET TERM /INQ
- every time I log in.
-
- Thanks for any help anyone can provide.
-
- - Miles -
-
- -------------------------------
- Miles Oursler
- Manager of Networks and Systems
- Kenyon College
- oursler@kenyon.edu
- -------------------------------
-
-