From: SMTP%"glenn@lightning.nsc.com" 17-MAY-1994 14:46:26.26 To: EVERHART CC: Subj: Re: accessing VAX/VMS with SUN keyboards ? X-Newsgroups: comp.os.vms From: glenn@lightning.nsc.com (Glenn Newell) Subject: Re: accessing VAX/VMS with SUN keyboards ? Message-ID: Sender: news@nsc.nsc.com (netnews maintenance) Nntp-Posting-Host: laurajean.nsc.com Reply-To: glenn@lightning.nsc.com Organization: Not an official spokesperson for NATIONAL SEMICONDUCTOR, (408)721-5000 Date: Tue, 17 May 1994 15:54:06 GMT Lines: 206 To: Info-VAX@CRVAX.SRI.COM X-Gateway-Source-Info: USENET In article 4zJ@walter.bellcore.com, wws@cc.bellcore.com (Wayne Scott) writes: > >Hi Folks: > > I need to access a VAX/VMS environment from a SUN/Solaris >workstation. I'm having trouble getting the keypad to behave as expected. >Has anyone out there been able to map the SUN keypad to work like a VT___? > >Thanks, >Wayne Scott Wayne, Here's a collection of posts on the subject. Also, I have an X application that puts up a little window with buttons for all the F and keypad keys. I'll send it to you if you want. I'm not on solaris but I understand it has been ported. ---------------------------------------------------------------------------------------From waraich@biostat.wisc.edu Sun Sep 12 14:54:32 1993 From: Saad M. Waraich Subject: Re: Xterm Keyboard Mapping To: glenn@rockie.nsc.com (Glenn Newell) Date: Sun, 12 Sep 93 16:48:47 CDT Cc: waraich@biostat.wisc.edu (Saad M. Waraich) X-Mailer: ELM [version 2.3 PL11] Content-Length: 1341 Glenn I was finally able to get what I wanted. Not only does the program work like a charm, but I was also able to create an XTerm mapping file by going through your source code. BTW: This mapping maps a Sun Type5 keyboard's numeric keypad to DEC LK201. Once again, thanks a lot. Saad XTerm*VT100.Translations: #override F9: keymap(vt) XTerm*vtKeymap.translations: F9: keymap(None) \n\ Num_Lock: string(0x1B) string("OP") \n\ KP_Divide: string(0x1B) string("OQ") \n\ KP_Multiply: string(0x1B) string("OR") \n\ KP_Subtract: string(0x1B) string("OS") \n\ KP_7: string(0x1B) string("Ow") \n\ KP_8: string(0x1B) string("Ox") \n\ KP_9: string(0x1B) string("Oy") \n\ KP_Add: string(0x1B) string("Om") \n\ KP_4: string(0x1B) string("Ot") \n\ KP_5: string(0x1B) string("Ou") \n\ KP_6: string(0x1B) string("Ov") \n\ KP_Enter: string(0x1B) string("Ol") \n\ KP_1: string(0x1B) string("Oq") \n\ KP_2: string(0x1B) string("Or") \n\ KP_3: string(0x1B) string("Os") \n\ KP_0: string(0x1B) string("Op") \n\ KP_Decimal: string(0x1B) string("On") \n -- ----- End Included Message ----- From jimmy@denwa.info.com (Jim Gottlieb) Newsgroups: comp.sys.sun.admin,comp.windows.x.apps Subject: Summary: xterm F-keys & Num keys Date: 11 Jan 1994 16:05:06 -0800 In article <2gakat$1uv@denwa.info.com> I wrote: > >One thing I'm desperately trying to do is get their numeric keypads and >function keys working. For reference, we are using the xterm that >comes with OpenWindows 3.0. Several people asked me to pass on the answer, so here we go... Although I have never seen reference to it in any manual, you can use the @Num_Lock modifier to reference keys pressed when the NumLock is on. Sun apparently released a patch that was just a new /usr/openwin/lib/app-defaults/XTerm file and it was in there. Here is the translations settings that we are now using. Note that you will have to monkey with your xterm termcap and terminfo entries to get them to match if you want to use the function key definitions we use. At least they are close to vt100, unlike the default xterm ones. Also note that all translations with a modifier must precede those without. And of course, these won't take effect until you exit the window system and restart or use xrdb to read them in. We have only type-4 keyboards on our Suns. I don't know what would need to be changed to make everything work on a type-5, though I would like to know since our financial people complain about the lack of separate cursor keys. I also modified this for use on our 386 machines running X386 by substituting the following Sun PC-AT --- ----- R7 Home R9 Prior R13 End R15 Next and eliminating other references to Sun-only keys. I still believe strongly that xterm as distributed should be more vt-100-like in its key mapping. XTerm*VT100.Translations: #override \ @Num_LockKP_0: string(0)\n\ @Num_LockKP_1: string(1)\n\ @Num_LockKP_2: string(2)\n\ @Num_LockKP_3: string(3)\n\ @Num_LockKP_4: string(4)\n\ @Num_LockKP_5: string(5)\n\ @Num_LockKP_6: string(6)\n\ @Num_LockKP_7: string(7)\n\ @Num_LockKP_8: string(8)\n\ @Num_LockKP_9: string(9)\n\ @Num_LockKP_Add: string(+)\n\ @Num_LockKP_Decimal: string(.)\n\ @Num_LockKP_Divide: string(/)\n\ @Num_LockKP_Enter: string(\015)\n\ @Num_LockKP_Equal: string(=)\n\ @Num_LockKP_Multiply: string(*)\n\ @Num_LockKP_Subtract: string(-)\n\ KP_Enter: string(0x1B) string("OM") \n\ F1: string(0x1B) string("OP") \n\ F2: string(0x1B) string("OQ") \n\ F3: string(0x1B) string("OR") \n\ F4: string(0x1B) string("OS") \n\ F5: string(0x1B) string("Ot") \n\ F6: string(0x1B) string("Ou") \n\ F7: string(0x1B) string("Ov") \n\ F8: string(0x1B) string("Ol") \n\ F9: string(0x1B) string("Ow") \n\ F10: string(0x1B) string("Ox") \n\ F11: string(0x1B) string("Oy") \n\ F12: string(0x1B) string("Oz") \n\ Insert: string(0x1B) string("Op") \n\ R13: string(0x1B) string("[F") \n\ Down: string(0x1B) string("OB") \n\ R15: string(0x1B) string("[G") \n\ Left: string(0x1B) string("OD") \n\ R11: string(0x1B) string("Ou") \n\ Right: string(0x1B) string("OC") \n\ R7: string(0x1B) string("[H") \n\ Up: string(0x1B) string("OA") \n\ R9: string(0x1B) string("[I") \n\ F28: string(0x7F) \n\ SunXK_F37: string(0x1B) string("OC") \n\ SunXK_F36: string(0x1B) string("OD") KP_Add: string(+)\n\ KP_Divide: string(/)\n\ KP_Enter: string(\015)\n\ KP_Equal: string(=)\n\ KP_Multiply: string(*)\n\ KP_Subtract: string(-)\n\ F16: start-extend() select-end(PRIMARY, CUT_BUFFER0, CLIPBOARD) \n\ F18: insert-selection(PRIMARY, CLIPBOARD) \n\ XTerm*tek4014.Translations: #override \ @Num_LockKP_0: string(0)\n\ @Num_LockKP_1: string(1)\n\ @Num_LockKP_2: string(2)\n\ @Num_LockKP_3: string(3)\n\ @Num_LockKP_4: string(4)\n\ @Num_LockKP_5: string(5)\n\ @Num_LockKP_6: string(6)\n\ @Num_LockKP_7: string(7)\n\ @Num_LockKP_8: string(8)\n\ @Num_LockKP_9: string(9)\n\ @Num_LockKP_Add: string(+)\n\ @Num_LockKP_Decimal: string(.)\n\ @Num_LockKP_Divide: string(/)\n\ @Num_LockKP_Enter: string(\015)\n\ @Num_LockKP_Equal: string(=)\n\ @Num_LockKP_Multiply: string(*)\n\ @Num_LockKP_Subtract: string(-)\n\ KP_Add: string(+)\n\ KP_Divide: string(/)\n\ KP_Enter: string(\015)\n\ KP_Equal: string(=)\n\ KP_Multiply: string(*)\n\ KP_Subtract: string(-)\n\ -- Jim Gottlieb E-Mail: jimmy@denwa.info.com In Japan: jimmy@denwa.linc.or.jp V-Mail: +1 310 551 7702 Fax: 478-3060 Voice: 824-5454 --- ________________________________________________________________________________ Glenn Newell I am not an official spokesperson for National National Semiconductor Semiconductor. All the above are my own (humble) glenn@lightning.nsc.com opinions. Use at your own risk. voice (408)721-4291 /---- / /---- /\ / /\ / fax (408)721-4785 / __ / /--- / \ / / \ / /____/ /____ /____ / \/ / \/ ________________________________________________________________________________