Yep, it's working fine in XT mode. Even in my crazy chain:
USB kbd-> 1st HIDMAN to PS/2 (my keyboard is buggy with kvm) + PS/2 mouse -> chineese PS/2 to USB adapter (kbd + mouse)-> USB IN on ATEN CS1734B-> PS/2 mouse and kbd in 2nd chineese ps/2 usb adapter-> 2nd HIDMAN -> XT
oO

DangerMouse wrote on 2025-05-14, 11:26:

No, it's clone. I think the reason is my AT-XT converter after hidman (but this chain works well), I didn't test hidman in XT mode in direct connection to XT yet. I'll check it soon.
[/quote]

Ahh, yes if you use an AT-XT converter HIDman has no way of detecting you have an XT.

Let me know if you have any problems in XT mode.

DangerMouse wrote on 2025-05-14, 11:47:

(my keyboard is buggy with kvm)

Yeah I've noticed that my crappy fake "Logitech" mouse is far more stable when going HIDman->USBtoPS/2 than direct to PC... weird.

OK v1.1.5 is out now. Enjoy!

https://github.com/rasteri/HIDman/releases/tag/v1.1.5

I notice you listed "XT compatibility improved" there. I'm interested to know what that means, as I've been using HIDMan on my 5160 with an old firmware version and it works just fine.

keenmaster486 wrote on Yesterday, 19:12:

I notice you listed "XT compatibility improved" there. I'm interested to know what that means, as I've been using HIDMan on my 5160 with an old firmware version and it works just fine.

XT-class machines were throwing a "301" error because hidman wasn't following the power-on sequence properly.

Some versions of the XT BIOS refuse to boot if you get a 301 error

more info here - https://minuszerodegrees.net/HIDman%20AXP/HIDman%20AXP.htm

rasteri wrote on Yesterday, 19:19:

XT-class machines were throwing a "301" error because hidman wasn't following the power-on sequence properly.

I noticed that error showing up sometimes, but only when I attempted to start the machine with my KVM switched to the other computer.