@nemo Unfortunately, #InputLeap has dropped official support for 32-bit platforms and talking to #Barrier or #Synergy. #DeskFlow is an alternative that adds support for newer technologies like Wayland while maintaining compatibility with legacy Barrier and Synergy clients so you can still interact with older hardware.

And if your hardware is *really* old, you may be interested in #minput_hop : https://github.com/indigoparadox/minput-hop 😌

GitHub - indigoparadox/minput-hop: Compact client-only library written in C89 for talking to Synergy KVM server and its forks

Compact client-only library written in C89 for talking to Synergy KVM server and its forks - indigoparadox/minput-hop

GitHub
The next step after #minput_hop is to design a hardware dongle that speaks the Synergy protocol and acts like a USB or PS/2 mouse.
I've been using #minput_hop on my 486 with Windows 3.1 and Trumpet Winsock 3 and... with the limitations what they are, it works as well as can be expected (or better, depending on how pessimist- I mean realistic you are)!
The whole reason I'd been working on #minput_hop recently is because my Teknor SBC (and my #Dolch, for that matter,) doesn't have a PS/2 mouse port, so I had to dig out the serial mice I had and try to get those to work, which I couldn't (but it's been years). I have some more somewhere, I'm pretty sure. I don't want to buy one off ebay. Windows says it supports "Genius" or "Mouse Systems," and the mouse I found as a n "MS/AM" switch, and Google is... not helpful.

After a six-month hiatus, I finally managed to bring out something I wasn't sure was possible: a kinda workable release of #minput_hop (a play on Input Leap, if you didn't notice).

This will let you use a #Windows95 / #Windows3 PC as a client for your #Synergy / #Barrier / #InputLeap server. In theory. I only really tested with Barrier and a VM so far, so maybe it's totally broken!

But I figured it I didn't cut a release this weekend, it wouldn't happen for long. 😌

https://github.com/indigoparadox/minput-hop/releases/tag/0.24.1

Release 0.24.1 Β· indigoparadox/minput-hop

This release runs on Windows 3.1, Windows 95, or Windows NT 4. Input is rough and it hasn't been thoroughly tested. Particularly in Windows 3.1, holding the mouse button down e.g. in MSPAINT can ca...

GitHub

I don't think there's a good way to programmatically move the mouse e.g. mouse_event or keybd_event in Win16. I might have to write a custom mouse driver that can be hooked by #minput_hop or something.

Windows 95 works great, tho! 😌

Journal for this evening in case power goes out: Fixed some bugs and added low(er)-res options to vbray.

Also seem to have fixed the long-standing jumbled packets causing a disconnect-every-so-often issue with #minput_hop by adding a second packet buffer that the recv buffer appends to the end to. Nothing fancy like a ring buffer, but keeping it simpler seems to have helped. Probably needs optimizing, now, since it's aimed at the 486. Maybe DOS on worse platforms isn't an impossible dream!