Reply 20 of 43, by javispedro1
LSS10999 wrote on 2022-03-01, 02:09:The prerequisite is that the mouse itself must be recognizable by BIOS/CSM as standard USB mouse. Some recent mice are too advanced to be recognized as standard mouse and they'll never work under BIOS/CSM. I also had USB mice that behaved erratically (like wrong X/Y axes) when operating in BIOS/CSM.
Considering that even the modernest of UEFI bioses is still using the USB boot protocol (the same protocol that was used by even the oldest of USB BIOSes) , this would mean that such a mouse would not work in e.g. UEFI setup. I suppose there is still some pressure to manufacturers to avoid breaking the USB boot protocol since graphical UEFI BIOSes are a thing, so I'm hoping such broken mice are a real minority.
All mouses I had did support the USB boot protocol, even complicated ones like Logitech Unifyng wireless receivers and some Bluetooth adapters (see HCI2HID). I have not tried Bolt receivers, but I suppose they also do -- otherwise users would complain about not being able to use the mouse on the BIOS setup.
LSS10999 wrote on 2022-03-01, 02:09:In that case the mouse will most likely behave the same when connected to PS/2 via adapter.
If the mouse is so recent that it does not work with the USB boot protocol, then it for sure does not offer passive PS/2 compatibility. The mouse basically needs additional hardware for that, I'd guess it'd be much higher in the manufacturer's list of things to cut 😀 . To make it work on PS/2, you'd need an active adapter (e.g. put a Raspberry Pi in the middle), and then you can use standard HID, not boot protocol, so that any mouse that works on Windows without drivers would work. See https://www.kickstarter.com/projects/dekunuke … retro-computers