How do I identify what each key does on a Model M 122-key?

[berserkfan]

Hello Everyone!

Since I haven't been able to get hold of a Model F 122-key, I finally broke out my Lexmark Model M 122 key that I was originally keeping new in box. And I am HORRIFIED. I can't find my way around! There are a lot of keycaps that don't match their actual functions, and I haven't been able to find numlock.

I heard from someone that numlock, on a terminal keyboard, is actually hidden under some layer.

I remember reading that there is a software that can analyze your keyboard for you, telling you what each key is and what they are even with layers like shift and ctrl. Does anyone know abut that?

I have autohotkey, so I just need to identify exactly what scancode each key sends and also if the key sends a different scancode when triggered by a modifier such as shift. Once I can figure that out, remapping via autohotkey is straightforward.

Right now I don't have soarer's teensy, so I'm afraid I am stuck. But I just ordered the teensies; am just waiting for shipment from the US. Surely they can translate Terminal Code Set 3 (or whatever this is called) to something a modern computer can recognize.

In the meantime, I eagerly await everyone's advice!

[jwaz]

http://geekhack.org/index.php?topic=34670.msg641440#msg641440

You can find aquas keys test in this thread above, I think that might be what you're looking for.

[Halvar]

I'd say if you're getting the converter anyway it doesn't make too much sense to try to connect it directly first.

Just wait until you have the teensy, and read this post for which keys you need to remap:

http://deskthority.net/post120632.html#p120632

[mich]

122k boards misinterpreted as scancode set 2 behave kinda like a Model F AT.

So numlock is keypad / and scrolllock is keypad *.

Alternatively, you can use this table

[fohat.digs]

Soarer included a very useful chart in his Teensy Converter documentation that is easier for the lay person to understand.

[berserkfan]

Nice of you to give the link, but it's a bit complicated for me to understand.

In any case, as mentioned in the post I can identify scancodes returned with ahk. But to identify additional scancodes that the keyboard can send (eg when left shift is pressed down, or when scrolllock is activated, whatever) is going to be a project of incredible trial-and-error frustration exacerbated by me having already remapped some of the keys to make them usable. So I will rather have some software do it systematically.

Anyway, fohat, nice to hear that soarer has documentation. My teensies should be coming in soon...

122k boards misinterpreted as scancode set 2 behave kinda like a Model F AT.

So numlock is keypad / and scrolllock is keypad *.

Alternatively, you can use this table

[mich]

But to identify additional scancodes that the keyboard can send (eg when left shift is pressed down, or when scrolllock is activated, whatever) is going to be a project of incredible trial-and-error frustration exacerbated by me having already remapped some of the keys to make them usable.

It's going to be a simple project with simple result - there are no such scancodes and every physical key produces a single scancode. Set 3 doesn't have such PC-style braindamage.

[fohat.digs]

Anyway, fohat, nice to hear that soarer has documentation. My teensies should be coming in soon...

When you have a Teensy, you can forget all that other stuff and program your changes directly into the Teensy using wcass's method.