Opera wrote [2012-03-30 12:58+0200]: > Using the same keyboard where I first saw the bug but connected to a > plain old PC. > > I use hexdump like this: > # hexdump -C > tap the problem key, then hit return and then Cntrol-D > > With numlock off I see: > ^[[3~ > 00000000 1b 5b 33 7e 0a > 00000005 > With numlock on: > . > 00000000 2e 0a > 00000002 > > Using the same keyboard with a ps2-USB adaptor I see the same > result as the numlock off test above whether numlock is on or off. > > This is what I see on the Shuttle also but it has no ps2 sockets > so on it I'm stuck with no working dot key on the numpad and > of course old habits die hard so I mess up lots of ip addresses. > > Is there something in wsconsctl or such that would let me patch > it? I've been hunting through various related man pages but I > have not hit on a hint so far.
Hey, baaaaaaaa-by! Just recently i've posted a patch to tech@ that let's you examine the scancode of a key via wsconsctl!!! Then you can use basic wsconsctl features to set the key to whatever you want, now that you can identify it!! By the way - Marco Peereboom has posted a great ksh(1) to tech@ on 2011-09-06 that let you do graceful multi-character-sequence key binding, which may also be of interest to you. Was for me. And YOU ARE THE FIRST Windows NT user i know of who cares about keyboard scancodes! This is just a FANTASTIC EXPERIENCE for me. THANK YOU!!!! (P.S.: there is a X program which gives you even more info, so that you can adjust your .xmodmaprc or so.) --steffen Forza Figa!
