You may recall a couple of weeks ago I asked around for a program that could let me control CPU access and time allocation for all the processes running on my computer. (Or you may have a life and don't bother to take note of every post I make, either way...) After it became clear that there was no such program, except for a half-baked utility by Tom's Hardware that didn't really fit the bill all that well, I decided to make my own utility if I could. I have done so. First and and most importantly, it's pretty. Not World-of-Warcraft pretty, but at least prettier than the Tom's Hardware utility. Second, it controls BOTH process priority and CPU masking in realtime, meaning you can reallocate CPU power at whim, and it reapplies those same settings when a process ends and restarts. Third, it can save separate scheduler profiles for recall at a later time, so you don't lose your usual settings when you have to make a temporary change. Fourth (and here is the feature I had really wanted but nothing else could offer), it provides the ability to set aside certain CPUs as being exclusively-allocated to certain processes. When a process with exclusive CPU access is started, the utility will automatically shift all other processes out of the way, and then redistribute them to the exclusively-allocated CPU when the VIP process quits. Also important for a program that idles away in the System Tray, it uses almost no CPU power to do its job. Having it running for almost six hours, I see that it's used only ~5 seconds of CPU time. I've already discovered this to be wonderful when using heavy-duty digital mapping software, and I imagine it would make other tasks like movie-rendering more stable without getting in the way of doing other things like web-surfing or instant-messaging. In fact, VIP processes perform even better than I expected when given exclusive CPU access, because the CPU doesn't have to dump the VIP process' code out of its cache memory as often. I'll post screenshots when I get time at work. My home computer is single-CPU, and I haven't ordered my dual-core laptop yet. There's no point in posting screenshots of single-CPU access and time allocation. EDIT: I don't know what capabilities Fedora, Debian, BSD, UNIX, etc. have. I do know that this program expands upon what Windows provides out of the box, hence the reason for my having spent three weeks developing it and writing a user's guide.