Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
By tutwabee at 2004-10-02 15:17
|
Make a new file falled f_lock_fix in /usr/bin, $HOME/bin, or /bin. Put this into the new file:
[code]#!/bin/sh
# This script fixes the F Lock problem on Microsoft Natural keyboards
setkeycodes bb 59 # Help -> F1
setkeycodes 88 60 # Undo -> F2
setkeycodes 87 61 # Redo -> F3
setkeycodes be 62 # New -> F4
setkeycodes bf 63 # Open -> F5
setkeycodes c0 64 # Close -> F6
setkeycodes c1 65 # Reply -> F7
setkeycodes c2 66 # Fwd -> F8
setkeycodes c3 67 # Send -> F9
setkeycodes a3 68 # Spell -> F10
setkeycodes d7 69 # Save -> F11
setkeycodes d8 70 # Print -> F12
###################################################
# Copyright
|
|
|
All times are GMT -5. The time now is 01:43 PM.
|
<FK02> = 136;
<FK03> = 135;
<FK04> = 119;
<FK05> = 120;
<FK06> = 121;
<FK07> = 122;
<FK08> = 194;
<FK09> = 195;
<FK10> = 163;
<FK11> = 215;
<FK12> = 216;
http://keytouch.sourceforge.net/
I worked really fine for me.
Discussed here:
http://ubuntuforums.org/showthread.php?t=185478&page=2
setkeycodes 0x8A 59
setkeycodes 0x83 60
setkeycodes 0xB6 61
setkeycodes 0xB5 62
setkeycodes 0x8F 63
setkeycodes 0xCE 64
setkeycodes 0xE8 65
setkeycodes 0xE9 66
setkeycodes 0xE7 67
#etkeycodes 0x00 68
setkeycodes 0xEA 69
setkeycodes 0xD2 70
node that F10 does not even emit a recognizable scan code, unless the "F-Lock" is on. Then it does just fine. Argh!!!!