This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Using Win7 ultimate on a variety of machines, when I plug in a 'USB' GPS the system does two things: it installs the support for the USB-Serial device, and then it (using 'serenum' apparently) begins mistaking the GPS for a serial mouse, and 'detects' and installs the microsoft serial ballpoint. I have editted /windows/inf/msmouse.inf, adding a line after line 28 (guessing at the syntax, copying from the alpha excludes)
ExcludeFromSelect.NTx86 = *PNP0F0C,*PNP0F08,*PNP0F09*PNP0F01,*PNP0F0A,*PNP0F1E
This does *NOT* do the trick. The GPS is consistently being enumerated by the system as a "serial ballpoint mouse".
This has been reported by numerous people in numerous forums on numerous configurations over multiple windows versions.
When is Microsoft going to fix this? This is not a GPS issue. This is not a serial device issue. This is not a USB issue. This is, pure and simple, a Microsoft issue.
Removing the 'upperdrivers' entry for serenum might do the trick, but the registry keys are not writeable now in Win7. Sweet. Thanks, Microsoft.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Well this soultion works for me. I can now use the GPS usb and it works well. This ballpoint serial mouse is still in the device manager, but it is disabled. It remains disabled after a reboot, so it is no longer troublesome. Who cares as long this solution works. By the way I use WIN 7.
GPSGate is good, used it for years, but does not solve the problem, while booting windows looks for the serial mouse, gpsgate is only loaded after windows, hence it comes to late.
Another nice (free) program is NavMonPC. I switched to it as it lets you monitor the dataflow from and to each virtual and actual com-port you have, not only that, you can apply filters much more easily, select "collect", all available nmea sentences are displayed spreadsheet style and you just click on wich port you want it available.
It does not solve the juming mouse though.. I bought a "shipmodul" miniplex multiplexer with bluetooth/usb, since then no more problem. BT because nowadays small PC come with less and less connections. using a http://www.buyqube.com/Q-Singles-QMiniPC-Specs-AMD.htm on board now, look at size and power consumption related to price!
Windows 7 sixty four bit does similar with the Sony Navu GPS type NV-U93TW. It thinks that the GPS is a phone! Presumably the Navu is running Windows CE that most mobile phones use. Trying to synchronise My Portable Device with the laptop is only partially successful (failure actually). The laptop can see the Navu and its expansion memory but it cannot read the memory contents or memory size. Later the message "Synchronisation did not complete" appeared. The object of the exercise was to try to load marine charts onto the Navu but it looks as if I'm stuffed for the lack of a few lines of code (I'm not a programmer just a dabbler) This is rather annoying especially as my well liked Advent (AKA Gericom Blockbuster) that ran Xp was stolen by burglars.
I've bought a Toughbook which should be here in a day or two and its running ME. Hopefully this will pair with the Navu.
If anyone knows how to pair a Navu with Windows 7 I'd be very pleased to know.
surf for my answer here dated 27-1-2012
I think I have a solution. Download Franson GPSgate client, which makes virtual com ports. Install it. Then plugin your GPS dongle (mine comes from eBay called: GPS usb receiver). It will show these problems mentioned above with the MS serial ballpoint. Just disable this nasty ballpoint under device manager and leave it like that. Have a look under device manager which new COM port was added, because of plugging in the GPS dongle. Remember it. Then to check if all works download freeware hyperterminal or another COM port terminal program, which checks data coming in from serial ports. In hyperterminal I opened COM port 19 (shown for my GPS in device manager) and, voila, lots of NMEA GPS sentences are rolling in :) Try it your self and post the result here!
Bill,
In my experience (I write weighbridge software) I think everytime that I have seen this...
the scale was set at 4800 baud.
Curious if you could confirm setting a higher baud rate dodges this issue in regards to scales.
