Microsoft Keyboards - F Lock Modifier - Scan Code Remap Method

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

While there is no way to control the F Lock key state programmatically, Windows 2000, Windows XP and Windows Server 2003 provide a method whereby keys can be remapped by using the Scan Code Mapper. The Scan Code Mapper can be used to change the functions of the function keys. Unfortunately, this functionality is not available for earlier Windows versions.

With the application of that knowledge, the two zip files below contain registry files that will alter the key mappings after Windows 2000, Windows XP or Windows Server 2003 is started up. When F Lock key is in the "off" position, the function keys will have their "normal" function, and when the F Lock key is in the "on" position, the function keys will have their "enhanced" function.  Note that these files will only alter the functionality of your function keys (for those who have Natural Multimedia Keyboard, Multimedia Keyboard, Wireless Optical Desktop Keyboard, Wireless Optical Desktop Pro Keyboard, Basic Wireless Optical Desktop Keyboard or Wireless Desktop Elite Keyboard, the function(s) of the PrtScn/Insert & Pause/ScrLk keys will not be changed).

Pick the appropriate file download based on the keyboard that you have.

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 Flip 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 .

If you do not like the "enhanced" function keys at all, a variation of the above method can be used to make the F Lock key irrelevant by using Scan Code Mapper. Essentially, this will make the function keys operate as "normal" function keys regardless of the F Lock key status. If you are interested in this, click here to access those registry files.

Other scan codes that might be of interest in case you want to try creating your own scan codes for the Microsoft keyboards...

The items shaded in gray will require the installation of the Intellitype software to have functionality. Any attempts to reprogram the default listed behaviour of the special keys must be done through Intellitype (you'll have to select a keyboard that actually has the key you wish to edit (as some Microsoft keyboards do not have the same keysets)).  Make sure you download the latest version of Intellitype (if available) from the Microsoft website (even if you have the installation CD) as the files can be updated without notice.  You can get it at http://www.microsoft.com/hardware.  * - On the Office keyboard, this is the scan code for Office Home.  Microsoft decided to change this on all their later keyboards (i.e. the ones I call second generation) so I'm not sure how this difference will be reconciled (I am guessing it depends on what keyboard you select in the keyboard control panel).

Please note that there are some limitations to this method:

• 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.