| Author |
Getting num-lock to behave as PF1 in DECwindows |
JonathanBelanger
Member
Posts: 42
Joined: 09.06.16 |
| Posted on June 12 2016 12:37 |
|
|
Hi All,
So, here is my configuration:
- Windows 10
- Xming 32-bit
- SimH VAX (MicroVAX 3900)
- OpenVMS VAX V7.3
- Multinet 5.5
- DECwindows 12.6
I have everything up and running and can create a session manager window. It all works really well. My one problem is that when editing a file with EDT, the PF1 key (Num Lock keypad key) does not appear to work. If I kit the ESC key and then the PF1 key, I see that <ESC>OP is sent (as it should be), but it does not put the remaining keys into their GOLD state. The PF2 key ('/' keypad key) does work as expected. What do I need to do to get the num-lock key to be recognized and processed as if it were the PF1 (Gold) key?
Thanks,
~Jon. |
|
|
| Author |
RE: Getting num-lock to behave as PF1 in DECwindows |
abrsvc
Member
Posts: 108
Joined: 12.03.10 |
| Posted on June 13 2016 04:38 |
|
|
A couple of things to verify:
1) What is your terminal type? (Show Term)
2) Are you actually in screen mode for EDT?
The first things to check are listed above. You can try a SET TERM/INQ as well to have the screen queried to set the terminal type.
Update this with the results.
Dan |
|
|
| Author |
RE: Getting num-lock to behave as PF1 in DECwindows |
JonathanBelanger
Member
Posts: 42
Joined: 09.06.16 |
| Posted on June 13 2016 12:38 |
|
|
Hi Dan,
1) It is a DECwindows Terminal. Here is the output of show term:
Terminal: _FTA3: Device_Type: VT300_Series Owner: _FTA3:
Username: SYSTEM
Input: 9600 LFfill: 0 Width: 132 Parity: None
Output: 9600 CRfill: 0 Page: 48
Terminal Characteristics:
Interactive Echo Type_ahead No Escape
Hostsync TTsync Lowercase Tab
Wrap Scope No Remote Eightbit
Broadcast No Readsync No Form Fulldup
No Modem No Local_echo No Autobaud No Hangup
No Brdcstmbx No DMA No Altypeahd Set_speed
No Commsync Line Editing Overstrike editing No Fallback
No Dialup No Secure server No Disconnect No Passthru
No Syspassword No SIXEL Graphics No Soft Characters No Printer Port
Application keypad ANSI_CRT No Regis No Block_mode
Advanced_video Edit_mode DEC_CRT DEC_CRT2
DEC_CRT3 No DEC_CRT4 No DEC_CRT5 No Ansi_Color
VMS Style Input
2) Yes, I'm in screen mode. Also, the problem occurs in LSE and TPU.
Thanks,
~Jon. |
|
|
| Author |
RE: Getting num-lock to behave as PF1 in DECwindows |
abrsvc
Member
Posts: 108
Joined: 12.03.10 |
| Posted on June 14 2016 10:57 |
|
|
Try the following:
SET TERM/NOEIGHT/NOAPPLICATION
The keypad is set to application mode (the eightbit probably has no effect here) and in application mode may override the standard. Mine are all set to numeric keypad mode.
Update this with the results. |
|
|
| Author |
RE: Getting num-lock to behave as PF1 in DECwindows |
JonathanBelanger
Member
Posts: 42
Joined: 09.06.16 |
| Posted on June 18 2016 03:59 |
|
|
I made the change and it made it worse. The "/" (PF2) key no longer worked. I think I know what the issue is. In my environment, I either need the X windows server to translate the PC keystrokes into equivalent LK201 keystrokes (keycode, etc.), or I need a keymap in the VAX for a PC keyboard (101/ 102 keys, I believe). Does anyone have a PC keyboard keymap file in the DECW$KEYMAP directories, or a way to configure Xming to emluate an LK keyboard?
Thanks,
~Jon. |
|
|
| Author |
RE: Getting num-lock to behave as PF1 in DECwindows |
JonathanBelanger
Member
Posts: 42
Joined: 09.06.16 |
| Posted on June 19 2016 09:55 |
|
|
I finally figured out what was going on. I used xmodmap and xev to determine that once I figured out the PF keys, that the other keypad keys, thou appeared to be doing what they were supposed to be doing, were in fact not. After defining the entire keypad and using xmodmap to load them, the keypad worked ass I had hoped. If need be, I can create a decw$keymap file and load it. I decided to just create a xmodmap file in sys$manager and a call in sylogin to load it for interactive mode when the decw$display logical is defined. At some point I'll go through all the other keys and redefine them as needed, but for now I have what I need.
~Jon. |
|
|
