Go to where ever you saved the text-only console executable and run it. You will be presented with a series of questions - answering them will set up the Folding@Home application.

+

Go to where ever you saved the text-only console executable and run it. If this is the first time you've run Folding@Home, you will be presented with a series of questions - answering them will set up the Folding@Home application.

Line 29:

Line 29:

'''Interval, in minutes, between checkpoints''': I like to set this to the minimum possible, 3 minutes. A checkpoint is when the work that is performed by Folding@Home is saved ... setting it to a lower timeframe will allow you to exit Folding@Home (manually, or through a system reboot) without losing too much of your work (only 3 minutes worth at most)

'''Interval, in minutes, between checkpoints''': I like to set this to the minimum possible, 3 minutes. A checkpoint is when the work that is performed by Folding@Home is saved ... setting it to a lower timeframe will allow you to exit Folding@Home (manually, or through a system reboot) without losing too much of your work (only 3 minutes worth at most)

+

+

'''Machine ID''': You can set up to 8 different machine IDs, allowing you to run multiple instances of Folding@Home on your computer (one instance for each CPU/core/HyperThread). As mentioned before, if you do run multiple instances, the executables must be in different folders.

----

----

=== Step 3 ===

=== Step 3 ===

+

Folding@Home will start processing after you have finished the configuration, or if this was not the first time you have run Folding@Home. You can quit Folding@Home by pressing "CTRL-C" to close the Folding@Home command line window.

+

+

You can create a shortcut to the Folding@Home executable, and place it in your Start Menu's "Startup" folder to make Folding@Home launch automatically on start up, if you wish.

+

+

And if you need to access the configuration again, click on the "Start" button, select "Run" and type in '''"C:\Program Files\Folding@Home\console1\FAH504-Console.exe" - config''' (change the path/filename to where you saved the text-only console executable, and don't forget the quotes around the path). There are some other [http://folding.stanford.edu/console-userguide.html text-console commands] that can be used in this way too.

+

+

[[Category:Site/Forum Help]]

Revision as of 07:59, 21 August 2007

This short guide shows you how to install the text-only console version of Folding@Home, and to set it up so you can join the Grim Rippers folding team.

Step 1

Go to the official Folding@Home download page and download the Windows NT/2000/XP/Vista "No nonsense" text-only console. Save the file to an empty folder on your computer (I like to create a folder in "C:\Program Files\Folding@Home\console1\" - I use "console1" because it is possible to run 2 different instances of the text-only console if you run them in different folder - useful for HyperThreading CPUs).

Step 2

Go to where ever you saved the text-only console executable and run it. If this is the first time you've run Folding@Home, you will be presented with a series of questions - answering them will set up the Folding@Home application.

You can pretty much follow the answers I've typed in above, just change your username. However, if you want an explanation of some of the more important options, look below:

Username: Choose an username to use on the Folding@Home network, or leave it blank to be anonymous

Team Number: Type in 51205 to join the DVF Grim Ripper team

Launch automatically at machine startup, installing this as a service: I chose "No", because a service is harder to shut down without losing work

Core Priority: This setting allows you to specify the running priority of Folding@Home. The default "idle" is recommended, as this will set Folding@Home to only run when other programs (who will have a "normal" priority) are not running. You can use the "low" option if you have other similar applications running already

CPU usage requested: If you never want Folding@Home to use more than X% of your CPU, you can set it here (anything less than 100% is not recommended, as you might waste precious CPU cycles ... if you don't want Folding@Home to interfere with other programs, use the "idle" priority setting above

Interval, in minutes, between checkpoints: I like to set this to the minimum possible, 3 minutes. A checkpoint is when the work that is performed by Folding@Home is saved ... setting it to a lower timeframe will allow you to exit Folding@Home (manually, or through a system reboot) without losing too much of your work (only 3 minutes worth at most)

Machine ID: You can set up to 8 different machine IDs, allowing you to run multiple instances of Folding@Home on your computer (one instance for each CPU/core/HyperThread). As mentioned before, if you do run multiple instances, the executables must be in different folders.

Step 3

Folding@Home will start processing after you have finished the configuration, or if this was not the first time you have run Folding@Home. You can quit Folding@Home by pressing "CTRL-C" to close the Folding@Home command line window.

You can create a shortcut to the Folding@Home executable, and place it in your Start Menu's "Startup" folder to make Folding@Home launch automatically on start up, if you wish.

And if you need to access the configuration again, click on the "Start" button, select "Run" and type in "C:\Program Files\Folding@Home\console1\FAH504-Console.exe" - config (change the path/filename to where you saved the text-only console executable, and don't forget the quotes around the path). There are some other text-console commands that can be used in this way too.