[greyfreak19]

Handle Txt changed to sys

Can someone re-upload this signed file? or a newer one?
I'm trying to overclock my IMO and it goes down to 62hz but not to 125hz.
Atsiv doesn't work with Riot Anticheat and no Test Mode doesn't work with Anticheat either.
This signed file worked but I no longer have it and need it once agian.
If any other method is availiable that works with Anticheat, please let me know.
Thanks.

 

[SweetLow]

Can someone re-upload this signed file? or a newer one?

hidusbff.zip.txt from here

 

[greyfreak19]

hidusbff.zip.txt from here

Both the links seem to be broken

 

[SweetLow]

links seem to be broken

You have to stop using "modern" web browsers with so called "security" and "protection".

 

[greyfreak19]

You have to stop using "modern" web browsers with so called "security" and "protection".

Ayoo, it worked on another browser. Much Thanks!

Edit: I tried zip the zip file, pops up with a warning error loading of service, certificate revoked by user and so on. I tried the Win 8 folder files as well no luck. I have disabled antivirus, and shut down any anti-cheat running. Would I need to enable test mode for this? that would make Anti-Cheat not work tho.

 

[greyfreak19]

Handle Txt changed to sys

This file is the one that worked last time for me, would appreciate if anyone could relink this one.

 

[nomdutilisateur354]

3

 

[Hun61ter]

Hi guys. I'm going to learn some information about the mouse buffer.
I heard that the higher the mouse polling rate, the larger the buffer we need.
What I mean:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\mouclass\Parameters]
"MouseDataQueueSize"=dword:00000019
Thus, for 1000hz we need 19hex (25), and for 8000hz we need 64hex (100).
Tell me, is it really true?

Now I have a keyboard with 8000hz and it also needs a larger buffer - "KeyboardDataQueueSize"

 

[pipes]

edit

 

[SweetLow]

Tell me, is it really true?

Partially - on slow PCs to prevent drops of mouse generated information. On modern (i.e. fast) PCs events usually processed much faster than generated so there is no needs for long buffers.

 

[Hun61ter]

							Partially - on slow PCs to prevent drops of mouse generated information. On modern (i.e. fast) PCs events usually processed much faster than generated so there is no needs for long buffers. Thanks for the answer. It would be interesting to find a tool that can measure whether information is lost when the mouse or keyboard clipboard is too small. I would like to find the optimal MouseDataQueueSize for 4000hz (1600dpi) and 8000hz.

 

[SweetLow]

This file is the one that worked last time for me, would appreciate if anyone could relink this one.

hidusbf.txt from here
P.S. As I have Windows 11 now - this version works fine in Windows 11 (usbxhci.sys 10.0.22621.608) even with Secure Boot on (as all conditions for this met), the sign is valid still (no matter that OS property sheet for signatures states other). And the next version of signature from winmast was revoked in (actual version of) Windows 11.

 

[schuldig]

Hi guys. I'm going to learn some information about the mouse buffer.
I heard that the higher the mouse polling rate, the larger the buffer we need.
What I mean:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\mouclass\Parameters]
"MouseDataQueueSize"=dword:00000019
Thus, for 1000hz we need 19hex (25), and for 8000hz we need 64hex (100).
Tell me, is it really true?

Now I have a keyboard with 8000hz and it also needs a larger buffer - "KeyboardDataQueueSize"

I thought the optimal buffer was depending on the sensor and not the Hz?
Link to PoolMon testing: MouseDataQueueSize Registry Tweak To Reduce Input Delay...

 

[pipes]

My logitech g502 hero has 64 of MouseDataQueueSize

 

[free_microwave]

\

hidusbf.txt from here
P.S. As I have Windows 11 now - this version works fine in Windows 11 (usbxhci.sys 10.0.22621.608) even with Secure Boot on (as all conditions for this met), the sign is valid still (no matter that OS property sheet for signatures states other). And the next version of signature from winmast was revoked in (actual version of) Windows 11.

how do i actually use this file? my windows defender throws a fit about it and spam deletes it on reboot no matter what measures i try and take to get it to leave it alone. i've tried the usual tricks, like adding specific exceptions for the file it self and even disabling windows defender entirely through gpedit, only to still find it still deleting the file after a reboot each time

 

[imanoobie]

hidusbf.txt from here
P.S. As I have Windows 11 now - this version works fine in Windows 11 (usbxhci.sys 10.0.22621.608) even with Secure Boot on (as all conditions for this met), the sign is valid still (no matter that OS property sheet for signatures states other). And the next version of signature from winmast was revoked in (actual version of) Windows 11.

