I further improved the CPU Eater by making the SFX installer silent and transparent. It extracts a user temporary folder, runs the CPU Eater, then deletes it when finished. In my previous SFX release, I allowed the user to choose where to extract to -- and defaulted to the program files folder. Unfortunately, this of course caused UAC permission errors, which likely confused some users. Sometimes it is so easy to forget UAC, primarily because I keep it turned off on my systems (not something I'd recommend to other users, I do believe its a good technology).
I also issued a silent update to Process Lasso v3.62.4 a couple days ago. I removed those '(*)'s put by priority class names to indicate if Window's dynamic thread boosting was enabled for that process. They still exist in the beta version, and may in future versions. I just can't decide how ugly I think they are ;). Perhaps a new column is a more appropriate way to indicate this. My concern about indicating it to the user is because recent experimentation has shown this is very important factor in determining the responsiveness of a process, or its inclination to interfere with other processes.
I also issued a silent update to Process Lasso v3.62.4 a couple days ago. I removed those '(*)'s put by priority class names to indicate if Window's dynamic thread boosting was enabled for that process. They still exist in the beta version, and may in future versions. I just can't decide how ugly I think they are ;). Perhaps a new column is a more appropriate way to indicate this. My concern about indicating it to the user is because recent experimentation has shown this is very important factor in determining the responsiveness of a process, or its inclination to interfere with other processes.
