AHKHID VS AutoHotInterception

; uses AHKHID from https://github.com/jleb/AHKHID

To follow up on this, here's the list of all keys. There's a whole bunch of non-standard keys that you probably don't have on your main keyboard, like Browser_Refresh and Launch_Mail. There's also projects like AHKHID (which admittedly, I haven't figured out how to use) that allow you to have hotkeys on a per-device basis, so you could have an additional standard keyboard exclusively for hotkeys.

Check out this forum post that shows how to detect events from specific devices based on HID using AHKHID.

I've managed to "accomplish" that with AHKHID (and I don't even recall if I got it working with AHI)... while the keyboards can be differentiated is *S*L*O*W*, so normal typing (even slow typing) is not quite possible (let alone a standard-ish 100+ WPM).

If not, tap into the USB-HID class exposed by the OS: AHKHID or at kernel level with AutoHotInterception, both are pretty different and both have its quirks/perks.

The Eject key is part of the USB HID Consumer input device keys. It's not part of the USB HID Keyboard device keys. So in Windows, that key won't have any corresponding virtual key code or scan code. You'll have to use AHKHID library to specifically receive inputs from Consumer-typed HID, or any other types of HID.

You could be able to remap your mouse buttons with AHKHID.

You can achieve that with Autohotkey and AutoHotInterception, which allows you to capture keypresses at a driver level from a specific input-device. I used that for turning a bluetooth numpad into a little macro pad.

I've had some good experiences with using Luamacros to intercept a second keyboard and forward the keypresses to autohotkey like this: https://miquelvir.medium.com/secondkeyboard-1c39e52e023b

Apparently there is also this: https://github.com/evilC/AutoHotInterception

AutoHotInterception might be a workaround for this. The docs cover how to do everything.

This may be what you're looking for: https://github.com/evilC/AutoHotInterception

I believe this is what you're looking for. Sorry, I haven't tried it yet.

I haven't used it yet, but I found AutoHotInterception which uses an "interception" driver to get you hotkeys with a lower level of keyboard interception - this will likely work for Dosbox, though it might be a bit excessive. I'll play around with it tomorrow and see how it works.

I would suggest using an alternative shortcut as CTRL+ALT+DEL is not something you generally want to mess with - but this library https://github.com/evilC/AutoHotInterception may help you achieve your goals, it is capable of blocking the input of ctrl+alt+del...

AHK can't differentiate between keyboards by itself. You need to use AutoHotInterception to find out which keyboard sent the data.

I used AutoHotInterception for making a cheap little bluetooth numpad into a macropad.