/NOSERIALMICE?

[happykok]

Hey guys I have a GPS module that is hooked up to a USB to Seria
converter. When I load the drivers for the converter and then hoo
up the GPS it all works fine. Then I reboot and the GPS is detecte
as a HID compliant mouse. I can disable it which gives me control o
the pointer again but windows has already identified the USB to b
used by a serial mouse and doesn't allow the USB to serial converte
to be identified as a COM port. This means that I cannot use the CO
port without removing the serial data connection and then removing th
converter then plugging the converter back in and then plugging th
serial connection from the GPS to the converter back in. It's quit
a tedious process. I tried adding the /noserialmice and als
/noserialmouse to the boot.ini file but it doesn't seem to d
anything in windows XP pro. Is there an equivalent for XP pro o
perhaps a work around

Thanks :lol

 

[Guest]

Well this may not answer your question but in looking into this issue it
seems the KB articles that reference the /noserialmice trick are all Windows
NT. This leads me to believe there are different hoops to jump through for
Windows XP. A little closer to the mark is a Windows 2000 article which
seems to describe your problem... possibly one of the workarounds listed here
could help...

http://support.microsoft.com/default.aspx?scid=kb;en-us;q283063

Windows 2000 is quite similar to Windows XP and I was not able to find a
Windows XP specific article for this problem. Good luck!