This guide will demonstrate how to use a batch file and the "start" command to run all of your clients from one shortcut or startup entry.
If you don't understand what a batch file is or how to make one, a guide is available here
Normally, when one makes a batch file, it will run all of the commands listed in sequential order, waiting for one process to complete before continuing on to the next. In the case of multiple folding clients, this isn't very helpful because if one is started in this manner, the next one will never start because the process is never finished, meaning you will only have one client running in stead of many.
This is where the start command comes in. If a program in a batch file is preceded by "start", the batch file will continue to run the next lines regardless of the status of the program. This way, all of your clients can be started in rapid succession by running a single file or shortcut.
OR, if your machine logs in automatically (using the userpasswords2 trick (excellent guide by Zodac), you can put a shortcut to the batch file in your start menu startup folder to have your clients start as part of the machine's normal login process.
Heres an example batch file to start 4 GPU clients and one -bigadv SMP client:
-Any flags can be used on the clients via this batch file method the same as a regular shortcut.
-Substitute your file paths instead of mine.
-The quotes are required if there are spaces in the file name.
Please note the "cd" commands before each start command. These are crucial to the successful operation of this file, otherwise all of the files F@H uses to operate (config file, core, etc) will be stored where the program was called from (ie, wherever the shortcut/batch file is), not the directory the program is in.
Using this method on a machine that automatically logs in, one could presumably make a folding rig that can recover from power outages and other accidental reboots without any user intervention (assuming the power comes back eventually)
Enjoy.
If you don't understand what a batch file is or how to make one, a guide is available here
Normally, when one makes a batch file, it will run all of the commands listed in sequential order, waiting for one process to complete before continuing on to the next. In the case of multiple folding clients, this isn't very helpful because if one is started in this manner, the next one will never start because the process is never finished, meaning you will only have one client running in stead of many.
This is where the start command comes in. If a program in a batch file is preceded by "start", the batch file will continue to run the next lines regardless of the status of the program. This way, all of your clients can be started in rapid succession by running a single file or shortcut.
OR, if your machine logs in automatically (using the userpasswords2 trick (excellent guide by Zodac), you can put a shortcut to the batch file in your start menu startup folder to have your clients start as part of the machine's normal login process.
Heres an example batch file to start 4 GPU clients and one -bigadv SMP client:
Code:
cd "C:\\Program Files (x86)\\Folding@Home\\GPU-1"
start Folding@home-Win32-GPU.exe -gpu 0
cd "C:\\Program Files (x86)\\Folding@Home\\GPU-2"
start Folding@home-Win32-GPU.exe -gpu 1
cd "C:\\Program Files (x86)\\Folding@Home\\GPU-3"
start Folding@home-Win32-GPU.exe -gpu 2
cd "C:\\Program Files (x86)\\Folding@Home\\GPU-4"
start Folding@home-Win32-GPU.exe -gpu 3
cd "C:\\Program Files (x86)\\Folding@Home\\SMP"
start Folding@home-Win32-x86.exe -smp -bigadv-Substitute your file paths instead of mine.
-The quotes are required if there are spaces in the file name.
Please note the "cd" commands before each start command. These are crucial to the successful operation of this file, otherwise all of the files F@H uses to operate (config file, core, etc) will be stored where the program was called from (ie, wherever the shortcut/batch file is), not the directory the program is in.
Using this method on a machine that automatically logs in, one could presumably make a folding rig that can recover from power outages and other accidental reboots without any user intervention (assuming the power comes back eventually)
Enjoy.
Too Many Changes to Keep Updating
(13 items) |
|
Too Many Changes to Keep Updating
(13 items) |
