[Info-vax] How to get F Keys to works on Putty Terminal Emulation

Stephen Hoffman seaohveh at hoffmanlabs.invalid
Thu Apr 4 17:37:54 EDT 2013


On 2013-04-04 20:30:38 +0000, sy3913 at googlemail.com said:

> Thanks for the responses - I am using MS Remote Desktop Connection from 
> my Toshiba laptop running Win 7 to connect to the win 2008 server, and 
> then puTTy from there.I tried the 3 options on Remote Desktop (on my 
> laptop) - Options - Local Resources - Keyboard - (Winows Key 
> Combinations), and they did not make any difference.
> I think i read somewhere in the puTTy FAQ to find out what the key 
> escape sequence is and email their support. Is there a way to find out 
> the key sequence received by the vms session when pressing a key ...or 
> is this approach a waste of time.
> Thanks again for any help.

This has nothing to do with OpenVMS, and probably nothing to do with PuTTY.

You might as well be asking your question of yaks and penguins, as this 
isn't a Microsoft Windows support newsgroup, and various denizens here 
are not known for a particular fondness of Windows for that matter.  
Consider raising your question with a VNC/RDP connection into Windows 
Server in a Windows discussion forum, or escalate this question with 
your organization's IT support folks.

Again, while OpenVMS is apparently central to your goal with the 
tool-chain used here, this issue very likely doesn't matter what 
operating system PuTTY might be connected into.

If you want to work this issue with the yaks and penguins here, see if 
PuTTY works when used directly on the Windows Server box.  It likely 
will.

That alone will tell you that this isn't an OpenVMS issue.

Then start replacing some of that gear on on the client and/or on the 
Windows Server, and see what starts working.

As an example, try a different VNC/RDP client at the remote site.  
Check with some WIndows folks for recommendations.  Or load Linux and a 
VNC/RDP client at the remote site and/or use OS X with CoRD or another 
VNC/RDP client installed at the remote site, or try a connection to a 
Linux VNC/RDP server on the target network (probably running dxterm or 
such).

Or work directly with your organization's IT group, as only folks with 
IT groups around will tend to set up connections that are this 
complicated.  See if they can set up a more direct approach for 
connecting to the target OpenVMS servers, and eliminate the need for 
this VNC/RDP connection, too.  Or different or better tools.


-- 
Pure Personal Opinion | HoffmanLabs LLC




More information about the Info-vax mailing list