Dual scancodes per key?

[super-6-1]

Alright, so here is the thing, i have a Unicomp terminal keyboard i think... its odd. What i was looking into was remaping a few keys and i did a couple of not all of them. I went into a game to play and i noticed i could click it once and it wont work after that. This was with all the keys. The code for the Q on normally is. 00_10 but if i hit it again it turns into E0_3F10 which to me is odd... i can type just fine but it just seems odd how that works and it makes it so i can't play games at all just type.

any ideas?

[super-6-1]

Yeah, this is what it looked like exactly, as far as details what i can only say is it seems like the each key as 2 codes in them. One being the normal and another being some other code no programs knows. I use Sharpkey to see remap them but since the program doesn't know what they are it wont map them for me. Like for example, Ill press the key in Sharpkey and it will being up Q for the q but press it again it gets another code all together

[super-6-1]

Alright, i wanted to keep this updated as much as i can so here is what is going on.
While typing it runs perfectly fine, windows sees the key as it is. I can type just fine and keep pressing the"same" key over and over and get that key. Now. in most applications this is not true. I can press q and it works, press it again i get a different button all together. Like the scan code changes its self. Iv never seen a keyboard like this. I was wondering if anyone could help in remapping these unknown key codes? Windows sees them there just not mapped to anything.

[breakaway]

have you tried using autohotkey to remap the unknown scan codes?

[mich]

It's either some strange keyboard or Windows bug. What is the scancode of CapsLock?

[super-6-1]

Caps lock works fine its 00_0A as far as autohotkey? No idea how to use it. But also the keyboard i have is a Unicomp Computer Lab International. The SN is CLI03560003300

[mich]

I can't see how Capslock can be 0A and working fine. It should be 1D, or maybe 3A if this keyboard somehow supports set 2.

Can you boot this Linux system you said you have and try this?
http://geekhack.org/showthread.php?23034-Vintage-KB-s-light-keep-blinking&p=433510#post433510

Hit Q and Capslock few times and copy the output it will generate.


BTW, if you boot Linux with i8042.direct=1 atkbd.set=3 atkbd.terminal=1 kernel parameters, most (all?) terminal Ms will work correctly.

[super-6-1]

Sorry ti took me so long to do this, i just got to it... long holidauy. Anyway as asked here is the keys between q and caps lock.

10
*
1d
9d
10

\
The * is the second time i pressed q as for going to caps lock twice i get this.

1d
9d

1d is down press
9d is up release.

[mich]

This * is printed by hexdump and means "any (nonzero) number of repetitions of previous line".

Your keyboard controller seems to be running in translated mode, so the keyboard sends 15 (which gets translated to 10) for Q (with nothing at release) and 14 (translated to 1D) for CapsLock (with F014, translated to 9D, at release). AT scancode and translation tables.

This indicates scancode set 3 and is the usual behavior for terminal Ms.

The keyboard doesn't seem to send either E0 or 3F (and, in fact, it shouldn't), so this E03F prefix is probably produced by some weird interactions between the keyboard and Windows driver (which AFAIK doesn't support set 3). I have no clue where E0 comes from, but 3F is translated 03 and 03 *might* be keyboard's response to scancode set query sent by Windows driver, misinterpreted by Windows as part of some scancode.

However, I don't really know if this is true and how to fix it. You might try this (XP/2k only) driver for terminal Fs, they are similar to Ms so it might work.

BTW, does this keyboard work in Linux? If Linux correctly interprets letters, (but not other keys), then with "i8042.direct=1 atkbd.set=3 atkbd.terminal=1" kernel parameters everything (except for the left block and high row of Fs) should work perfectly. This, if true, would be a definitive proof that we are dealing with Windows bug

[super-6-1]

ok well here is what i have to ask now, how do i build the second driver? i did install the registry to see if it works and it seems like it has taken effect to a extendt, the the "Field exit" key is now the enter key and so on but i stil have the issue if beeing in a game or application and its not working. It types very well with no issues but seeing as im a gamer it not pactical to use normally or everyday.

Now im wondering how to "make' this driver?

[mich]

Quick google search for "site:geekhack.org i8042prt.sys" revealed http://geekhack.org/showwiki.php?title=Island:8046 . It seems that there is a precompiled binary there so you don't have to build the driver from source.

I have no clue if it works because the only computer on which I have Windows installed is a laptop without PS/2 port, but the source code looks sensible.

This driver should enable sending break (release) codes for all keys, making the keyboard usable for gaming (by default it doesn't send them for most keys and there is no way for software to know when such key has been released).

If you are lucky, lack of break codes might turn out to be the exact reason for Windows going crazy and inserting this E0F3 garbage when you run a program which wants to know when keys are released. In such case installing modified driver will fix also this issue and you will get a fully usable keyboard.


If not - well, there is still one solution more - use Linux

[super-6-1]

lol yeah im trying it out now, If anything i am looking to go back to linux anyway because most of the games i play now i can run on wine. Or i can just make a simple dual boot for windows for JUST gaming.
Also,i wanted if there was a way to use this on windows 7? i know it said xp or 2000 but maybe someone re made it for windows 7 64 bit?

Edit: Someone posted it on the disccusion side never mind

Edit 2: well i installed the right sys file and not the keyboard doesn't work at all... this is getting a little annoying lol.

Edit 3: I fixed it, re reading the forum that you game me i needed to disable the driver enforcement. and this keyboard works like it should now! its awesome, i fells nice to use "old' fasion and odd keyboard. even tho this thing is a buckling spring it still keeps so much better to me then a membrand keyboard, im coming from a logictech g15 and razer acsosona.

[super-6-1]

Hello everyone! So now i am back with the same keyboard. The issue is i have done a lot of installs and i have lost the .sys 64bit driver.  Does anyone happen to have this driver around? I miss using this keyboard!

[super-6-1]

No one has information? This stinks... i love this keyboard! I wish to use it again. I may have to wait till i convert to linux.

[metalliqaz]

Wow old thread.  I've never heard of this.