Xilikon
12-15-2008, 07:50 PM
Folding@Home installation guides
Welcome to the R3 F@H installation guides page. You will find the guides you need to setup a Windows SMP (both MPICH and DEINO versions), linux SMP or Windows GPU, including a multi-GPU guide. This is 99% identical to the official guides which can be found on the Folding@Home official site at http://folding.stanford.edu/English/Guide.
If even after following the guides, you have questions or clarification to ask, make a new thread and we will be glad to help.
To reach the desired guide, just click on the index link :
The R3 F@H team ID is 156204
Note: I'm the author of the guides and I'm giving permission for this copy of the guides to be available here. Don't reproduce any or all parts of the guides without my express permission.
Windows uniprocessor (classic) client
There are two types of client available, which is a Systray version and a Console version. The advantage of the Systray version is that you have a icon on the task bar that you can use to control the client. The Console version use the command prompt to run but the main advantage is that version can be configured as a service, thus concealing the client entirely from the user.
Note: Under Windows, antivirus software can interfere with the Folding@Home client files and cause errors. We suggest that you configure the antivirus software to exclude the F@H client directory and especially the work directory inside of it from the antivirus scanning list. This can be done by going into the exclusion list panel that every antivirus should have. The work subdirectory contains semi-random binary data and can confuse overly aggressive heuristic virus scanning.
Installation (Systray version)
Note: The viewer included with the Systray client is not working properly and it's a known bug. The Pande Group is aware of the issue and is working to fix it. In the meanwhile, don't use it (it's not required to open the viewer to make the client run, having the Systray icon on the taskbar is enough).
You can download the Systray client installer from the Download (http://folding.stanford.edu/English/Download) page. After it has downloaded, run the installer package by double clicking the downloaded file (If it doesn't start automatically, it probably means you need to install the Windows Installer 3.1 package first, which you can get through Windows automatic update). You will see this window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray1.png
Click on the Next button to continue to the License agreement window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray2.png
If you accept the license, click on the I Agree button then click on the Next button. There is no configuration to edit :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray3.png
Click on the Next button to start the installation process. When it's done, you will see the last window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray4.png
Click on the Close button to end the installation process.
During the installation process, the installer will have created a new folder in the Start menu. You can find it under Start -> Programs -> Folding@Home-x86 as indicated here :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray5.png
There are two shortcuts, the first is to run the program whenever you want and the second is to go in the data folder where the client is storing the work unit's data, configuration and executable files for any maintenance need. For now, we need to configure it so click on the first one (Folding@Home). As you are running the client for the first time, a configuration window will appear :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray6.png
In this panel, if you want to fold under your own username, enter it here along with the team number if you are part of the team. If all you want is to contribute while not caring about a username or team, leave them as is. If you have a passkey associated to your username, enter it (if you want to know what is a passkey and how to obtain one, check this page (http://folding.stanford.edu/English/FAQ-passkey)). When you are done, click on the Connection tab on the top to get to the next panel :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray7.png
The first checkbox should be checked if you want the client to ask before downloading or uploading a work unit. This is useful if you are on a non-permanent connection like dialup or to control when to download/upload. If you are connected behind a proxy, you'll need to configure the client for it (if you need the information about configuring a proxy, ask your administrator). The last checkbox will let you decide if you would like to receive large work units (they have bigger bandwidth and memory requirements). After doing this, click on the Advanced tab to get to the next panel :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray8.png
These are the advanced configuration of the client so if you are unsure about them, you can leave them alone since the defaults are suitable for the majority of users. Here is what each element does :
Core priority : If you are running multiple clients or have another program running continuously in the background, you may need to adjust the priority so it won't sit idle while waiting for free cycles.
CPU Usage Percent : If you don't want the CPU to allocate all the cycles to F@H, adjust the percentage to suit your needs.
Disable highly optimized assembly code : If you are having problems running the client due to a processor incompatibility or any weird error, check this to disable the SSE optimizations. Doing this will cause the client to run slower depending on the workunit.
Checkpointing frequency : Increase or decrease the frequency of Work Unit progress backups. This won't prevent the client from writing the data before the checkpoint if the next frame is completed before.
Do NOT lock cores to specific CPU : If you have more than one core, checking this will allow the client to use any free CPU/core. If it is left unchecked, it will only use one core no matter if others is free or not.
Core Network Address (Advanced) : For future use
Pause work while battery power is being used : This is useful for laptops to stop the client from running when it's on battery power, to avoid draining power.
Additional Client Parameters : This is where you can save the frequently used flags like -verbosity 9 or -advmethods.
Machine ID : This is the client ID and it needs to be different if you are running more than one client under the same OS. An example would be if you are running the Systray client and the GPU2 client at the same time, in which case each client will use Machine ID 1 and 2 respectively.
When you are done, click on Ok. If you entered any Additional Client Parameters during configuration, you may need to restart the client to use them. It will now run in the background with a icon in the Taskbar. You can hover on it to check the current client status but if you want to see what is the last actions of the client, you can check the log file generated by the client. For that, right-click on the taskbar icon and you will see this :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray9.png
Click on Status then on Log file to open a notepad window with the log file contents. This is useful to see if there are errors and if you need help, you can copy the contents of this log file to the forum.
Windows SMP client installation (MPICH version)
Note: Due to the way the Windows SMP client is setup, it's a complicated process to install it properly. For this reason, it's essential to read the whole guide first before attempting the installation. There is a lot of things to be careful like the -smp flag requirement or it won't work properly.
In addition to the instructions below, we also suggest you check out instructions on the FAH wiki (http://fahwiki.net/index.php/How_do_I_install_the_SMP_Console_client_in_Windows _Vista).
Requirements for installation
Before you start the installation process of the SMP console client, there are a few requirements you must check to make sure the client will work correctly :
You have a computer with at least a recent dual core or better to run the SMP client. This means than the older single core processors won't be able to run it. Since it's a high performance client, if you notice that after installation, it doesn't always meet the deadlines, please use the uniprocessor client instead.
If you are installing this under Windows XP, you are required to install the Microsoft .NET framework v2.0. You can download the package from Microsoft (http://www.microsoft.com/downloads/details.aspx?familyid=0856eacb-4362-4b0d-8edd-aab15c5e04f5&displaylang=en). Windows Vista already includes the necessary package by default so it's not necessary to do it if you install the client under Vista.
The Windows user account you are using to install the client must have a password and have enough administrator rights. Blank passwords will not work and you must have a password only with those valid characters : A-Z, a-z and 0-9. Special characters should not be used to avoid any potential issues. If you change the password of the Windows user account, you need to rerun install.bat. The password being used to install is encrypted in the registry and not transmitted to the Stanford servers.
Installation
Note: Under Windows, antivirus software can interfere with the Folding@Home client files and cause errors. We suggest that you configure the antivirus software to exclude the F@H client directory and especially the work directory inside of it from the antivirus scanning list. This can be done by going into the exclusion list panel that every antivirus should have. The work subdirectory contains semi-random binary data and can confuse overly aggressive heuristic virus scanning.
First, create a new folder on C:\Users\\ or on the root of C:\ (what matters here is to not put it in C:\Program Files\ to avoid issues with permissions, especially under Vista) with a simple name without spaces or special characters. A good suggestion is to name it FAH. The reason for this suggestion is because Vista has some strict restrictions when a program is run from the Program Files folder. Doing this will avoid lots of issues.
Go to the High performance Windows clients (http://folding.stanford.edu/English/DownloadWinOther) download page. There will be a DEINO or MPICH package available for download. Pick the MPICH version in this case.
After you downloaded it, you will see a executable installer package so run it. You will be presented with this window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPInst1.png
Click on Next to bring the next window, which is a Readme with the client notes. Click on Next again to bring the following window:
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPInst2.png
It's up to you to pick which option. I recommend picking the first option for All Users to make things simpler but if you don't want others users to see this, leave the default option as is. After this, click on Next to bring the next window:
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPInst3.png
If you followed the recommendation to make a new folder, pick this one by clicking on the Browse button to get the following window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPInst4.png
After you picked the desired folder where you will install the client, click on Ok then on Next on the previous window. At this point, the installer knows everything required to proceed with the installation so click on Next to run it. When it's done, click on Finish to close the installer.
With Windows Explorer, browse to the folder you just installed the client and you will see a bunch of files like this :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPInst5.png
To make the following steps easier to do, it's suggested to rename the executable to something easy to remember and to type like fah6.exe (right-click on the executable file, select Rename and change to a new name).
[U]MPICH Configuration
Open the Command Prompt window by clicking on the Start menu then type cmd.exe on the Run box and click on Ok. If you are under Vista, you must run it with the Run as administrator option or you will not have sufficient rights to complete the following steps (to get this, right-click on Command Prompt icon then select Run as administrator). With Windows XP, it's sufficient to run cmd.exe as is.
Here is what it should look under Vista (typed cmd.exe then right-click on it) :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPRunAs.png
You can use CD to change the directory and type D:\ (or any other letter) to change the drive if the client is not installed on C:\ by default. With those commands, move to the folder you created earlier (C:\FAH in our example). When you are here, type install.bat and you will see a message like this :
MPICH2 Process Manager, Argonne National Lab installed.
account (domain\user) [FAH\Username]:Note: When you execute install.bat, you may get a firewall popup asking to allow or block twice, once for mpiexec.exe and once for smpd.exe. You should make sure both are allowed or the program won't work.
If the domain and user account is correct, just click on Enter but if you want to use a different account, enter the proper information (If you are on Active Directory, enter the Domain name but if it's not the case, it's the computer name you need to enter). After you press enter, you will see a password prompt :
password:Enter the Windows user password (you will see nothing on screen but type away). It will ask for a confirmation so enter the password again. If you did this correctly, you will see the following messages :
password:
confirm password:
Password encrypted into the Registry.
If you see this twice, MPI is working
If you see this twice, MPI is working
Press a key to continue...The important thing is to see that the If you see this twice, MPI is working is displayed twice. If you don't see this or you see a different error, check why and fix this before retrying. When MPICH is working correctly, it's time to configure the client below.
Client configuration
The next step is to configure it by typing the following command (if you used a different one, use the correct name) :
fah6 -configonlyYou will see a list of configuration options. Here is an sample with an explanation about each option :
Launch directory: C:\FAH
Executable: fah6
Arguments: -configonly
[16:25:22] Configuring Folding@Home...
User name [Anonymous]?
Team Number [0]?
Passkey []?Enter your user name (not the Windows user name but your folding name), team number and passkey here
Ask before fetching/sending work (no/yes) [no]?If you are not on a permanent connection, select this to yes to wait for your permission to upload/download work units. Because of the short deadlines on SMP work assignments, persistent connections are strongly recommended so this option should not be set to yes.
Use proxy (yes/no) [no]?If you are connected to a proxy, enter yes and configure the proxy options.
Acceptable size of work assignment and work result packets (bigger units
may have large memory demands) -- 'small' is <5MB, 'normal' is <10MB, and
'big' is >10MB (small/normal/big) [normal]?This is related to the size of downloaded and uploaded work units. Bigger units will also have bigger memory requirement. If you run on a slow broadband or dialup internet connection, it's suggested to pick small to ease the bandwidth usage. However, all SMP WUs are big, so setting it to small or normal will often lead to long periods where no assignments are available.
Change advanced options (yes/no) [no]? yesIf you want to change the advanced options, enter yes but it's not mandatory.
Launch automatically, install as a service in this directory (yes/no) [no]?You can install the client as a service but currently, it's not recommended. If you still insist to do this, there are special steps to do after installing the service but before running it for the first time. See below for detailed instructions.
Core Priority (idle/low) [idle]?This adjusts the priority level. Any priority higher than idle can cause some slowdown during general computer usage.
CPU usage requested (5-100) [100]?This will adjust the percentage of CPU usage. If you want to limit temperature issue or to keep some CPU cycles for more intensive computer tasks, enter a number below 100.
Disable highly optimized assembly code (no/yes) [no]?If you are having issues running the client, disable this. For 99% of the users, leave this alone since this could reduce the client performance a lot.
Pause if battery power is being used (useful for laptops) (no/yes) [no]?If you run a laptop, set this to yes to pause if the laptop is not plugged on the wall. This will avoid the client draining the battery.
Interval, in minutes, between checkpoints (3-30) [15]?Number of minutes between each checkpoint where the client is writing the client progress on disk in case of unexpected interruption.
Memory, in MB, to indicate (1013 available) [1013]?Set the amount of memory available to the client. By default, it show the full memory amount but if you have programs which require lots of memory, it's suggested to reduce this.
Set -advmethods flag always, requesting new advanced scientific cores and/or work units if available (no/yes) [no]?This is the same as using the -advmethods flag. This will allow you to grab workunits with bigger requirements (often with more points value) than the normal units. Keep in mind this will often have a higher risk of failure so use this flag only if you are ready to accept the risks.
Ignore any deadline information (mainly useful if system clock frequently has errors) (no/yes) [no]?Set this to yes if your local computer clock is having issues keeping the correct date and time. For 99% of the users, leave this to no.
Machine ID (1-16) [1]?This is the ID of the client. If you are running more than one client under the same OS, you need to have a different machine ID for each client. If you are installing on multiple computers, you don't need to change this since this is only for installing multiple clients on the same computer.
The following options require you to restart the client before they take effect Disable CPU affinity lock (no/yes) [no]?Not useful for SMP since it use all cores.
Additional client parameters []?You can enter the client flags here so you don't have to type the flag each time. I strongly suggest you enter the -smp -verbosity 9 flag here to make things easier. Don't enter -config or -configonly or any single-use flag to avoid issues.
IP address to bind core to (for viewer) []?For future use
When you are done, the configuration will end and you will be back to the command prompt. You have successfully configured the client so the next step is to start the client. Here are 2 ways :
By clicking on the executable icon (this assumes you entered the proper flags during configuration).
By typing fah6 on the same command prompt window. Enter the necessary flags (including the mandatory -smp flag) if you didn't enter during configuration.
Normally, if everything is done correctly, it will be chugging fine. To check this, open the task manager and make sure there is 4 instances of FahCore_Ax.exe in the list.
Configuring the SMP client as a service
Warning: If you want to run the SMP client as a service, be aware this is currently unsupported by the developers. A bad configuration can cause the client to have issues and lose work units.
Note: The guide is validated with Windows Vista. A lot of people have a problem starting the service under XP so follow the steps at your own risks.
In addition to this guide, there is also a very detailed guide available on the Folding Forum (http://foldingforum.org/viewtopic.php?p=15051#p15051%27%20rel=nofollow) which is a bit outdated but still valid.
The first step is to start the client in configuration mode with the -configonly flag. When you are in the Advanced options section, find this entry :
Launch automatically, install as a service in this directory (yes/no) [no]?Enter yes to confirm the service installation. Continue (edit the options if needed) until you reach this line :
Additional client parameters []?Since the client will be running as a service, the additional flags must be entered here to make it work in SMP mode. In our case, enter -smp -verbosity 9 -d "C:\FAH" then finish the configuration. The essential piece is the -d "[client path]" where [client path] is the folder where you installed the client (don't forget the quotes). This tell Windows to use the specific path since by default, it will use C:\Windows\System32 as the working folder which cause the client to stop with a 1067 error.
At this stade, don't start the service yet because it must be edited to run with the proper parameters and permissions. For this, open the Services MMC by clicking on the start menu then type services.msc in the Run... box (XP) or the search field (Vista). When the Services console is started, find the newly added F@H service, which should be called Folding@Home-CPU-[1] :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPService1.png
If you didn't see, restart the client in configuration mode again and double-check that the service is being installed. Now, double-click on it and it will bring the Properties window. Click on the Log On tab to get this :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPService2.png
Select the This Account button then enter the same account you used to configure the MPICH client above. To make sure the account name is correct, it's suggested to click on the Browse button and find the account. Even if the password fields seems populated, delete them and enter the corresponding password.
When you are done, you can either start the service yourself (suggested) by clicking on the first tab then click on the Start button or by rebooting. Check if it is started correctly and if not, double-check the account details.
Windows SMP client installation (DEINO version)
Note: Due to the way the Windows SMP client is setup, it's a complicated process to install it properly. For this reason, it's essential to read the whole guide first before attempting the installation. There is a lot of things to be careful like the -smp flag requirement or it won't work properly.
In addition to the instructions below, we also suggest you check out instructions on the FAH wiki (http://fahwiki.net/index.php/How_do_I_install_the_SMP_Console_client_in_Windows _Vista).
Requirements for installation
Before you start the installation process of the SMP console client, there are a few requirements you must check to make sure the client will work correctly :
You have a computer with at least a recent dual core or better to run the SMP client. This means than the older single core processors won't be able to run it. Since it's a high performance client, if you notice that after installation, it doesn't always meet the deadlines, please use the uniprocessor client instead.
If you are installing this under Windows XP, you are required to install the Microsoft .NET framework v2.0. You can download the package from Microsoft (http://www.microsoft.com/downloads/details.aspx?familyid=0856eacb-4362-4b0d-8edd-aab15c5e04f5&displaylang=en). Windows Vista already includes the necessary package by default so it's not necessary to do it if you install the client under Vista.
The Windows user account you are using to install the client must have a password and have enough administrator rights. Blank passwords will not work and you must have a password only with those valid characters : A-Z, a-z and 0-9. Special characters should not be used to avoid any potential issues. If you change the password of the Windows user account, you need to rerun install.bat. The password being used to install is encrypted in the registry and not transmitted to the Stanford servers.
Installation
Note: Under Windows, antivirus software can interfere with the Folding@Home client files and cause errors. We suggest that you configure the antivirus software to exclude the F@H client directory and especially the work directory inside of it from the antivirus scanning list. This can be done by going into the exclusion list panel that every antivirus should have. The work subdirectory contains semi-random binary data and can confuse overly aggressive heuristic virus scanning.
Note: Under Windows, antivirus software can interfere with the Folding@Home client files and cause errors. We suggest that you configure the antivirus software to exclude the F@H client directory and especially the work directory inside of it from the antivirus scanning list. This can be done by going into the exclusion list panel that every antivirus should have. The work subdirectory contains semi-random binary data and can confuse overly aggressive heuristic virus scanning.
First, create a new folder on C:\Users\\ or on the root of C:\ (what matters here is to not put it in C:\Program Files\ to avoid issues with permissions, especially under Vista) with a simple name without spaces or special characters. A good suggestion is to name it FAH. The reason for this suggestion is because Vista has some strict restrictions when a program is run from the Program Files folder. Doing this will avoid lots of issues.
Go to the High performance Windows clients (http://folding.stanford.edu/English/DownloadWinOther) download page. There will be a DEINO or MPICH package available for download. For the current guide, download the DEINO package.
After you downloaded it, you will see a package in .zip format so you need to unpack it to the folder you created above. With Windows Explorer, browse to the folder you just unzipped the client and you will see a bunch of files like this :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPDeino1.png
To make the following steps easier to do, it's suggested to rename the executable to something easy to remember and to type like fah6.exe (right-click on the executable file, select Rename and change to a new name).
[U]DEINO Configuration
Open the Command Prompt window by clicking on the Start menu then type cmd.exe on the Run box and click on Ok. If you are under Vista, you must run it with the Run as administrator option or you will not have sufficient rights to complete the following steps (to get this, right-click on Command Prompt icon then select Run as administrator). With Windows XP, it's sufficient to run cmd.exe as is.
Here is what it should look under Vista (typed cmd.exe then right-click on it) :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPRunAs.png
You can use CD to change the directory and type D:\ (or any other letter) to change the drive if the client is not installed on C:\ by default. With those commands, move to the folder you created earlier (C:\FAH in our example). When you are here, type install.bat and you will get the installer messages (in a command prompt) like that :
C:\FAH>install.bat
C:\FAH>msiexec /i DeinoMPI.msiThis will start the installation of the DEINO MPI client. You will see a dialog box like this :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPDeino2.png
Just press Next to get the next window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPDeino3.png
Check to accept the license terms and click Next to enter the path :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPDeino4.png
Unless you want to install in a different place, you should leave the default path there and press Next. The next window will just confirm the options so press Next once more to install it. When it's done, press Finish to close it. The batch will then present you with the credentials store installation and configuration below.
C:\FAH>create_credential_store true
This program creates a Credential Store for the current user.
The credential store contains a public and private security key
and zero or more secure user credentials.
Deino MPI uses this store to establish secure connections between machines
and store sensitive information like user credentials.
Do you want to create a new store (yes, no)? [yes]Press enter since we want to create a new credentials store
Please enter a passphrase to protect the private key:Don't enter anything, just press enter since we don't want to use a passphrase.
Are you sure you want no password for the private key (yes,no)? [no]
yesType yes and press enter to confirm we don't want a passphrase.
Options for encrypting the private key:
protect - Use the ProtectedData.Protect/Unprotect methods to encrypt.
none - Do not encrypt.
Please enter a method to encrypt the private key: [protected]Just press enter since protect is what we wanted.
Available locations to create the store:
(1) Windows Registry
(2) Hard drive
Where would you like to create the store (1,2): [1]Press enter again since we want it to be stored in the registry. If you have a removable media plugged, the available locations list will be different (the removable media entry will be (1) so select (2) instead for the Windows Registry).
Credential store written to the Windows Registry.
C:\FAH>manage_credentials /add
Enter the account name: [COMPUTERNAME\Username]
Enter the account password:
************
Enter the password again to verify:
************Accept the account name by pressing enter and enter your Windows password twice here. If you need to use a different username (like a local windows account instead of a domain account), change the information first.
C:\FAH>net start deinopm
The DeinoMPI process manager service service is starting.
The DeinoMPI process manager service service was started successfully.
C:\FAH>mpiexec -np 2 foo
If you see this twice, MPI is working
If you see this twice, MPI is working
C:\FAH>When the line mpiexec -np 2 foo is executed, you may get a firewall popup asking you to allow or deny mpiexec.exe. Make sure you allow it or it won't run properly. When you are done, you should see the If you see this twice, MPI is working being displayed twice. If you don't see this or you see a different error, check why and fix this before retrying. If it is running correctly, continue with the client configuration below.
Client configuration
The next step is to configure it by typing the following command (if you used a different one, use the correct name) :
fah6 -configonlyYou will see a list of configuration options. Here is an sample with an explanation about each option :
Launch directory: C:\FAH
Executable: fah6
Arguments: -configonly
[16:25:22] Configuring Folding@Home...
User name [Anonymous]?
Team Number [33]?
Passkey []?Enter your user name (not the Windows user name but your folding name), team number and passkey here
Ask before fetching/sending work (no/yes) [no]?If you are not on a permanent connection, select this to yes to wait for your permission to upload/download work units. Because of the short deadlines on SMP work assignments, persistent connections are strongly recommended so this option should not be set to yes.
Use proxy (yes/no) [no]?If you are connected to a proxy, enter yes and configure the proxy options.
Acceptable size of work assignment and work result packets (bigger units
may have large memory demands) -- 'small' is <5MB, 'normal' is <10MB, and
'big' is >10MB (small/normal/big) [normal]?This is related to the size of downloaded and uploaded work units. Bigger units will also have bigger memory requirement. If you run on a slow broadband or dialup internet connection, it's suggested to pick small to ease the bandwidth usage. However, all SMP WUs are big, so setting it to small or normal will often lead to long periods where no assignments are available.
Change advanced options (yes/no) [no]? yesIf you want to change the advanced options, enter yes but it's not mandatory.
Launch automatically, install as a service in this directory (yes/no) [no]?You can install the client as a service but currently, it's not recommended. If you still insist to do this, there are special steps to do after installing the service but before running it for the first time. See below for detailed instructions.
Core Priority (idle/low) [idle]?This adjusts the priority level. Any priority higher than idle can cause some slowdown during general computer usage.
CPU usage requested (5-100) [100]?This will adjust the percentage of CPU usage. If you want to limit temperature issue or to keep some CPU cycles for more intensive computer tasks, enter a number below 100.
Disable highly optimized assembly code (no/yes) [no]?If you are having issues running the client, disable this. For 99% of the users, leave this alone since this could reduce the client performance a lot.
Pause if battery power is being used (useful for laptops) (no/yes) [no]?If you run a laptop, set this to yes to pause if the laptop is not plugged on the wall. This will avoid the client draining the battery.
Interval, in minutes, between checkpoints (3-30) [15]?Number of minutes between each checkpoint where the client is writing the client progress on disk in case of unexpected interruption.
Memory, in MB, to indicate (1013 available) [1013]?Set the amount of memory available to the client. By default, it show the full memory amount but if you have programs which require lots of memory, it's suggested to reduce this.
Set -advmethods flag always, requesting new advanced scientific cores and/or work units if available (no/yes) [no]?This is the same as using the -advmethods flag. This will allow you to grab workunits with bigger requirements (often with more points value) than the normal units. Keep in mind this will often have a higher risk of failure so use this flag only if you are ready to accept the risks.
Ignore any deadline information (mainly useful if system clock frequently has errors) (no/yes) [no]?Set this to yes if your local computer clock is having issues keeping the correct date and time. For 99% of the users, leave this to no.
Machine ID (1-16) [1]?This is the ID of the client. If you are running more than one client under the same OS, you need to have a different machine ID for each client. If you are installing on multiple computers, you don't need to change this since this is only for installing multiple clients on the same computer.
The following options require you to restart the client before they take effect Disable CPU affinity lock (no/yes) [no]?Not useful for SMP since it use all cores.
Additional client parameters []?You can enter the client flags here so you don't have to type the flag each time. I strongly suggest you enter the -smp -deino -verbosity 9 flag here to make things easier. Don't enter -config or -configonly or any single-use flag to avoid issues.
IP address to bind core to (for viewer) []?For future use
When you are done, the configuration will end and you will be back to the command prompt. You have successfully configured the client so the next step is to start the client. Here are 2 ways :
By clicking on the executable icon (this assumes you entered the proper flags during configuration).
By typing fah6 on the same command prompt window. Enter the necessary flags (including the mandatory -smp -deino flag) if you didn't enter during configuration.
Normally, if everything is done correctly, it will be chugging fine. To check this, open the task manager and make sure there is 4 instances of FahCore_Ax.exe in the list.
Configuring the SMP client as a service
Warning: If you want to run the SMP client as a service, be aware this is currently unsupported by the developers. A bad configuration can cause the client to have issues and lose work units.
Note: The guide is validated with Windows Vista. A lot of people have a problem starting the service under XP so follow the steps at your own risks.
In addition to this guide, there is also a very detailed guide available on the Folding Forum (http://foldingforum.org/viewtopic.php?p=15051#p15051) which is a bit outdated but still valid.
The first step is to start the client in configuration mode with the -configonly flag. When you are in the Advanced options section, find this entry :
Launch automatically, install as a service in this directory (yes/no) [no]?Enter yes to confirm the service installation. Continue (edit the options if needed) until you reach this line :
Additional client parameters []?Since the client will be running as a service, the additional flags must be entered here to make it work in DEINO SMP mode. In our case, enter -smp -deino -verbosity 9 -d "C:\FAH" then finish the configuration. The essential piece is the -d "[client path]" where [client path] is the folder where you installed the client (don't forget the quotes). This tell Windows to use the specific path since by default, it will use C:\Windows\System32 as the working folder which cause the client to stop with a 1067 error.
At this stade, don't start the service yet because it must be edited to run with the proper parameters and permissions. For this, open the Services MMC by clicking on the start menu then type services.msc in the Run... box (XP) or the search field (Vista). When the Services console is started, find the newly added F@H service, which should be called Folding@Home-CPU-[1] :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPService1.png
If you didn't see, restart the client in configuration mode again and double-check that the service is being installed. Now, double-click on it and it will bring the Properties window. Click on the Log On tab to get this :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPService2.png
Select the This Account button then enter the same account you used to configure the DEINO client above. To make sure the account name is correct, it's suggested to click on the Browse button and find the account. Even if the password fields seems populated, delete them and enter the corresponding password.
You also need to make sure that the F@H service is started only when the DeinoPM service is started first. For this, you need to make sure that both the F@H and DeinoPM services is stopped (you can right-click on each service in the Services console and stop them if it is started).
Open the registry editor by going on the Start menu and type regedit.exe (same place as above to start services.msc). When the Registry editor window is open, find the service which is normally in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es branch. When you find it, click on it then add a new Multi-string value (REG_MULTI_SZ) then name it DependOnService :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPService3.png
When it ask for the value, enter DeinoPM which is the service name of DEINO then confirm it. You should see the result like that :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPService4.png
Close the registry editor then go back to the Services console. Double-click on the F@H service then click on the Dependencies tab. You should see that DeinoPM is listed as a dependency :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPService5.png
Alternatively, you can also create a .reg file to add the new entry. Open Notepad and paste this :
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Folding@home-CPU-[MachineID]]
[/img]DependOnService"=hex(7):44,00,65,00,69,00,6e,00,6f,00,50,00,4d,00, 00,00,00,00Change the contents of [MachineID] to the Machine ID your SMP client is configured. In our example, we assume it's 1 so it would look like [1]. When you are done, click on File then on Save As... to save as a .reg file (Give a name like fahservice.reg). When you are done, just click on the newly created file and it will pop a window asking if you want to add to the registry. Confirm the action and it will be added.
When you are done, you can either start the service yourself (suggested) by clicking on the first tab then click on the Start button or by rebooting. Check if it is started correctly and if not, double-check the account details.
Windows GPU2 client installation
Requirements for installation
Before you start the installation process of the GPU client, there is a few requirements you must check to make sure the client will work correctly :
AMD/ATI
If you have a ATI GPU, the requirement is to be compatible with CAL and this mean that any card from X2xxx (R6xx) series and above can run any CAL application. This also means that unfortunately, X1xxx and older is not compatible because the shaders architecture is not unified.
ATI driver supported for folding is currently the Catalyst 8.7 (or newer) that you can find it here (http://ati.amd.com/support/driver.html). To update the driver, it's suggested that you uninstall the old driver, reboot then install the new driver.
NVIDIA
If you own a NVIDIA card, it must be compatible with CUDA, so the 8 series and above is compatible (a list (http://www.nvidia.com/object/cuda_learn_products.html) is available to check if your card is compatible, including the GeForce, Tesla and Quadro lines). The GeForce series 7 and older is not compatible due to a lack of unified shaders.
You need to run the proper driver to run CUDA. NVIDIA official CUDA 177.35 (or newer) driver can be downloaded here (http://www.nvidia.com/object/cuda_get.html) and you should use this version unless there is a compelling reason to use a different one. To update the driver, it's suggested that you uninstall the old driver, reboot then install the new driver.
There are two types of client available, which is a Systray version and a Console version. The advantage of the Systray version is that you have a icon on the task bar that you can use to control the client. The Console version use the command prompt to run but the main advantage is that version can be configured as a service, thus concealing the client entirely from the user. However, the service mode doesn't work at all under Vista.
Note: Under Windows, antivirus software can interfere with the Folding@Home client files and cause errors. We suggest that you configure the antivirus software to exclude the F@H client directory and especially the work directory inside of it from the antivirus scanning list. This can be done by going into the exclusion list panel that every antivirus should have. The work subdirectory contains semi-random binary data and can confuse overly aggressive heuristic virus scanning.
Installation (Systray version)
Note: The viewer included with the Systray client is not working properly and it's a known bug. The Pande Group is aware of the issue and is working to fix it. In the meanwhile, don't use it (it's not required to open the viewer to make the client run, having the Systray icon on the taskbar is enough).
You can download the GPU Systray client installer from the Download (http://folding.stanford.edu/English/DownloadWinOther) page. After it has downloaded, run the installer package by double clicking the downloaded file (If it doesn't start automatically, it probably means you need to install the Windows Installer 3.1 package first, which you can get through Windows automatic update). You will see this window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray1.png
Click on the Next button to continue to the License agreement window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray2.png
If you accept the license, click on the I Agree button then click on the Next button. There is no configuration to edit :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray3.png
Click on the Next button to start the installation process. When it's done, you will see the last window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray4.png
Click on the Close button to end the installation process.
During the installation process, the installer will have created a new folder in the Start menu. You can find it under Start -> Programs -> Folding@Home-x86 as indicated here :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray5.png
There are two shortcuts, the first is to run the program whenever you want and the second is to go in the data folder where the client is storing the work unit's data, configuration and executable files for any maintenance need. For now, we need to configure it so click on the first one (Folding@Home). As you are running the client for the first time, a configuration window will appear :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray6.png
In this panel, if you want to fold under your own username, enter it here along with the team number if you are part of the team. If all you want is to contribute while not caring about a username or team, leave them as is. If you have a passkey associated to your username, enter it (if you want to know what is a passkey and how to obtain one, check this page (http://folding.stanford.edu/English/FAQ-passkey)). When you are done, click on the Connection tab on the top to get to the next panel :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray7.png
The first checkbox should be checked if you want the client to ask before downloading or uploading a work unit. This is useful if you are on a non-permanent connection like dialup or to control when to download/upload. If you are connected behind a proxy, you'll need to configure the client for it (if you need the information about configuring a proxy, ask your administrator). The last checkbox will let you decide if you would like to receive large work units (they have bigger bandwidth and memory requirements). After doing this, click on the Advanced tab to get to the next panel :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray8.png
These are the advanced configuration of the client so if you are unsure about them, you can leave them alone since the defaults are suitable for the majority of users. Here is what each element does :
Core priority : If you are running multiple clients or have another program running continuously in the background, you may need to adjust the priority so it won't sit idle while waiting for free cycles.
CPU Usage Percent : If you don't want the CPU to allocate all the cycles to F@H, adjust the percentage to suit your needs.
Disable highly optimized assembly code : If you are having problems running the client due to a processor incompatibility or any weird error, check this to disable the SSE optimizations. Doing this will cause the client to run slower depending on the workunit.
Checkpointing frequency : Increase or decrease the frequency of Work Unit progress backups. This won't prevent the client from writing the data before the checkpoint if the next frame is completed before.
Do NOT lock cores to specific CPU : If you have more than one core, checking this will allow the client to use any free CPU/core. If it is left unchecked, it will only use one core no matter if others is free or not.
Core Network Address (Advanced) : For future use
Pause work while battery power is being used : This is useful for laptops to stop the client from running when it's on battery power, to avoid draining power.
Additional Client Parameters : This is where you can save the frequently used flags like -verbosity 9 or -advmethods.
Machine ID : This is the client ID and it needs to be different if you are running more than one client under the same OS. An example would be if you are running the Systray client and the GPU2 client at the same time, in which case each client will use Machine ID 1 and 2 respectively.
When you are done, click on Ok. If you entered any Additional Client Parameters during configuration, you may need to restart the client to use them. It will now run in the background with a icon in the Taskbar. You can hover on it to check the current client status but if you want to see what is the last actions of the client, you can check the log file generated by the client. For that, right-click on the taskbar icon and you will see this :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray9.png
Click on Status then on Log file to open a notepad window with the log file contents. This is useful to see if there are errors and if you need help, you can copy the contents of this log file to the forum.
Installation (console version)
First, download the console client from the Download (http://folding.stanford.edu/English/DownloadWinOther) page (There is 2 distinct packages, one for Windows XP and 2003 and one for Vista so make sure to pick the correct one for your OS). If you wanted to use a installer, the Console client doesn't come with one so it's suggested to use the Systray client instead. After you are done downloading the package, unzip the package in any place except the Program Files folder (due to potential permissions issues). A good suggestion is to create a new folder on C:\Users\\FAH! for Vista or C:\Documents and Settings\[username]\FAH for XP. You can also place it on the desktop or on a custom folder like C:\FAH\. After you are done unzipping, it's suggested you rename the executable file name to fah6.exe to make the following steps easier to do.
Note: If you are using the Vista GPU Console client, don't install as a service since it's currently not working properly. If you need a unobstructive client under Vista, it's suggested to use the Systray version.
The next step is to configure it by typing the following command (if you used a different one, use the correct name) :
fah6 -configonly
You will see a list of configuration options. Here is an sample with an explanation about each option :
Launch directory: C:\FAH
Executable: fah6
Arguments: -configonly
[16:25:22] Configuring Folding@Home...
User name [Anonymous]?
Team Number [0]?
Passkey []?
Enter your user name (not the Windows user name but your folding name), team number and passkey here
Ask before fetching/sending work (no/yes) [no]?
If you are not on a permanent connection, select this to yes to wait for your permission to upload/download work units.
Use proxy (yes/no) [no]?
If you are connected to a proxy, enter yes and configure the proxy options.
Acceptable size of work assignment and work result packets (bigger units
may have large memory demands) -- 'small' is <5MB, 'normal' is <10MB, and
'big' is >10MB (small/normal/big) [normal]?
This is related to the size of downloaded and uploaded work units. Bigger units will also have bigger memory requirement. If you run on a slow broadband or dialup internet connection, it's suggested to pick small to ease the bandwidth usage.
Change advanced options (yes/no) [no]? yes
If you want to change the advanced options, enter yes but it's not mandatory.
Launch automatically, install as a service in this directory (yes/no) [no]?
If you want the client to run as a service, say yes and it will install a new entry in the services list. Next time you restart the computer, the service will start automatically and run in the background.
Core Priority (idle/low) [idle]?
This adjusts the priority level. Any priority higher than idle can cause some slowdown during general computer usage.
CPU usage requested (5-100) [100]?
This will adjust the percentage of CPU usage. If you want to limit temperature issue or to keep some CPU cycles for more intensive computer tasks, enter a number below 100.
Disable highly optimized assembly code (no/yes) [no]?
If you are having issues running the client, disable this. For 99% of the users, leave this alone since this could reduce the client performance a lot.
Pause if battery power is being used (useful for laptops) (no/yes) [no]?
If you run a laptop, set this to yes to pause if the laptop is not plugged on the wall. This will avoid the client draining the battery.
Interval, in minutes, between checkpoints (3-30) [15]?
Number of minutes between each checkpoint where the client is writing the client progress on disk in case of unexpected interruption.
Memory, in MB, to indicate (1013 available) [1013]?
Set the amount of memory available to the client. By default, it show the full memory amount but if you have programs which require lots of memory, it's suggested to reduce this.
Set -advmethods flag always, requesting new advanced
scientific cores and/or work units if available (no/yes) [no]?
This is the same as using the -advmethods flag. This will allow you to grab workunits with bigger requirements (often with more points value) than the normal units. Keep in mind this will often have a higher risk of failure so use this flag only if you are ready to accept the risks.
Ignore any deadline information (mainly useful if
system clock frequently has errors) (no/yes) [no]?
Set this to yes if your local computer clock is having issues keeping the correct date and time. For 99% of the users, leave this to no.
Machine ID (1-16) [2]?
This is the ID of the client. If you are running more than one client under the same OS, you need to have a different machine ID for each client. If you are installing on multiple computers, you don't need to change this since this is only for installing multiple clients on the same computer.
The following options require you to restart the client before they take effect
Disable CPU affinity lock (no/yes) [no]?
If you disable the affinity lock, the client will pick any free CPU core. Leave to no if you want the client to be locked to a CPU core. If you run a NVIDIA card, you can adjust the affinity by using the NV_FAH_CPU_AFFINITY environment variable (check the NVIDIA FAQ for more details). For this to work, you need to enter no or it will ignore the affinity you configured.
Additional client parameters []?
You can enter the client flags here so you don't have to type the flag each time. -verbosity 9 flag here to make things easier. Don't enter -config or -configonly'' or any single-use flag to avoid issues.
IP address to bind core to (for viewer) []?
For future use
When you are done, the configuration will end and you will be back to the command prompt. You have successfully configured the client so the next step is to start the client. Here are 2 ways :
By clicking on the executable icon (this assumes you entered the proper flags during configuration).
By typing fah6 on the same command prompt window. Enter the necessary flags if you didn't enter during configuration.
Normally, if everything is done correctly, it will be chugging fine. To check this, open the task manager and make sure there is a process called FahCore_xx.exe in the list.
Installation for a multi-GPU system
Here is some specific requirements to follow for the multi-GPU setup to work :
The current multi-GPU installation guide requires some knowledge of the Windows system, if you are having issues, you can ask for help.
If you are running multiple GPU cards with SLI or Crossfire, you need to unlink the cards by disabling SLI or Crossfire in the driver control panel. Also, you need to extend the desktop for the client to recognize the cards.
When Windows ask to look for a driver hit CANCEL. If you let Windows install the driver automatically, there is a big risk of having sub-par performances or client issues.
If you run Windows Vista, you need to have each GPU connected to a monitor (a KVM can also work but not all models of KVM will provide a signal when it's not switched as current monitor) or a VGA dummy plug.
Before you start doing the installation, make sure to grab the latest CUDA driver and the latest client. You can find the links in the Requirements section above. Also, the following guide is based on the GPU Systray client installation so if you didn't install the client yet, follow the Systray instructions above first before following the instructions below.
Note: First of all, make sure the GPU2 client didn't copy the shortcut in the startup folder during installation because we don't want it to start automatically. The current client doesn't do it but previous clients did, hence the warning. The shortcut is usually found in ''Start -> Programs -> Startup".
Next, open up Windows Explorer and find the directory where the installer created a folder under your user name. Below is the path of the folder depending on the OS :
XP : C:\Documents and Settings\[username]\Application Data\
Vista: C:\Users\[username]\AppData\Roaming\
Note: This folder is usually hidden so you may need to type the whole path in the address bar or to enable the option to view all files and folders.
Once you’ve located the directory, copy the folder called Folding@Home-gpu and paste into the same location. Rename the new copy by cutting the “Copy of” off and adding a 2 (or more for extra cards) after the directory name. You will need to repeat the same steps if you have 3 or more GPU you want to use. Here is what it should look :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinGPU1.png
Now, go in the C:\Program Files\Folding@Home\Folding@Home-gpu folder (with Vista, it's in the x86 folder). You should find the client executable here so make a new shortcut of the client (right-click on the executable icon then select Create Shortcut). After creating the shortcut, move the shortcut to the desktop then rename with a short name like GPU1. Don't copy more than one shortcut since you will do it after doing some modifications :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinGPU2.png
Right-click on the first shortcut then select Properties. It should bring up the following screen:
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinGPU3.png
Now, replace the Start in: path with the path of the data file which is stored in either those places (replace [username] with your Windows user name) :
XP : C:\Documents and Settings\[username]\Application Data\Folding@Home-gpu
Vista: C:\Users\[username]\AppData\Roaming\Folding@Home-gpu
Make sure there are quotes at the start and end of the Start in: path.
Add the -gpu 0 flag at the end of the Target: path, after the quotes (make sure there is a space between the quote and the flag). It should look like this in the Target: field:
"C:\Program Files\Folding@home\Folding@home-gpu\Folding@home.exe" -gpu 0
Once you are done, the properties should look like this for the first client. Click on Ok to close the panel afterwards :
Target: "C:\Program Files\Folding@home\Folding@home-gpu\Folding@home.exe" -gpu 0
Start in: "C:\Documents and Settings\[username]\Application Data\Folding@Home-gpu" (XP/2003) or "C:\Users\[username]\AppData\Roaming\Folding@Home-gpu" (Vista)
Now that you are done editing the shortcut, it's time to create more for the other GPU cards. Copy the first shortcut and paste as many copies (based on how many GPU cards you want to run) you need on the desktop. Rename each shortcut copy with a simple yet distinct names (to help identify which client) like GPU2, GPU3, etc. When you are done, right-click on each new shortcut and select Properties to edit the properties. This time, since you did most of the configuration above, all you need to do is to point the Start in: path to each data folder that you created and put -gpu 1 flag (or higher for subsequent cards). After you are done, you should have something like that :
Target: "C:\Program Files\Folding@home\Folding@home-gpu\Folding@home.exe" -gpu 1
Start in: "C:\Documents and Settings\[username]\Application Data\Folding@Home-gpu2" (XP/2003) or "C:\Users\[username]\AppData\Roaming\Folding@Home-gpu2" (Vista)
When you are done editing each shortcut, click on the first shortcut and configure your client as demonstrated in the [url=http://folding.stanford.edu/English/WinGPUGuide#ntoc2]Systray installation guide above. The key things to make sure you do are :
On the Connection tab :
Click yes to accept WUs larger than 10 megabytes.
On the Advanced tab :
Check the Core Priority for Slightly Higher
Click do not lock cores to specific CPU
Make sure the Machine ID is different then any CPU or GPU client you have running. Note: default is 2.
Now hit accept and repeat the step above for each shortcut and make sure you pick a unique machine ID for each client. When you are done, all that remain to do is to click every shortcut to start the clients and monitor them closely to make sure they run fine (it's often tricky due to a possible driver version conflict).
Linux Installation Instructions
The following instructions is for the unified Linux 6.02 client. To run in SMP mode, just add the -smp flag to run it.
Go to Terminal. Depending of your desktop engine (KDE, GNOME, ...) the Terminal application can be at different places, but you'll find it. GNOME has it at "Applications->Accessories->Terminal". Open Terminal.
In the Terminal window you should see a prompt that looks something like this: yourusername@yourcomputername ~ $
To get the FAH client going type in (or copy/paste) the following commands:
mkdir -p ~/folding
cd ~/folding
curl -O http://www.stanford.edu/group/pandegroup/folding/release/FAH6.02-Linux.tgz
tar xzf FAH6.02-Linux.tgzNote: If you don't have curl available on your machine, use wget instead:
wget http://www.stanford.edu/group/pandegroup/folding/release/FAH6.02-Linux.tgzBefore you run the client, you will have to unzip it first. After this, execute these commands to make the fah6 executable with the appropriate libs (only if you are running a 64 bit version of Linux) :
chmod 755 fah6
sudo apt-get install ia32-libsNow you should have the FAH client in place and you'll have to configure it. It can be done by running following command:
./fah6 -configonlyAfter setting the configuration there are couple of ways to start the FAH client. One way is to start it is by typing in each time the following command (If you run SMP, put the -smp flag there as well):
./fah6 -verbosity 9OPTIONAL: To make it a little easier for yourself, you can make a script by running the following commands:
echo "./fah6 -verbosity 9 $* &" > fah
chmod +x fahNow you'll just have to run
./fahand all those additional FAH client flags will get added by itself.
Note: All those listed commands MUST be typed/pasted from this little HOWTO to the terminal (window) of your machine.
Example:
user@box ~ $ mkdir -p ~/folding
user@box ~ $ cd ~/folding
user@box FAH $ curl -O http://www.stanford.edu/group/pandegroup/folding/release/FAH6.02-Linux.tgz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 138k 100 138k 0 0 34461 0 0:00:04 0:00:04 --:--:-- 39789
user@box FAH $ tar xzf FAH6.02-Linux.tgz
user@box FAH $ ls -la
total 960
drwxr-xr-x 5 user guest 170 Nov 6 23:58 .
drwx------ 18 user guest 612 Nov 6 23:55 ..
-rw-r--r-- 1 user guest 138145 Nov 6 23:56 FAH6.02-Linux.tgz
-rwxr-xr-x 1 user guest 282796 Nov 4 07:04 fah6
-rwxr-xr-x 1 user guest 60156 Oct 27 16:52 mpiexec
user@box FAH $ ./fah6 -configonly
...
user@box FAH $ echo "./fah6 -verbosity 9 $*" > fah
user@box FAH $ chmod +x fah
user@box FAH $ ./fah
... [U]How to start the linux client as a service
Note: Adding the client as a service in Linux depends on which distribution you are using. The instructions below should work for the majority of distributions available in the market. If nothing works, you might need to do some research to find out what your distribution needs to install as a service.
Do not change accounts or change directory location then create a script named folding by pasting the following commands:
echo "# chkconfig: 345 93 14" > ./folding
echo "# description: will start FAH client as a service" >> ./folding
echo "su - $USER -c \"cd $PWD; ./fah6 -verbosity 9 < /dev/null > /dev/null 2>&1 &\"" >> ./folding
chmod +x ./foldingNote: In the following steps, replace [fahdir] with the value you saw on screen during the previous installation steps (don't include the brackets).
To mark down where you installed the FAH client just run:
echo "[fahdir]=$PWD"Note: All the following steps need root privileges to be carried out successfully.
For Debian-based distributions run:
sudo cp [fahdir]/folding /etc/init.d/For other distributions run:
su - -c "cp [fahdir]/folding /etc/init.d/"Note: If you installed the client under root user account, do this instead :
echo "# chkconfig: 345 93 14" > ./folding
echo "# description: will start FAH client as a service" >> ./folding
echo "cd $PWD; ./fah6 -verbosity 9 < /dev/null > /dev/null 2>&1 &" >> /etc/init.d/folding
chmod +x /etc/init.d/foldingLast step is to register the folding service.
For Debian-based distributions run:
sudo update-rc.d folding defaultsFor other distributions run:
su - -c "chkconfig --add folding"That's all so reboot the computer to make the new script start the client. To check if it is working fine, just go to your folding folder and open fahlog.txt or run:
tail -f [fahdir]/FAHlog.txt
Welcome to the R3 F@H installation guides page. You will find the guides you need to setup a Windows SMP (both MPICH and DEINO versions), linux SMP or Windows GPU, including a multi-GPU guide. This is 99% identical to the official guides which can be found on the Folding@Home official site at http://folding.stanford.edu/English/Guide.
If even after following the guides, you have questions or clarification to ask, make a new thread and we will be glad to help.
To reach the desired guide, just click on the index link :
The R3 F@H team ID is 156204
Note: I'm the author of the guides and I'm giving permission for this copy of the guides to be available here. Don't reproduce any or all parts of the guides without my express permission.
Windows uniprocessor (classic) client
There are two types of client available, which is a Systray version and a Console version. The advantage of the Systray version is that you have a icon on the task bar that you can use to control the client. The Console version use the command prompt to run but the main advantage is that version can be configured as a service, thus concealing the client entirely from the user.
Note: Under Windows, antivirus software can interfere with the Folding@Home client files and cause errors. We suggest that you configure the antivirus software to exclude the F@H client directory and especially the work directory inside of it from the antivirus scanning list. This can be done by going into the exclusion list panel that every antivirus should have. The work subdirectory contains semi-random binary data and can confuse overly aggressive heuristic virus scanning.
Installation (Systray version)
Note: The viewer included with the Systray client is not working properly and it's a known bug. The Pande Group is aware of the issue and is working to fix it. In the meanwhile, don't use it (it's not required to open the viewer to make the client run, having the Systray icon on the taskbar is enough).
You can download the Systray client installer from the Download (http://folding.stanford.edu/English/Download) page. After it has downloaded, run the installer package by double clicking the downloaded file (If it doesn't start automatically, it probably means you need to install the Windows Installer 3.1 package first, which you can get through Windows automatic update). You will see this window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray1.png
Click on the Next button to continue to the License agreement window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray2.png
If you accept the license, click on the I Agree button then click on the Next button. There is no configuration to edit :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray3.png
Click on the Next button to start the installation process. When it's done, you will see the last window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray4.png
Click on the Close button to end the installation process.
During the installation process, the installer will have created a new folder in the Start menu. You can find it under Start -> Programs -> Folding@Home-x86 as indicated here :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray5.png
There are two shortcuts, the first is to run the program whenever you want and the second is to go in the data folder where the client is storing the work unit's data, configuration and executable files for any maintenance need. For now, we need to configure it so click on the first one (Folding@Home). As you are running the client for the first time, a configuration window will appear :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray6.png
In this panel, if you want to fold under your own username, enter it here along with the team number if you are part of the team. If all you want is to contribute while not caring about a username or team, leave them as is. If you have a passkey associated to your username, enter it (if you want to know what is a passkey and how to obtain one, check this page (http://folding.stanford.edu/English/FAQ-passkey)). When you are done, click on the Connection tab on the top to get to the next panel :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray7.png
The first checkbox should be checked if you want the client to ask before downloading or uploading a work unit. This is useful if you are on a non-permanent connection like dialup or to control when to download/upload. If you are connected behind a proxy, you'll need to configure the client for it (if you need the information about configuring a proxy, ask your administrator). The last checkbox will let you decide if you would like to receive large work units (they have bigger bandwidth and memory requirements). After doing this, click on the Advanced tab to get to the next panel :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray8.png
These are the advanced configuration of the client so if you are unsure about them, you can leave them alone since the defaults are suitable for the majority of users. Here is what each element does :
Core priority : If you are running multiple clients or have another program running continuously in the background, you may need to adjust the priority so it won't sit idle while waiting for free cycles.
CPU Usage Percent : If you don't want the CPU to allocate all the cycles to F@H, adjust the percentage to suit your needs.
Disable highly optimized assembly code : If you are having problems running the client due to a processor incompatibility or any weird error, check this to disable the SSE optimizations. Doing this will cause the client to run slower depending on the workunit.
Checkpointing frequency : Increase or decrease the frequency of Work Unit progress backups. This won't prevent the client from writing the data before the checkpoint if the next frame is completed before.
Do NOT lock cores to specific CPU : If you have more than one core, checking this will allow the client to use any free CPU/core. If it is left unchecked, it will only use one core no matter if others is free or not.
Core Network Address (Advanced) : For future use
Pause work while battery power is being used : This is useful for laptops to stop the client from running when it's on battery power, to avoid draining power.
Additional Client Parameters : This is where you can save the frequently used flags like -verbosity 9 or -advmethods.
Machine ID : This is the client ID and it needs to be different if you are running more than one client under the same OS. An example would be if you are running the Systray client and the GPU2 client at the same time, in which case each client will use Machine ID 1 and 2 respectively.
When you are done, click on Ok. If you entered any Additional Client Parameters during configuration, you may need to restart the client to use them. It will now run in the background with a icon in the Taskbar. You can hover on it to check the current client status but if you want to see what is the last actions of the client, you can check the log file generated by the client. For that, right-click on the taskbar icon and you will see this :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray9.png
Click on Status then on Log file to open a notepad window with the log file contents. This is useful to see if there are errors and if you need help, you can copy the contents of this log file to the forum.
Windows SMP client installation (MPICH version)
Note: Due to the way the Windows SMP client is setup, it's a complicated process to install it properly. For this reason, it's essential to read the whole guide first before attempting the installation. There is a lot of things to be careful like the -smp flag requirement or it won't work properly.
In addition to the instructions below, we also suggest you check out instructions on the FAH wiki (http://fahwiki.net/index.php/How_do_I_install_the_SMP_Console_client_in_Windows _Vista).
Requirements for installation
Before you start the installation process of the SMP console client, there are a few requirements you must check to make sure the client will work correctly :
You have a computer with at least a recent dual core or better to run the SMP client. This means than the older single core processors won't be able to run it. Since it's a high performance client, if you notice that after installation, it doesn't always meet the deadlines, please use the uniprocessor client instead.
If you are installing this under Windows XP, you are required to install the Microsoft .NET framework v2.0. You can download the package from Microsoft (http://www.microsoft.com/downloads/details.aspx?familyid=0856eacb-4362-4b0d-8edd-aab15c5e04f5&displaylang=en). Windows Vista already includes the necessary package by default so it's not necessary to do it if you install the client under Vista.
The Windows user account you are using to install the client must have a password and have enough administrator rights. Blank passwords will not work and you must have a password only with those valid characters : A-Z, a-z and 0-9. Special characters should not be used to avoid any potential issues. If you change the password of the Windows user account, you need to rerun install.bat. The password being used to install is encrypted in the registry and not transmitted to the Stanford servers.
Installation
Note: Under Windows, antivirus software can interfere with the Folding@Home client files and cause errors. We suggest that you configure the antivirus software to exclude the F@H client directory and especially the work directory inside of it from the antivirus scanning list. This can be done by going into the exclusion list panel that every antivirus should have. The work subdirectory contains semi-random binary data and can confuse overly aggressive heuristic virus scanning.
First, create a new folder on C:\Users\\ or on the root of C:\ (what matters here is to not put it in C:\Program Files\ to avoid issues with permissions, especially under Vista) with a simple name without spaces or special characters. A good suggestion is to name it FAH. The reason for this suggestion is because Vista has some strict restrictions when a program is run from the Program Files folder. Doing this will avoid lots of issues.
Go to the High performance Windows clients (http://folding.stanford.edu/English/DownloadWinOther) download page. There will be a DEINO or MPICH package available for download. Pick the MPICH version in this case.
After you downloaded it, you will see a executable installer package so run it. You will be presented with this window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPInst1.png
Click on Next to bring the next window, which is a Readme with the client notes. Click on Next again to bring the following window:
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPInst2.png
It's up to you to pick which option. I recommend picking the first option for All Users to make things simpler but if you don't want others users to see this, leave the default option as is. After this, click on Next to bring the next window:
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPInst3.png
If you followed the recommendation to make a new folder, pick this one by clicking on the Browse button to get the following window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPInst4.png
After you picked the desired folder where you will install the client, click on Ok then on Next on the previous window. At this point, the installer knows everything required to proceed with the installation so click on Next to run it. When it's done, click on Finish to close the installer.
With Windows Explorer, browse to the folder you just installed the client and you will see a bunch of files like this :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPInst5.png
To make the following steps easier to do, it's suggested to rename the executable to something easy to remember and to type like fah6.exe (right-click on the executable file, select Rename and change to a new name).
[U]MPICH Configuration
Open the Command Prompt window by clicking on the Start menu then type cmd.exe on the Run box and click on Ok. If you are under Vista, you must run it with the Run as administrator option or you will not have sufficient rights to complete the following steps (to get this, right-click on Command Prompt icon then select Run as administrator). With Windows XP, it's sufficient to run cmd.exe as is.
Here is what it should look under Vista (typed cmd.exe then right-click on it) :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPRunAs.png
You can use CD to change the directory and type D:\ (or any other letter) to change the drive if the client is not installed on C:\ by default. With those commands, move to the folder you created earlier (C:\FAH in our example). When you are here, type install.bat and you will see a message like this :
MPICH2 Process Manager, Argonne National Lab installed.
account (domain\user) [FAH\Username]:Note: When you execute install.bat, you may get a firewall popup asking to allow or block twice, once for mpiexec.exe and once for smpd.exe. You should make sure both are allowed or the program won't work.
If the domain and user account is correct, just click on Enter but if you want to use a different account, enter the proper information (If you are on Active Directory, enter the Domain name but if it's not the case, it's the computer name you need to enter). After you press enter, you will see a password prompt :
password:Enter the Windows user password (you will see nothing on screen but type away). It will ask for a confirmation so enter the password again. If you did this correctly, you will see the following messages :
password:
confirm password:
Password encrypted into the Registry.
If you see this twice, MPI is working
If you see this twice, MPI is working
Press a key to continue...The important thing is to see that the If you see this twice, MPI is working is displayed twice. If you don't see this or you see a different error, check why and fix this before retrying. When MPICH is working correctly, it's time to configure the client below.
Client configuration
The next step is to configure it by typing the following command (if you used a different one, use the correct name) :
fah6 -configonlyYou will see a list of configuration options. Here is an sample with an explanation about each option :
Launch directory: C:\FAH
Executable: fah6
Arguments: -configonly
[16:25:22] Configuring Folding@Home...
User name [Anonymous]?
Team Number [0]?
Passkey []?Enter your user name (not the Windows user name but your folding name), team number and passkey here
Ask before fetching/sending work (no/yes) [no]?If you are not on a permanent connection, select this to yes to wait for your permission to upload/download work units. Because of the short deadlines on SMP work assignments, persistent connections are strongly recommended so this option should not be set to yes.
Use proxy (yes/no) [no]?If you are connected to a proxy, enter yes and configure the proxy options.
Acceptable size of work assignment and work result packets (bigger units
may have large memory demands) -- 'small' is <5MB, 'normal' is <10MB, and
'big' is >10MB (small/normal/big) [normal]?This is related to the size of downloaded and uploaded work units. Bigger units will also have bigger memory requirement. If you run on a slow broadband or dialup internet connection, it's suggested to pick small to ease the bandwidth usage. However, all SMP WUs are big, so setting it to small or normal will often lead to long periods where no assignments are available.
Change advanced options (yes/no) [no]? yesIf you want to change the advanced options, enter yes but it's not mandatory.
Launch automatically, install as a service in this directory (yes/no) [no]?You can install the client as a service but currently, it's not recommended. If you still insist to do this, there are special steps to do after installing the service but before running it for the first time. See below for detailed instructions.
Core Priority (idle/low) [idle]?This adjusts the priority level. Any priority higher than idle can cause some slowdown during general computer usage.
CPU usage requested (5-100) [100]?This will adjust the percentage of CPU usage. If you want to limit temperature issue or to keep some CPU cycles for more intensive computer tasks, enter a number below 100.
Disable highly optimized assembly code (no/yes) [no]?If you are having issues running the client, disable this. For 99% of the users, leave this alone since this could reduce the client performance a lot.
Pause if battery power is being used (useful for laptops) (no/yes) [no]?If you run a laptop, set this to yes to pause if the laptop is not plugged on the wall. This will avoid the client draining the battery.
Interval, in minutes, between checkpoints (3-30) [15]?Number of minutes between each checkpoint where the client is writing the client progress on disk in case of unexpected interruption.
Memory, in MB, to indicate (1013 available) [1013]?Set the amount of memory available to the client. By default, it show the full memory amount but if you have programs which require lots of memory, it's suggested to reduce this.
Set -advmethods flag always, requesting new advanced scientific cores and/or work units if available (no/yes) [no]?This is the same as using the -advmethods flag. This will allow you to grab workunits with bigger requirements (often with more points value) than the normal units. Keep in mind this will often have a higher risk of failure so use this flag only if you are ready to accept the risks.
Ignore any deadline information (mainly useful if system clock frequently has errors) (no/yes) [no]?Set this to yes if your local computer clock is having issues keeping the correct date and time. For 99% of the users, leave this to no.
Machine ID (1-16) [1]?This is the ID of the client. If you are running more than one client under the same OS, you need to have a different machine ID for each client. If you are installing on multiple computers, you don't need to change this since this is only for installing multiple clients on the same computer.
The following options require you to restart the client before they take effect Disable CPU affinity lock (no/yes) [no]?Not useful for SMP since it use all cores.
Additional client parameters []?You can enter the client flags here so you don't have to type the flag each time. I strongly suggest you enter the -smp -verbosity 9 flag here to make things easier. Don't enter -config or -configonly or any single-use flag to avoid issues.
IP address to bind core to (for viewer) []?For future use
When you are done, the configuration will end and you will be back to the command prompt. You have successfully configured the client so the next step is to start the client. Here are 2 ways :
By clicking on the executable icon (this assumes you entered the proper flags during configuration).
By typing fah6 on the same command prompt window. Enter the necessary flags (including the mandatory -smp flag) if you didn't enter during configuration.
Normally, if everything is done correctly, it will be chugging fine. To check this, open the task manager and make sure there is 4 instances of FahCore_Ax.exe in the list.
Configuring the SMP client as a service
Warning: If you want to run the SMP client as a service, be aware this is currently unsupported by the developers. A bad configuration can cause the client to have issues and lose work units.
Note: The guide is validated with Windows Vista. A lot of people have a problem starting the service under XP so follow the steps at your own risks.
In addition to this guide, there is also a very detailed guide available on the Folding Forum (http://foldingforum.org/viewtopic.php?p=15051#p15051%27%20rel=nofollow) which is a bit outdated but still valid.
The first step is to start the client in configuration mode with the -configonly flag. When you are in the Advanced options section, find this entry :
Launch automatically, install as a service in this directory (yes/no) [no]?Enter yes to confirm the service installation. Continue (edit the options if needed) until you reach this line :
Additional client parameters []?Since the client will be running as a service, the additional flags must be entered here to make it work in SMP mode. In our case, enter -smp -verbosity 9 -d "C:\FAH" then finish the configuration. The essential piece is the -d "[client path]" where [client path] is the folder where you installed the client (don't forget the quotes). This tell Windows to use the specific path since by default, it will use C:\Windows\System32 as the working folder which cause the client to stop with a 1067 error.
At this stade, don't start the service yet because it must be edited to run with the proper parameters and permissions. For this, open the Services MMC by clicking on the start menu then type services.msc in the Run... box (XP) or the search field (Vista). When the Services console is started, find the newly added F@H service, which should be called Folding@Home-CPU-[1] :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPService1.png
If you didn't see, restart the client in configuration mode again and double-check that the service is being installed. Now, double-click on it and it will bring the Properties window. Click on the Log On tab to get this :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPService2.png
Select the This Account button then enter the same account you used to configure the MPICH client above. To make sure the account name is correct, it's suggested to click on the Browse button and find the account. Even if the password fields seems populated, delete them and enter the corresponding password.
When you are done, you can either start the service yourself (suggested) by clicking on the first tab then click on the Start button or by rebooting. Check if it is started correctly and if not, double-check the account details.
Windows SMP client installation (DEINO version)
Note: Due to the way the Windows SMP client is setup, it's a complicated process to install it properly. For this reason, it's essential to read the whole guide first before attempting the installation. There is a lot of things to be careful like the -smp flag requirement or it won't work properly.
In addition to the instructions below, we also suggest you check out instructions on the FAH wiki (http://fahwiki.net/index.php/How_do_I_install_the_SMP_Console_client_in_Windows _Vista).
Requirements for installation
Before you start the installation process of the SMP console client, there are a few requirements you must check to make sure the client will work correctly :
You have a computer with at least a recent dual core or better to run the SMP client. This means than the older single core processors won't be able to run it. Since it's a high performance client, if you notice that after installation, it doesn't always meet the deadlines, please use the uniprocessor client instead.
If you are installing this under Windows XP, you are required to install the Microsoft .NET framework v2.0. You can download the package from Microsoft (http://www.microsoft.com/downloads/details.aspx?familyid=0856eacb-4362-4b0d-8edd-aab15c5e04f5&displaylang=en). Windows Vista already includes the necessary package by default so it's not necessary to do it if you install the client under Vista.
The Windows user account you are using to install the client must have a password and have enough administrator rights. Blank passwords will not work and you must have a password only with those valid characters : A-Z, a-z and 0-9. Special characters should not be used to avoid any potential issues. If you change the password of the Windows user account, you need to rerun install.bat. The password being used to install is encrypted in the registry and not transmitted to the Stanford servers.
Installation
Note: Under Windows, antivirus software can interfere with the Folding@Home client files and cause errors. We suggest that you configure the antivirus software to exclude the F@H client directory and especially the work directory inside of it from the antivirus scanning list. This can be done by going into the exclusion list panel that every antivirus should have. The work subdirectory contains semi-random binary data and can confuse overly aggressive heuristic virus scanning.
Note: Under Windows, antivirus software can interfere with the Folding@Home client files and cause errors. We suggest that you configure the antivirus software to exclude the F@H client directory and especially the work directory inside of it from the antivirus scanning list. This can be done by going into the exclusion list panel that every antivirus should have. The work subdirectory contains semi-random binary data and can confuse overly aggressive heuristic virus scanning.
First, create a new folder on C:\Users\\ or on the root of C:\ (what matters here is to not put it in C:\Program Files\ to avoid issues with permissions, especially under Vista) with a simple name without spaces or special characters. A good suggestion is to name it FAH. The reason for this suggestion is because Vista has some strict restrictions when a program is run from the Program Files folder. Doing this will avoid lots of issues.
Go to the High performance Windows clients (http://folding.stanford.edu/English/DownloadWinOther) download page. There will be a DEINO or MPICH package available for download. For the current guide, download the DEINO package.
After you downloaded it, you will see a package in .zip format so you need to unpack it to the folder you created above. With Windows Explorer, browse to the folder you just unzipped the client and you will see a bunch of files like this :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPDeino1.png
To make the following steps easier to do, it's suggested to rename the executable to something easy to remember and to type like fah6.exe (right-click on the executable file, select Rename and change to a new name).
[U]DEINO Configuration
Open the Command Prompt window by clicking on the Start menu then type cmd.exe on the Run box and click on Ok. If you are under Vista, you must run it with the Run as administrator option or you will not have sufficient rights to complete the following steps (to get this, right-click on Command Prompt icon then select Run as administrator). With Windows XP, it's sufficient to run cmd.exe as is.
Here is what it should look under Vista (typed cmd.exe then right-click on it) :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPRunAs.png
You can use CD to change the directory and type D:\ (or any other letter) to change the drive if the client is not installed on C:\ by default. With those commands, move to the folder you created earlier (C:\FAH in our example). When you are here, type install.bat and you will get the installer messages (in a command prompt) like that :
C:\FAH>install.bat
C:\FAH>msiexec /i DeinoMPI.msiThis will start the installation of the DEINO MPI client. You will see a dialog box like this :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPDeino2.png
Just press Next to get the next window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPDeino3.png
Check to accept the license terms and click Next to enter the path :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPDeino4.png
Unless you want to install in a different place, you should leave the default path there and press Next. The next window will just confirm the options so press Next once more to install it. When it's done, press Finish to close it. The batch will then present you with the credentials store installation and configuration below.
C:\FAH>create_credential_store true
This program creates a Credential Store for the current user.
The credential store contains a public and private security key
and zero or more secure user credentials.
Deino MPI uses this store to establish secure connections between machines
and store sensitive information like user credentials.
Do you want to create a new store (yes, no)? [yes]Press enter since we want to create a new credentials store
Please enter a passphrase to protect the private key:Don't enter anything, just press enter since we don't want to use a passphrase.
Are you sure you want no password for the private key (yes,no)? [no]
yesType yes and press enter to confirm we don't want a passphrase.
Options for encrypting the private key:
protect - Use the ProtectedData.Protect/Unprotect methods to encrypt.
none - Do not encrypt.
Please enter a method to encrypt the private key: [protected]Just press enter since protect is what we wanted.
Available locations to create the store:
(1) Windows Registry
(2) Hard drive
Where would you like to create the store (1,2): [1]Press enter again since we want it to be stored in the registry. If you have a removable media plugged, the available locations list will be different (the removable media entry will be (1) so select (2) instead for the Windows Registry).
Credential store written to the Windows Registry.
C:\FAH>manage_credentials /add
Enter the account name: [COMPUTERNAME\Username]
Enter the account password:
************
Enter the password again to verify:
************Accept the account name by pressing enter and enter your Windows password twice here. If you need to use a different username (like a local windows account instead of a domain account), change the information first.
C:\FAH>net start deinopm
The DeinoMPI process manager service service is starting.
The DeinoMPI process manager service service was started successfully.
C:\FAH>mpiexec -np 2 foo
If you see this twice, MPI is working
If you see this twice, MPI is working
C:\FAH>When the line mpiexec -np 2 foo is executed, you may get a firewall popup asking you to allow or deny mpiexec.exe. Make sure you allow it or it won't run properly. When you are done, you should see the If you see this twice, MPI is working being displayed twice. If you don't see this or you see a different error, check why and fix this before retrying. If it is running correctly, continue with the client configuration below.
Client configuration
The next step is to configure it by typing the following command (if you used a different one, use the correct name) :
fah6 -configonlyYou will see a list of configuration options. Here is an sample with an explanation about each option :
Launch directory: C:\FAH
Executable: fah6
Arguments: -configonly
[16:25:22] Configuring Folding@Home...
User name [Anonymous]?
Team Number [33]?
Passkey []?Enter your user name (not the Windows user name but your folding name), team number and passkey here
Ask before fetching/sending work (no/yes) [no]?If you are not on a permanent connection, select this to yes to wait for your permission to upload/download work units. Because of the short deadlines on SMP work assignments, persistent connections are strongly recommended so this option should not be set to yes.
Use proxy (yes/no) [no]?If you are connected to a proxy, enter yes and configure the proxy options.
Acceptable size of work assignment and work result packets (bigger units
may have large memory demands) -- 'small' is <5MB, 'normal' is <10MB, and
'big' is >10MB (small/normal/big) [normal]?This is related to the size of downloaded and uploaded work units. Bigger units will also have bigger memory requirement. If you run on a slow broadband or dialup internet connection, it's suggested to pick small to ease the bandwidth usage. However, all SMP WUs are big, so setting it to small or normal will often lead to long periods where no assignments are available.
Change advanced options (yes/no) [no]? yesIf you want to change the advanced options, enter yes but it's not mandatory.
Launch automatically, install as a service in this directory (yes/no) [no]?You can install the client as a service but currently, it's not recommended. If you still insist to do this, there are special steps to do after installing the service but before running it for the first time. See below for detailed instructions.
Core Priority (idle/low) [idle]?This adjusts the priority level. Any priority higher than idle can cause some slowdown during general computer usage.
CPU usage requested (5-100) [100]?This will adjust the percentage of CPU usage. If you want to limit temperature issue or to keep some CPU cycles for more intensive computer tasks, enter a number below 100.
Disable highly optimized assembly code (no/yes) [no]?If you are having issues running the client, disable this. For 99% of the users, leave this alone since this could reduce the client performance a lot.
Pause if battery power is being used (useful for laptops) (no/yes) [no]?If you run a laptop, set this to yes to pause if the laptop is not plugged on the wall. This will avoid the client draining the battery.
Interval, in minutes, between checkpoints (3-30) [15]?Number of minutes between each checkpoint where the client is writing the client progress on disk in case of unexpected interruption.
Memory, in MB, to indicate (1013 available) [1013]?Set the amount of memory available to the client. By default, it show the full memory amount but if you have programs which require lots of memory, it's suggested to reduce this.
Set -advmethods flag always, requesting new advanced scientific cores and/or work units if available (no/yes) [no]?This is the same as using the -advmethods flag. This will allow you to grab workunits with bigger requirements (often with more points value) than the normal units. Keep in mind this will often have a higher risk of failure so use this flag only if you are ready to accept the risks.
Ignore any deadline information (mainly useful if system clock frequently has errors) (no/yes) [no]?Set this to yes if your local computer clock is having issues keeping the correct date and time. For 99% of the users, leave this to no.
Machine ID (1-16) [1]?This is the ID of the client. If you are running more than one client under the same OS, you need to have a different machine ID for each client. If you are installing on multiple computers, you don't need to change this since this is only for installing multiple clients on the same computer.
The following options require you to restart the client before they take effect Disable CPU affinity lock (no/yes) [no]?Not useful for SMP since it use all cores.
Additional client parameters []?You can enter the client flags here so you don't have to type the flag each time. I strongly suggest you enter the -smp -deino -verbosity 9 flag here to make things easier. Don't enter -config or -configonly or any single-use flag to avoid issues.
IP address to bind core to (for viewer) []?For future use
When you are done, the configuration will end and you will be back to the command prompt. You have successfully configured the client so the next step is to start the client. Here are 2 ways :
By clicking on the executable icon (this assumes you entered the proper flags during configuration).
By typing fah6 on the same command prompt window. Enter the necessary flags (including the mandatory -smp -deino flag) if you didn't enter during configuration.
Normally, if everything is done correctly, it will be chugging fine. To check this, open the task manager and make sure there is 4 instances of FahCore_Ax.exe in the list.
Configuring the SMP client as a service
Warning: If you want to run the SMP client as a service, be aware this is currently unsupported by the developers. A bad configuration can cause the client to have issues and lose work units.
Note: The guide is validated with Windows Vista. A lot of people have a problem starting the service under XP so follow the steps at your own risks.
In addition to this guide, there is also a very detailed guide available on the Folding Forum (http://foldingforum.org/viewtopic.php?p=15051#p15051) which is a bit outdated but still valid.
The first step is to start the client in configuration mode with the -configonly flag. When you are in the Advanced options section, find this entry :
Launch automatically, install as a service in this directory (yes/no) [no]?Enter yes to confirm the service installation. Continue (edit the options if needed) until you reach this line :
Additional client parameters []?Since the client will be running as a service, the additional flags must be entered here to make it work in DEINO SMP mode. In our case, enter -smp -deino -verbosity 9 -d "C:\FAH" then finish the configuration. The essential piece is the -d "[client path]" where [client path] is the folder where you installed the client (don't forget the quotes). This tell Windows to use the specific path since by default, it will use C:\Windows\System32 as the working folder which cause the client to stop with a 1067 error.
At this stade, don't start the service yet because it must be edited to run with the proper parameters and permissions. For this, open the Services MMC by clicking on the start menu then type services.msc in the Run... box (XP) or the search field (Vista). When the Services console is started, find the newly added F@H service, which should be called Folding@Home-CPU-[1] :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPService1.png
If you didn't see, restart the client in configuration mode again and double-check that the service is being installed. Now, double-click on it and it will bring the Properties window. Click on the Log On tab to get this :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPService2.png
Select the This Account button then enter the same account you used to configure the DEINO client above. To make sure the account name is correct, it's suggested to click on the Browse button and find the account. Even if the password fields seems populated, delete them and enter the corresponding password.
You also need to make sure that the F@H service is started only when the DeinoPM service is started first. For this, you need to make sure that both the F@H and DeinoPM services is stopped (you can right-click on each service in the Services console and stop them if it is started).
Open the registry editor by going on the Start menu and type regedit.exe (same place as above to start services.msc). When the Registry editor window is open, find the service which is normally in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es branch. When you find it, click on it then add a new Multi-string value (REG_MULTI_SZ) then name it DependOnService :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPService3.png
When it ask for the value, enter DeinoPM which is the service name of DEINO then confirm it. You should see the result like that :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPService4.png
Close the registry editor then go back to the Services console. Double-click on the F@H service then click on the Dependencies tab. You should see that DeinoPM is listed as a dependency :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinSMPService5.png
Alternatively, you can also create a .reg file to add the new entry. Open Notepad and paste this :
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Folding@home-CPU-[MachineID]]
[/img]DependOnService"=hex(7):44,00,65,00,69,00,6e,00,6f,00,50,00,4d,00, 00,00,00,00Change the contents of [MachineID] to the Machine ID your SMP client is configured. In our example, we assume it's 1 so it would look like [1]. When you are done, click on File then on Save As... to save as a .reg file (Give a name like fahservice.reg). When you are done, just click on the newly created file and it will pop a window asking if you want to add to the registry. Confirm the action and it will be added.
When you are done, you can either start the service yourself (suggested) by clicking on the first tab then click on the Start button or by rebooting. Check if it is started correctly and if not, double-check the account details.
Windows GPU2 client installation
Requirements for installation
Before you start the installation process of the GPU client, there is a few requirements you must check to make sure the client will work correctly :
AMD/ATI
If you have a ATI GPU, the requirement is to be compatible with CAL and this mean that any card from X2xxx (R6xx) series and above can run any CAL application. This also means that unfortunately, X1xxx and older is not compatible because the shaders architecture is not unified.
ATI driver supported for folding is currently the Catalyst 8.7 (or newer) that you can find it here (http://ati.amd.com/support/driver.html). To update the driver, it's suggested that you uninstall the old driver, reboot then install the new driver.
NVIDIA
If you own a NVIDIA card, it must be compatible with CUDA, so the 8 series and above is compatible (a list (http://www.nvidia.com/object/cuda_learn_products.html) is available to check if your card is compatible, including the GeForce, Tesla and Quadro lines). The GeForce series 7 and older is not compatible due to a lack of unified shaders.
You need to run the proper driver to run CUDA. NVIDIA official CUDA 177.35 (or newer) driver can be downloaded here (http://www.nvidia.com/object/cuda_get.html) and you should use this version unless there is a compelling reason to use a different one. To update the driver, it's suggested that you uninstall the old driver, reboot then install the new driver.
There are two types of client available, which is a Systray version and a Console version. The advantage of the Systray version is that you have a icon on the task bar that you can use to control the client. The Console version use the command prompt to run but the main advantage is that version can be configured as a service, thus concealing the client entirely from the user. However, the service mode doesn't work at all under Vista.
Note: Under Windows, antivirus software can interfere with the Folding@Home client files and cause errors. We suggest that you configure the antivirus software to exclude the F@H client directory and especially the work directory inside of it from the antivirus scanning list. This can be done by going into the exclusion list panel that every antivirus should have. The work subdirectory contains semi-random binary data and can confuse overly aggressive heuristic virus scanning.
Installation (Systray version)
Note: The viewer included with the Systray client is not working properly and it's a known bug. The Pande Group is aware of the issue and is working to fix it. In the meanwhile, don't use it (it's not required to open the viewer to make the client run, having the Systray icon on the taskbar is enough).
You can download the GPU Systray client installer from the Download (http://folding.stanford.edu/English/DownloadWinOther) page. After it has downloaded, run the installer package by double clicking the downloaded file (If it doesn't start automatically, it probably means you need to install the Windows Installer 3.1 package first, which you can get through Windows automatic update). You will see this window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray1.png
Click on the Next button to continue to the License agreement window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray2.png
If you accept the license, click on the I Agree button then click on the Next button. There is no configuration to edit :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray3.png
Click on the Next button to start the installation process. When it's done, you will see the last window :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray4.png
Click on the Close button to end the installation process.
During the installation process, the installer will have created a new folder in the Start menu. You can find it under Start -> Programs -> Folding@Home-x86 as indicated here :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray5.png
There are two shortcuts, the first is to run the program whenever you want and the second is to go in the data folder where the client is storing the work unit's data, configuration and executable files for any maintenance need. For now, we need to configure it so click on the first one (Folding@Home). As you are running the client for the first time, a configuration window will appear :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray6.png
In this panel, if you want to fold under your own username, enter it here along with the team number if you are part of the team. If all you want is to contribute while not caring about a username or team, leave them as is. If you have a passkey associated to your username, enter it (if you want to know what is a passkey and how to obtain one, check this page (http://folding.stanford.edu/English/FAQ-passkey)). When you are done, click on the Connection tab on the top to get to the next panel :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray7.png
The first checkbox should be checked if you want the client to ask before downloading or uploading a work unit. This is useful if you are on a non-permanent connection like dialup or to control when to download/upload. If you are connected behind a proxy, you'll need to configure the client for it (if you need the information about configuring a proxy, ask your administrator). The last checkbox will let you decide if you would like to receive large work units (they have bigger bandwidth and memory requirements). After doing this, click on the Advanced tab to get to the next panel :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray8.png
These are the advanced configuration of the client so if you are unsure about them, you can leave them alone since the defaults are suitable for the majority of users. Here is what each element does :
Core priority : If you are running multiple clients or have another program running continuously in the background, you may need to adjust the priority so it won't sit idle while waiting for free cycles.
CPU Usage Percent : If you don't want the CPU to allocate all the cycles to F@H, adjust the percentage to suit your needs.
Disable highly optimized assembly code : If you are having problems running the client due to a processor incompatibility or any weird error, check this to disable the SSE optimizations. Doing this will cause the client to run slower depending on the workunit.
Checkpointing frequency : Increase or decrease the frequency of Work Unit progress backups. This won't prevent the client from writing the data before the checkpoint if the next frame is completed before.
Do NOT lock cores to specific CPU : If you have more than one core, checking this will allow the client to use any free CPU/core. If it is left unchecked, it will only use one core no matter if others is free or not.
Core Network Address (Advanced) : For future use
Pause work while battery power is being used : This is useful for laptops to stop the client from running when it's on battery power, to avoid draining power.
Additional Client Parameters : This is where you can save the frequently used flags like -verbosity 9 or -advmethods.
Machine ID : This is the client ID and it needs to be different if you are running more than one client under the same OS. An example would be if you are running the Systray client and the GPU2 client at the same time, in which case each client will use Machine ID 1 and 2 respectively.
When you are done, click on Ok. If you entered any Additional Client Parameters during configuration, you may need to restart the client to use them. It will now run in the background with a icon in the Taskbar. You can hover on it to check the current client status but if you want to see what is the last actions of the client, you can check the log file generated by the client. For that, right-click on the taskbar icon and you will see this :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinUNISystray9.png
Click on Status then on Log file to open a notepad window with the log file contents. This is useful to see if there are errors and if you need help, you can copy the contents of this log file to the forum.
Installation (console version)
First, download the console client from the Download (http://folding.stanford.edu/English/DownloadWinOther) page (There is 2 distinct packages, one for Windows XP and 2003 and one for Vista so make sure to pick the correct one for your OS). If you wanted to use a installer, the Console client doesn't come with one so it's suggested to use the Systray client instead. After you are done downloading the package, unzip the package in any place except the Program Files folder (due to potential permissions issues). A good suggestion is to create a new folder on C:\Users\\FAH! for Vista or C:\Documents and Settings\[username]\FAH for XP. You can also place it on the desktop or on a custom folder like C:\FAH\. After you are done unzipping, it's suggested you rename the executable file name to fah6.exe to make the following steps easier to do.
Note: If you are using the Vista GPU Console client, don't install as a service since it's currently not working properly. If you need a unobstructive client under Vista, it's suggested to use the Systray version.
The next step is to configure it by typing the following command (if you used a different one, use the correct name) :
fah6 -configonly
You will see a list of configuration options. Here is an sample with an explanation about each option :
Launch directory: C:\FAH
Executable: fah6
Arguments: -configonly
[16:25:22] Configuring Folding@Home...
User name [Anonymous]?
Team Number [0]?
Passkey []?
Enter your user name (not the Windows user name but your folding name), team number and passkey here
Ask before fetching/sending work (no/yes) [no]?
If you are not on a permanent connection, select this to yes to wait for your permission to upload/download work units.
Use proxy (yes/no) [no]?
If you are connected to a proxy, enter yes and configure the proxy options.
Acceptable size of work assignment and work result packets (bigger units
may have large memory demands) -- 'small' is <5MB, 'normal' is <10MB, and
'big' is >10MB (small/normal/big) [normal]?
This is related to the size of downloaded and uploaded work units. Bigger units will also have bigger memory requirement. If you run on a slow broadband or dialup internet connection, it's suggested to pick small to ease the bandwidth usage.
Change advanced options (yes/no) [no]? yes
If you want to change the advanced options, enter yes but it's not mandatory.
Launch automatically, install as a service in this directory (yes/no) [no]?
If you want the client to run as a service, say yes and it will install a new entry in the services list. Next time you restart the computer, the service will start automatically and run in the background.
Core Priority (idle/low) [idle]?
This adjusts the priority level. Any priority higher than idle can cause some slowdown during general computer usage.
CPU usage requested (5-100) [100]?
This will adjust the percentage of CPU usage. If you want to limit temperature issue or to keep some CPU cycles for more intensive computer tasks, enter a number below 100.
Disable highly optimized assembly code (no/yes) [no]?
If you are having issues running the client, disable this. For 99% of the users, leave this alone since this could reduce the client performance a lot.
Pause if battery power is being used (useful for laptops) (no/yes) [no]?
If you run a laptop, set this to yes to pause if the laptop is not plugged on the wall. This will avoid the client draining the battery.
Interval, in minutes, between checkpoints (3-30) [15]?
Number of minutes between each checkpoint where the client is writing the client progress on disk in case of unexpected interruption.
Memory, in MB, to indicate (1013 available) [1013]?
Set the amount of memory available to the client. By default, it show the full memory amount but if you have programs which require lots of memory, it's suggested to reduce this.
Set -advmethods flag always, requesting new advanced
scientific cores and/or work units if available (no/yes) [no]?
This is the same as using the -advmethods flag. This will allow you to grab workunits with bigger requirements (often with more points value) than the normal units. Keep in mind this will often have a higher risk of failure so use this flag only if you are ready to accept the risks.
Ignore any deadline information (mainly useful if
system clock frequently has errors) (no/yes) [no]?
Set this to yes if your local computer clock is having issues keeping the correct date and time. For 99% of the users, leave this to no.
Machine ID (1-16) [2]?
This is the ID of the client. If you are running more than one client under the same OS, you need to have a different machine ID for each client. If you are installing on multiple computers, you don't need to change this since this is only for installing multiple clients on the same computer.
The following options require you to restart the client before they take effect
Disable CPU affinity lock (no/yes) [no]?
If you disable the affinity lock, the client will pick any free CPU core. Leave to no if you want the client to be locked to a CPU core. If you run a NVIDIA card, you can adjust the affinity by using the NV_FAH_CPU_AFFINITY environment variable (check the NVIDIA FAQ for more details). For this to work, you need to enter no or it will ignore the affinity you configured.
Additional client parameters []?
You can enter the client flags here so you don't have to type the flag each time. -verbosity 9 flag here to make things easier. Don't enter -config or -configonly'' or any single-use flag to avoid issues.
IP address to bind core to (for viewer) []?
For future use
When you are done, the configuration will end and you will be back to the command prompt. You have successfully configured the client so the next step is to start the client. Here are 2 ways :
By clicking on the executable icon (this assumes you entered the proper flags during configuration).
By typing fah6 on the same command prompt window. Enter the necessary flags if you didn't enter during configuration.
Normally, if everything is done correctly, it will be chugging fine. To check this, open the task manager and make sure there is a process called FahCore_xx.exe in the list.
Installation for a multi-GPU system
Here is some specific requirements to follow for the multi-GPU setup to work :
The current multi-GPU installation guide requires some knowledge of the Windows system, if you are having issues, you can ask for help.
If you are running multiple GPU cards with SLI or Crossfire, you need to unlink the cards by disabling SLI or Crossfire in the driver control panel. Also, you need to extend the desktop for the client to recognize the cards.
When Windows ask to look for a driver hit CANCEL. If you let Windows install the driver automatically, there is a big risk of having sub-par performances or client issues.
If you run Windows Vista, you need to have each GPU connected to a monitor (a KVM can also work but not all models of KVM will provide a signal when it's not switched as current monitor) or a VGA dummy plug.
Before you start doing the installation, make sure to grab the latest CUDA driver and the latest client. You can find the links in the Requirements section above. Also, the following guide is based on the GPU Systray client installation so if you didn't install the client yet, follow the Systray instructions above first before following the instructions below.
Note: First of all, make sure the GPU2 client didn't copy the shortcut in the startup folder during installation because we don't want it to start automatically. The current client doesn't do it but previous clients did, hence the warning. The shortcut is usually found in ''Start -> Programs -> Startup".
Next, open up Windows Explorer and find the directory where the installer created a folder under your user name. Below is the path of the folder depending on the OS :
XP : C:\Documents and Settings\[username]\Application Data\
Vista: C:\Users\[username]\AppData\Roaming\
Note: This folder is usually hidden so you may need to type the whole path in the address bar or to enable the option to view all files and folders.
Once you’ve located the directory, copy the folder called Folding@Home-gpu and paste into the same location. Rename the new copy by cutting the “Copy of” off and adding a 2 (or more for extra cards) after the directory name. You will need to repeat the same steps if you have 3 or more GPU you want to use. Here is what it should look :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinGPU1.png
Now, go in the C:\Program Files\Folding@Home\Folding@Home-gpu folder (with Vista, it's in the x86 folder). You should find the client executable here so make a new shortcut of the client (right-click on the executable icon then select Create Shortcut). After creating the shortcut, move the shortcut to the desktop then rename with a short name like GPU1. Don't copy more than one shortcut since you will do it after doing some modifications :
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinGPU2.png
Right-click on the first shortcut then select Properties. It should bring up the following screen:
http://i30.photobucket.com/albums/c338/Xilikon/FAH/WinGPU3.png
Now, replace the Start in: path with the path of the data file which is stored in either those places (replace [username] with your Windows user name) :
XP : C:\Documents and Settings\[username]\Application Data\Folding@Home-gpu
Vista: C:\Users\[username]\AppData\Roaming\Folding@Home-gpu
Make sure there are quotes at the start and end of the Start in: path.
Add the -gpu 0 flag at the end of the Target: path, after the quotes (make sure there is a space between the quote and the flag). It should look like this in the Target: field:
"C:\Program Files\Folding@home\Folding@home-gpu\Folding@home.exe" -gpu 0
Once you are done, the properties should look like this for the first client. Click on Ok to close the panel afterwards :
Target: "C:\Program Files\Folding@home\Folding@home-gpu\Folding@home.exe" -gpu 0
Start in: "C:\Documents and Settings\[username]\Application Data\Folding@Home-gpu" (XP/2003) or "C:\Users\[username]\AppData\Roaming\Folding@Home-gpu" (Vista)
Now that you are done editing the shortcut, it's time to create more for the other GPU cards. Copy the first shortcut and paste as many copies (based on how many GPU cards you want to run) you need on the desktop. Rename each shortcut copy with a simple yet distinct names (to help identify which client) like GPU2, GPU3, etc. When you are done, right-click on each new shortcut and select Properties to edit the properties. This time, since you did most of the configuration above, all you need to do is to point the Start in: path to each data folder that you created and put -gpu 1 flag (or higher for subsequent cards). After you are done, you should have something like that :
Target: "C:\Program Files\Folding@home\Folding@home-gpu\Folding@home.exe" -gpu 1
Start in: "C:\Documents and Settings\[username]\Application Data\Folding@Home-gpu2" (XP/2003) or "C:\Users\[username]\AppData\Roaming\Folding@Home-gpu2" (Vista)
When you are done editing each shortcut, click on the first shortcut and configure your client as demonstrated in the [url=http://folding.stanford.edu/English/WinGPUGuide#ntoc2]Systray installation guide above. The key things to make sure you do are :
On the Connection tab :
Click yes to accept WUs larger than 10 megabytes.
On the Advanced tab :
Check the Core Priority for Slightly Higher
Click do not lock cores to specific CPU
Make sure the Machine ID is different then any CPU or GPU client you have running. Note: default is 2.
Now hit accept and repeat the step above for each shortcut and make sure you pick a unique machine ID for each client. When you are done, all that remain to do is to click every shortcut to start the clients and monitor them closely to make sure they run fine (it's often tricky due to a possible driver version conflict).
Linux Installation Instructions
The following instructions is for the unified Linux 6.02 client. To run in SMP mode, just add the -smp flag to run it.
Go to Terminal. Depending of your desktop engine (KDE, GNOME, ...) the Terminal application can be at different places, but you'll find it. GNOME has it at "Applications->Accessories->Terminal". Open Terminal.
In the Terminal window you should see a prompt that looks something like this: yourusername@yourcomputername ~ $
To get the FAH client going type in (or copy/paste) the following commands:
mkdir -p ~/folding
cd ~/folding
curl -O http://www.stanford.edu/group/pandegroup/folding/release/FAH6.02-Linux.tgz
tar xzf FAH6.02-Linux.tgzNote: If you don't have curl available on your machine, use wget instead:
wget http://www.stanford.edu/group/pandegroup/folding/release/FAH6.02-Linux.tgzBefore you run the client, you will have to unzip it first. After this, execute these commands to make the fah6 executable with the appropriate libs (only if you are running a 64 bit version of Linux) :
chmod 755 fah6
sudo apt-get install ia32-libsNow you should have the FAH client in place and you'll have to configure it. It can be done by running following command:
./fah6 -configonlyAfter setting the configuration there are couple of ways to start the FAH client. One way is to start it is by typing in each time the following command (If you run SMP, put the -smp flag there as well):
./fah6 -verbosity 9OPTIONAL: To make it a little easier for yourself, you can make a script by running the following commands:
echo "./fah6 -verbosity 9 $* &" > fah
chmod +x fahNow you'll just have to run
./fahand all those additional FAH client flags will get added by itself.
Note: All those listed commands MUST be typed/pasted from this little HOWTO to the terminal (window) of your machine.
Example:
user@box ~ $ mkdir -p ~/folding
user@box ~ $ cd ~/folding
user@box FAH $ curl -O http://www.stanford.edu/group/pandegroup/folding/release/FAH6.02-Linux.tgz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 138k 100 138k 0 0 34461 0 0:00:04 0:00:04 --:--:-- 39789
user@box FAH $ tar xzf FAH6.02-Linux.tgz
user@box FAH $ ls -la
total 960
drwxr-xr-x 5 user guest 170 Nov 6 23:58 .
drwx------ 18 user guest 612 Nov 6 23:55 ..
-rw-r--r-- 1 user guest 138145 Nov 6 23:56 FAH6.02-Linux.tgz
-rwxr-xr-x 1 user guest 282796 Nov 4 07:04 fah6
-rwxr-xr-x 1 user guest 60156 Oct 27 16:52 mpiexec
user@box FAH $ ./fah6 -configonly
...
user@box FAH $ echo "./fah6 -verbosity 9 $*" > fah
user@box FAH $ chmod +x fah
user@box FAH $ ./fah
... [U]How to start the linux client as a service
Note: Adding the client as a service in Linux depends on which distribution you are using. The instructions below should work for the majority of distributions available in the market. If nothing works, you might need to do some research to find out what your distribution needs to install as a service.
Do not change accounts or change directory location then create a script named folding by pasting the following commands:
echo "# chkconfig: 345 93 14" > ./folding
echo "# description: will start FAH client as a service" >> ./folding
echo "su - $USER -c \"cd $PWD; ./fah6 -verbosity 9 < /dev/null > /dev/null 2>&1 &\"" >> ./folding
chmod +x ./foldingNote: In the following steps, replace [fahdir] with the value you saw on screen during the previous installation steps (don't include the brackets).
To mark down where you installed the FAH client just run:
echo "[fahdir]=$PWD"Note: All the following steps need root privileges to be carried out successfully.
For Debian-based distributions run:
sudo cp [fahdir]/folding /etc/init.d/For other distributions run:
su - -c "cp [fahdir]/folding /etc/init.d/"Note: If you installed the client under root user account, do this instead :
echo "# chkconfig: 345 93 14" > ./folding
echo "# description: will start FAH client as a service" >> ./folding
echo "cd $PWD; ./fah6 -verbosity 9 < /dev/null > /dev/null 2>&1 &" >> /etc/init.d/folding
chmod +x /etc/init.d/foldingLast step is to register the folding service.
For Debian-based distributions run:
sudo update-rc.d folding defaultsFor other distributions run:
su - -c "chkconfig --add folding"That's all so reboot the computer to make the new script start the client. To check if it is working fine, just go to your folding folder and open fahlog.txt or run:
tail -f [fahdir]/FAHlog.txt