Originally Posted by pyro451
Ok, I emailed screenshots of the configuration screen in MobileSSH and of the problem screens when connected to our server to Idokorro support this morning. I anxiously await a reply.
Thanks for the offer to help!
Workaround: Use a UNIX/Linux server to be your VT52->VT100 translator.
In other worlds: You can run a VT52 terminal inside a shell running inside a VT100 terminal, which you can connect to using existing telnet/ssh clients.
In more technical words: Setup a UNIX or Linux box. telnet/ssh to to UNIX/Linux box using VT100. Install and run a VT52 terminal application that's designed to run at the console. Use this application to connect to your VT52 host. Presto - it will translate VT52 sequences to VT100 sequences.
As far as I know, there are a number of VT52 sequences that are not supported by some modern VT100 clients, because they are rarely used. If you have a UNIX box, and still want Idokorro to fix this, you can capture these VT sequences by using the 'script' command right before your 'telnet' / 'ssh' command (to record a 'typescript' logfile that contains all the raw escape sequences). Mail this raw capture of your telnet/ssh session to Idokorro and they may be able to identify certain escape sequences that were not supported (i.e. certain VT52 sequences that were not supported). This type of debugging was invaluable to Idokorro a few years ago in refining their VT100 support.