I'm very intrigued by it and impressed with the hack, great job comrade! It'll be great to have the 128kDrexel/Plus/Micromac KVM'd with the rest of the goodies!
The programmable scan code conversion capability of the controller has me even more excited! I've always wanted to have an easily programmable hardware remapping converter:
Caps Lock: make it do useful as opposed to destructive things . . . or nothing at all! [}
] ]'>
- turn it off on (PS/2->PS/2 version, please!) the scan converter by remapping the capslock state to the standard keystroke map.
- use it to map the capslock state to a custom embedded numeric/pagenav(igation) setup for any KBD!
That's all a big assumption on my part, my (Murphy's Law) guess is that CapsLock on the PS/2 interface never hits the CPU/KCHR resource level like it does on the Mac. :-/
Is the scan code for a capslocked k(K) the same for a shift-k(K) on the PS/2 interface or is it a state level difference? :?:
The programmable scan code conversion capability of the controller has me even more excited! I've always wanted to have an easily programmable hardware remapping converter:
Caps Lock: make it do useful as opposed to destructive things . . . or nothing at all! [}
] ]'>- turn it off on (PS/2->PS/2 version, please!) the scan converter by remapping the capslock state to the standard keystroke map.
- use it to map the capslock state to a custom embedded numeric/pagenav(igation) setup for any KBD!
That's all a big assumption on my part, my (Murphy's Law) guess is that CapsLock on the PS/2 interface never hits the CPU/KCHR resource level like it does on the Mac. :-/
Is the scan code for a capslocked k(K) the same for a shift-k(K) on the PS/2 interface or is it a state level difference? :?: