![]() ![]() ![]() 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. A 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. 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. I'm working on a device which communicates with a PC through a (virtual) serial port. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |