Yes, the thread is very old. I know that.
But I've been searching for a general alternative keyboard driver for many years. There are no suitable hits on google with any help at all. I found your thread searching my wish.
What _you_ want could maybe achieved if you have a programmable keyboard. For example: Sayo keyboards (like 3x3 or 2x6) have an option to program keys in that way (add a 'release shift' to every key from a..z). But there is no programmable TKL (or full size) Sayo keyboard. Also, I could not find Sayo's with blue switches (probably doesn't exist).
What I _myself_ am looking for in a keyboard driver, for a gazzillion years now, is a way to fasten the keyboard response in Windows.
In DOS we have: mode con rate=32 delay=1
Maximum rate=32: which is equal to 'Repeat rate' = 'fast' at keyboard settings, is not fast enough for me.
Minimum delay=1: which is equal to 'Repeat delay' = 'short' at keyboard settings, is too slow for me; I have to wait too long before Windows is responding, if I for example press and hold the cursor keys.
I'd like to have a setting possible:
Mode con rate=64 delay=0.25
If anybody knows a mechanical TKL (with special drivers) with that possibility... or a general Windows keyboard driver which can do that... please notify me
.
Especially the delay=1 (DOS) or 'Repeat delay' (Windows) is a problem for me. It costed me over the years many days of useless waiting time. Waiting before Windows does respond. On a global scale, this costs billions in lost productivity.
Microsoft doesn't want to speed up things. Of course delay=0 would give a keyboard usability problem; but give us at least a shorter delay than what is currently possible, Microsoft! What we are missing, is a general Windows keyboard driver with more options; like what you want to do and what I want to change. (If it is not a hardware issue? In that case, we need special keyboards / other factory specifications.)
Maybe someone who knows a lot about Linux, can tell me if Linux has such speedy keyboard options. If so, than it is not a hardware problem, and a better Windows driver should be possible.