02-24-2005 07:46 PM
I want to migrate my users to PuTTy.
I have to adjust my application to use PuTTy.
Can I somehow detect from Tru64, with which terminal emulator software I had logged in?
I've found following info in PuTTy documentation:
"Most servers you might connect to with PuTTY are designed to be connected to from lots of different types of terminal. In order to send the right control sequences to each one, the server will need to know what type of terminal it is dealing with. Therefore, each of the SSH, Telnet and Rlogin protocols allow a text string to be sent down the connection describing the terminal.
PuTTY attempts to emulate the Unix xterm program, and by default it reflects this by sending xterm as a terminal-type string. If you find this is not doing what you want - perhaps the remote system reports ‘Unknown terminal type’ - you could try setting this to something different, such as vt220.
If you're not sure whether a problem is due to the terminal type setting or not, you probably need to consult the manual for your application or your server.
- I.e. Tru64 should know about terminal.
Solved! Go to Solution.
02-24-2005 09:27 PM
But I think it is important what terminal type will be emulated by your windows software and depending on the used type you can set the terminal emulation on unix side - which is a standard (the windows application itself is not a standard, it is only an emulation of a standard terminal like VT100, VT200 etc.)
02-25-2005 12:03 AM
1) It is possible in PuTTy to specify terminal type (xterm by default), any other will do the trick (but Tru64 may complain on 'terminal type is unknown')
In Unix You can see it in $TERM variable.
2) PuTTY can set environment variable on the host upon login.
Make variable Putty=Y
and check it in script.
I've hit another problem - it cannot show
ASCII symbols 1-32 (old terminal shows misc. faces&arrows). But it's unlikely Tru64 problem.
03-10-2005 09:59 PM
Does it work if you specify another terminal type (like vt220?)
03-13-2005 07:37 PM
It does show lots of info, I have to RTFM to understand whats it all about.
2) If I specify VT200 to Putty - connection - terminal type string, this value is successfully translated to UNIX.
and it seems working OK with command prompt.
My problems are futher down - my application (Concorde XAL) using screen with colours,
linedrawing and keyboard with ALT, CTRL and Russian language.
I had to launch my application with another options to operate against PuTTy.
03-13-2005 11:21 PM
but why not stty -a >file1 and the same for a working terminal session. Using diff to get the differences between them? Then reading "man termios" to get an explanation.
Life could be so easy!