djangoa

@dkit Please can you share your helper program source? I'm trying to get my 56 core CPU working with corecycler and have hit the same problem. @sp00n please reconsider a...

FYI: I've hacked together some powershell script that implements [SetThreadGroupAffinity](https://learn.microsoft.com/en-us/windows/win32/api/processtopologyapi/nf-processtopologyapi-setthreadgroupaffinity), see attached zip: [affinity.ps1.zip](https://github.com/sp00n/corecycler/files/15402098/affinity.ps1.zip). I imagine integrating this into `corecycler.ps1` should be fairly trivial. Using [SetProcessDefaultCpuSetMasks](https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-setprocessdefaultcpusetmasks) & [SetThreadSelectedCpuSetMasks](https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-setthreadselectedcpusetmasks) might be...

> Can you check if the processor groups are actually filled up to 64 before they spill over to another group, or if they are evenly split between the cores?...

Here's the output from coreinfo for my machine: [coreinfo.txt](https://github.com/sp00n/corecycler/files/15409630/coreinfo.txt) I think in the blog you reference the reason his groups are split evenly is due to the machine having multiple...

@sp00n Hi, > One thing I noticed is that the main process affinity does not change if you change its threads affinity values. It also shows up unchanged in Process...

@sp00n Hi, So I tested and can report that affinity is set correctly but I had to comment out: ``` # Maybe also set the process affinity now? #$Script:stressTestProcess.ProcessorAffinity =...

Hi again, I disabled the CPU utilisation check and that resolved the previous error. But I also checked using 2 threads and have come across another problem: ``` 13:26:03 -...

> @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...

> 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...

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