The only problem is that I'm not quite certain what patterns to avoid.Īpparently Microsoft's Mouse protocol consists of packets of four bytes where the MSB of the first is set and that of the last three is clear.

Instead I'd like to avoid the problem by changing our protocol to not send any data which may get us misidentified as a mouse. Especially not when the fix is dependent on the Windows version and the user may well be using a bus mouse. That it is a lot to demand from our users however and I'd rather not have our application messing around with the user's registry.

The problem is that the data we are sending occasionally gets incorrectly identified by Windows as a bus mouse, after which the 'Microsoft Serial Ballpoint' driver is loaded and the mouse pointer starts jumping around on the screen and randomly clicking on things.Ī bit of Googling reveals that is an old and well-known problem with serial devices where the usual work-around is a bit of registry hacking to disable the offending driver. I'm working on a device which communicates with a PC through a (virtual) serial port.

Uninstall mouse driver