Putty & Teemtalk

[PeterP]

We currently use teemtalk as our emulator. It works fine but it doesn't
support colour. I'm trying to use Putty emulator insetead of teemtalk
but I can't get it to display correctly. I can enter my login name &
password no problem but after that everything goes wrong. I tried
different settings but no success. I included my teemtalk settings and
I hope someone would help me to find which setting to use for putty?
I got terminal type as follows:
$ set | grep TERM
TERM=wy50
but when I longin Putty I get a message "unknow teminal type wy50"
Can anyone help?
Thanks.
Peter Paxman

Teemtalk settings:
http://www.savefile.com/files/8092030

[Ian Wilson]

Post by PeterP
We currently use teemtalk as our emulator. It works fine but it doesn't
support colour. I'm trying to use Putty emulator insetead of teemtalk
but I can't get it to display correctly. I can enter my login name &
password no problem but after that everything goes wrong. I tried
different settings but no success. I included my teemtalk settings and
I hope someone would help me to find which setting to use for putty?
$ set | grep TERM
TERM=wy50
but when I longin Putty I get a message "unknow teminal type wy50"
Can anyone help?

It seems to me that message isn't consistent with the rest of the
description, nevertheless ...

AFAIK Putty isn't a Wyse-50 emulator, I'd choose one of the ANSI
variants for yout TERM settings - I use TERM=xterm

