• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Mouse Pointer Gone Wiled

A

APice

Junior Member
:shocked: :shocked: :shocked:

Mouse Pointer Goes Wiled, Iam booting up XP Pro. using a PS2 mouse.
I have a communication software program that uses com 1 to collect ASCI data 9600 8N1 using pins 2&5 only.
But when data comes in the Com1 port the Mouse pointer thinks that the port is a mouse port and the mouse pointer responds to the data and goes all over th place.
Is there any way to stop XP from thinking there is a mouse on com1 and keep it seeing the PS2 mouse?
This never happend on 2K pro. and I have same problem on 4 other XP PCs.

:shocked: :shocked: :shocked:
 
Is there a "Serial Mouse" showing under Device Manager, attached to COM1? If there is, disable it.
It doesn't surprise me that it doesn't happen in W2K, they changed the HID input layer quite a bit in XP. (IMHO, made it worse.)
 
Hi VirtualLarry
That has bin done in trying to fix the the problem. I had that problem once on another PC that the OS was loaded using a serial mouse then changed to a PS2 mouse.

I started working with Computers when the OS was loaded using 5 1/4 " disk and have MCSE, Networking .... etc but this problem just keeps poping up. I cant find any IRQ or memory address conflick and I just dont know programming that well to start changing lines of code.
 
Here's another question. Are you using only just the stock MS mouse drivers, or have you installed MS Intellipoint, or Logitech MouseWare, or some other 3rd-party mouse drivers? The reason I ask is, they often "probe" the COM ports during startup, and if they detect anything at all connected, they might decide that a mouse "lives" on that port, and enable it in the driver.

Alternatively, you might actually *want* to install the Logitech MouseWare drivers, because I believe that you can configure what ports they search on via some registry keys, and you might be able to exclude COM1 from detection that way.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top