FIX: Windows sees GPS as mouse & pointer goes nuts

FIX: Windows sees GPS as mouse & pointer goes nuts

Postby strosien » Sun Aug 15, 2004 6:17 pm

Ever boot up Windows with your GPS active then Windows sees it as a serial mouse then goes nuts requiring you to reboot without the GPS attached? Quite a pain, no? There is an easy fix.

For NT4 on up through XP, modify your boot.ini to include /noserialmouse=comx where comx is the com port you will have your GPS attached to.

i.e: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /noserialmouse=com2

will prevent a GPS on com2 from being detected as a mouse. enjoy.
Just wanna drive....
Mini Stumbler
Posts: 55
Joined: Thu Jun 12, 2003 7:41 pm
Location: Michigan, hehe...

Postby G8tK33per » Wed Sep 08, 2004 1:59 am

Found the following syntax instruction as well:

NoSerialMice Syntax

/NoSerialMice - Disables the detection of serial mice on
all COM ports.

/NoSerialMice:COMx - Disables the detection of serial mice on
COM x, where x is the number of the port.

/NoSerialMice:COMx,y,z - Disables the detection of serial mice on
COM x, y and z.

EDIT: I've been advised that the "noserialmouse" syntax is incorrect and won't be accepted by the OS. You may also try disabling the serial mouse thru device manager although I personally haven't tried it.
"Make yourselves sheep and the wolves will eat you." ~ Benjamin Franklin

Sons of Confederate Veterans
User avatar
Posts: 6078
Joined: Fri May 09, 2003 4:00 am
Location: Goomba's Booty Boardwalk

FIX: Windows sees GPS as mouse & pointer goes nuts

Postby theprez98 » Fri Jun 24, 2005 9:53 am

This is an additional fix to the thread title listed above. It worked for me with no problems.

The original sticky is here.

This fix is based on a Windows 2000 problem but works with XP as well. I've cut and paste the applicable portions from Microsoft and modified them for XP.

When you are using a Windows 2000/XP-based computer, a serial device may be detected as a serial mouse. Your computer may actually notify you that a new mouse has been connected, and/or the mouse cursor may jump uncontrollably around the screen.

This problem can occur because most of the devices that are detected as serial mice that are some other type of device constantly send data to the serial port which causes the detection code to incorrectly identify the device as a serial mouse.

In Windows 2000, you first need to update to the latest service pack, if necessary. The English-language version of this fix should have the following file attributes or later (XP users shouldn't need this step):

1/17/2001 03:48p 5.0.2195.3156 13,936 Serenum.sys

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

After you apply the hotfix or the service pack, follow these steps:

1. Start Registry Editor (Regedt32.exe). To do this, click Start, click Run, type regedt32 in the Open box, and then press ENTER.

2. For instructions on how to identify the Enumerator, DeviceID, and InstanceID for your COM Port refer to the More Information section *below* (the device name, description, drivers, etc., should clue you into to the port information):

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\Enumerator\DeviceID\InstanceID\Device Parameters

Note that there is one InstanceID for each port.

3. On the Edit menu, click Add Value, and then add the following registry value:
Value Name: SkipEnumerations
Data Type: REG_DWORD
Radix: Hexidecimal
Value: 0 through FFFFFFFE

Note that a value of zero (0) disables the feature and device detection can resume. Each time that Plug and Play does an enumeration, it counts down one, and when it counts down to zero, it re-enumerates the hardware and then starts counting down again from the registry value. When you reboot the computer, Plug and Play starts the count again at the value that you typed.

4. Quit Registry Editor.


Motherboard based COM Ports
First, you need to determine which HAL is being used before you can make the registry change. To determine which HAL is running on the system open Device Manager and expand Computer.

If the system has an ACPI HAL you can add the SkipEnumerations Reg_DWORD Value shown in Step 3 above to the serial port of choice located under

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ACPI\PNP0501\Port#\Device Parameters
If the system has a Standard (Non-ACPI HAL) you can add the SkipEnumerations Reg_DWORD Value shown in Step 3 above to the serial port of choice located under

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\*PNP0501\Port#\Device Parameters

NOTE: Port# = InstanceID
User avatar
Posts: 3638
Joined: Tue Jan 11, 2005 8:23 pm
Location: Maryland

Return to WarDriving

Who is online

Users browsing this forum: No registered users and 1 guest