Just downloaded that new 64bit executable, the problem that you described was exactly what I was thinking, which is why I tried the not-working 64bit one first, hehe. Well, I'll try this now and report back!
Edit: You're right on spot with that correction:
Code: Select all
Auto detecting CPU configuration. Please wait.
14.11.2008 21:04:41: Found 4 CPUs:
CPU0 has mask 0000000000000001
CPU1 has mask 0000000000000002
CPU2 has mask 0000000000000004
CPU3 has mask 0000000000000008
14.11.2008 21:04:41: Found 2 PAIRs:
PAIR0<CPU0,CPU1> has mask 0000000000000003
PAIR1<CPU2,CPU3> has mask 000000000000000C
14.11.2008 21:04:41: C:\Users\root\FAH-GPU2\FahCore_11.exe with PID 3512, set affinity to CPU3
14.11.2008 21:04:41: C:\Users\root\FAH-GPU2\FahCore_11.exe with PID 3512, set priority to High.
14.11.2008 21:04:41: C:\Users\root\FAH-GPU\FahCore_11.exe with PID 3480, set affinity to CPU1
14.11.2008 21:04:41: C:\Users\root\FAH-GPU\FahCore_11.exe with PID 3480, set priority to High.
14.11.2008 21:05:29: C:\Users\root\FAH-GPU2\FahCore_11.exe with PID 3512, set affinity to CPU3
14.11.2008 21:05:29: C:\Users\root\FAH-GPU2\FahCore_11.exe with PID 3512, set priority to High.
14.11.2008 21:05:29: C:\Users\root\FAH-GPU\FahCore_11.exe with PID 3480, set affinity to CPU1
14.11.2008 21:05:29: C:\Users\root\FAH-GPU\FahCore_11.exe with PID 3480, set priority to High.
14.11.2008 21:05:29: C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe with PID 2812, set affinity to CPU0+CPU1
14.11.2008 21:05:29: C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe with PID 2812, set priority to Idle.
14.11.2008 21:05:29: C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe with PID 2312, set affinity to CPU2+CPU3
14.11.2008 21:05:29: C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe with PID 2312, set priority to Idle.
Thanks alot! Care to explain what the problem was?