AutoHotkey VS AutoHotInterception

DownloadAHK() { global wb wb.Stop() file := A_Temp "\ahk-install.exe" switchPage("downloading") Sleep 10 if !Download("https://autohotkey.com/download/ahk-install.exe", file, "DownloadAHK_Progress") { MsgBox 0x2010,, Download failed. switchPage("start") return } Run "%file%" /exec waitclose %A_ScriptHwnd% /exec downloaded "%file%" ExitApp } Exec_WaitClose(hwnd) { DetectHiddenWindows On WinWaitClose ahk_id %hwnd% } Exec_Downloaded(file) { ; global SilentMode := true DetermineVersion() QuickInstall()

All you have to do (other than have autohotkey installed) is

But, if you just install AutoHotKey, you can run these two scripts to select a first and a second dictionary: Select Dictionaries Zipfile

You could try (and I have no affiliation with) http://autohotkey.com - then allocate the key to something like ctrl-F13 (often unused - but reachable via sending system keystroke).

Honestly, it's a bit silly of autohotkey.com to have such strict protections, especially on its downloads. You may be able to workaround by using the github releases instead which are far less restrictive.

try out autohotkey.com

autohotkey.com Go to the ahk website, click download, then choose 'Download v1.1 (deprecated)'

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.