My trusty DOS keyboards are all suffering from coffee damages, and I am finally forced to use one of these new windows 95 keyboards with shortened space-bars and new microsoft-logo-keys that have popped up everywhere in recent decades. It's particulary unpleasant in countries that use the right Alt key as AltGr key (for entering symbols like square brackets). The AltGr key is mounted right behind the aforementioned coffee cup, and I am hitting one of the new microsoft-logo-keys everythime when fiddling for AltGr, causing my input window to lose keyboard focus, and windows opening the start menu, apparently believing that I would want to visit my favourites, which, no, I don't want that, thanks.
Looking for workarounds, I've found this method: http://hackage.haskell.org/package/GLFW ... 2_enable.c - it's using WH_KEYBOARD_LL hook (for WinNT) and SPI_SETSCREENSAVERRUNNING flag (for Win9x). It's somewhat working, and I was happy with it... until I had noticed that the screensaver trick disables nearly all hotkeys, up to including Ctrl+Alt-Del.
Another method is reportedly editing scancode entries via regedit, but I didn't got that working under win98.
So here's another approach (exe and source code):
So far, it's working more or less okay under win98, and it's almost certainly better than the screensaver trick. One (dis-)advantage is that system key combinations are still working (eg. LWIN+D brings up the desktop).
One possible issue is that the start menu does pop up occassionally when quickly hammering both LWIN and RWIN keys as fast as possible (that's rarely happening during normal use, and I don't know if it's actually ever happening on normal keyboards; as opposed to my crappy-cheap keyboard with bugged firmware). Well, and another issue is LWIN/RWIN seems to get stuck occassionally, so pressing D would be seen as LWIN+D (again, that might be a keyboard firmware bug).
Does that new method sound useful to anybody? Would be interesting to know if it's working with all windows versions, and if the above two issues occur on other keyboards, too.
Usage is: Start the Nokey95.exe file manually (or automatically via StartUp folder). And use Ctrl+Alt+Del if you want to terminate Nokey95.
Looking for workarounds, I've found this method: http://hackage.haskell.org/package/GLFW ... 2_enable.c - it's using WH_KEYBOARD_LL hook (for WinNT) and SPI_SETSCREENSAVERRUNNING flag (for Win9x). It's somewhat working, and I was happy with it... until I had noticed that the screensaver trick disables nearly all hotkeys, up to including Ctrl+Alt-Del.
Another method is reportedly editing scancode entries via regedit, but I didn't got that working under win98.
So here's another approach (exe and source code):
Attachment:
It's using WH_KEYBOARD hook (instead of WH_KEYBOARD_LL) and sends a dummy keybd_event to fool windows into thinking that another key was pressed or released while LWIN/RWIN was held down - so it won't freak out with start menu if the user releases the LWIN/RWIN key.So far, it's working more or less okay under win98, and it's almost certainly better than the screensaver trick. One (dis-)advantage is that system key combinations are still working (eg. LWIN+D brings up the desktop).
One possible issue is that the start menu does pop up occassionally when quickly hammering both LWIN and RWIN keys as fast as possible (that's rarely happening during normal use, and I don't know if it's actually ever happening on normal keyboards; as opposed to my crappy-cheap keyboard with bugged firmware). Well, and another issue is LWIN/RWIN seems to get stuck occassionally, so pressing D would be seen as LWIN+D (again, that might be a keyboard firmware bug).
Does that new method sound useful to anybody? Would be interesting to know if it's working with all windows versions, and if the above two issues occur on other keyboards, too.
Usage is: Start the Nokey95.exe file manually (or automatically via StartUp folder). And use Ctrl+Alt+Del if you want to terminate Nokey95.