MeeLee wrote:I think this is incorrect.
Then we shall have to agree to differ
... but we may actually be agreeing more than differing to be honest - I am answering the thread question of 32 max threads on WIndows - which is a wholly FAHClient/FAHControl artefact and not a limit set by the OS or the FAHCore ... If it were OS then the extra cores would simply not be visible in the OS ... If it were FAHCore then it wouldn't run with more than 32 (and it does).
"Windows Home should be able to handle up to 64 cores, and the pro version should also be able to handle 128 cores, enterprise 256 cores." is absolutely correct - and hence is why any limitation to 32 threads in a cpu slot is not a licensing issue !!
... Yes there are licensing limits for number of cores but these are not relevant to the FAHClient/FAHControl 32 thread limit on a windows cpu slot - if software is limited to fewer than the number of cores available to the OS then it is the software itself that is limiting that use.
https://en.wikipedia.org/wiki/Windows_1 ... ison_chart
Home does 64 others 128 or more ... and having run FAHCore with more than 32 threads from command line on Enterprise and Pro I know for a fact that the it works and that the issue is not a FAHCore or OS issue that is limiting the usage of CPU Slot threads under windows to 32
... As to windows Home I have seen no evidence to make me think that the wiki page is incorrect - especially as I recall this changing many years back and there being press releases from MS about past limitations being removed.
The issue appears most likely down to the FAHClient being 32bit and using a call that only recognises up to 32 threads (as shown by calxalot earlier in this thread https://foldingforum.org/viewtopic.php? ... 36#p355011
) when auto generating cpu slots and the coding in the FAHClient/FAHControl having a hard limit at 32 that cannot be overridden in settings ... Home can do 64 threads but FAHClient/FAHControl won't let those settings be made ... So I repeat my assertion that this is not a licensing issue nor is it an operating system issue.
However - as I said at the start - and hey we beg to differ
Oh yes just to go back to original solution posted of subscribing to Windows Enterprise - THIS DOES NOT WORK - I run various systems including Win Enterprise Systems and FAHClient/FAHControl still limits cpu slots to a maximum on 32 threads on these ... hence my previous "This is Incorrect" post ... Windows Enterprise IS NOT a solution for this issue and tbh your original posted core limit of windows enterprise was a tad out too
>>> If anyone reads this thread and who might be looking to run cpu slots greater than 32 threads on windows please not a this time take out a windows enterprise subscription as contrary to statements that may indicate that this will then allow you to run slots greater than 32 threads this will not work at this time as it is not a licensing issue <<<