Forum

VT Emulation detect...
 
Notifications
Clear all

VT Emulation detection issue?

0 Posts
4 Users
0 Reactions
159 Views
(@bayp)
Active Member
Joined: 22 years ago
Posts: 4
Topic starter  

Did something change in the VT102 and VT220 emulations between version 3.00 and v3.50?

The reason that I ask is because I use Absolute Telnet to access a VMS machine at work. v3.0 would have the VT settings auto-detect just fine. v3.50 it errors out on the auto-detect saying that it's receiving a "partial escape". Has anyone else experienced this problem? Any ideas on how to fix it other then reinstalling v3.0?


   
ReplyQuote
(@bpence)
Member Admin
Joined: 10 months ago
Posts: 1374
 

Kurt,

Can you give me a screen snapshot of the problem you are having? I assume you're using telnet.

Does the error occur immediately at login?

Also, if you could provide a logfile, beginning before login all the way through till you get the error (File->Open log & file->Close Log)

Brian


   
ReplyQuote
(@bayp)
Active Member
Joined: 22 years ago
Posts: 4
Topic starter  

Brian: Yes, I am using Telnet.

This is a telnet through a secure VPN connection. The error occurs when it attempts to determine the terminal type (which is at login, but also can be done manually from the command line). In either case, it fails. To spare you from having to look through a ton of logs, I've taken a log and screen shot of just the automatic detection command sequence. SET TERM/INQUIRE is the command.

Here is the screen shot: <broken link removed>

Here is the log file: <broken link removed>

Please let me know if there is any additional information that you need from me. Thanks for your help!

kec

[size=1][ November 09, 2004, 07:34 PM: Message edited by: Kurt Claussen ][/size]

This post was modified 3 months ago by bpence

   
ReplyQuote
(@bhpence)
New Member
Joined: 20 years ago
Posts: 2
 

Try this and let me know how it goes:

Beta Testing

Brian

This post was modified 3 months ago by bpence

   
ReplyQuote
(@bayp)
Active Member
Joined: 22 years ago
Posts: 4
Topic starter  

Brian:

That worked. It detects properly without error now. Thanks for the help!

kec


   
ReplyQuote
(@zwill)
Active Member
Joined: 22 years ago
Posts: 8
 

I had the same problem after upgrading to 3.50 from 3.13 when trying to log into HP-UX 10.20 machines. I downloaded and installed 3.51 and that seemed to fix the problem. Thanks!


   
ReplyQuote
Share: