M 122-key PS/2 NIB $80 + SH

[nowsharing]

:mod: :mod:
New, Open-Box IBM M 122-Key PS/2 Terminal Emulator:
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=140523496700
An already very rare M variant, available new in open-box.

The seller has 10 listed, with various model numbers. Request one that you have researched to be certain it is PS/2. The 1397000 & 1397050 are for sure (I think). International Shipping is available.

Listed at $95 OBO; the seller will accept offers of $80 (you could try for less, but I gave up since I already have 6 Unicomp term emulators). You should also confirm hat these are new--the cable in the pictures looks suspiciously used.

They also have these boards listed on their website, nyceonline.net, and with luck you might be able to save some money buying direct.

[nicolasavru]

Got mine today. I can confirm that it is new. It comes in the original IBM box and packaging and the keyboard comes with the original tape attaching it to the packaging (shown in the seller's photo). It even includes the original manual and Windows driver floppy (both still wrapped in plastic). It did not come with a cable, but I don't see any space for the cable in the box or packaging, nor do I see any mention of it on the box. I'll make a complete unboxing post (have lots of photos!) after I have time to mess around with scancodes and key bindings. The LEDs do work, though the lock keys don't work by default in X, while they do in BIOS/while booting (don't recall whether they worked in a console or not).

Some images are attached. Pardon the dirtiness of the normal Model M above it, it really needs a good cleaning (which I plan on giving it this weekend). The cable attached to it is mine and is from a different Model M.

[theferenc]

I can offer some help to make it work in X, if you need it. I have a script that adds the extra scan codes (runs at boot), and an xmodmap file that remaps everything to sane locations. Mine, by default, maps it to UNIX layout (think HHKB), but that's fairly easy to change, as the file is pretty clear and self explanatory.

[nicolasavru]

Sure theferenc, your script/xmodmap config would be appreciated. I know how to do it, but it would've been a pain going through all the scan codes. I shouldn't have any problems modifying it for my config. I'd like to try to re-arrange the home/end/pg up/pg down buttons to a more conventional arrangement, and I have Hyper bound to my Caps Lock key (I'm an emacs user, haha) and Super to the Right Control key.

[REVENGE]

Hmm, I don't know what sort of offer prices this seller is accepting, but Alan Computech accepted an offer of $40 free shipping for brand new Unicomp 122-key terminal emulation boards.

EDIT: Here it is: http://cgi.ebay.com/Unicomp-Terminal-Emulator-PS2-Keyboard-NEW-AK278AA-ABA-/390321898305?pt=PCA_Mice_Trackballs&hash=item5ae0ff8341#ht_1965wt_1139 It's even cheaper now, so maybe an offer of $35 will do.

[theferenc]

I had to add a .txt extension to both to make them attach, but here they are. The xmodmap file does bring sanity to the navigation cluster, and there are comments for all of the extra keys to do with as you wish.

I believe you can get a full list of your current layout with

Code: [Select]

xmodmap -pke

[xwhatsit]

Here are mine (atkbd.softraw=0 passed to kernel at boot, haven't tested if this is necessary any more):

/etc/rc.local

Code: [Select]

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

# Map Unicomp 122-key keyboard appropriately
setkeycodes 5a  221 # Dup/PA1
setkeycodes 5b  222 # F13
setkeycodes 5c  223 # F14
setkeycodes 5d  224 # F15
setkeycodes 63  225 # F16
setkeycodes 64  237 # F17
setkeycodes 65  238 # F18
setkeycodes 66  228 # F19
setkeycodes 67  229 # F20
setkeycodes 68  230 # F21
setkeycodes 69  231 # F22
setkeycodes 6a  232 # F23
setkeycodes 6b  233 # F24
setkeycodes 71  151 # Attn
setkeycodes 72  204 # CrSel
setkeycodes 74  205 # ExSel
setkeycodes 6d  234 # ErEOF
setkeycodes 6f  172 # Copy/Play
setkeycodes 75  206 # Blank L
setkeycodes 6c  207 # Blank R

# Remap some keycaps
setkeycodes 29  1   # Grave -> Esc
setkeycodes 56  41  # lessthan -> grave
#setkeycodes 01  86  # Esc (on the numpad) -> lessthan

exit 0

and ~/.Xmodmap

Code: [Select]

remove Lock = Caps_Lock
keysym Caps_Lock = Control_L
add Control = Control_L

keycode 105 = Multi_key
keycode 108 = Alt_R

keycode 77 = Num_Lock

keycode 110 = Home 3270_Rule
keycode 229 = 3270_PA1 3270_Duplicate
keycode 115 = End ISO_Left_Tab
keycode 230 = F13
keycode 231 = F14
keycode 232 = F15
keycode 233 = F16
keycode 245 = F17
keycode 246 = F18
keycode 236 = F19
keycode 237 = F20
keycode 238 = F21
keycode 239 = F22
keycode 240 = F23
keycode 241 = F24
keycode 159 = 3270_Attn
keycode 93 = Clear
!keycode 212 = 3270_CursorSelect
keycode 212 = Pointer_EnableKeys
keycode 213 = 3270_ExSelect
keycode 242 = 3270_EraseEOF
keycode 180 = XF86AudioPlay 3270_Copy
keycode 214 = XF86AudioPrev

Madness that X has keysyms for a 3270 terminal (that's the 3270_Attn etc.).

[JohnElliott]

So I succumbed to temptation, and bought one of these. It's so similar to the Affirmative 1227T that most of the writeup on my site is a straight copy-and-paste job from the 1227T page. The only external differences are that the IBM has an oval logo, a nicer-looking LED insert, an SDL connector and no drainage channels. Oh, and the barrel plate is cream-coloured, rather than black.

Anyway, like nicolasavru's, it arrived in its original box, without a cable but with a Windows 3.0 driver floppy. (I think 1396400 must be the serial number of the box+keyboard+driver package). I went to the trouble of installing Windows 3.0 on my scratch PC, just to take a look at the driver. With the driver installed, all the extra keys sent VK_ codes, but the codes sent by F17 to F24 don't match the ones in . I went digging, and found that the 16-bit Windows DDK (at least, the two versions I could check) has incorrect definitions for F17 and F18, and no definitions at all for F19 to F24. Fortunately the Windows 2000 DDK seems to get it right.

And yes, the LEDs work :-)