How To Install Folding@Home Version 7 Beta Client

Add Your Comments

Howdy and welcome to another Overclockers.com How-To guide. This time its on the new Version 7 Beta FAH client. With this version you will be able to consolidate all your clients into one central client.

List of links:

Yes you might feel like this is a lot of info to take in but what you have to remember is that this is a breeze to setup. Here I have laid out for you a step by step install guide (All pictures courtesy of FAH website).

  1. Install it using the custom install option.
    Folding At Home ver. 7beta install process #1

    Folding At Home ver. 7beta install process #1

    2. At this point pick the users that will be using F@H

    Folding At Home ver. 7beta install process #2

    Folding At Home ver. 7beta install process #2

    3.  FAH will ask you about 2 install paths first is the client install path and next is the  FAH control install path.

    Folding At Home ver. 7beta install process #4

    Folding At Home ver. 7beta install process #3

    Folding At Home ver. 7beta install process #4

    4.  Set as service if you really want to. However I use manual control of all of my FAH clients.
    ATTN: Please note the following Service Mode is not available to GPU clients in Windows Vista and Windows 7.

    Folding At Home ver. 7beta install process #5

    Folding At Home ver. 7beta install process #5

     

    5.  FAH will ask you for your info and yes a passkey is needed.

    Folding At Home ver. 7beta install process #6

    Folding At Home ver. 7beta install process #6

    6. Now that the install is done we will look at how to setup this new client.

ATTN:  Please note the following during setup of client; save on every tab or the info on that tab will not be saved.

Step by Step Setup of client:

  1. Open the program and you’ll see your loopback address (127.0.0.1) grayed out.

    Folding At Home ver. 7beta install process #7

    Folding At Home ver. 7beta install process #7

  2. Switch to Expert view Located in the top right corner.
  3. Click configure in upper left hand corner.
  4. Then press the start button on first tab in the local console.

    Folding At Home ver. 7beta install process #8

    Folding At Home ver. 7beta install process #8

  5. After that you will need to click the slots tab and add the needed items, CPU and GPU clients.
    Folding At Home ver. 7beta install process #9

    Folding At Home ver. 7beta install process #9

    Folding At Home ver. 7beta install process #10

    Folding At Home ver. 7beta install process #10

  6. Setup items on advanced tab: CPU usage to 100%, I like to use checkpointing every 30 mins (Saves on writes to your hard drive), Verbosity should be set to 5 (as 5 is now the highest form of verbosity).
  7. Stop the client. Just like you started it in step #4, using the Stop button.
  8. Open the install folder and open your config.xml in notepad, Edit your config to look like mine and then save it then delete WUs which are located in the work folder which is inside of your FAHclient folder. Please do not change info in FOLDING SLOT as it is different on each computer.

Below is a copy of my config file I’m posting it for reference pay close attention to the bold areas:

<config>
<!– FahCore Control –>
<checkpoint v=’30’/>

<!– Folding Slot Configuration –>
<client-type v=’advanced’/>
<extra-core-args v=’-forceasm’/>
<max-packet-size v=’big’/>

<!– Logging –>
<verbosity v=’5’/>

<!– Network –>
<proxy v=’:8080’/>

<!– User Information –>
<passkey v=’enter your passkey here’/>
<team v=’32’/>
<user v=’The_Penguin’/>

<!– Work Unit Control –>
<next-unit-percentage v=’98’/>
<!– Folding Slots –>
<slot id=’0′ type=’SMP’/>
<slot id=’1′ type=’GPU’/>
</config>

Restart the client. Just like step #4 using the start button.

If you didn’t install as a service: To start the client each time you’ll need to open FAH control click on your client, hit config and start client just like you did to setup the client.

 

After following this procedure you should now have all your clients in this one central version. Don’t forget to monitor your PPD using our in house monitoring application, HFM.net created by Harlam357 (testing with this client version now..please go to his thread (HERE) to support the effort). If you have any questions about FAH, please visit the Overclockers.com Team32 Folding section with its helpful and very knowledgeable members who are dedicated to this great cause.  This concludes my guide on installing F@H ver7 Beta.

Note: At the time of this publication, HFM does not support the ver7 beta client to my knowledge.

~ AmbientFiction

Leave a Reply

Your email address will not be published. Required fields are marked *

Discussion
  1. Ambient,

    Thanks for the nice article! :attn:

    dfonda
    Is there an ETA on an expiration for the old clients? The Beta's used to run out, but that hasn't been the case lately. Sticking with the old clients until forced off...or until Harlam can do his magic with HFM.

    Thanks for the write up AF


    I hope that the v.6 clients will continue to be available, well into the future.
    Is there an ETA on an expiration for the old clients? The Beta's used to run out, but that hasn't been the case lately. Sticking with the old clients until forced off...or until Harlam can do his magic with HFM.

    Thanks for the write up AF
    Thanks to AF for the nice guide.

    A few comments:

    As AF notes, you can't yet monitor v7 with HFM. Harlam is working on it, but still has a ways to go. The v7 client will not yet correctly calculate ppd. If you have several machines to monitor, you don't want v7 yet.

    For the normal smp client on a connection faster than dial up, you will lose ppd if you set the download % to anything less than 100%. It doesn't matter on the gpu client.

    If you intend to run -bigadv WUs, do not set the -advmethods.

    -forceasm does nothing on the gpu and smp fah cores. They are hard coded to use optimizations and in fact will not run at all without them. -forceasm does work on some of the uniprocessor cores.

    Verbosity should be set to 3 not 5. At 5 it fills the log with fairly useless client debugging information that is of no use in diagnosing folding problems. It wouldn't be such an issue, except the log from each local fah core is displayed combined. If you have 2 gpus and a smp instance all written to the same log with debugging information, it becomes indecipherable.