I've recently purchased a very nice Chinese mechanical keyboard, a Durgod K-320 Corona, an excellent mechanical keyboard which works just fine with Linux.

When used under Windows, a downloadable program called the Durgod Zeus Engine (DZE) can be used to reconfigure keys, create text blocks and macros for assignment to particular keys, and similar functionality; one can then download these to a shadow profile on the keyboard itself.

There are, to be sure, some oddities with the DZE software, but I've been able to assign a few things, download them to the K-320, move the keyboard to a Linux machine, and use the (Fn+F12) hot key combination, which causes the shadow profile to become active; a small LED on the keyboard is lit to indicate that the secondary profile is active, and the remapped keys work as advertised.

But I don't want to traipse over to a Windows machine every time I want to create a new macro or whatever, and such mapping cannot be done on the keyboard itself (unlike my Kinesis FreeStyle Edge, which I think sets the standard for how programmable keyboards ought to work, but that's another discussion).

So I attempted to run the DZE using Wine on my Linux Mint 20/Cinnamon 4.6.7/5.4 kernel, and have had no luck whatsoever. When the DZE is started on Windows, it automagically detects the model of the keyboard and displays the appropriate set of screens. Under Wine, the program doesn't seem to see the keyboard at all. Just to eb clear, if I run "wine64 uninstaller" from the terminal, the keyboard works normally.

So I trolled the web for some solutions or at least some hints and found the usual collection of undated postings, obviously outdated postings, and even "official" postings (such as the Wine site itself) whose advice refers to locations that don't exist on my machine or similar.

Several postings indicate that I need to be in either the sys or dialout groups for access to com ports in wine, so after confirming that these groups already existed, I ran:
... and then, of course, rebooted. The DZE still could not see the keyboard.

So, if anyone has ideas, or a better understanding of Wine than I do (sadly, not a very high bar), here is what I've been able to locate so far:

Running lsusb shows the keyboard on the following line:
Running ls -l from the ~/.wine/dosdevices lists links for:
... as well as links from:
... through
There are no entries there (nor in /dev itself) similar to the ttyUSB* referred to in many posts.

My keyboard is at: /dev/usb/hiddev0

From the ~/.wine/dosdevices directory I removed the com1 link:
... and added a new one to my keyboard's device.
Still no luck.

Poking around further, I found something interesting when running xinput list, whose output is listed below:

The Hoksi Durgod keyboard is listed on five lines, with separate entries for "System Control" and "Keyboard." This leads me to suspect that possibly I should be trying to connect the app to the "System Control" rather than the "Keyboard" but also leads me to the conclusion that I have no idea what I'm looking at and need some adult supervision. Concerning the line with "Hoksi Technology DURGOD Taurus K310 Mouse" I can confirm that I do not have a Durgod mouse, though I disconnected my USB mouse plug just in case my mouse was OEM'd from them; since the DZE permits assigning mouse key functions to keyboard keys, I'm guessing that mouse entry might have to do with that.

Unplugging the keyboard itself, and using the Kinesis standalone Number Pad (which I'm guessing is the Cypress Semiconductor HID Keypad and MOSART stuff) above to repeat the xinput command in the terminal, I get the following.

In the /dev/input/by-id directory, my machine has:
In the /dev/input/by-path directory, my machine has:
As I said above, it's a great keyboard - built like a tank and a delight to type on, so it would be nice to use all of its capabilities, and I'd appreciate any assistance anyone can offer.

Frank

Kind of a duplicate post...
https://www.linuxquestions.org/quest...le-4175675234/

The keyboard is not a serial port and would not think that anything related line on thinking would work. wine has implemented direct HID support in its recent versions but that does not necessarily mean the DZE program can access the keyboard.

https://wiki.winehq.org/Hid

I take it you could never get david0's program to work.

Thanks for responding, and sorry for the apparent duplication. For some reason I was unable to locate the original post and, in any case, I still have a few other devices (e.g. Logitech remote control and various USB printers) that Wine seems unable to send anything to, so it seemed like it might be a more general question anyway, assuming there's a common cause (??).

And, no, I was unable to get davidO's script to work, and am reluctant to mess around with adding additional python versions since I have other python-based utilities that seem to be functioning and don't want to step off that ledge.

I guess I need to look into HID a bit further; keyboards are serial (with a small "s" and as opposed to parallel) devices, albeit traditionally uni-directional, though I know what you're saying. I had just assumed (using that bad word again) that, like many other protocols stuffed onto the USB connectors over the past decade, that this was yet another layer that piggybacked on to the connector.

My Kinesis Freestyle Edge, by the way, is also connected via a wired USB, and I've never had any issues running its software under Wine and saving the configuration to one of its profile layers (it actually supports lots of programming right from the keyboard, but some things are just easier using the Windows app). Its connection to the on-board profiles is probably "hard-wired" though, since the Windows program is stored and run from an internal drive within the keyboard which also holds the key mappings and macros.

Given that it's a very good keyboard at a reasonable price (for such things), I figured I would post to see if any one had figured out a solution yet.

Again, thanks for responding.

Frank