Do you need this if running driver version 5.0.9.0?
There were some rumours that Razer incorporated the so called "CPL fix" into their drivers.
As far as I understand Windows' pointer ballistics, this fix is broken - it completely ignores the coherence between the X and Y values.
My patch is no registry fix. It disables the capability of cursor acceleration inside the system driver responsible for that, so it won't matter what registry values you have.
Personally, I tested it with registry values that lead to the cursor's deadlock if acceleration is enabled (Didn't want to suffer from any placebo).
Just to let peeps know that might not know otherwise, you can do this change by booting into 'safe mode' then applying the patch.
It should work with any mode, but in Safe Mode you won't get the WFP errors.
Personally, I wouldn't boot into Safe Mode for this, because it can perfectly handle WFP.
I must admit, I don't notice any acceleration in Win XP SP 2, but maybe I've just grown used to it so I shall definitely give this a try once my backup images are written.
My description may be a bit misleading. If you uncheck "Enhance pointer precision", you won't have acceleration anymore. But in some circumstances (as I already explained in previous posts), cursor acceleration gets reenabled when you don't want it to be.
This patcher renders the "Enhance pointer precision" checkbox completely useless as the registry values concerning the acceleration are, then.
1) I assume that the patch will work with any newer versions of win32k.sys if it's applied at a later date as it searches for and replaces certain code rather than replacing the whole file?
This is a search-and-replace (or search-and-destroy) byte patcher.
It does not overwrite the whole file, but searches for a certain sequence of bytes and changes them.
Basically, it only has to decrease one byte by one point, but I had to increase another byte in order to keep the CRC valid (otherwise the driver crashes the system).
It changes the following sequence (pseudo code):
If MouseSpeed = 0 -> CHANGE: If MouseSpeed >= 0
then NoAccel
else Accel
2) As it is to "completely disable any mouse acceleration, smoothing or scaling" does it render the mouse speed slider in Windows mouse control panel non-functional?
The customizable mouse
sensitivity should not be affected by this at all.
When searching for possible manipulation attempts, I found one section where I could have disabled both sensitivity and acceleration settings (leaving only the raw input), but decided against this solution.
