Changing USB Polling Rate to 1000hz (or lower) - Page 9

Can someone do what I asked please? I'd appreciate it!

hidusbf.sys is the mod file. It doesn't exist on normal windows systems.

Alright then. Thanks!

Whoa, never though I'd overclock my mouse
I'm not going to try it, but +rep for teaching me about polling rates

I only use logitech 2 button marble mouse trackball

I was using an old green usb mouse adapter plug was getting 90hz lol ... now I'm up to ~648hz ...

There's a command for Ubuntu that let's you do it.

Open up terminal, type:

"sudo gedit /etc/modules"

Add to the end of the text doc:

"-r usbhid
usbhid mousepoll=x"

X=Polling rate
1=1000
2=500
4=250
8=125
10=100

After you restart you can type in terminal to confirm change:

"cat /sys/module/usbhid/parameters/mousepoll"

It'll respond with the number you inputted.

The difference with my Microsoft Intellimouse 1.1 is definitely there. Feels a lot smoother and more responsive.

Just did this with my mx518, other guides online left me with dead usb ports (until i uninstalled the driver), this is perfect many thanks +rep

please let me know what you did - i have a mx518 as well, and i've been gaming at 1000hz for three years on XP and XP64, and there's no going back for me - i'm going to give up on 7 if i can't get it working soon.

at first i couldn't even get test mode in DSEO working properly, i found that it didn't play well with the loader i was using (test mode watermark never popped up). but i got a different loader and now DSEO works fine. can anyone confirm whether they've got 500 or 1000 hz working on 7 x64, build 7600 *with 7loader by hazar 1.6*? could i look for a better loader?

i've tried every guide out there, including epicnerd's and alan's from here, but they're really all just different iterations of the same things; signing the HIDUSBF.sys file before and after installing the INF, installing the INF with right-click vs clicking "install service". some instructions later in the threads also say to dump a copy of the signed file into \\windows\\sysWOW64\\drivers, but i don't see why - a regedit search turns up nothing calling the driver in sysWOW64 (if i'm looking at it right). adam^, please let me know whether you included this step. glad this thread's still kind-of alive.

on the setup.exe that comes with hidusbf.zip, some guides say to click "install service" (which is really just the same as right-clicking the INF and installing yourself); some say do not. i've tried both ways.

some guides say to click "restart" in setup.exe, and some do not. and i've tried both ways. sometimes the screen goes black for a moment, and sometimes it doesn't.

and i gather that i really only need to sign the one in the AMD64 folder, though i've been known to sign all 6 others anyway

i'm past the point of "breaking" the ports, i've gotten pro at uninstalling HID devices in task manager with a keyboard only, i've removed every extra USB device including switching to my old ps/2 keyboard so i can just delete them all and then re-plug the mouse cord. when i follow every guide to the letter, the mouse always works on reboot, just at 125hz. it's as if i hadn't just done a 20-minute, 5-reboot process for the fifth time. i always uninstall hidusbf through the INF and/or wipe it with autoruns. i always delete the newly signed .sys's in the setup folder and start fresh from the .zip.

nothing's worked yet, and i'm getting frustrated because i can usually work these things out. and for every post that says "i followed the instructions and got my mx518 working", there's another like mine.

16 straight hours of this *****, i can only bring myself to write this after a long break from the computer entirely.

UAG slider is all the way down. by the way, i'm new to windows 7 so please tell me; if UAG is all the way down, and you're the only account (administrator), does right-click, run as administrator actually do anything? also, is it still possible to skip DSEO and driver signing entirely and just use the f8-method every boot? and about DSEO - can you just leave it in test mode the whole time as you go through several attempts and reverts?, or is it more advisable to end test mode, reboot, enter test mode, reboot again on every fresh start?

protip: put your dimr.exe/mouserate.exe in your startup folder, so you don't have to wait to open it and be disappointed

and i'm just gonna leave this here; looks like a good sign to me though?




if there's anything i can be more clear on (other than "i've tried everything"), please let me know. at this point i'm beginning to wonder if some recent windows update has changed the game entirely.
how do i even know if the mouse is currently being run under hidusbf.sys or the old hidusb.sys?? the images show the driver is signed, though it shouldn't even matter with test mode on right?
Edited by d3phext - 1/23/11 at 1:14am

something i just ran across; i'm getting conflicting information whether the driver is signed or not.



i'd really appreciate seeing the results of someone who has it working when you check the same things. (you don't need autoruns, you can just right-click the file in explorer to get to the file's properties).
Edited by d3phext - 1/23/11 at 2:20am