Microsoft Keyboards - F Lock Key Eliminator

To learn more about the F Lock key, click here.

The registry files on this page will make the F Lock key irrelevant while you are in Windows 2000, Windows XP or Windows Server 2003. Your function keys will act as "normal" function keys regardless of the F Lock key state. This method will only work on a PS2 port. For a method that will work with a USB keyboard, click here

Each file contains 2 registry files and a readme.txt file. I strongly encourage you to read the readme.txt file so that you understand what is being altered. If you decide you are not happy with the changes, use the provided undo.reg file to undo the changes that were made.

Due to popular demand, I have created a couple variations of the F Lock Key Eliminator so that the PrtScn/Insert button can be manipulated on the "second generation" of Microsoft keyboards with the F Lock key (as listed above). Feel free to test it out here .

Please note that there are some limitations to using the Scan Code Mapper.

• A system reboot is required to activate these key mappings;
• The scancode mapper only works when the keyboard is plugged into the computer using a PS/2 port. It doesn't work when using a keyboard plugged into the computer using a USB port (this includes the Bluetooth keyboard set). For a method that will work with USB port, click here;
• The mappings stored in the registry work at system level and apply to all users. These mappings cannot be set to work differently depending on the current user;
• The current implementation restricts the functionality of the map such that mappings always apply to all keyboards connected to the system. It is not currently possible to create a map on a per-keyboard basis;
• The mappings only take effect after Windows 2000/XP/Server 2003 has loaded;
• This will not work on applications that use DirectInput, as applications that use this interface expect scan codes/hid codes directly from the hardware. As a result, it bypasses Intellitype Pro or the Scan Code Mapper completely; and,
• the Pause/Break key cannot be remapped or remapped to using the scan code mapper (for the inquisitive, it is because the pause key doesn't generate break codes).

For more information, please see Scan Code Mapper for Windows website.

Thank you to Doug Harrison (Microsoft MVP Visual C++) for determining the scan codes for the function keys while F Lock key is in its "off" state and for his assistance in the development of the registry files and all ancillary information found in the readme.txt files.

No guarantee is made of the overall effect of the registry files contained in these zip files. You have only my assurance that these have worked for me and for many others, and that I do not personally know of any problems. Running them is your own responsibility. I recommend that you back up your registry. If problems result, please use the provided undo.reg file or restore your registry from the backup that you have you made.  A copy of the undo.reg file can also be downloaded here (after saving, remove the .munged part of the extension so that the filename is undo.reg)

Please provide any feedback in the microsoft.public.mshardware.product newsgroup on the msnews.microsoft.com NNTP (news) server or at my blog..

To return to the F Lock key main page, click here.

Thanks and enjoy,

Jason Tsang, Microsoft MVP (Windows Shell/User - 2001-2004, Media Center - 2004-Present)

Also visit my other website, Classics Unveiled or my blog.