FAH problem

[LOUISSSSS]

i'm trying to run FAH on my comp CPU and x1900xt. when i open Foling@home 5.03 and the latest downloaded x1900xt gpu client, it seems like i am only running one of them. i get that little red symbol in my taskbar even when i open up winFah-ATI-beta2 then when i try to open up my usual folding at home 5.03 it says there is arleady anotehr F@H running and only 1 copy may run at a time. time copy will now quit. how can i get both my cpu and gpu to to work?

 

[Rattledagger]

Well, not having a compatible GPU (nor OS), just a couple general folding-tips...

Make sure installed to different directories.
Make sure configured with different machineid.
Atleast one of the instances should use the -local switch then starting.
Also, you can't run 2 gui-clients, one of them must be cli. Would guess this is also true then it comes to the gpu-client...

 

[GLeeM]

I would guess that both clients have the same MachineID. You should be able to change the GUIs' to "2" by entering config again. If you need help with that just let me know. 🙂

 

[LOUISSSSS]

i think the problem is the machine ID, how do i change that?

 

[GLeeM]

"i think the problem is the machine ID, how do i change that?"

Oh wait! Is there a GUI GPU client? Probably you can only run one GUI type client. I wish someone that knows about the GPU client would help you out.

I haven't run the GPU client, but I think it is similar to the CPU Console client.

F@H clients must be in their own separate directories.
If running, stop the GPU client.
Right click the GPU client exe and select Create Shortcut.
Right click the new shortcut and select Properties.
In the Target textbox, at the end of what is in there, add a space, a dash, and "configonly" without the quotes (do the same for "local"). This is what mine looks like for the cpu client:

C:\FAH2\FAH5.04b.exe -local -configonly

You can also rename the shortcut from the General tab.

During config, you probably have to answer "Yes" to "Enter Advanced Options" to get to the Change MachineID question.

When you run this shortcut it will enter config and quit when done. If you want the client to run after config just start it like you normally do.

If you want the client to start immediately after config use the "config" flag instead of "configonly".

PS: Possibly, the start up shortcut for the GPU needs to have the "local" flag. This is how my start up shortcut Target textbox looks:

C:\FAH2\FAH5.04b.exe -local -forceasm -verbosity 9

If you have a known F@H stable computer I recommend using the -forceasm flag, it will force the client to use optimizations on restart if your computer crashes or loses power. The -verbosity 9 flag shows more information in the FAHlog.txt file - good for trouble shooting.

If you have any questions or this doesn't work for you, please don't hesitate to ask 🙂