Function Keys F1 to F12 Do Not Work

  • Thread starter Thread starter Roberty
  • Start date Start date
R

Roberty

I installed Logitech MX5000 Bluetooth keyboard/mouse (upgrade from MS
Wireless Desktop Elite keyboard/mouse) and the function keys F1 to F12 no
longer work. I've checked the ModeF key to ensure that it is on so the
standard function keys should work. When in IE 7, F11 should resize to full
screen and F5 should refresh the page. Alt+F4 should close the active
window. F1 should open a Help page. All of these functions do not work. If
I go into the BIOS setting page during startup, I'm able to use the F10 key
to Save & Exit.

I've connected a spare keyboard and mouse via PS/2 connection and still have
the same problem on this keyboard as well. I connected the MX5000 to a
laptop computer and was able to use the function keys without any problems.

Any suggestions would be appreciated. I'm running Windows XP Pro, SP3 with
2 GB RAM.
 
I installed Logitech MX5000 Bluetooth keyboard/mouse (upgrade from MS
Wireless Desktop Elite keyboard/mouse) and the function keys F1 to F12 no
longer work. I've checked the ModeF key to ensure that it is on so the
standard function keys should work. . . .

I've connected a spare keyboard and mouse via PS/2 connection and still have
the same problem on this keyboard as well. I connected the MX5000 to a
laptop computer and was able to use the function keys without any
Click to expand...
problems.

These experiments suggest hardware failure in the motherboard .
Its manufacturer may be able to suggest another test to localise
the fault.
 
Don,

Thank you for you response. If it is a motherboard issue, why would the
function key F10 (& F1) work in the BIOS setting page but not under the
Operating System?
 
Roberty said:
Don,

Thank you for you response. If it is a motherboard issue, why would the
function key F10 (& F1) work in the BIOS setting page but not under the
Operating System?
Click to expand...

It's not a hardware issue, but a software issue, probably the
keyboard drivers. When a key is pressed a keycode is
generated by the keyboard that is decoded by the driver,
or application to perform a specific function, such as generate
a character, move the cursor, open the help menu, etc. The
Fxx keys were devised as ways to directly perform specific
functions by applications or the OS. With the advent of
programmable keyboards these keys can now have multiple
functions. They are no different from any other key, hardware
wise.

Do you have the Logitech Setpoint drivers installed? If so,
try uninstalling, then reinstalling Setpoint. If not, go to Device
Manager, and reinstall the MS keyboard driver. If that doesn't
work, uninstall the driver, and reboot.
 
Ian,

Thank you for your suggestions.

I have the most current version of SetPoint (4.60.122) and have uninstalled
and reinstalled many times (kind of an expert at it now). I uninstalled the
"PS/2 Keyboard" entry under Keyboards in Device Manager, rebooted but still
no Function Key activity (on the Logitech and the no-name PS/2 keyboards). I
rebooted again and went into the BIOS settings and the F1 (Help) and F10
(Save & Exit) keys worked (on both keyboards).

Any other suggests?
 
Roberty said:
Ian,

Thank you for your suggestions.

I have the most current version of SetPoint (4.60.122) and have
uninstalled
and reinstalled many times (kind of an expert at it now). I uninstalled
the
"PS/2 Keyboard" entry under Keyboards in Device Manager, rebooted but
still
no Function Key activity (on the Logitech and the no-name PS/2 keyboards).
I
rebooted again and went into the BIOS settings and the F1 (Help) and F10
(Save & Exit) keys worked (on both keyboards).

Any other suggests?
Click to expand...

Do the F keys show up when pressed, in the Setpoint control panel?

Here's a keyboard tester from cnet. It's only a 30 day demo, but
that's all you need. Seems highly rated.

http://www.download.com/KeyboardTest/3000-2086_4-10066962.html
 
Ian,

Again Thank You for your assistance and suggestions.

I've downloaded/installed the Keyboard Tester and here's what I've observed:

Keyboard Type: AT107+Mouse

Windows Key Code values:
F1-F12: 255 (0xff)

BIOS Key Code values:
F1: 59 (0x3b)

F2: 8 (0x8)

F3: 7 (0x7)

F4: 62 (0x3e)

F5: 63 (0x3f)

F6: 64 (0x40)

F7: 65 (0x41)

F8: 66 (0x42)

F9: 67 (0x43)

F10: 35 (0x23)

F11: 87 (0x57)

F12: 88 (0x58)


Hope that you can make something out of this. If you need more info, please
let me know what you need.

Robert
 
Roberty said:
Ian,

Again Thank You for your assistance and suggestions.

I've downloaded/installed the Keyboard Tester and here's what I've
observed:

Keyboard Type: AT107+Mouse

Windows Key Code values:
F1-F12: 255 (0xff)

BIOS Key Code values:
F1: 59 (0x3b)

F2: 8 (0x8)

F3: 7 (0x7)

F4: 62 (0x3e)

F5: 63 (0x3f)

F6: 64 (0x40)

F7: 65 (0x41)

F8: 66 (0x42)

F9: 67 (0x43)

F10: 35 (0x23)

F11: 87 (0x57)

F12: 88 (0x58)


Hope that you can make something out of this. If you need more info,
please
let me know what you need.

Robert
Click to expand...

I installed the Keyboard tester and tried it with my
Logitech MX-3000 keyboard/mouse. My keyboard
type is also AT107+Mouse.

The BIOS keycodes for F1 - F10 should be 59 - 68,
F11 & F12 should be 87 & 88. It looks like there are
problems with F2, F3, & F10.

The windows keycodes for F1 - F12 in F mode should be
112 - 123. The value of 255 indicates the F mode is Off
and the F keys are in programmable mode.

It appears that when the F mode is On, Windows actions the
F keys directly, or passes them to an application. When F mode
is Off, (programmable mode), Windows ignores the F keys,
(value=255), and nothing happens, unless you have a keyboard
driver, (Setpoint), that can action them.
 
Ian D said:
I installed the Keyboard tester and tried it with my
Logitech MX-3000 keyboard/mouse. My keyboard
type is also AT107+Mouse.

The BIOS keycodes for F1 - F10 should be 59 - 68,
F11 & F12 should be 87 & 88. It looks like there are
problems with F2, F3, & F10.

The windows keycodes for F1 - F12 in F mode should be
112 - 123. The value of 255 indicates the F mode is Off
and the F keys are in programmable mode.

It appears that when the F mode is On, Windows actions the
F keys directly, or passes them to an application. When F mode
is Off, (programmable mode), Windows ignores the F keys,
(value=255), and nothing happens, unless you have a keyboard
driver, (Setpoint), that can action them.
Click to expand...
I forgot to ask; do the F2, F3, & F10 keys show up properly in the
keypress record line, and as the last pressed key?
 
After much hunting around, I backed up and deleted the Scancode Map entry in
my registry. F1 to F12 now work as they should.
 
Back
Top