[Bill Clark]

WBK,

As you can see I have not given up on this NUMPAD issue yet!

As another approach, I took the time to install a "pristine" version of FS9 on another, older computer I have running Win XP. The installation of FS9 in this case has no add-ons, except the SP1 that Microsoft did later to correct some missing bridges and some other minor bugs. I also installed touch screen HW and TB software........ran it in "Local" mode.

What I discovered, is that no matter which set of TB commands used (all the commands suggested by you listed above in this thread, as well as other combinations I came up with ), I essentially got the same results as before.

However, I did try something different this time, while FS9 was running in "windowed mode" I noticed that I could open up the "Controls Assignments" dialog box in FS9 and select any command to initiate a new keystroke assignment.

What I discovered is that FS9 is always seeing the following input, which is "SHIFT + Num 1," whenever I sent commands from TB. This happened every time, regardless of whether the Numlock LED indicator on the keyboard was on or off. One of the command strings was as simple as sending macro = predef:NUMPAD1. It should have only seen "Num 1".

Conclusion - It appears that either TB is automatically adding a shift to the NUMPADx number, or FS9 is?

What are your thoughts on this? Any other ideas?

Bill