How do I remap WindowsMenu key to RAmiga? (NOT entirely solved after all)

I've bought a new keyboard, which lacks RightWindows key. It does however have a WindowMenu key there instead. I foolishly assumed it'd be easy to remap this to RAmiga, but I can't see any special keys in the standard keymap. So how can I do it?

@ChrisH

check my old post here:

http://amigaworld.net/modules/newbb/v ... p?topic_id=33620&forum=14

i wanted to remap the function key but it was impossible, then i've remapped right ctrl...

I solved the problem, on my logitech K520 is simple to have a RAmiga key, i must press func "FN" key+Print(Menu) key, yes i know i have to press two keys but now i have it, however i found another solution setting "rgui" variable in env-archive/usb/hid.keyboard/ and it works very well, these are the code i tried:

'0x00070044' to remap F11 to RAmiga
'0x00070045' for F12
'0x000700E6' for R-ALT
'0x000700E4' for R-CTRL (yes it works also if we see with AllKeys prg the same code for LCTRL and RCTRL)

@sofistisoftware
Your old AW.net post contains non-working links to the HID Usage Tables pdfs. Here are the current ones:
http://www.usb.org/developers/hidpage/HID1_11.pdf
http://www.usb.org/developers/hidpage/Hut1_12v2.pdf

I have two problems at the moment:

1. I can't find the code for Right (Windows) Menu. I don't even know what they call it. It might be called the "Keyboard Menu" key, in which case the final hex digit would appear to be "76"...

2. Assuming I know it's code, it's still not clear to me how I would use it. Let's pretend I want to use R-Alt as R-Amiga (it'll be better than nothing). Should I do the following?

SetEnv "usb/hid.keyboard/rgui" SAVE "0x000700E6"

@ChrisH,
for keyboard without right win key, you must set
the kbddev_norwin variable to 1, something like
setenv -p kbddev_norwin 1 in the cfe prompt for the X1000

Maybe it's called context menu? And I see that keytweak has it registered as key #64. Dunno if that helps a bit.

The following post has some helpful stuff:
http://amigaworld.net/modules/newbb/v ... =262729&refresh=Go#263093

Actually, the solution I'm asking for seems to be given here:
http://amigaworld.net/modules/newbb/v ... =262729&refresh=Go#263404

Not tested yet though. (It seems to indicate that the "Windows Menu" key is known as the "Keyboard Application" key!)

I am happy to confirm that the following remaps the (Right Windows) Menu key to Right Amiga:
SetEnv SAVE usb/hid.keyboard/rgui 0x00070065

@pvanni
I believe your suggestion would work too, but it's much fiddlier to change that, and the precise command is X1000 specific (so it won't help non-X1000 owners, although it might point them in the right direction). OTOH, your suggestion would survive OS4's partition being formatted & reinstalled, which some people might prefer.

@all

pvannis' solution is not X1000 specific even if his example was, as you can see from the variable it works through keyboard.device, Over the years I've used it on an XE, Micro, Flex and X1000.

Other systems can use NVSetvar or uboot prefs so it's no more difficult than using setenv. Doing it via env is fine though, you just lose r-amiga if you ever have to boot with no startup.

@Severin
I have to disagree: "setenv -p" is VERY X1000 specific! (I am looking at this from the general-end-user POV.) I did however say it might point them in the right direction (to a similar command for other AmigaOne models).

@ChrisH

You're quick, you replied while I was rewording my reply... I agree btw.

@ChrisH,
yes, setenv -p it's X1000 specific, I used it because
you have an X1000 and I overlooked you also have a 440,
but the U-Boot syntax it's not much different, something like:
setenv .....
saveenv

so almost everyone can be happy

Unfortunately it seems that OS4 only PARTIALLY translates the Menu key to RAmiga. If I keep the Menu key held down, then it still generates a Menu key event after a short while, and very annoyingly this causes CygnusEd to erase the document I was working on.

AllKeys shows the following events:
* RAmiga
* RAmiga + Menu (repeat)
(No upstrokes are shown)

Now, I *can* use AllKeys to catch that particular set of events, so it's no-longer quite so bad, but it still doesn't stop various other events, such as if I have the Menu key held down & then tap RAlt. So it now becomes "whack-a-mole" trying to think of every possible key combination that I might do