In the land of the unsupported, previous blogs and tools can be king

by Michael S. Kaplan, published on 2012/08/16 07:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2012/08/16/10340297.aspx

Hi Michael!

I've been enjoying you topics regarding the keyboard dlls (kbd**.dll) files and how to mess with them :)

Earlier I decided to create a onscreenkeyboard of my own, based on scan codes, so I could take the advantage of these existing keyboards dlls.

In my path of development; I did not get it to work on a 64-bit system, the pVkToWcharTable was always NULL. It only worked if I compiled a 64-bit version of my app.

I've written a class to actually manage 32-bit app on a 64-bit system, and it works. I've even shared it to the public, by writing an article: http://lars.werner.no/?p=870

Since you always investigate deep, do you have any root cause of what actually fails?

Hope to see an article on that later on!

Cheers,

Lars Werner

http://lars.werner.no

We don't actually document how to act like Windows does when it uses one of these keyboard layout DLLs.

Yet by looking at what happens differently in 64-bit builds, one can reverse engineer the differences for 64-bit builds either directly here or indirectly by looking at kbd.h and how it defines the structure differently for the 64-bit case.

I'd help, but that would be a Microsoft employee doing the work to document the stuff that we decided not to document....