I recently began using a new keyboard (Logitech diNovo) and about the same time noticed that some of the usual shortcuts were not functioning.
The most important one for me was the Run Command shortcut -- Alt+F2
Others were working as expected, for instance Ctrl+Esc, to show System Activity.
Everything appeared to be correct in the installation, so today I decided to sort it out.
The correct Alt+F2 was in place so I decided to replace it with a Custom combination.
I chose the same keys in the custom setup, and found that the F2 key was not reported as F2, but as "Reply" (which is also written on the F2 key)
So now I use the same key combo as before, and all is well.
Digging a little deeper I found there is a key to the left of the Function keys, called F-Lock.
With this pressed, the Function keys again report their 'normal' name (F1, F2, F3 ...), and not the other name assigned to the keys (New, Reply, Forward ...).
This is most likely not news to lots of you, but it was to me
hence this post.
Now rather than reassigning shortcuts for those that were not working, all I have to do is hit the F-Lock key and all is well. Duh!
... I wonder if there is a means to ensure the F-Lock is active on start-up ...... some other time perhaps