Erratic PS2/USB Wheel Mouse- cursor locks, LED goes out Driver already updated; Registry cleaned via JV16?

Question

Thanks for reading more:

For about the past month, I've been having trouble with the operation of my Microsft Optical Wheel mouse which was PS2 and USB compatible.

I suspect the problem is with the computer, but you tell me.

The computer is running XP pro and is constantly being updated by auto updates of whatever it is Microsoft is pushing at it and with JAVA updates.

I was running the mouse via the PS/2 adapter when the problem started. Under those conditions, the mouse pointer would stop moving and only a reboot (sometimes several reboots) would get it working again.

I have since switched to USB operation and downloaded the latest driver, which comes in the form of an Intellipoint dealy that allegedly can be configured to work for about a zillion mice.

Under those conditions, I can get the mouse to work again by waiting for XP to complain that it doesnt recognize something on the USB bus and dis/reconnecting the mouse cable. LEDs go out during fault.
Thoughts?

Thanks for the answer. Device Manager "trouble shooting" lead me to pages of manual registry cleaning instructions...I ran JV16 and registry mechanic instead. It also said get new drivers...which lead me to the intellipoint thingy... I just looked at the logs as you suggested...nothing there looks related...athough there were a few odd cdrom faults and atapi errors...but far fewer of those than there are mouse locups....so, I don't think they are related.

Answer 1

Since nobody else will bite, I'll take a stab at it with a couple things.

Look at Device Manager--while not very useful, it does have a troubleshooting fuction that may yield some answers.

Look at your Event Log for the time frame of the failures. There are event ID numbers that may be useful in tracking down the source. (Control Panel > Admin Tools > Event Viewer)

Hope this helps
.

Answer 2

Ah, the twisted good judgment of activities info. For the sub to get the sparkling sheet infrequently seems straightforward, rather if he performed in basic terms a restricted nunber of minutes. It strikes me that with the intention to get the credit for the shutout, the keeper needs to play a particular minimum time (60 minutes seems genuine looking). evaluate baseball stats: with the intention to be credited with a win, a starting up pitcher ought to play a minimum of 5 (of 9) innings and be top-rated at the same time as replaced. A sub coming in to close the game receives credited with a "keep", so both pitchers come away with something. except "keep" can be a tricky call for a goalkeeping stat.