Detecting 0 processing cores

Hi,

I have several computers that I have tried this on. Core detection has only worked on Core 2 Duo machines and not for quad-core processors (either Q9550 or i7 860 on ASUS and MSI motherboards, respectively). Resultantly, I am only able to fold using the single-core client, not the SMP client. Do you have any idea how to adjust this?

[21:39:18] --------------------------------------------------
[21:39:18] FAH GPU Tracker v3.33 Startup
[21:39:18] --------------------------------------------------
[21:39:18] Detected OS: Windows XP
[21:39:21] User cancelled FAH client download
[21:39:21] To download the clients later you can click
[21:39:21] Setup -> Download FAH Clients
[21:39:24] Detected CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
[21:39:24] 0 Cores, 0 Threads, 2,399 MHz
[21:39:44] Downloading updated projects list...
[21:39:44] Download projects attempt failed
[21:40:28] Creating client folders...
[21:40:28] Downloading FAH clients...
[21:40:49] Extracting clients...
[21:40:49] Clients extracted successfully
[21:40:49] Setting up clients...
[21:40:55] Client setup completed successfully
[21:40:55] Setting up client configs...
[21:40:55] Setting up GPU0 client config
[21:40:56] Setting up GPU1 client config
[21:40:56] Setting up GPU2 client config
[21:40:56] Setting up GPU3 client config
[21:40:56] Setting up GPU4 client config
[21:40:57] Setting up GPU5 client config
[21:40:57] Setting up GPU6 client config
[21:40:57] Setting up GPU7 client config
[21:40:57] Setting up CPU client config
[21:40:58] Setting up SMP client config
[21:40:58] Client configs generated successfully
[21:40:58] Cleaning up client folders...
[21:40:58] Initial setup complete

What are the specs and os's of these computers. Its more the os I am wondering because we have had someone with a bug for start and stop of clients on xp. Im wondering if the program just doesn't like xp. Ill see what jedi says in relation to this.

I don't know why exactly the CPU detection isn't working for you but there is a workaround. Just add the -nocpudetect flag to the Tracker and you won't have a problem.

Thanks I will try the flag. Do I add it to a shortcut for the tracker? If so, "target" or "start in" sections?

6 boxes I've tried this on.

Q6600 at 2.4
4GB RAM
9800GT EE
XP 32 bit
--Would not detect the cores, loads single CPU core.

Q8200 at 2.8
4GB RAM
9600GT
XP 32 bit
--Would not detect the cores, loads single CPU core.

Q9550 at 2.83
4GB RAM
2 x GTX 450
XP 32 bit
--Would not detect the cores, loads single CPU core.

i7 860 at 2.8
4GB RAM
2 x GTX 260
XP 32 bit
--Would not detect the cores, loads single CPU core.

2 x Xeon 4 core
4 GB RAM
XP 32 bit
--Recognizes 8 cores, loads SMP client without difficulty.

E8200 at 2.66
2 GB RAM
XP 32 bit
--Recognizes 2 cores, loads SMP client no problem.

T7200 at 2.0
1 GB RAM
XP 32 bit
--Recognizes 2 cores, loads SMP client no problem.

T7500 at 2.2
2 GB RAM
XP 32 bit
--Recognizes 2 cores, loads SMP client no problem.


Thanks for your help and advice.
--KK

Looks like it is working with the -nocpudetect flag on the Q9650 rig above. I'll use this with the other boxes and report back if there is a problem starting up CPU folding on them.

Thanks very much for this program and for the suggestion.

i have this same issue as well it be very usefull if you could just give an warning that its not detected cpu cores and default to -nocpudetect on its own insted of having to do this as it would be the expected action (i guess the norm .net niggle things not working correctly this mite be related to dif versions of .net framework so you may have to test it with every version 3.5, 3.5 sp1 and 4.0 on xp, win7 (ignore vista) and there x64 and x86 versions )

other niggle as well at no point do you state you need .net 3.5 framework in the read me file as to why you get questons relateing to the very unuseful crash on trying to start the tracker (as XP tends to be the best OS to use CPU and GPU folding, it does not come with .net framework)

i am running 2003 x64 server (basicly XP 64x is also same build as this with bits turned on) i think it has .net 4.0 installed get back to the system later on

my xp 32 system worked fine but that was an fresh install of with .net 3.5

if you have an debug version i can run it for you if you wish as i guess it throws some kind of hidden error

leexgx wrote:i have this same issue as well it be very usefull if you could just give an warning that its not detected cpu cores and default to -nocpudetect on its own insted of having to do this as it would be the expected action (i guess the norm .net niggle things not working correctly this mite be related to dif versions of .net framework so you may have to test it with every version 3.5, 3.5 sp1 and 4.0 on xp, win7 (ignore vista) and there x64 and x86 versions )

other niggle as well at no point do you state you need .net 3.5 framework in the read me file as to why you get questons relateing to the very unuseful crash on trying to start the tracker (as XP tends to be the best OS to use CPU and GPU folding, it does not come with .net framework)

i am running 2003 x64 server (basicly XP 64x is also same build as this with bits turned on) i think it has .net 4.0 installed get back to the system later on

my xp 32 system worked fine but that was an fresh install of with .net 3.5

if you have an debug version i can run it for you if you wish as i guess it throws some kind of hidden error

CPU Detection under Windows XP isn't very reliable. If you don't use -nocpudetect and it detects 0 cores the SMP client will be unlocked, but not selected by default. The only time you will need -nocpudetect is if you want to run -bigadv.

To be preciese you need sp2 for the wmi calls to work ( or was it sp3, think it was 2 ). For server 03 there is a hotpatch on ms servers which makes these wmi queries possible as well. If you want specific links I could look them up, should be on ff in on of the older posts.

Reminder to self: get back to doing something more usefull