Thanks for all the replies! It's quite difficult for me to describe this mouse problem, please excuse my moderate English skills.
eL_PuSHeR wrote:Have you thought that the bios on your machine may need updating?
No, because when I connect any mouse directly to the computer (without the KVM switch in between), it all works fine, even on my 486.
eL_PuSHeR wrote:Did you also tried getting one online?
Not yet, I think a suitable mouse would be easy to get online, if I only knew which one is compatible with my KVM.
HunterZ wrote:You could plug a separate mouse into each computer as well.
Yeah, I already had this kind of setup before I got the KVM. However, having to grab the correct mouse after each switch tends to get annoying after a short while 🙄
HunterZ wrote:Most PS/2-only optical wheel mice that I've seen are very poor quality, but I haven't seen any for a few years.
I'm using one of these right now, that's why I want to find a replacement. The casing is disintegrating, the mouse wheel gets mechanically stuck, and I've already fixed the cable three times... 😒
collector wrote:I have a USB mouse with a PS/2 adapter on a KVM and have no problems with it.
May I ask which brand/model that is? Maybe it would also work with mine.
HunterZ wrote:Another thought: Are you (5u3) using the USB-to-PS/2 adapter that came with the mouse? I've noticed that trying to mix-and-match adapters with mice that they didn't come with will sometimes not work.
Hmmm, good idea. I'm pretty sure I have the right adapter, but it might be worth a try. Somewhere at work I have a box with about 50 USB-to-PS/2 adapters 🤣
I have my own theory why combo mice do not work with my KVM: It has to do something with the initalization and determining in which mode (USB or PS/2) the mouse should work. Maybe the mouse first tries to communicate via one of the two protocols, and if there is a specific reaction from the port (which my KVM fails to emulate), it decides in which mode to operate.
When connected to my KVM (Aten MasterView Plus CS-114), combo mice seem to operate in the wrong mode after initialization.
I don't know if this sounds reasonable, but I've not been able to come up with a better explanation yet.