hii i know im not maybe in the correct place but i could really use your advice on overclocking the ps5 pad to 8k its very very inconsistent sometime applied sometimes feels not applied tried many pads and 2 different pcs 1 windows 10 and 1 windows 11 both running secure boot off and stock 13700k cpus same with another 12700k win11 build we have here maybe im doing something wrong is there a specific version i need to get a stable 8k on the pad i have been using the last commited hidusbf.zip on github

edit im on windows 11 and have this plugged into usb 3 root hub on motherboard

 

[ali0090]

chat any one help me i have usb 3.20 but not work for me

 

[greyfreak19]

hidusbf.txt from here
P.S. As I have Windows 11 now - this version works fine in Windows 11 (usbxhci.sys 10.0.22621.608) even with Secure Boot on (as all conditions for this met), the sign is valid still (no matter that OS property sheet for signatures states other). And the next version of signature from winmast was revoked in (actual version of) Windows 11.

I appreciate the link, but unfortunately it doesn't work still for me [Windows 10 22H2] tried USB 2.0 and 3.0 ports. It pops out an error when I check filter on device, and upon restarting the device it fails to work until I uninstall it from device manager and re-plug it back in. I assume this has to do with the certificate, which is odd because you mention it works for you. I even closed everything in the background, even vangaurd anti-cheat but to no avail. The default hidusbf.sys files don't pop out this error but again they fail to overlock.

Currently I can get my mouse to overclock using the Atsiv methood, it runs at 1000mhz. The only downside is that Vangaurd blocks Atsiv from loading the driver, so I have to close that for this method to work which means I can't play Valorant with it and also have to restart my pc whenever I wish to play. Trying to automate the loading of the driver upon boot in hopes it loads before Vangaurd also doesn't work. So if anyone is in the same situation as me and doesn't play valorant, go ahead with the Atsiv method.

The previously signed file used to work well on my previous windows install, i reinstalled windows but then the file was unavailable to download, and now since you were kind enough to re-link the file, it just doesn't work for me. If it's working as expected for you, I assume it could be my windows install. If I can grab another pc to try it on I'll update this post.

Update: Tried on another Windows 11 PC, same issue.

 

[free_microwave]

I appreciate the link, but unfortunately it doesn't work still for me [Windows 10 22H2] tried USB 2.0 and 3.0 ports. It pops out an error when I check filter on device, and upon restarting the device it fails to work until I uninstall it from device manager and re-plug it back in. I assume this has to do with the certificate, which is odd because you mention it works for you. I even closed everything in the background, even vangaurd anti-cheat but to no avail. The default hidusbf.sys files don't pop out this error but again they fail to overlock.

View attachment 2627928

Currently I can get my mouse to overclock using the Atsiv methood, it runs at 1000mhz. The only downside is that Vangaurd blocks Atsiv from loading the driver, so I have to close that for this method to work which means I can't play Valorant with it and also have to restart my pc whenever I wish to play. Trying to automate the loading of the driver upon boot in hopes it loads before Vangaurd also doesn't work. So if anyone is in the same situation as me and doesn't play valorant, go ahead with the Atsiv method.

The previously signed file used to work well on my previous windows install, i reinstalled windows but then the file was unavailable to download, and now since you were kind enough to re-link the file, it just doesn't work for me. If it's working as expected for you, I assume it could be my windows install. If I can grab another pc to try it on I'll update this post.

Had the same issue, my guess is the certificate died since the time it was posted. With the way MS has locked down drivers post-Win7, for ppl trying to OC old school mice to game with, this method is more or less outdated IMO. With astiv you severely limit the games you can play and the certificate work arounds aren't reliable.

Here's a thread that has all the info you need to set a dongle that lets you OC old school devices up to 1khz in a way that's far more compatible with modern OS's and anti-cheats.

 

[greyfreak19]

Had the same issue, my guess is the certificate died since the time it was posted. With the way MS has locked down drivers post-Win7, for ppl trying to OC old school mice to game with, this method is more or less outdated IMO. With astiv you severely limit the games you can play and the certificate work arounds aren't reliable.

Here's a thread that has all the info you need to set a dongle that lets you OC old school devices up to 1khz in a way that's far more compatible with modern OS's and anti-cheats.

Ah, that looks like a neat solution, unfortunately not as cheap. I'll just have to stick with my ghetto solution of Atsiv when wanting to play other games and rebooting to play Valorant. (An even better solution would be to uninstall Valorant lol)