sp00n

I'm currently testing your code @djangoa. One thing I noticed is that the main process affinity does not change if you change its threads affinity values. It also shows up...

Here's a first experimental version. It does try to set the main process affinity after having set the thread group affinity, let me know if this actually sets the correct...

The signed `[Int64]` I was using actually had a buffer overflow at core 63, I changed it `[UInt64]`, so it should work. At least for the new functionality with `SetThreadGroupAffinity`,...

@djangoa Can you check which affinity is returned after you've manually set a process to CPU 63 (and 62+63), e.g. via the Task Manager? The calculated value is 2^63, so...

Also, here's a second version, which should fix the error for core 63. [script-corecycler-0.9.5.0alpha4-experimental2.zip](https://github.com/sp00n/corecycler/files/15440559/script-corecycler-0.9.5.0alpha4-experimental2.zip) Can you check that both the new functionality as well as the old one works? For...

> > @djangoa Can you check which affinity is returned after you've manually set a process to CPU 63 (and 62+63), e.g. via the Task Manager? > > The calculated...

> > You can just run `(Get-Process 'notepad').ProcessorAffinity`, which returns a value when executed in a PowerShell terminal. > > It returns -1 as you expected. Huh, I actually expected...

> > Can you also check if setting the affinity via PowerShell with `(Get-Process 'notepad').ProcessorAffinity = -9223372036854775808` and/or `(Get-Process 'notepad').ProcessorAffinity = -1` correctly sets the affinity to core 63 in...

Ok, that's weird. Can you set that affinity over the command line? `(Get-Process 'notepad').ProcessorAffinity = 864691128455135232`

I wanted to keep the original functionality to be able to debug issues more easily. It's much more convenient if you can tell people to just check the affinity in...