Progress report and assessment:

I made an explicit rule for Eudora.exe in PT, to "Force Low" priority. But it doesn't achieve what I need. PT doesn't prevent Eudora from jumping to 25% CPU, apparently because no other programs are competing for the CPU. So Eudora is actually not "in the way" of other programs and slowing them down, and PT doesn't see a need to intervene.

So my goal is still to prevent Eudora from using so much CPU that it normally doesn't need, and thereby heating up the computer. PT doesn't do this.

I tried Battle Encoder Shirase, and it does accomplish what I need -- it reduces a specific program's CPU usage by a specified %, regardless of what CPU other programs may or may not need. Although the BES homepage says it is for "Windows XP/2000," it works fine on my Win7/64.

I'm having a problem with a specific program. I think PT can help, but I don't know how to set it up.

I use Eudora for my email client. Usually it runs on very low CPU, but occasionally when I open an email message, CPU usage jumps up to 25% until I close that message. It doesn't slow down my computer, but its temperature rises.

I'd like to somehow prevent Eudora from running away like that. Can PT do that? If so, how? If not, can Process Lasso do it? Thanks very much.

EDIT: I should add that there are enough CPU cycles available for all my programs; I'm not experiencing a slowdown due to Eudora taking 25%. What I am trying to prevent is Eudora suddenly taking a lot of CPU cycles that it normally doesn't need -- and thereby prevent the extra heat in the computer.

EDIT 2: Perhaps what I need to use is an absolute, program-specific limiter such as Battle Encoder Shirase http://mion.faireal.net/BES/ (thanks to rasmnick for the tip https://www.donationcoder.com/forum/index.php?topic=13003.0 )  Any comments on that as an option? I'm using Win7/64.

Thanks, skwire -- this is wonderful! I haven't experienced any data loss in the several days I've been using 1.0.6. The new icon is more distinctive and representative, and the single-click opening makes it noticeably easier. Also it is really nice to have a link from any meter bar directly back to its configuration -- much more efficient. The color picker module is still a bit odd, so I have sent you details by email.

What do you think of a dynamic update of the meter display (if already shown) when the configuration is changed, rather than needing to click on the refresh button? Lack of that feels a bit awkward to me.