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.
I had the same problem, cursor sometimes jumps all over the screen
Here's the fix: Open Regedit. Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SerMouse, and change the value "Start" from 3 to 4. Reboot.
I found this on a website for a program to help with gps . Worked like a charm for me.
There is a reg file that will do the editing for you also. http://www.curioustech.net/downloads/reg.zip
AMAZING!!!!
=====================================================
Here's the fix: Open Regedit. Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SerMouse, and change the value "Start" from 3 to 4. Reboot.
=====================================================
Work 100%
Just test on 3 systems
This is first realy working solution for this crazy mouse with beliewed from M$ balls!!!
Thanks!!! Thanks!!! Thanks!!! Thanks!!! Thanks!!! Thanks!!! Thanks!!! Thanks!!! Thanks!!!
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.
Mark, this has been a major issue with most dongle USB GPS devices for ages. I have a GlobalSat ND 100 dongle that every single time it has been plugged in to either my XP Pro laptop, OR my new Windows 7 Home Premium system, that it enumerates my GPS as a "MICROSOFT SERIAL BALLPOINT MOUSE". Now, here's the real problem: With my old XP Pro system, you could open the control panel, open device manager, and expand the tree - and then open mouse and pointing devices, and wait...when the enumeration process began once you plugged the dongle GPS in, if you were really fast, you could select the freshly-enumerated "MICROSOFT SERIAL BALLPOINT MOUSE" line, right click it (before your cursor went totally NUTS from the GPS words) and then hit ALT-U (uninstall driver). Then, you could get enough control to hit "OK" to confirm...once done, the GPS driver would enumerate properly...FOR THIS SINGULAR BOOT-UP.
Sadly, with Windows 7, you can try this trick, but the sorry-thing wants to keep checking enumeration, and within seconds, it overrides the GPS enumeration and goes NUTS again. My $75 GPS dongle no longer works, as a result...Guess I'll keep XP Pro so I can actually work with my computer in the field!
Yes, it is all the fault of the GPS device manufacturer apparently conflicting with MS naming/enumeration...then again, what is so important about 'SERIAL BALLPOINT' that it has to cyclicly check enumeration for itself...XP didn't do this?!!! I mean, geesh, if I UNINSTALL the driver, Win7 should get a clue that I don't want that driver! How about being able to uninstall that complete driver? I mean, you can do that now...but as soon as you plug in the GPS dongle, it re-installs and prioritize-enumerates, overriding other drivers...what gives?
By the way, this is also a majority issue with anyone using plug-in GPS'. Just do a GOOGLE search for "UNINSTALL MS SERIAL BALLPOINT" and you will see EVERYONE asking how to stop this insanity...dating back over 5-years....
If you get any actual, working, semi-permanent solutions - PLEASE e-mail me! My GlobalSat GPS dongle is EXCELLENT for use with Streets & Trips, especially when ATV and off-roading...but it is worthless when Win7 won't support the dongle to work!
Of course the registry is writeable. Make sure you have administrative permissions.
