1) The console version is significantly faster than the graphical version. The graphical version uses up extra CPU cycles to draw those pretty pictures on the screen.
2) command line switches
-advmethods "Request to be assigned work units from new projects, before they are broadly released to the rest of Folding@home. As among the first to try out new advanced simulations, you may wish to post any observations (positive or negative), questions, or issues at the user Forum."
-forceasm recommended for Intel "Instruct the core to use SSE/3DNow assembly instructions if possible, even if it has previously made the determination that the machine may not be handling this well."
-forceSSE recommended for AMD "On machines with an AMD processor, Core_78 gives priority to 3DNow over SSE -- this overrides that." NOTE: AMD TBird processors do NOT support SSE.
-local "Use configuration files from local directory. It instructs the client to read its config information from the client.cfg file in the current directory rather than, on Windows, from the installation directory specified in the registry, or, on Macintosh, the Library/Folding@home directory."
for a complete list of command line switches go to http://folding.stanford.edu/console-userguide.html
e.g. C:\FAH1\FAH1.exe -local -advmethods -forceasm
3) Multiple Instances
This primarily for Pentium 4 machines with Hyper-Threading but also applies to all multi-processor systems.
1st create seperate directories for each instance of Folding; FAH1, FAH2.
2nd place a copy of the folding executable in both directories, create a shortcut for each.
3rd edit the shortcuts with the necessary command line switches, at least the -local switch
4th set the machine IDs to two different numbers [1-8], ideally use 1 and 2.
2 instances on a hyper threading P4 generally improve point output of the machine by 5-10%
Taken from http://www.devhardware.com/forums/de...aks-33532.html








Linear Mode
21 OCZ Fans!