Overclock.net - An Overclocking Community - Reply to Topic

Thread: USB mouse hard overclocking (2000 Hz+) Reply to Thread
Title:
Message:

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in


  Additional Options
Miscellaneous Options

  Topic Review (Newest First)
06-02-2020 05:42 AM
Threetimes Hi, it does not seem possible to overclock my WMO with "VANGUARD". Is there a workaround ?
06-01-2020 07:02 AM
SweetLow
Quote: Originally Posted by rqrqqaz View Post
x86 test OK, perfect, thank you

X64 hidusbfp.sys 9.17KB
Sorry! English is not my mother tongue.
0X0000001 does not appear for the first load after rebooting.
Now if hidusbfp.sys loads and finds sequence for patching then atsiv will report success
Ok. Thanks for your efforts in testing, i appreciate your help.

>Sorry! English is not my mother tongue.
I understand, don't worry.
06-01-2020 06:26 AM
rqrqqaz Thank you SweetLow
06-01-2020 06:07 AM
rqrqqaz
Quote: Originally Posted by SweetLow View Post
Did it really work as expected:
>Now if hidusbfp.sys loads and finds sequence for patching then atsiv will report success
? (on the first loading after reboot, of course)
x86 test OK, perfect, thank you

X64 hidusbfp.sys 9.17KB
Sorry! English is not my mother tongue.
0X0000001 does not appear for the first load after rebooting.
Now if hidusbfp.sys loads and finds sequence for patching then atsiv will report success
06-01-2020 05:35 AM
SweetLow
Quote: Originally Posted by rqrqqaz View Post
Test X64 version OK
Did it really work as expected:
>Now if hidusbfp.sys loads and finds sequence for patching then atsiv will report success
? (on the first loading after reboot, of course)
06-01-2020 05:24 AM
rqrqqaz
Quote: Originally Posted by SweetLow View Post
Ok, version for Windows 10 2004 on github:
https://github.com/LordOfMice/hidusb...r/hidusbfn.zip
Additionally:
Behavior of patcher (hidusbfp.sys, for using with atsiv) slightly changed.
Now if hidusbfp.sys loads and finds sequence for patching then atsiv will report success (instead of "Error 0xc0000001, operation failed").
But you have to unload hidusbfp.sys after that i.e.
PathToAtsiv\atsiv.exe -f PathToHidusbfp\hidusbfp.sys
PathToAtsiv\atsiv.exe -u hidusbfp.sys
or hidusbfp.sys will remain in memory.
Test X64 version OK, X86 wait for me to test. Thank you SweetLow
05-31-2020 10:07 AM
SweetLow Ok, version for Windows 10 2004 on github:
https://github.com/LordOfMice/hidusb...r/hidusbfn.zip
Additionally:
Behavior of patcher (hidusbfp.sys, for using with atsiv) slightly changed.
Now if hidusbfp.sys loads and finds sequence for patching then atsiv will report success (instead of "Error 0xc0000001, operation failed").
But you have to unload hidusbfp.sys after that i.e.
PathToAtsiv\atsiv.exe -f PathToHidusbfp\hidusbfp.sys
PathToAtsiv\atsiv.exe -u hidusbfp.sys
or hidusbfp.sys will remain in memory.
05-31-2020 08:16 AM
rqrqqaz Sorry, it is indeed possible to use this file on the 19041 version,
the problem is that I changed the file path myself, big NG.
Thank you
05-31-2020 07:21 AM
SweetLow
Quote: Originally Posted by rqrqqaz View Post
Yes, higher frequency cannot be changed in WIN10 2004 19041 x64 version.
Maybe Microsoft changed ... USBXHCI.SYS again.
Yes, compared with 1903/1909, but version of patcher that i gave you HAVE TO work.
Ok, will try to isolate problem. Send me "Copy IDs" result with applied driver ("Selected Rate"=1000, "Filter on Device" checked, and Restart Button or after reboot) on x64 with the latest setup.exe.
05-31-2020 03:45 AM
rqrqqaz Yes, higher frequency cannot be changed in WIN10 2004 19041 x64 version.
Maybe Microsoft changed usbport.sys and USBXHCI.SYS again.
But the X86 version can also change the frequency.
This thread has more than 10 replies. Click here to review the whole thread.

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off