Folding Forum

and what client you recomend to run on these machine

laptop

athlon x2 2.2 ghz ( or.3)
nvidia 6150 (64 mb)
vista 64 premium
4gb ddr 2 667


computer

athlon 64 3000+ 2.0 ghz
2 gb of ram ddr400
ti 4600 agp nvidia ( or run fx5200 agp, x300 pcie or firegl x3300pcie ?)

Going to EXTREMLY over clock them. Maybe that 3.4 ghz pentium 4 as well in other machine

kliddo wrote:It wasn't the graphic card. Could've been driver but i may never find it..

I think it's a bug in gpu client. I ran the command line gpu client and the system try gpu client. Both were running fine for few seconds but my fahmon did not update so i clicked "display" system tray gpu client. My mouse pointer was only monving and every thing else was hung and then, a restart. Later i tried just the system tray client only and clicked "display" and it hunged again whih resulted in a restart. I don't know if it's only me or with all the clients but it happened to me.

I know that "jrweiss" already told you that the viewer in the GPU systray client is known to be buggy but I want to re-emphasize that fact. The GPU clients work fine except for one part - - the viewer which is activated when you click "display" There have been a variety of crashes reported and some fixes incorporated but I still recommend you avoid the "display" function unless you've tried it enough times to know that you can safely activate it on your system without crashing.

FahMon is a third-party tool and is totally independent of the client. If you want it to update before the next timer-scheduled refresh, you can press F6.

kliddo wrote:and what client you recomend to run on these machine

laptop
athlon x2 2.2 ghz ( or.3)
nvidia 6150 (64 mb)
vista 64 premium
4gb ddr 2 667

computer
athlon 64 3000+ 2.0 ghz
2 gb of ram ddr400
ti 4600 agp nvidia ( or run fx5200 agp, x300 pcie or firegl x3300pcie ?)

Going to EXTREMLY over clock them. Maybe that 3.4 ghz pentium 4 as well in other machine

The Athlon x2 MIGHT successfully run the SMP client. However, you may find it doesn't do as well as 2xCPU clients.

While it's great to be exuberent about the Project, you don't do the Project any more good by trying to run configurations that are not recommended or supported. AT BEST you slow down the return of the WUs you download...

The A64 will only run the CPU client.

Be careful with overclocking. A computer that otherwise appears stable may fail when stressed by F@H -- even if temps stay within limits. Come to think of it, that may be part of your P4 problems...

that may be part of your P4 problems...]

My P4 was fine.. And sorry, that was turion x2/

EDIT: Now i'm getting 750 PPD from 200PPD just on cpu system tray client. GPU2 is getting 3500 on avg. 40% cpu is idle. I guess, i will have to try different clients every time. Gonna take long time.. I think i would go back to 2 cpu and gpu as long as it doesn't effect this software thingy. My hardware is under warranty and i will make sure that (combining all) they all don't use 100% system usage, but seeing 40%+ going into waste, i think i should run another client. Here is the average PPD

2 cpu 1 gpu

3300 for gpu
350 for cpu
200 for cpu
=3850

3500 for gpu
750 for cpu
=4250

GPU
=3600(maybe 3900?)

And is there any difference between smp michi and deino client?

One more thing, i have to different ID for folding. Is it possible to combine them? Or will it be possible sometime soon?

No.

Thanks JS for all your help. I still encountered several restarts, but i wasn't sure if it was because of folding or something else; i just installed vista and things working fine so far

jrweiss wrote:Several people have reported problems with the GPU Systray client causing problems with another client running alongside. Changing to the console client seems to resolve those problems. If you are running XP, running both the GPU console client and the CPU console client as Services works well and resolves most interference problems.

There always have been reports of problems when running multiple systray clients. I have never seen problems with multiple console clients as long as there is only one client per MachineID and queue.dat. One systray client seems to work with multiple console clients but I'm not really sure about that. (In v5, the rule was not more than one GUI client. The systray client seems to be a derivative of the GUI client.)