v1c7r1x has written a small tool to fix Painkillers “turbospeed” problems in an automated way. It runs in the background and waits until Painkiller starts, then automatically sets it CPU affinity to CPU #1.
- .NET is required, probably 4.0; lower versions may work but this hasn’t been tested.
For a simple test, start PkCPUEnforcer.exe, then Painkiller. The output window should indicate that Painkiller was detected and that the CPU affinity has been set. You can verify that with checking the CPU affinity in TaskManager.
Automating the startup
When you checked it works, you can make a permanent background install. Download Hidden Start, extract hstart.exe to PkCPUEnforcers directory, and then create a link to HStart_PkCPUEnforcer.bat in your AutoStart in the Start Menu. This will make sure PkCPUEnforcer runs each time you boot/logon.
Currently there are no known bugs, but v1c7r1x suspects that there may be permission problems on some machines. Please provide feedback if you run into any problems. Post here or write mail to v1c7r1x@hotCOLDmail.com (remove the COLD first, though).