New CPU Eater goes final

The previous CPU Eater demo I had to take a heavy handed approach to demonstrating the problem because each system is different. Often, the demonstration was therefore overly aggressive. With this new CPU Eater demo, you can set just how many threads to create and at what CPU affinity. This allows you to see exactly how susceptible you are to the critical scheduler problem Process Lasso's ProBalance addresses. You will be surprised how little it takes, but I will let you explore yourself.

I am soon going to add another option to also create a CPU eating foreground thread. Remember, this CPU Eater only creates background threads in a purely background process. A single foreground thread has more of an impact due to Windows giving the foreground thread longer time slices and other boosts in precedence. Of course, ProBalance ignores foreground processes by default, to ensure that its priority adjustment doesn't hinder application performance. Yes, we are very cautious with our algorithms. If you have a problem with a foreground process, click away from it to let ProBalance do its job. For those who don't know, the foreground process is the process that owns the window that has keyboard and mouse focus. This means there is only ever one foreground process at a time.

UPDATE: I did make one post-release update, where I added a new statusbar control to the bottom of the dialog. This shows total running processes and threads on the system, as well as the current state of the CPU Eater. I was forced to disable Russian and German translations pending updates. Other languages are functional, but some text is not translated.