Ultimate Guide To Folding@home

The original explanation said you didn't need the "-forceasm" option because it would use it anyway if available.

Now that I've added that option I see "Extra 3DNow boost OK" in my log file which wasn't there before, so hopefully things should be working faster.
 
Originally posted by {I}{K}{E}@25 January 2004 - 22:48
stopped using it srry, it was causing to much 'errors' and 'lags' on my custom GUI. even on the lowest CPU

{I}{K}{E}
Seti is better in my eyes, nothing against it - both are useful...

I used long time Seti@home, but finally prefer Kazaa running ;) But, no Seti is nice...
 
INSTALLATION GUIDE
Step One: Installing the Client
The first step is to download the Folding@Home GUI client from the Folding@Home client download page. Log in as Administrator (if necessary), and double-click on the downloaded file to start the installation. You will see a welcome screen as shown below. Click next at that screen, and then proceed to click through the license and readme screens.
gui_1_intro.png

Next, you must enter the username you wish to use to be identified in the Folding@Home statistics. If this is the first system you are setting up for Folding@Home, you should check to see whether or not the username that you want to use is already used by someone else (it is ok, however, to use the same username on multiple computers that you own). Go to the Folding@Home User Rankings page and use the box next to the search button to see if the name you want is already taken. If it isn't, you're ready to proceed on to the next screen.
gui_2_username.png

Now, you can choose what folder to install Folding@Home to (the default is fine), and what you want the Start menu group to be called. The next screen asks you to confirm your settings before the installation begins. Finally, after the installation is complete, uncheck "View Readme" and press "Finish."
gui_6_finishinst.png


Step Two: Client Configuration
After the installation has been completed successfully, a configuration panel window will appear. You may adjust your settings in this window. If at any time you wish to change these settings in the future, you may access the dialog again from the menu obtained by right clicking on the Folding@Home system tray icon.

Your username should already be filled in properly if you entered it correctly while installing the Folding@Home client. If it is not, here is your chance to change it. For the team number, enter "34905"
gui_7_cp_user.png

On the Connection tab you will find the network settings. These will probably not need to be changed, however it is a good idea for you to check them out anyway to make sure.
gui_8_cp_net.png

Finally, on the Advanced tab, you will find more in-depth settings. Most of them do not need to be changed, but you should set the Client Type to Folding@Home.
gui_9_cp_adv.png


Step Three: The Client in Action
After Ok-ing the Configuration dialog, the client will begin running as an icon in the system tray. You can right click on it and choose display to observe it as it sets up files and prepares to work on a unit.
gui_10_systray.png

Immediately after configuration, the client will attempt to download the scientific core and begin to process a work unit. If you display it soon enough after configuration, you will see it downloading the core as shown in the screenshot below.
gui_11_core.png

Once the core has downloaded, the Folding@Home client will download its first work unit and begin to process it. When this happens, you will see a screen similar to the one shown below. You can safely minimize the client to the system tray by clicking on its "X" button. To restore it, right click on its icon, and choose Display.
gui_12_fah.png


and thts it...i will be adding GROMACS and other stuff soon..
 
:blink: But I finally moved into 9th place the other day:cry:

I can't believe how long it is taking to catch up to all the inactive members ahead of me, really makes me feel inferior:blushing:

:lol: :lol:
 
Has anyone tryed running this as a service in win nt/2k/xp?

Anyways here are some direction on how to do it. It seems to work for me. Don't blame me if your comp blows up or something if this does something weird.

First make sure the folding@home Client is properly setup.

Then download the consol version of the client and this. Make sure the consol client is working properly first (run it first).

1. Then make a folder somewhere on your hard drive e.g
 
Originally posted by summerlinda@24 January 2004 - 19:23
I'm sure theres an easier way to explain this prog. :blink:

To much abracadabra in this thread to me. Thanks to Slinger i had it working in a few minutes, while reading this thread only gave my headaches.

You have got to remember that theres a lot of foreign non geeks on this board who would like to contribute as well.

Just my 2 cents :)
if they don't understand they can post here and ask ;) :lol:
 
Originally posted by lynx@8 February 2004 - 02:47
I don't know what's happening recently, but FAH is screwing my machines.

I did a full reinstall of XP on my newest machine, now it usually hangs after a few minutes with FAH. It isn't overclocked or anything. If I start FAH and then stop it, it still hangs after a while. But if I never start FAH then it doesn't hang.

My old machine has run for 2 years without hanging. I installed Linux on it the day before yesterday. If I run FAH it hangs within an hour, even if FAH has been cancelled. Without running FAH, it has been up for 30 hours.

Something has obviously happened with the type of projects I am currently receiving (which may have changed because of the reinstallation?), because I never had hanging problems before. I'll keep trying new projects occasionally, but until these problems go away, sadly, I can no longer commit my machines permanently.

I know it doesn't help, but Rocktron and I both had similar problems. They started last Thursday.

I had serious problems with a WU from project 524,
locked up the machine 3 times in a row, every time restarting at 0/500 :angry:
Deleting the work-folder doesn't help as the F@H servers just hand out the same WU over and over again.

As a temp solution I made a backup of my WU several times a day using WinZip.
Shutdown F@H first before zipping it, as F@H writes "shutdown in a normal way" to disk.
Failure to do so (as in a lockup) will restart your WU @ 0/500 when you use the backed up files.

Now what is the cause?
The only thing I can think of:
I used a proggy "CWShredder" mentioned here on the forum. Could it be we all used the same proggy? :unsure:
 
That sucks I checked the team stats and got the same results as you all the stuff done is gone. The units complete seem to have been wiped from the user stats too. Its really weird.

Nothing on the F@H homepage about it either.


I almost always notice the size of the units I get because whenever I leave my computer I open the display and put it full screen.
 
Back
Top