|Topic Review (Newest First)|
|09-07-2019 07:55 PM|
yay 8khz working again.
info and my procedure (i'm not sure what's actually necessary, but this worked for me without much effort)
0. my laptop is on win 10, version 1903, os build 18917.1000
1. enable test signing
run command prompt as administrator, then run
Bcdedit.exe -set TESTSIGNING ON
2. download hidusb.zip from https://github.com/LordOfMice/hidusb...er/hidusbf.zip
download hidusbfn.zip from
3. run hidusb\Driver\Setup.exe
make sure "Filter on Device" is unchecked for now.
click "Install Service"
4. in hidusbfn\DRIVER\AMD64, copy hidusbf.sys to C:\Windows\System32\drivers
replace existing file.
5. open Setup.exe again. check "Filter on Device", set the rate, and click restart
|08-30-2019 01:55 PM|
Sorry for my english, I use google translator
For several days now I can’t accelerate the mouse to 500hz. After reading many posts on this forum, I could not find the answer.
I have Windows 7 7601 x64. Mouse: WMO 1.1. I'm trying to overclock the mouse on USB 2.0 and 3.0 but all to no avail. Above 125hz does not accelerate. Can only lower to 31hz and 62hz. Tell me pls the actual ways to solve overclocking to 500hz.
update: After a few hours of searching, I found advice to remove the USB HUB 3.0 driver. The mouse disconnected, usb ports stopped working. Within 5 minutes, all drivers (except 3.0) were installed and everything worked.
|08-26-2019 02:01 AM|
Ok, little guide - how to completely unload atsiv (its driver) after using.
In archive you will find the real atsiv's drivers (which are just incorporated in atsiv.exe - but can be extracted).
You have to (all with elevated rights)
0. Copy atsiv.sys to any folder, but the usual path for drivers is %windir%\system32\drivers (only once)
1. Create service for driver (only once):
sc create atsiv type= kernel start= demand binpath= system32\Drivers\atsiv.sys
(spaces are MATTER). The example is in Create_Service.cmd
2. then you can start and stop this service (and load atsiv.sys in & unload it from memory) by usual way in any time:
sc start atsiv
sc stop atsiv
So to load atsiv, then load hidusbfp and then unload atsiv:
sc start atsiv
atsiv.exe /f d:\path\hidusbfp.sys
sc stop atsiv
Hope this help.
pwd to internal archive is my exact nickname
|08-23-2019 12:04 AM|
|08-21-2019 02:57 PM|
|Ultimauser||How can i check if my mouse supports ocing? I have an issue with a4 custom driver which seems to block refresh rates highet than 145. And cheapest possible logi with stock win 10 driver oces surprisingly good so its not the fault of pc i think.|
|08-02-2019 01:07 AM|
P.S. usbxhci.sys was changed
|08-01-2019 06:52 AM|
|X7SHaDe||atsiv method broken on latest windows build (18945 - 1907). Can downclock but no overclock. The attached file is a zip of usbport.sys and USBXHCI.sys. File sizes larger than 1903|
|06-29-2019 03:23 PM|
Im moving from windows 7 to 10 soon because they are abandoning it and im also buying a ryzen 9.
The problem is I don't know how things are in windows 10 in order to oc my wmo to 500hz without test mode. Can it be done?
I cannot read 63 pages.
I have also found this guide, is it legit?
|06-28-2019 12:23 AM|
|06-27-2019 08:53 AM|
For some reason, I was able to use overclocking on Windows 1903 without test mode, and even without sweetlow's hidusbf.dll and by only using hidusbf.dll atsiv method. I think the overclock gets loaded into memory without accessing the driver itself.
I'm not yet able to reproduce but here's the steps anyway.
1.) Enable Testsigning (this is temporary only)
2.) Install the new drivers (1000 hz version first? just to check if this really works) for 1903 and setup atsiv too, but do not load atsiv, just prepare the task scheduler to launch atsiv for the next reboot.
3.) Set your desired polling rate.
4.) Verify that it works and then reinstall the "nopatch" driver.
5.) Disable testsigning.
These steps enabled me to retain the overclocked polling rate, but I think if I try to change it again, the overclock will be disabled because I only have the "nopatch" driver now.
|This thread has more than 10 replies. Click here to review the whole thread.|