I am trying to increase the USB sampling rate of my USB mouse. This is how I used to do it in Windows 7: Run DSEO and enable test mode. Reboot. Right click HIDUSBF.INF and select Install. Configure the driver and set the polling rate to 500 hz. Run DSEO and sign these two files: C:\Windows\System32\Drivers\HIDUSBF.sys and C:\Windows\SysWOW64\Drivers\HIDUSBF.sys Reboot. And voila! My mouse runs at 500 hz! Apparently, enabling DSEO in test mode does not work anymore, so here's what I've done so far in Windows 8: In elevated cmd, I ran this command: bcdedit -set TESTSIGNING ON Reboot. Right click HIDUSBF.INF and select Install. Configure the driver and set the polling rate to 500 hz. Run DSEO and sign these two files: C:\Windows\System32\Drivers\HIDUSBF.sys and C:\Windows\SysWOW64\Drivers\HIDUSBF.sys Reboot. My mouse is still running at 125 Hz. This is a nightmare. Then, I tried: In elevated cmd, I ran this command: bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS Reboot. Mouse is still at 125 Hz. Do I need to convert the INF file to a CAT file?
Thank you so much. I appreciate it. Driver direct download: ngohq.com/attachments/news/1954d1243462515-how-to-increase-usb-sample-rate-in-windows-vista-7-hidusbf.zip The file that I right clicked and installed was: Extracted Directory\DRIVER\HIDUSBF.INF
It didn't work, but I think this is my fault because of my rather limited knowledge of how this entire driver signature enforcement thing works. Here is what I did: I am still in test mode. I extracted the 7z file to New Folder on my desktop. I right clicked HIDUSBF.INF and selected Install. I ran DSEO and signed the following: C:\Windows\System32\Drivers\HIDUSBF.sys and C:\Windows\SysWOW64\Drivers\HIDUSBF.sys and C:\Users\Owner\Desktop\New folder\DRIVER\hidusbf.cat I rebooted. I suspect it's because I wasn't supposed to sign the cat file that was on my desktop? Or maybe I was supposed to install the cat file instead of the inf file? Right clicking the cat file didn't seem to give me an install option. I did a search on my computer and the only hidusbf.cat file I can find was on my desktop.
Hey 100 I have a question for you. I have a driver that only works in 32 bit and I want to use x64. The driver is not available for x64, I know this as fact. The device is a MN-510 USB wireless network adapter. MS has stopped support for this device and only has 32 bit drivers on there site. If I give you the driver can you see if you can change it to work in x64. When I try to install the driver in Windows 8 x64 it gives me the error inf not supported or signed.
Hey 100 - I tried this as well but still stuck at 125mhz. I've been able to successfully install the hidusbf.sys on Windows 7 x64 many times before so I'm pretty sure I'm following the correct steps. This leads me to believe that Windows 8 is somehow preventing this change. I'm not seeing anything out of the ordinary in the System event log as well. 59 tahayassen, In looking at the steps you followed - I see that you are signing the driver in the SysWOW64 folder. The driver should have been installed to the System32 folder. I think SysWOW64 - is for 32bit binaries and you cannot use 32bit drivers in x64. But if the driver package we are using does have an x64 version. Give it another try but sign from "C:\Windows\System32\Drivers\hidusbf.sys"
Ok, well, don't know then. I know Windows 8 requires .cat files for drivers, so I figured that may have been the issue. Inf2cat didn't give me any errors when making the .cat No, sorry. You would need a version of the driver that is compiled for x64, which is not possible to do without the driver source code.
@obsidience: Still not working. I think the problem is with the actual driver - not the driver signature enforcement. Windows 8 probably has a new version of the usbport.sys file and therefore this patch is no longer working. I suppose I can hex edit the usbport.sys and patch it myself. The hard part is finding what to hex edit. I need to change the delay from 8 ms to 2 ms. I've found a temporary work-around: use a USB to PS/2 converter and use this application (link: majorgeeks.com/PS2_Mouse_Adjuster_d298.html) to increase the sample rate to 200 Mhz. Because it's a PS/2 port (PS/2 is a packet driven serial bus), 200 Mhz for PS/2 feels the same as 500 Mhz for USB.
Hey tahassen, I was going to give that a try and then remembered I had thrown away all of my PS/2 hardware away a few weeks ago (thinking I would never need that again). Hah! I might order another from eBay but it would be nice to keep this USB. Glad you found a work-around. vymrdal - other than maddog we were trying to use a x64 driver. I've heard your argument before (get a better mouse). The thing is - the expensive gaming mice would still have the limitations of the polling frequency of the USB port until their drivers correct this issue via software. So the issue isn't really a hardware issue it's a software issue. I have a cheapo Microsoft Compact Optical that turns into a very precise "buttery" mouse when you up the polling frequency from 125mhz to 500mhz. Thanks anyway
adf.ly/gW3b1 < All Files in one archive Me using Windows 8.1 X64 Build 9600, Works 1 : Installed Windows8.1-KB2908279-v2-x64.msu 2 : Restart 3 : In elevated cmd, I ran this command: bcdedit -set TESTSIGNING ON 4 : Right click HIDUSBF.INF and Install 5 : Open Setup.exe set your settings 6 : Restart * : I added with Gamemouse.diagcab :explorer.exe , dx_mouse_timer_dialog.exe , and game.exe . Maybe its not necesary to do this, I just did it without checking before if it already works. Sources : mediafire.com/download/d5ui3s3429bzvo4/usbhidf.7z SOURCE > forums.mydigitallife.net/threads/41351-Need-help-with-driver-signature-enforcement-in-Windows-8?p=698354&viewfull=1#post698354 Windows8.1-KB2908279-v2-x64.msu SOURCE > support.microsoft.com/kb/2908279 Gamemouse.diagcab SOURCE> go.microsoft.com/?linkid=9844530 (from support.microsoft.com/kb/2908279)