So - these two keyboards are Model M, so buckling spring over membrane, hence, not nkro regardless of converter used.
The 102 might well work as is with a mere cable-swap to PS/2. The 122 can be made to largely work with windows or linux via a cable-swap and messing with your XP drivers, but it's not fun, and at least one key simply cannot be remapped and will always generate an error (where home is normally on the cursor pad, if I remember correctly - more details are available on the other threads here) and hence we sometimes call it the 'beep key'. :)
A Teensy can be used to make a converter (as opposed to a whole new controller) from the variant protocol that the 122 uses, to USB. This ends up working much like the cheap PS/2 to USB converters that one can purchase, except it supports the 122 (and other PS/2, AT and PC/XT keyboards if you use Soarer's firmware, which I recommend as mine just supports 122, and is poorly maintained at present.) I might get key-mapping working before Christmas, and I might not - but Soarer is very close to the same, now so will surely have that feature working first.
So: I suggest a quick conversion to PS/2 for the 102 key, confirm that it 'just works', then worry about the 122. If the this doesn't work (and you confirm you got the pinout correct) then check for jumpers on the IBM PCB - might have one to default to AT-protocol (the PS/2 protocol is the same as the AT protocol, just the connector changed), otherwise it might be stuck using the same protocol as the 122...
Poke around on this site a bit more for info on the 102, I don't think I have one, so I'm largely guessing on that front. I very much suggest building a converter to USB for the 122, however, as the patches required to get it working under windows and linux are a right PITA, and you can kiss mac support goodbye. The USB conversion is transparent, the keyboard will now work with almost any device that accepts a USB keyboard, laptops, macs, lucky PS3 consoles... :)
g'luck!
dfj
