Jamie wrote:
> Hi,
>
> I have a USB GPS device that I am using in windows XP, when I plug it
> into the USB port, windows autodetects it as a mouse, and the data that
> is sent by the GPS device makes the mouse cursor move around. The GPS
> software I have works properly and also can read the GPS device, but it
> is hard to use since the mouse cursor moves around by itself. Is there
> a way to prevent windows from autodetecting this USB device as a mouse?
>
> cheers,
> Jamie
>
My guess would be as follows.
1) The USB GPS is really an RS232 GPS with a USB to RS232 adapter
chained to it. So really, it appears to Windows as a serial port.
2) They used to make serial mice. That was a mouse that plugged into
an RS232 port. There was code to check RS232 ports, and see if one
of those kind of mice was connected.
I suspect that is how a mouse is being detected on that port. First,
Windows detects a serial (RS232) port. Then, the mouse detection
function tests for a serial mouse, and thinks it has found one.
The question then is, can you disable serial mouse detection on
WinXP, in the same way as you can in these articles ?
(WinNT and /NoSerialMice)
http://support.microsoft.com/kb/131976
(Win2K and registry hack for serenum)
http://support.microsoft.com/default.aspx?scid=kb;en-us;q283063
According to this, the /fastdetect option in boot.ini , does the
same thing as /NoSerialMice used to do. I don't see /fastdetect
offered in the "msconfig" utility that manages boot.ini , so
you might have to hack boot.ini the hard way (with Notepad).
http://web.archive.org/web/20061206...technet/sysinternals/information/bootini.mspx
If "msconfig" doesn't have the necessary option, a recipe for
using Notepad is included in this article. Apparently, the
attrib command, used in a command window, changes the boot.ini
so it is no longer read-only.
http://www.howtogeek.com/howto/wind...rrect-or-duplicate-entry-on-the-xp-boot-menu/
I'd test this for you, if I could only remember where I left
my serial mouse
I own one, but never used it.
I checked my boot.ini and it already includes /fastdetect.
So it looks like I may already be protected from something
like this happening.
Paul