Sorry for the posting delays (been busy getting locked up in server room over the new year).
GAFBlizzard is the winner :) I got it working on Windows 7 Ultimate x86 JPN and Windows 7 Ultimate x64 JPN (on x64 system I had to test-sign the driver files and enable TESTSIGNING via bcdedit).1. Do you think GAFBlizzard is the winner? If not, please tell everyone why or what needs to be improved.
Since my Japanese chatpad (X814369-001) has some Japanese language specific key combinations, verbose output of the CHADPAD_KEY_XXX constants would be great for re-configuration.
Considering that Windows 7 x64 test mode can be easily activated via bcdedit , test-signing chatpad driver files with some random certificate should be enough for general use.3. Question from GAFBlizzard : If the donators agree that unsigned kernel drivers, or test-signed kernel drivers, are a problem because of 64-bit operating systems, then a few hundred could be set aside to cover the cost of a driver signing certificate. I need to find out the full details of what would be required, but I do not think the cost is too bad and my understanding is that we would not need to go through the Windows quality labs just to sign a driver. The certificate might only last for a year, but as long as the kernel components are stable by the end of the year, I would hope that the signed kernel components would still be valid after that point.
However it might be an interesting experience for one to go through with the Windows quality labs routine. If that work is not taxing for GAFBlizzard, I sure can toss in some more money into the pot to compensate for the official certificate.