Windows 7: Save process priority and affinity

Hello,



I'm running a few gameservers myself on Windows Server 2008 R2 but I'm wondering if it's possible to make my system recognize that the process was ran earlier, and it'll apply the correct affinity and priority.

The problem is that I used to use ProcessLasso, but after 40 days of uptime (and then a restart) I'm not able to run the program without purchasing it.

Purchase the program. Of find an alternative. I don't have one.

I didn't really create this thread to be told to purchase the program. It's $89 just because I'm using Windows Server 2008, otherwise it'd be $30, which isn't such a deal.

If the program need purchased to play then that is what is needed. We are not going to tell you how to bypass the any copyright. Please read our rules. #4
Windows 7 Forums - Forum Rules

Hello Cyberuben,

If you wish to continue using ProcessLasso, then you'll just need to purchase it.


As an alternative, you could use the tutorials below to make setting CPU affinity and priority easier to do via the context menu.

"Run with Priority" - Add or Remove from Context Menu

and

Processor Affinity - Add Set Affinity to Context Menu

Hope this helps,
Shawn

Is there a way to do this using batch? So I can just make a "start.bat" that makes it run with the correct affinity and priority? The problem is that I'm trying to run Source servers, which don't really work properly on multiple cores. So I'd like to run my servers each on a single core, unless they are like a 10 slot server.

Currently I work with a set of shortcuts. The shortcuts have the following "command":
Is it possible to run the same "command" but with parameters that make it have the correct affinity and priority?

Found a way. Instead of running that command directly, you need to run it though the "start" built-in command, it allows to set both the starting priority and affinity mask:

This one starts the server with the lowest possibly priority and running on CPU 0 only. Just adjust the first parameters to whatever you need in the command line from your shortcut and you're done.

Thanks a ton!

I found out the following:
CPU 0 = 1
CPU 1 = 2
CPU 3 = 4
CPU 4 = 8
CPU 5 = 16
CPU 6 = 32
CPU 7 = 64
CPU 8 = 128.

But when I use the start command with 128, it'll run core 3 and 5, which is 20. Strange.

Apparently, the affinity mask seems to be an hex number, not decimal as we though. And 128 in hex equals 100101000 in binary, which enables CPU 3, 5 and 8. So, the actual table should be:

CPU 0=1
CPU 1=2
CPU 2=4
CPU 3=8
CPU 4=10
CPU 5=20
CPU 6=40
CPU 7=80

And add those values in any combination to enable more than one CPU. But add them in hexadecimal (Windows built-in calculator in programmer mode can do the math).