WinXP Pro Screwy Mouse behavior

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all

Got XP Pro installed on a PIII, 600 Mhz box

Using a Microsoft Intellimouse Optical Mouse

Lately, the Arrow cursor stalls frequently, and at times issues various clicks (like the 'Back' button and right click) all by itself

I've replaced the mouse with another... no effect
I've re-installed Windows... no effect
I've re-downloaded and re-installed IntelliPoint 5.0... no effect
The next thing may be to re-flash the BIOS, but why, when the mouse worked fine a week+ ago..

Sysinfo reports no problem devices..

I really like XP (its head and shoulders above 2K), but this one has me beaten.

Suggestions, anyone, PLEASE?
TIA Jac
 
CapnJackD said in
Hi all!

Got XP Pro installed on a PIII, 600 Mhz box.

Using a Microsoft Intellimouse Optical Mouse.

Lately, the Arrow cursor stalls frequently, and at times issues
various clicks (like the 'Back' button and right click) all by
itself.

I've replaced the mouse with another... no effect.
I've re-installed Windows... no effect.
I've re-downloaded and re-installed IntelliPoint 5.0... no effect.
The next thing may be to re-flash the BIOS, but why, when the mouse
worked fine a week+ ago...

Sysinfo reports no problem devices...

I really like XP (its head and shoulders above 2K), but this one has
me beaten..

Suggestions, anyone, PLEASE??
TIA Jack
Click to expand...

Is it a cordless mouse? Presumably you have already checked for low
power by installing fresh or newly recharged batteries. Are there any
other cordless mice around? If so, how far away are they? Was the
"re-install" of Windows a Repair, parallel install, overwrite install,
or a fresh install (format and install)? If it is connected to the USB
port, have you tried using the adapter with the mouse to use it on the
PS/2 mouse port?
 
is this a new mouse, with the new tilt wheel?

if not then don't use Intellipoint 5, stick w/ 4.12. it has more features
and works better with the "older" mice. IP 5 offers nothing to users w/o
the tilt wheel.
 
Thanks for the reply, Vanguard

No. Its a tethered mouse. I've tried connecting it to both the USB and PS/2 ports, with no difference

The re-install was an overwrite (Bill calls it an upgrade, I think). It re-installs everything but leaves the user settings intact

This is a dual-boot configuration with win2k on drive c and winxp pro on drive f

Jack
 
Thanks for the reply, frodo

No, its an older (1-2 years old) mouse. I think it came with v3.2. I'll search around for v4.12

Jack
 
Well, it could be a couple of things, none good.

It's possible that some rouge SW is screwing w/ you, tho unlikely. Run
AdAware etc to double check.

Try exiting all unnecessary processes and system tray things. See if it
returns to normal along the way. I've seen strange interactions that you
wouldn't expect (zone alarm preventing windows explorer from opening a
search for files window for example).

It's possible that the mouse port HW is bad. no real fix for that, other
than a new motherboard. perhaps reseating/wiggleing the connector will
show up something. If it acts up when wiggled it could indicate a bad
solder joint, which a careful tech (or you) could repair.

Did you try raising the interrupt rate? [dev manager | mouse | advanced
settings tab].

You could try removing all drivers and force a return to the native XP
driver. look in windows/inf for an OEM*.INF file that ids the mouse.
delete it AND the corresponding .PNF file. then use add/remove programs
to uninstall intellipoit completely. then go into dev mngr, select
the mouse and press delete. then let it auto-detect it again.

good luck
 
CapnjackD said in
Thanks for the reply, Vanguard.

No. Its a tethered mouse. I've tried connecting it to both the USB
and PS/2 ports, with no difference.

The re-install was an overwrite (Bill calls it an upgrade, I think).
It re-installs everything but leaves the user settings intact.

This is a dual-boot configuration with win2k on drive c and winxp pro
on drive f.

Jack
Click to expand...

Try going into the mouse's properties (in Device Manager) and see if
upping the sampling rate will help. If not then try to up the buffer
size.
 
Back
Top