My putty settings for SCO OSR5 are
{menu} {new settings}
{terminal} {keyboard}
Backspace: Control-H
Home and End keys: standard
Function keys: Esc[n~
{connection}
Options to send to server
Terminal-type: xterm

This works fine with terminfo based apps like vi and termcap based apps
(I can't remember if I had to tweak xterm in termcap)

I also have the following:
{window} {translation}
Received data assumed to be: CP437
Handling of line-draw: Unicode
I use this with a suitable font like Lucida Console.
YMMV

[Tom Parsons]

Ian Wilson enscribed:
| PeterP wrote:
| > We currently use teemtalk as our emulator. It works fine but it doesn't
| > support colour. I'm trying to use Putty emulator insetead of teemtalk
| > but I can't get it to display correctly. I can enter my login name &
| > password no problem but after that everything goes wrong. I tried
| > different settings but no success. I included my teemtalk settings and
| > I hope someone would help me to find which setting to use for putty?
| > I got terminal type as follows:
| > $ set | grep TERM
| > TERM=wy50
| > but when I longin Putty I get a message "unknow teminal type wy50"
| > Can anyone help?
|
| It seems to me that message isn't consistent with the rest of the
| description, nevertheless ...
|
| AFAIK Putty isn't a Wyse-50 emulator, I'd choose one of the ANSI
| variants for yout TERM settings - I use TERM=xterm
|
| My putty settings for SCO OSR5 are
| {menu} {new settings}
| {terminal} {keyboard}
| Backspace: Control-H
| Home and End keys: standard
| Function keys: Esc[n~
| {connection}
| Options to send to server
| Terminal-type: xterm
|
| This works fine with terminfo based apps like vi and termcap based apps
| (I can't remember if I had to tweak xterm in termcap)
|
| I also have the following:
| {window} {translation}
| Received data assumed to be: CP437
| Handling of line-draw: Unicode
| I use this with a suitable font like Lucida Console.
| YMMV

We have a poster who didn't bother to include a description of the OS
he is using so we can't be specific however at least 5.0.6 and 5.0.7
have an inconsistency in the xterm termcap entry for the HOME key.

ho=\E[H
kh=\E[8 -- should be the same as ho, as least with PuTTy

This can cause some interesting problems.

[Bill Vermillion]

Post by Tom Parsons
| > We currently use teemtalk as our emulator. It works fine but it doesn't
| > support colour. I'm trying to use Putty emulator insetead of teemtalk
| > but I can't get it to display correctly. I can enter my login name &
| > password no problem but after that everything goes wrong. I tried
| > different settings but no success. I included my teemtalk settings and
| > I hope someone would help me to find which setting to use for putty?
| > $ set | grep TERM
| > TERM=wy50
| > but when I longin Putty I get a message "unknow teminal type wy50"
| > Can anyone help?
|
| It seems to me that message isn't consistent with the rest of the
| description, nevertheless ...
|
| AFAIK Putty isn't a Wyse-50 emulator, I'd choose one of the ANSI
| variants for yout TERM settings - I use TERM=xterm
|
| My putty settings for SCO OSR5 are
| {menu} {new settings}
| {terminal} {keyboard}
| Backspace: Control-H
| Home and End keys: standard
| Function keys: Esc[n~
| {connection}
| Options to send to server
| Terminal-type: xterm
|
| This works fine with terminfo based apps like vi and termcap based apps
| (I can't remember if I had to tweak xterm in termcap)
|
| {window} {translation}
| Received data assumed to be: CP437
| Handling of line-draw: Unicode
| I use this with a suitable font like Lucida Console.
| YMMV
We have a poster who didn't bother to include a description of the OS
he is using so we can't be specific however at least 5.0.6 and 5.0.7
have an inconsistency in the xterm termcap entry for the HOME key.
ho=\E[H
kh=\E[8 -- should be the same as ho, as least with PuTTy
This can cause some interesting problems.

He also posted the original question to comp.unix.bsd.freebsd.misc
with no indiation of ANY OS.

Bill

[Thomas Dickey]

...

Post by Tom Parsons
| AFAIK Putty isn't a Wyse-50 emulator, I'd choose one of the ANSI
| variants for yout TERM settings - I use TERM=xterm
|
| My putty settings for SCO OSR5 are
| {menu} {new settings}
| {terminal} {keyboard}
| Backspace: Control-H
| Home and End keys: standard
| Function keys: Esc[n~
| {connection}
| Options to send to server
| Terminal-type: xterm

...

Post by Tom Parsons
We have a poster who didn't bother to include a description of the OS
he is using so we can't be specific however at least 5.0.6 and 5.0.7
have an inconsistency in the xterm termcap entry for the HOME key.
ho=\E[H
kh=\E[8 -- should be the same as ho, as least with PuTTy

PuTTY's sense for standard (see above) is xterm's (not rxvt's).
Quoting from PuTTY's help-file:

The Unix terminal emulator rxvt disagrees with the rest of the world
about what character sequences should be sent to the server by the Home
and End keys.

xterm, and other terminals, send ESC [1~ for the Home key, and ESC [4~
for the End key. rxvt sends ESC [H for the Home key and ESC [Ow for
the End key.

If you find an application on which the Home and End keys aren't
working, you could try switching this option to see if it helps.

The reason of course is that xterm is emulating a vt100/etc rather than
an IBM PC derivative.

[PeterP]

sorry, my OS is: Digital UNIX V4
I tried all the suggestions but it didn't work. I don't think Putty
supports TVI920 emulation.
Thanks.

[Tom Parsons]

PeterP enscribed:
| sorry, my OS is: Digital UNIX V4
| I tried all the suggestions but it didn't work. I don't think Putty
| supports TVI920 emulation.

The PuTTY documentation is somewhat specific about what terminals it
supports. Damn few.

I wouldn't consider using it except where the ssh features are needed,
those are worthwhile.

[Steve M. Fabac, Jr.]

Post by Tom Parsons
| sorry, my OS is: Digital UNIX V4
| I tried all the suggestions but it didn't work. I don't think Putty
| supports TVI920 emulation.
The PuTTY documentation is somewhat specific about what terminals it
supports. Damn few.
I wouldn't consider using it except where the ssh features are needed,
those are worthwhile.
--
==========================================================================
==========================================================================

I've developed a usable work around for using VisionFS Termlite over
forwarded ssh tunnels that might be acceptable to the OP.

On my Windows desktop system, I have installed TerraTerm Pro with ssh
extensions. I configure TerraTerm Pro to set up port forwarding for port
23 (standard telnet) from local host on my Windows system to local host
on the remote SCO UNIX system. Once TerraTerm Pro is connected via
ssh to the remote system, I have a desktop icon for my TermLite with
the target set to "-host local host" so that it connects to the local
host port on my windows box. Port forwarding 23 to the remote UNIX
system then results in a login from the remote UNIX box being presented
on the Termlite session.

This requires me to login as myself once via TerraTerm Pro and then I have
to login again with Termlite. This allows me to login on TermLite as
root (or any other user account) over the encrypted tunnel setup by
TerraTerm Pro. >I always configure sshd to deny root login on my client's
systems as root is a known account and we log 100 to 1000+ connection
attempts using root each month.<

This setup consumes two user licenses and is probably too complicated for
non administrative system users. Although, I have several clients where
I set this up on their laptops so that they can work from home with
TermLite just the same as they do when at the office.

This technique is usable for any non ssh capable terminal emulation program
that is able to connect via TCP. If the OP has a TVI920 emulator program, he
can use this technique to forward it to his UNIX server. No need to use
TerraTerm Pro if putty has port forwarding capability.


--

Steve Fabac
S.M. Fabac & Associates
816/765-1670

[u***@hotpop.com]

On Wed, 17 Aug 2005 17:30:34 GMT, "Steve M. Fabac, Jr."

Post by Steve M. Fabac, Jr.

Post by Tom Parsons
| sorry, my OS is: Digital UNIX V4
| I tried all the suggestions but it didn't work. I don't think Putty
| supports TVI920 emulation.
The PuTTY documentation is somewhat specific about what terminals it
supports. Damn few.
I wouldn't consider using it except where the ssh features are needed,
those are worthwhile.
--
==========================================================================
==========================================================================

I've developed a usable work around for using VisionFS Termlite over
forwarded ssh tunnels that might be acceptable to the OP.
On my Windows desktop system, I have installed TerraTerm Pro with ssh
extensions. I configure TerraTerm Pro to set up port forwarding for port
23 (standard telnet) from local host on my Windows system to local host
on the remote SCO UNIX system. Once TerraTerm Pro is connected via
ssh to the remote system, I have a desktop icon for my TermLite with
the target set to "-host local host" so that it connects to the local
host port on my windows box. Port forwarding 23 to the remote UNIX
system then results in a login from the remote UNIX box being presented
on the Termlite session.
This requires me to login as myself once via TerraTerm Pro and then I have
to login again with Termlite. This allows me to login on TermLite as
root (or any other user account) over the encrypted tunnel setup by
TerraTerm Pro. >I always configure sshd to deny root login on my client's
systems as root is a known account and we log 100 to 1000+ connection
attempts using root each month.<
This setup consumes two user licenses and is probably too complicated for
non administrative system users. Although, I have several clients where
I set this up on their laptops so that they can work from home with
TermLite just the same as they do when at the office.
This technique is usable for any non ssh capable terminal emulation program
that is able to connect via TCP. If the OP has a TVI920 emulator program, he
can use this technique to forward it to his UNIX server. No need to use
TerraTerm Pro if putty has port forwarding capability.

Perhaps stunnel would also work, I haven't used it in a few years,
and only used it to get nntp acces from a non-ssl news reader, but I
think it can be used to allow any non-ssl terminal emulator to access
a ssl connection.
http://www.stunnel.org/download/binaries.html

[mbennett]

Why not try AlphaCom from
http://www.omnicomtech.com/
It has wyse50 emulation, color and ssh.

[Tony Lawrence]

Post by Tom Parsons
| sorry, my OS is: Digital UNIX V4
| I tried all the suggestions but it didn't work. I don't think Putty
| supports TVI920 emulation.
The PuTTY documentation is somewhat specific about what terminals it
supports. Damn few.
I wouldn't consider using it except where the ssh features are needed,
those are worthwhile.

Alphacom is cheap ($25.00) and does a nice SCO emulation.

But see http://aplawrence.com/SCOFAQ/FAQ_scotec1winterm.html for a large
list of ssh and telnet emulators.

[Brian K. White]

----- Original Message -----
From: "PeterP" <***@yahoo.com>
Newsgroups: comp.unix.sco.misc
To: <***@jpr.com>
Sent: Wednesday, August 17, 2005 9:14 AM

Post by PeterP
sorry, my OS is: Digital UNIX V4
I tried all the suggestions but it didn't work. I don't think Putty
supports TVI920 emulation.
Thanks.

You are correct. It doesn't.

It emulates a small family ansi and vt based terminal types, including sco
ansi, freebsd, linux, (and probably any other unix console), xterm, and
rxvt.
Those are all very similar terminal types.

Generally speaking, that doesn't matter to you at all and you can use any
kind of terminal or emulator you want, including putty.
The server has something called a terminal capabilities database. 2
different ones usually, the single text file /etc/termcap, and a directory
tree of compiled binary files and text sources collectively called terminfo.
Ideally the way it works is:
* You have something like a dictionary entry in the termcap & terminfo that
describes all the details of your terminal. If they are not there or if they
are not quite accurate, it's easy to just add them or edit them at will.
* Sometimes your application has it's own terminal database that also needs
to be edited the same way.
* You configure your terminal emulator to tell the server what type of
terminal you are using, ie, so that after logging in TERM=<the correct entry
in termcap & terminfo>

However a common problem I do encounter, that you might have as well, is
when application vendors who just about know how to spell "unix" install a
server and they hard code the TERM value in everyones .profile or in
/etc/profile or even in their applications start-script, which throws away
and overwrites the _correct_ TERM value that your terminal emulator
supplied. This is a completely broken type of arrangement that really should
be fixed "just because".

Only extremely rarely, probably never since at least 10 years, is an
application actually hard coded to only know how to work with a particular
type of terminal.
Only in that case do you really need specifically a TVI920 emulator and only
a TVI920 emulator.

You just need someone with basic unix skills to properly configure termcap,
terminfo, login profiles, app start scripts, and a terminal emulator of your
choice to make them all agree with each other.
Then the server and/or the application is no longer hard coded to only work
with one type of terminal and you can use anything that strikes your fancy
from then on.

Or go to aplawrence.com and punch in "termcap" or "terminal emulator" into
the search box. Or any words or phrases in this post, and start reading.
He's got lots of nice tutorials and recipes and articles that spell it all
out in detail and describe all the variables and optional ways of doing
things.

Or find a terminal emulator that claims TVI920 among it's list of terminals
it emulates. Also note that sometimes a terminal emulator might not say it
emulates "tvi920" specifically, but it may list some other terminal that is
a perfectly compatible superset or subset and would work fine. Anzio for
instance lists TV965. Try that and it might just work without changing
anything anywhere.

Brian K. White -- ***@aljex.com -- http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!

[Simon Hobson]

Post by PeterP
sorry, my OS is: Digital UNIX V4
I tried all the suggestions but it didn't work. I don't think Putty
supports TVI920 emulation.

As others have pointed out, you probably don't need that specific terminal.
However, if you really do it might be worth a look at www.ttwin.com, where
you will find TVI950 and TVI955 emulations (I've no idea if they are
compatible with TVI920).

I have seen every problem described by Brian K White on just one system !
Once you realise what's going on then it is easy to fix most of them - but
not applications with terminal specific codes built in (in our case, an old
application that directly accessed the print through facility of the terminal
to use an attached serial printer).

At work we use the web deployable version (ttweb) which is quite good as you
can set up a web page with a button which will automatically download the
software and settings - if you need to alter the settings or update the
software, simply alter the master copy on the web server and next time people
connect they will get the update. It has issues with people who aren't power
users or local admins on their machines as it needs to install an OCX
component to work - but that's get aroundable.

Simon