HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Why the telnet output looks different?
Operating System - HP-UX
1834639
Members
2696
Online
110069
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2002 04:40 PM
09-29-2002 04:40 PM
Why the telnet output looks different?
I had some problem with the output that i received when i open the microsoft builtin telnet and Qvt Term 5.1. Please view the attachment for the difference. I believe because maybe Qvt Term is pointing to vt100. So in microsoft telnet i set term vt100, also in the unix i type TERM=vt100 then export $TERM. But it still cannot work. I am using windows xp but i remember that in windows 98 users can change the telnet properties. Can it be done for windows 2000 or windows xp. My college is using HP-UX 10.20. Thank you.
wenching
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2002 05:42 PM
09-29-2002 05:42 PM
Re: Why the telnet output looks different?
Did you tell your telnet to use vt100 ??? Telling the system is one thing, telling the PC what terminal emulation to use is another.
What are the colleges plans to upgrade before 6/30/2003 ??
live free or die
harry
Live Free or Die
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-29-2002 06:10 PM
09-29-2002 06:10 PM
Re: Why the telnet output looks different?
Your problem is with the application program. It apparently expects a line drawing set to be installed in the terminal. There are no ASCII characters that produce the lines shown in the example. Therefore, your HP-UX program is sending some special escape sequence (or the ASCII shift-out and shifty-in characters) to turn on these characters, and the terminal emulator you are using simply doesn't have any method to handle them--so it puts out the letters that make up these line drawing elements.
The terminal emulators built into Windows are true vt100 emulators. The vt100 designation means the DEC VT100 terminal, circa 1970's and special characters were never a part of that original design. Your program should have specified a list of compatible terminals and emulators. If this is a home-grown program using the Curses library, when you make a call to the library, ALWAYS check for an error exit. If you are using a script and tput, always check the error return from tput. Also use the untic command to see what a particular terminal has available:
untic vt100
Bill Hassell, sysadmin
The terminal emulators built into Windows are true vt100 emulators. The vt100 designation means the DEC VT100 terminal, circa 1970's and special characters were never a part of that original design. Your program should have specified a list of compatible terminals and emulators. If this is a home-grown program using the Curses library, when you make a call to the library, ALWAYS check for an error exit. If you are using a script and tput, always check the error return from tput. Also use the untic command to see what a particular terminal has available:
untic vt100
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2002 07:36 AM
09-30-2002 07:36 AM
Re: Why the telnet output looks different?
I tried to use untic vt100...i saw a long of arguments. Actually what is tic and untic for? Can i do curses with untic command? So it means that it is impossible for me to use windows xp microsoft telnet to view the lines? What is circa 1970 for? Anyway thanks for your help.
wenching
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP