Windows detects USB GPS as Serial Ballpoint - please suggest permanent modification to prevent any serial mouse detection

Per all of you who are having trouble with this in XP, open up the boot.ini in c:\ and add  /NoSerialMouse right after (no space) the /fastdetect command.  This should do it.  It is a huge nuisance but solvable.

Still waiting too, in my case its for the "real" RS232 com ports.

I am on a sail boat, USB-stuff is ok as these have their own drivers, but dataflow (NMEA0183) is a plain text string, endless.

I use a software multiplexer and everything went fine for years after disabling serial mouse checking in XPpro, until I installed windows7.

On the com ports are: com1=ICOM Radio, com2=Airmar weather sensor PB200, com3=Raymarine AIS500, COM4=Raymarine Autopilot. Soon there will be 2 more serial ports for weather fax demodulator and another ICOM SSB Radio

Can it be rally true that a problem solved ages ago for win98, winME, winXP now pops up in win7 again and is UNSOLVEABLE????

I do not seem to be the only one who does not find a maybe obious solution, but why the heck is there no help from the company that had no problems asking for my money? A little customer service would help a lot, gain more goodwill on customer side  than Mr. Gates money for welfare.

It only needs that command line again to stop windows installing an obsolete serial ballmouse whenever there is any data flow at a serial port.

Yes, starting windows first and then switching on other devices helps. But, bad habit, from time to time windows thinks it must check ports again and in middle of nowhere, usually at inconvenient times, it installs it again. Not funny to switch off all navigation electronics in the middle of the night in close quarters and make a reboot. Btw. in those cases shut down takes a long time too, only work around: the old electric off-switch. Welcome in the 21 century

Well i havent found a reliable solution in the couple of months. Sadly microsoft's idea of "is there data over the serial port? must me a mouse." means i'll likely buy a new gps, or get linux up and running as my in vehicle system...but that has bad support for my wlan/bluetooth combo :) either way it's probably worth buying a new piece of hardware. Thanks Mark and microsoft for not responding to the thread :P

Hi TNator, I followed your advice: installed WDDK7.1, built the environment as directed in the manual and ran devcon, disabling *PNP0F09. And yes, this solved the problem of the adapter installing itself as a serial ballpoint mouse; but only "one way". It only works when I switch off my GPS and then start the computer. But if I perform the sequence the other way round, which I normally do when sailing: the GPS runs and incidentally I start the laptop, just for a check-up on my paper-chart navigation, the mouse starts jumping again. However, it doesn't install itself as a serial ballpoint mouse anymore, but under Devices it then lists itself still as a mouse, albeit as a com-port.

Obviously it is already a giant step for mankind that the connection now works if I remember to do some switching on and off for certain instruments, but the system is still not completely okay. If you have an other suggestion, I would be most grateful.

Witte Raaf

I've made the registry change from above, and it works for awhile, but for some reason the reg setting keeps reverting back to a 3.

I'm also sometimes getting a bluscreen that I believe is also caused by the GPS being connected at boot. After the BSOD is when the reg setting reverts back to 3.