200hz ps/2 refresh in win2k?

[Floydian]

I just got a new Intellimouse Explorer 3.0 and the MS drivers dont allow ps/2 rate changing, like the logitech drivers, up to a full 200hz. The highest I can get is 100 hz with windows' mouse properties refresh changing in device manager. I've also tried the MemSoft ps/2 mouse adjuster for windows 2000, as well as the original ps/2 rate changer (which is just win98 I believe), niether of which work, or from what I can tell. If i set the MemSoft adjuster to 60hz theres no difference from 200 hz, so I take it its not working.

Anyone got a MS mouse working with the MS drivers (for full functionality) at 200hz in win2k?

Any other ideas on what to do?

Thanks!

 

[John]

<< Any other ideas on what to do?

Thanks! >>



Use the USB adapter and get 125Hz

 

[Floydian]

How would I go about adjusting it up to 125 hz? Same problem :/

MS put 200hz integrated in to XP, unlike the win2k version - that goes up to 100hz - why cant they just patch it and make everyone happy.

bleh

 

[John]

USB mouse refresh rate is 125Hz native. No adj. needed.

 

[Floydian]

Any ps/2 solutions yet? anyone able to make a program for this maybe?

For FPS, I noticed a difference going from 200-> 100, not as smooth moving around the mouse it seems like

 

[S0me1X]

I had a Microsoft Wheel Mouse Optical, it was much smoother in USB than PS/2 (even after I set poll rate to 200hz). I think optical mice in general work better on USB.

edit: I switched back to my good ol' logitech mouseman wheel (ball mouse, ps/2, super smooth )

 

[Floydian]

Thinkin about switchin back, but finally got ps/2 to 200hz ugh

Went in to regedit and searched for samplerate, found the mouse one, changed it from the 100 it was at to 200, and now the mouserate prog I got reads 200! w00t axion
Now lets see if I notice a difference

Had a mouseman wheel ps/2 as my old mouse, still thinking about whether I should keep this or not...

My settings that I changed that finally worked (note- none of those progs I d/l'd worked..... erm doh) was under the ACPI section in the registry, dunno why... oh well, at least it works at 200 now