Hello Alex, > As I continue to work with your document and the registry keys > in question, I further appreciate the effort you have obviously > put in to give us this much information.
Thanks -- it was an interesting puzzle > Could you please tell us how you determined e.g. the F-Lock key to be > controlled by registry code 399 and Mute by 106? Describing your method > will hopefully help us find the relevant codes for the other special > keys on our keyboards. This is not a problem for those keys which are listed in iTouchcf. Just set each key to do "Keystroke" with the "Name" set to what is printed on the physical key. Then browse through all the \703\ keys UserName values and add them to your list matching a key to its regkey. For the others, its a game of exclusion and some testing. Some you can guess from details in their values. I had to find the right regkeys for LF5 to LF8 Mute, Vol Up, Vol Down, User/Sleep, Media and F Lock and there was the same number of mystery regkeys. I set all the unknown regkeys to do the Keystroke job with a different SC-VK code each, then made a PowerPro hotkey for each vk code with command: Debug VKnnn. Rebooted. Then watched the Debug window while tapping each mystery key in turn. It would do no harm if you accidentally disabled the F Lock key's usual function for this short session. You can track it down by what it shows in Debug, which will be in some key's xx\703\ VirtualKey number. Then you know xx is the regkey for the F Lock key and you can return it to its default values before rebooting. Anyway, now we know F Lock is 399. For most of those tested, you want to keep the Keystroke settings you just made for the tests. You just need to fix your list to attach each key's identity to its regkey number, which you do by seeing what it sends to debug then find its regkey as described above. That list should also show each key's new vk number in decimal which is what you set as its PP virtual hotkey. > This probably deserves another thread off the main post but it seems > possible to use just one free scan code and set all of the special keys > to send out that scan code with a unique VK code. Have you tried this > yet or know any reasons not to? I can't remember whether I actually tested that, or just assumed that it could lead to many events being triggered by one keypress. Just an intuition that it would cause Trouble. Please let us know of any experiments you do. Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
