Discussion:
I Need to Disable the F1 Key
(too old to reply)
Cyberherbalist
2003-11-14 19:57:06 UTC
Permalink
I have a legacy client-server application that operates through
Citrix/XP. The application has a help system already, accessed
through clicking on a Help button on each windows form. We recently
found that pressing the F1 key in these forms causes the client-server
API to go looking for the help file named in the VB project Help File
Name property. Unfortunately, none of the hundred or so VB projects
in this system had anything entered in this property, so the API goes
off trying to find a help file named ".hlp", which of course doesn't
exist (and can't exist).

Rather than going through all the projects and putting a stub help
file in the Help File Name property (and recompiling and deploying the
whole mess!), I'd like to find out if there's a way to disable the F1
key at the server level. Anyone have any idea?
Cyberherbalist
2003-11-21 16:48:04 UTC
Permalink
OK, nobody answered this, which is sad, but our project lead finally
found the answer (or, at least, one answer) offline. For the benefit
of future generations, let me put the solution here.

This solution requires a registry change (cringe). Ah-hem.

Start up the Registry Editor, go into HKEY_LOCAL_MACHINE, SYSTEM,
CurrentControlSet, Control, and KeyboardLayout. In KeyboardLayout
create key a new binary key (in Hex format) called SCANCODE MAP and
make the value equal to:

00000000000000000200000000003B0000000000

For WinNT you'll be able to cut and paste this string into the key
value; for Win2k you'll have to enter it digit by digit.

Once you've got this in the registry as described, reboot and viola'!
The F1 key is disabled.

Loading...