LK463
dit...@dittman.net
OS X. To do this I need a complete list of the keycodes since the
current keymaps don't pass them all.
Does anyone have a complete list they could send me? Once I have the
new keyboard map finished I'll put it online for interested parties
to download.
--
Eric Dittman
dit...@dittman.net
Bob Koehler
If you bring up X11 (Apple's current server for OS X is pretty good)
and run somthing like xev, you can read off the keycodes yourself.
dit...@dittman.net
I tried that already and apparently OS X doesn't pass on keycodes it doesn't
know.
--
Eric Dittman
dit...@dittman.net
Ken Fairfield
I don't have a solution, but an observation. The LK463 is a USB
keyboard. In principle, USB is "universal" and all the key codes
sent should be received by the host system.
What a coworker and I discovered is that under Windows XP, there
are several keys the Windows system, or the application running
under Windows, just doesn't "see", e.g., Do and Help, IIRC...there
may well be others.
My coworker spent some time with the Attachmate(?) folks using some
diagnostic under KEAterm (which "saw" more of the keys than does
Exceed) and they concluded that there simply was nothing being sent
by the keyboard for those keys. I'm almost certain that's wrong,
but it may very well be the case that the Windows USB driver for the
keyboard is "swallowing" things it doesn't recognize and not sending
them onto the application. This key works, as reported by Fred K.,
on VMS-supported USB equipment, e.g., the Itanium systems.
You may very well be between a rock and a hard place with your Mac.
This keyboard works with Windows if and only if I use the supplied
USB <-> PS/2 adapter, but I do Mac's have PS/2 ports?
The other possiblity/necessity would be to modify the USB keyboard
driver for the Mac. I have no idea how one would go about doing
that or where to find the source!
If you need the X-windows key codes and key symbols produced under
DECwindows/Motif native on a DPW, I can probably provide those,
but I expect your problem is much more basic than that.
-Ken
--
I don't speak for Intel, Intel doesn't speak for me...
Ken Fairfield
D1C Automation VMS System Support
who: kenneth dot h dot fairfield
where: intel dot com
Forrest Kenney
I don't have the specification for the LK463 at hand but it sends
no unique key codes. Every key code needed already existed in the
USB Human Interface Device specification for keyboards.
In PS2 mode the LK463 sends exactly the same data at the other
LK4XX keyboards. So if the applications are not seeing the keycodes
it is because Windows or OS-X are not passing them through.
Forrest Kenney
OpenVMS
Dave Weatherall
<forrest_dot_kenney@hp_dot.com> wrote:
>
> I don't have the specification for the LK463 at hand but it sends
> no unique key codes. Every key code needed already existed in the
> USB Human Interface Device specification for keyboards.
>
> In PS2 mode the LK463 sends exactly the same data at the other
> LK4XX keyboards. So if the applications are not seeing the keycodes
> it is because Windows or OS-X are not passing them through.
I'm no WinXP keyboard expert but when trying to get a german keyboard
working with a mate's UK version of XP recently, (not as simple as in
previous versions of Windaz) I read the Help documentation on
keyboards. It had some explanations, maybe there's a clue for you
there. I don't use XP on anything running at the moment or I'd quote
chapter and verse.
--
Cheers - Dave W.
William Webb
http://www.macwindows.com/keyboard.html
WWWebb
--
NOTE: This email address is only used for noncommerical VMS-related
correspondence.
All unsolicited commercial email will be deemed to be a request for
services pursuant to the terms and conditions located at
http://bellsouthpwp.net/w/e/webbww/
Forrest Kenney
Attached is the HID keyboard page definitions. ID's with "*"
are used by LK463. The HID table is complete but I could have missed
a mapping for the LK463.
Forrest
Usage ID Usage ID Usage Name
(Dec) (*) (Hex)
0 * 00 Reserved (no event indicated)
1 * 02 Keyboard POSTFail
3 * 03 Keyboard ErrorUndefined
4 * 04 Keyboard a and A
5 * 05 Keyboard b and B
6 * 06 Keyboard c and C
7 * 07 Keyboard d and D
8 * 08 Keyboard e and E
9 * 09 Keyboard f and F
10 * 0A Keyboard g and G
11 * 0B Keyboard h and H
12 * 0C Keyboard i and I
13 * 0D Keyboard j and J
14 * 0E Keyboard k and K
15 * 0F Keyboard l and L
16 * 10 Keyboard m and M
17 * 11 Keyboard n and N
18 * 12 Keyboard o and O
19 * 13 Keyboard p and P
20 * 14 Keyboard q and Q
21 * 15 Keyboard r and R
22 * 16 Keyboard s and S
23 * 17 Keyboard t and T
24 * 18 Keyboard u and U
25 * 19 Keyboard v and V
26 * 1A Keyboard w and W
27 * 1B Keyboard x and X
28 * 1C Keyboard y and Y
29 * 1D Keyboard z and Z
30 * 1E Keyboard 1 and !
31 * 1F Keyboard 2 and @
32 * 20 Keyboard 3 and #
33 * 21 Keyboard 4 and $
34 * 22 Keyboard 5 and %
35 * 23 Keyboard 6 and ^
36 * 24 Keyboard 7 and &
37 * 25 Keyboard 8 and *
38 * 26 Keyboard 9 and (
39 8 27 Keyboard 0 and )
40 * 28 Keyboard Return (ENTER)
41 * 29 Keyboard ESCAPE
42 * 2A Keyboard DELETE (Backspace)
43 * 2B Keyboard Tab
44 * 2C Keyboard Spacebar
45 * 2D Keyboard - and (underscore)
46 * 2E Keyboard = and +
47 * 2F Keyboard [ and {
48 * 30 Keyboard ] and }
49 * 31 Keyboard \ and |
50 * 32 Keyboard Non-US # and ~
51 * 33 Keyboard ; and :
52 * 34 Keyboard and 4
53 * 35 Keyboard Grave Accent and Tilde
54 36 Keyboard, and <
55 37 Keyboard . and >
56 38 Keyboard / and ?
57 39 Keyboard Caps Lock
58 * 3A Keyboard F1
59 * 3B Keyboard F2
60 * 3C Keyboard F3
61 * 3D Keyboard F4
62 * 3E Keyboard F5
63 * 3F Keyboard F6 (keypad , VMS)
64 * 40 Keyboard F7
65 * 41 Keyboard F8
66 * 42 Keyboard F9
67 * 43 Keyboard F10
68 * 44 Keyboard F11
69 * 45 Keyboard F12
70 46 Keyboard PrintScreen
71 47 Keyboard Scroll Lock
72 48 Keyboard Pause
73 * 49 Keyboard Insert (PF4 VMS)
74 * 4A Keyboard Home (Find VMS)
75 * 4B Keyboard PageUp (Prev VMS)
76 * 4C Keyboard Delete Forward (Remove VMS)
77 * 4D Keyboard End (Select VMS)
78 * 4E Keyboard PageDown (Next VMS)
79 * 4F Keyboard RightArrow
80 * 50 Keyboard LeftArrow
81 * 51 Keyboard DownArrow
82 * 52 Keyboard UpArrow
83 53 Keypad Num Lock and Clear
84 54 Keypad /
85 55 Keypad *
86 * 56 Keypad - (Keypad enter VMS)
87 57 Keypad +
88 58 Keypad ENTER
89 * 59 Keypad 1 and End
90 * 5A Keypad 2 and Down Arrow
91 * 5B Keypad 3 and PageDn
92 * 5C Keypad 4 and Left Arrow
93 * 5D Keypad 5
94 * 5E Keypad 6 and Right Arrow
95 * 5F Keypad 7 and Home
96 * 60 Keypad 8 and Up Arrow
97 * 61 Keypad 9 and PageUp
98 * 62 Keypad 0 and Insert
99 63 Keypad . and Delete
100 64 Keyboard Non-US \ and |
101 65 Keyboard Application 10
102 66 Keyboard Power 9
103 67 Keypad =
104 * 68 Keyboard F13
105 * 69 Keyboard F14
106 * 6A Keyboard F15
107 * 6B Keyboard F16
108 * 6C Keyboard F17
109 * 6D Keyboard F18
110 * 6E Keyboard F19
111 * 6F Keyboard F20
112 * 70 Keyboard F21 (PF1 VMS)
113 * 71 Keyboard F22 (PF2 VMS)
114 * 72 Keyboard F23 (PF3 VMS)
115 73 Keyboard F24
116 * 74 Keyboard Execute (DO key VMS)
117 * 75 Keyboard Help
118 76 Keyboard Menu
119 77 Keyboard Select
120 78 Keyboard Stop
121 79 Keyboard Again
122 7A Keyboard Undo
123 7B Keyboard Cut
124 7C Keyboard Copy
125 7D Keyboard Paste
126 7E Keyboard Find
127 7F Keyboard Mute
128 80 Keyboard Volume Up
129 81 Keyboard Volume Down
130 82 Keyboard Locking Caps Lock
131 83 Keyboard Locking Num Lock
132 84 Keyboard Locking Scroll Lock
133 * 85 Keypad Comma
134 86 Keypad Equal Sign
135 87 Keyboard International1
136 88 Keyboard International2
137 89 Keyboard International3
138 8A Keyboard International4
139 8B Keyboard International5
140 8C Keyboard International6
141 8D Keyboard International7
142 8E Keyboard International8
143 8F Keyboard International9
144 90 Keyboard LANG1
145 91 Keyboard LANG2
146 92 Keyboard LANG3
147 93 Keyboard LANG4
148 94 Keyboard LANG5
149 95 Keyboard LANG6
150 96 Keyboard LANG7
151 97 Keyboard LANG8
152 98 Keyboard LANG9
153 99 Keyboard Alternate Erase
154 9A Keyboard SysReq/Attention
155 9B Keyboard Cancel
156 9C Keyboard Clear
157 9D Keyboard Prior
158 9E Keyboard Return
159 9F Keyboard Separator
160 A0 Keyboard Out
161 A1 Keyboard Oper
162 A2 Keyboard Clear/Again
163 A3 Keyboard CrSel/Props
164 A4 Keyboard ExSel
165-175 A5-CF Reserved
176 B0 Keypad 00
177 B1 Keypad 000
178 B2 Thousands Separator
179 B3 Decimal Separator
180 B4 Currency Unit
181 B5 Currency Sub-unit
182 B6 Keypad (
183 B7 Keypad )
184 B8 Keypad {
185 B9 Keypad }
186 BA Keypad Tab
187 BB Keypad Backspace
188 BC Keypad A
189 BD Keypad B
190 BE Keypad C
191 BF Keypad D
192 C0 Keypad E
193 C1 Keypad F
194 C2 Keypad XOR
195 C3 Keypad ^
196 C4 Keypad %
197 C5 Keypad <
198 C6 Keypad >
199 C7 Keypad &
200 C8 Keypad &&
201 C9 Keypad |
202 CA Keypad ||
203 CB Keypad :
204 CC Keypad #
205 CD Keypad Space
206 CE Keypad @
207 CF Keypad !
208 D0 Keypad Memory Store
209 D1 Keypad Memory Recall
210 D2 Keypad Memory Clear
211 D3 Keypad Memory Add
212 D4 Keypad Memory Subtract
213 D5 Keypad Memory Multiply
214 D6 Keypad Memory Divide
215 D7 Keypad +/-
216 D8 Keypad Clear
217 D9 Keypad Clear Entry
218 DA Keypad Binary
219 DB Keypad Octal
220 DC Keypad Decimal
221 DD Keypad Hexadecimal
222-223 DE-DF Reserved
224 E0 Keyboard LeftControl
225 * E1 Keyboard LeftShift
226 * E2 Keyboard LeftAlt
227 * E3 Keyboard Left GUI (L Compose VMS)
228 E4 Keyboard RightControl
229 * E5 Keyboard RightShift
230 * E6 Keyboard RightAlt
231 * E7 Keyboard Right GUI (R Compose VMS)
Ken Fairfield
> Attached is the HID keyboard page definitions. ID's with "*"
> are used by LK463. The HID table is complete but I could have missed
> a mapping for the LK463.
>
>
> Forrest
>
> Usage ID Usage ID Usage Name
> (Dec) (*) (Hex)
> 0 * 00 Reserved (no event indicated)
> 1 * 02 Keyboard POSTFail
> 3 * 03 Keyboard ErrorUndefined
[snip]
> 50 * 32 Keyboard Non-US # and ~
> 51 * 33 Keyboard ; and :
> 52 * 34 Keyboard and 4
> 53 * 35 Keyboard Grave Accent and Tilde
> 54 36 Keyboard, and <
> 55 37 Keyboard . and >
> 56 38 Keyboard / and ?
> 57 39 Keyboard Caps Lock
> 58 * 3A Keyboard F1
> 59 * 3B Keyboard F2
> 60 * 3C Keyboard F3
[snip]
Surely the LK463 must use 54-57, or some alternatives. I don't
see them marked in your table.
Thanks, Ken
Forrest Kenney
Like I said I could have missed a couple the LK463
specification has a really complex table with really tiny font. Those
are ones that I managed to miss there could be others.
Forrest
Ken Fairfield
> Attached is the HID keyboard page definitions. ID's with "*"
> are used by LK463. The HID table is complete but I could have missed
> a mapping for the LK463.
>
>
> Forrest
>
> Usage ID Usage ID Usage Name
> (Dec) (*) (Hex)
> 0 * 00 Reserved (no event indicated)
> 1 * 02 Keyboard POSTFail
> 3 * 03 Keyboard ErrorUndefined
> 4 * 04 Keyboard a and A
> 116 * 74 Keyboard Execute (DO key VMS)
> 117 * 75 Keyboard Help
> 225 * E1 Keyboard LeftShift
> 226 * E2 Keyboard LeftAlt
> 227 * E3 Keyboard Left GUI (L Compose VMS)
> 228 E4 Keyboard RightControl
> 229 * E5 Keyboard RightShift
> 230 * E6 Keyboard RightAlt
> 231 * E7 Keyboard Right GUI (R Compose VMS)
Just to complete this discussion, I did dome more thorough
testing. Vital statistics:
IBM Thinkpad T41 laptop
Windows XP Professional SP2 (with a whole bunch of security
patches that our coprporate IT
manages :-)
Hummingbird Exceed 9.0.0.0
Attachmate KEA! 340 V 5.10j (Build 3470)
LK463-A2
Under normal day-to-day work, the laptop is used in an IBM "port
replicator" which allows use of an external monitor (HP 1955 LCD flat
panel, HP 3-button USB mouse 3X-PBQWS-WB, and the LK463-A2 keyboard),
with mouse attached to a USB port and the keyboard attached with the
supplied USB-to-PS/2 adapter to the PS/2 keyboard input on the
replicator. In this configuration, all LK463 keys are available and
I've successfully mapped them within Exceed and KEA! 340 to their
"correct" LK4xx functions.
I have now done testing with the LK463 attached directly to one
of the USB ports. I've found application-specific deficiencies, but
also more general Windows problematic behavior.
1) Under Exceed, using the keyboard mapping configuration
utility (Xkeys), Exceed doesn't "see" the following keys
and therefore can't map them:
Help, Do, PF1, PF2, PF3, PF4, or keypad-comma.
2) Under KEA! 340, the keyboard mapping tool fails to "see" the
following keys and therefore can't map them:
Help and Do
3) Under both applications, I can map the left and right Compose
keys, BUT when pressed, Windows intercepts them as the "Windows
Key" and opens the Start menu! :-(
My theory is that most or all of the keys (HIDs?) are being sent
correctly to Windows, but (a) Windows is intercepting and acting on
"Keyboard Left GUI" and "Keyboard Right GUI", which VMS wants to use
as Compose; (b) Windows is intercepting and "dumping on the floor"
the "Keyboard Help" and "Keyboard Execute" keys. I don't understand
why it would do that, and indeed it's possible that a newer version
of Exceed and/or KEA! might be able to tell Windows "don't do that"
and grab these keys (as they have been able to do for a long time
with, e.g., NumLock, Pause and PrintScr).
On a personal note, since I'm in US-EN mode and very rarely
have need for the Compose function/key, and since one can always
get to Help from the EVE command line, I could *almost* manage
with the above noted limitations. However, lack of the Do key
is pretty much a show-stopper! Sigh...
William Webb gave a link to website that deals with keyboards
and one of the links off that site pointed to a free utility that
uses a Windows registry hack to remap keys. It has a number of
limitations, i.e., mostly swapping the location of a pair of keys
rather than changing what Windows does with a given key. It does
include a utility to find out whether a key (that Windows doesn't
know about) has been pressed. I'm just very timid about dropping
a .EXE from the net onto my corporate laptop...
So as far as Eric Dittman's original request goes, it sure looks
like the USB functions of this keyboard are there. The trick will
be how to access and remap those HIDs to make this keyboard usable
on the Mac (and one assumes, on VMS through a DECterm/Xterm or
telnet session).
Regards, Ken
Paul Sture
> On a personal note, since I'm in US-EN mode and very rarely
> have need for the Compose function/key, and since one can always
> get to Help from the EVE command line, I could *almost* manage
> with the above noted limitations. However, lack of the Do key
> is pretty much a show-stopper! Sigh...
>
FWIW in similar situations I have mapped CTRL/D to Do. (I don't think
that CTRL/D is used by anything else in VMS.)
Forrest Kenney
Actually, CTRL-D is used by TTDRIVER it is the alternate to
left arrow.
Forrest
Ken Fairfield
Actually it is, although I *never* use it. From HELP Line_Editing,
Edit Key Function
-------- --------
Ctrl/A or Switches between overstrike mode and insert mode. The
F14 default mode is reset at the beginning of each line.
Ctrl/D or Moves the cursor one character to the left. <--
Left Arrow
Ctrl/E Moves the cursor to the end of the line.
Ctrl/F or Moves the cursor one character to the right.
Right Arrow
Ctrl/H or Moves the cursor to the beginning of the line.
Backspace or
F12
Ctrl/J or Deletes the word to the left of the cursor.
Linefeed or
F13
Ctrl/U Deletes characters from the beginning of the line to
the cursor.
I have always used Ctrl/B in EVE when using a "foreign" keyboard or
installation. It gets you the command line, which you can edit, but
it's far from convenient in normal, everyday use. Your idea of using
Ctrl/D as a fall back isn't half bad. :-)
Paul Sture
>
> Paul Sture wrote:
>
>>Ken Fairfield wrote:
>>
>>
>>> On a personal note, since I'm in US-EN mode and very rarely
>>>have need for the Compose function/key, and since one can always
>>>get to Help from the EVE command line, I could *almost* manage
>>>with the above noted limitations. However, lack of the Do key
>>>is pretty much a show-stopper! Sigh...
>>>
>>
>>FWIW in similar situations I have mapped CTRL/D to Do. (I don't think
>>that CTRL/D is used by anything else in VMS.)
> Actually, CTRL-D is used by TTDRIVER it is the alternate to
> left arrow.
>
Thanks for the reminder. I should have said I define it _within_ EVE;
not VMS-wide.
Paul Sture
Thanks :-) Going back to the time when I was using terminal servers, I
defined CTRL/F and CTRL/D as next session and previous session
respectively, so got used to not using them for line editing (console
excepted). Looking at the keyboard they are the only pair of adjacent
keys which don't conflict with other control characters I want.
VAXman-
Hi Paul,
If you happen upon a driver for the Mac (OS X) which will allow me to use
the LK463, do let me know.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM
"Well my son, life is like a beanstalk, isn't it?"
Paul Sture
>
> Hi Paul,
>
> If you happen upon a driver for the Mac (OS X) which will allow me to use
> the LK463, do let me know.
>
Hi Brian,
Did you see the beginning of the thread? The OP was asking for keycode
details so he can build a new OS X keyboard map for the LK463.
Full thread at http://tinyurl.com/9ew5f
dit...@dittman.net
> If you happen upon a driver for the Mac (OS X) which will allow me to use
> the LK463, do let me know.
Brian, I asked the question in the first place so I could create a driver
for OS X.
--
Eric Dittman
dit...@dittman.net
VAXman-
>
>
>VAXman- wrote:
>> If you happen upon a driver for the Mac (OS X) which will allow me to use
>> the LK463, do let me know.
>
>for OS X.
I was out of touch for a while. Week in LA and then off to the UK. Talk
about being (time) zoned out.
al.j....@gmail.com
Stephen Hoffman
> So, this is a rather long time ago.. Has anyone successful built a key
> map file for the LK-463 keyboard that works on MAC OS X, or with the
> iTerm terminal emulator ?
your newsreaders, and are wondering what Google Groups just allowed Al
to reply to...
<https://groups.google.com/d/msg/comp.os.vms/EI4Q4Ks92Rw/TSgAYZUs4VYJ>
Possibly-related and might be useful, or might not...
<https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller/wiki/How-to-Use-Custom-Keyboard-Mapping>
<http://www.usboverdrive.com/USBOverdrive/News.html>
<http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=ukelele>
<https://pqrs.org/osx/karabiner/index.html.en>
--
Pure Personal Opinion | HoffmanLabs LLC
ayushi...@gmail.com
A Gaelic origin for the word hoodoo will, believe it or not, add up in terms of African yank history, for an over sized proportion of yank sailors throughout the nineteenth century, particularly before the warfare, were African Americans, and that they mingled freely with Irish sailors within the Atlantic shipping trade and in seaports from the big apple to urban center.
http://www.powerfulprophets.com/how-to-get-to-hoodoo-voodoo-maplestory/