1
Hardware / Re: Report Your Working ArcaOS-OS2 Hardware Month
« on: November 23, 2024, 12:22:08 am »
Model F Labs makes reproduction Model F keyboards. If you have ever typed on IBM PC, XT, or early AT you probably remember the sound and feel of the keyboard; those all used Model F keyboards. IBM AT computers, from 1985 onwards shipped with the then new Model M keyboard which was cheaper to manufacture and had a revised key layout that established to modern keyboard standard used today.
This particular keyboard is a Model F Labs F104 Classic. It is basically a USB connected keyboard that uses the open source QMK programmable keyboard controller with Model F internals in a metal case with the looks and key layout of the IBM Model M keyboard. The pic shows an IBM Model M made in 1993 and a new Model F Labs F104 for comparison; the F104 is on top. The two keyboards are the exact same size; it is the angle of the pic that makes the F104 look smaller. The two main visual differences between the new F104 and the Model M, other than color, is there is no label in the upper left, and what is between the CTRL and ALT keys on the left and right side. On the Model M the case fills in that space, on the F104 a key is inserted in that space; those 2 additional keys are mapped to the Windows key and Windows Menu key by default. Hence the name F104 instead of F102.
The F104 Classic comes in a variety of case and key colors
https://www.modelfkeyboards.com/product/classic-f104-model-f-keyboard
My F104 in the pic has an industrial grey case with standard pearl keyset plus mopar blue keys and a red escape key.
In addition to the two extra keys between ALT and CTRL on each side, you can also split any of the long keys into two keys - the long keys being: backspace, left shift, right shift, enter, keypad plus, keypad enter, keypad zero or space bar. To utilize those extra keys in OS/2 you would have to map the extra key(s) to a key that OS/2 recognizes such as F13 - F24, or assign a keyboard macro to the key that generates a key press combination that OS/2 recognizes.
My F104 Classic in the picture has the short spacebar option which allows for an extra key in between the right ALT and right CTRL keys - the blue key in the pic - which I have mapped to F24.
You can use the open source graphical keyboard manager application called Vial, which runs on Windows, Linux and Mac, to create keyboard macros or to remap keys. Or masochists can achieve the same thing by modifying the keyboard controller firmware and reflashing the controller. If you pick a standard layout and you don t have any "extra" keys you probably won t need to map the keys.
The main Vial screen is split between a top half that shows the current key map of your keyboard, and a bottom screen that shows available keys that can be mapped - you may have to select one of the tabs on the bottom screen to see the key you want. You remap a key by clicking on the key you want to remap in the top half, and then clicking on the key you want to assign in the bottom half. If you don t see the key you want in the bottom half you can double click the key on the top half and type the key code you want to map to that key.You get no feed back that the change has taken place other than the "current" key selection changing in the top half to some other key. If you want to map to a key that does not appear in the layout in the bottom half you can either click on one of the tabs in the bottom half to see additional keys, or you can double click on the key in the top half and type the key code in the dialog box. The possible key codes are shown in
https://docs.qmk.fm/keycodes_basic
Be aware that OS/2 does not recognize all the key codes in the list. The version of OS/2 and the version of the USB keyboard driver will determine which keys are recognized. You can use the utility keyscanr.zip from Hobbes to show the scan codes of keys that your version of OS/2 does recognize.
You can see in the Vial layout pic that I mapped the blue key between the right ALT and CTRL to F24.
In OS/2 you have 3 ways of utilizing keys mapped in your keyboard: 1) use an application that recognizes the key, 2) use the ôKeyboard - OEM Keysö object in the System Setup folder to assign actions to the left and right Windows keys and the Windows Menu key, 3) use the Hotkeys feature of ArcaDesktop or XWorkplace to assign any key that ArcaDesktop/xWorkplace recognizes to a WPS object. You assign a key on the Icons page of the object s Properties notebook - for xWorkplace you must enable the hotkey feature first.
The F104 Classic, like many gaming keyboards that use the QMK controller, can have issues with some KVMs. My F104 works correctly with my Trenda NetIO TK-409K KVM, but does not work correctly with my IOGear Dual Display KVMP switch.
The issue for the IOGear KVMP is if the F104 is plugged into the console keyboard port the KVMP will recognize hot keys to switch between computers, but no other key presses - in other words you cannot type on it. If the keyboard is plugged in to a switchable USB port on the KVMP it will work correctly, except that hot key sequences for switching between computers or programming the KVMP will not work. It appears it may be possible to modify and reflash the firmware for the QMK controller to fix this problem. Or you can plug two keyboards into the KVMP: one in the console keyboard for entering hotkey sequences, and the main keyboard in a switchable USB port. I chose the two keyboard option.
For my second keyboard I chose the programmable YMDK YMD09 nine key keypad and created macros for the hot key sequences the IOGear KVMP wants to switch between computers. There are a number of programmable keypads out there but most of them require you download an executable from their website, and some of them warn you that if you are worried about viruses don t buy their product. A refreshing bit of candor. The YMDK uses the QMK controller and the third party keyboard management application VIA to program macros and key layouts. Via is a graphical program similar to Vial - while is it not open source it is widely used and owned by a third party.
This particular keyboard is a Model F Labs F104 Classic. It is basically a USB connected keyboard that uses the open source QMK programmable keyboard controller with Model F internals in a metal case with the looks and key layout of the IBM Model M keyboard. The pic shows an IBM Model M made in 1993 and a new Model F Labs F104 for comparison; the F104 is on top. The two keyboards are the exact same size; it is the angle of the pic that makes the F104 look smaller. The two main visual differences between the new F104 and the Model M, other than color, is there is no label in the upper left, and what is between the CTRL and ALT keys on the left and right side. On the Model M the case fills in that space, on the F104 a key is inserted in that space; those 2 additional keys are mapped to the Windows key and Windows Menu key by default. Hence the name F104 instead of F102.
The F104 Classic comes in a variety of case and key colors
https://www.modelfkeyboards.com/product/classic-f104-model-f-keyboard
My F104 in the pic has an industrial grey case with standard pearl keyset plus mopar blue keys and a red escape key.
In addition to the two extra keys between ALT and CTRL on each side, you can also split any of the long keys into two keys - the long keys being: backspace, left shift, right shift, enter, keypad plus, keypad enter, keypad zero or space bar. To utilize those extra keys in OS/2 you would have to map the extra key(s) to a key that OS/2 recognizes such as F13 - F24, or assign a keyboard macro to the key that generates a key press combination that OS/2 recognizes.
My F104 Classic in the picture has the short spacebar option which allows for an extra key in between the right ALT and right CTRL keys - the blue key in the pic - which I have mapped to F24.
You can use the open source graphical keyboard manager application called Vial, which runs on Windows, Linux and Mac, to create keyboard macros or to remap keys. Or masochists can achieve the same thing by modifying the keyboard controller firmware and reflashing the controller. If you pick a standard layout and you don t have any "extra" keys you probably won t need to map the keys.
The main Vial screen is split between a top half that shows the current key map of your keyboard, and a bottom screen that shows available keys that can be mapped - you may have to select one of the tabs on the bottom screen to see the key you want. You remap a key by clicking on the key you want to remap in the top half, and then clicking on the key you want to assign in the bottom half. If you don t see the key you want in the bottom half you can double click the key on the top half and type the key code you want to map to that key.You get no feed back that the change has taken place other than the "current" key selection changing in the top half to some other key. If you want to map to a key that does not appear in the layout in the bottom half you can either click on one of the tabs in the bottom half to see additional keys, or you can double click on the key in the top half and type the key code in the dialog box. The possible key codes are shown in
https://docs.qmk.fm/keycodes_basic
Be aware that OS/2 does not recognize all the key codes in the list. The version of OS/2 and the version of the USB keyboard driver will determine which keys are recognized. You can use the utility keyscanr.zip from Hobbes to show the scan codes of keys that your version of OS/2 does recognize.
You can see in the Vial layout pic that I mapped the blue key between the right ALT and CTRL to F24.
In OS/2 you have 3 ways of utilizing keys mapped in your keyboard: 1) use an application that recognizes the key, 2) use the ôKeyboard - OEM Keysö object in the System Setup folder to assign actions to the left and right Windows keys and the Windows Menu key, 3) use the Hotkeys feature of ArcaDesktop or XWorkplace to assign any key that ArcaDesktop/xWorkplace recognizes to a WPS object. You assign a key on the Icons page of the object s Properties notebook - for xWorkplace you must enable the hotkey feature first.
The F104 Classic, like many gaming keyboards that use the QMK controller, can have issues with some KVMs. My F104 works correctly with my Trenda NetIO TK-409K KVM, but does not work correctly with my IOGear Dual Display KVMP switch.
The issue for the IOGear KVMP is if the F104 is plugged into the console keyboard port the KVMP will recognize hot keys to switch between computers, but no other key presses - in other words you cannot type on it. If the keyboard is plugged in to a switchable USB port on the KVMP it will work correctly, except that hot key sequences for switching between computers or programming the KVMP will not work. It appears it may be possible to modify and reflash the firmware for the QMK controller to fix this problem. Or you can plug two keyboards into the KVMP: one in the console keyboard for entering hotkey sequences, and the main keyboard in a switchable USB port. I chose the two keyboard option.
For my second keyboard I chose the programmable YMDK YMD09 nine key keypad and created macros for the hot key sequences the IOGear KVMP wants to switch between computers. There are a number of programmable keypads out there but most of them require you download an executable from their website, and some of them warn you that if you are worried about viruses don t buy their product. A refreshing bit of candor. The YMDK uses the QMK controller and the third party keyboard management application VIA to program macros and key layouts. Via is a graphical program similar to Vial - while is it not open source it is widely used and owned by a third party.