I need someone to assist that is a terminal emulation wizard.
Funny I am asking this under General Formums. Anyfoo, let's begin:

I am trying to make powerterm not echo back this character:



≥



When I press control-C I get it that one char garbage echoed back.

How to turn off? where? what config? is there.

Redhats offical statement is:

"I will look over the provided profile script, but as we discussed this issue is only reproducible with the specific terminal emulation being used in powerterm, and therefore falls outside the scope of support."

Which means, they don't know how to control emulation, or there is no one on staff in that past 1 month who can do it via paid$$$ RH support.

What we know:
Linux to Linux via powerterm - works!
Windows to Linux via powerterm - echos garbage.

When I switch UPS set, to latin-1, echos diff garbage.
New version of powerterm has UTF-8 option, but demo I can not save. This is not an option at this time to upgrade.

Out environment:
We are stuck with wyse-60 emulator using telnet, not ssh, nor putty ssh at this time.

possibles:
termcap, terminfo, inputrc, /etc/profile.d/myloginscript.sh, anything you suggest!

No, it means that Red Hat has no say over what the PowerTerminal folks do. Report the bug to the PowerTerminal folks.

termcap is a good start, maybe terminfo as well. Figure out the names of your term entries and try them out. Maybe once you log in, a simple TERM=vt100 or TERM=ansi might make programs and program output behave a little nicer. vt100 is really basic, black-and-white, compatible even with HyperTerminal. Not everybody has a "linux" term setting, and not every "linux" term is the same. Should you have an /etc/termcap, read it and see if there's anything compatible in there. The goal is to find a compatible term setting pair between the two points and use them. It might not even work out to be ansi and ansi, or vt100 and vt100.

It's out of my scope of expertise, though. I use Slackware and probably use a different getty (which can determine the term used at logon), different termcap, different init system (which means I don't know the Red Hat equivalent of /etc/inittab). The last time I dealt with a different system, it was using a FreeBSD PC to connect to Linux via serial, and TERM=ansi on both sides seemed to work better than other options.