I'm going to join Folding@home hook me up :)

[DAPUNISHER]

I'm in SETI race that'll be over in less than 2weeks win, lose, or draw and I'm gonna switch a P4@2.24ghz and P4@2.4ghz to folding@home as it seems to be a very worthy project Now, which is the fastest software version for winXP? how do I make sure I'm on our TeAm? anything else I need to know? TIA for any and all help and I'm lookin' forward to being a part of the project soon

 

[Reel]

Welcome to the team in advance.

I have downloaded the command line version and have it as a service using FireDaemon on WinXP. I have not noticed any problems with either piece. When you first run the f@h software, it will ask you to enter a username and a team ID. That is how you sign up on our team. The link that will detail all this stuff for you is here.

 

[Slomover2001]

DAPUNISHER,

I'm very new to F@H, but these links are from jliechty's signature block, and should help.

F@H starting links


Gordon

 

[ProviaFan]

The CLI is fastest (and great to run with FireDaemon as a totally hidden service), but the system tray GUI isn't noticably slower (unlike the SETI CLI vs. GUI), and provides convenient access (and visualizations) if you happen to keep yourself logged in all the time (bear in mind that the systray GUI will not run when you're logged out; the CLI will not by default, but if you set it up with FireDaemon, it will run even when no one is logged in). I strongly advise against using the screensaver client, as it is terribly slow.

When you install the client, pick a unique username, and enter the number 198 when it asks for a team number. That is all you need to do to join Team AnandTech.

 

[kadajawi]

and enter -advmethods when using the command line version. That will make your P4s FLY! It should then use the gromacs core, which is amazingly fast (i get around 70 points... while with the tinker core I get maybe around 30 points on my XP. The optimizations work even much better for the P4s). Although it may make your system unstable as its even using the CPU more than Prime95.

 

[Syntax]

Welcome Aboard!!

 

[Slider76]

welcome to the team

 

[DAPUNISHER]

Thanx guys I just tried installing the CLI version and running it as a service with Firedaemon and it seemed to work but it gave me the tinker core so I must have entered the -advmethods in the wrong space It also seemed to show in the log that I was anonymous and team=0 even though it initially excepted DAPUNISHER and team198, was I not supposed to click on the cli I downloaded to try to view the progress since it was already running as a service? Sorry about the questions but I have no idea what I'm doing here I went ahead and deleted the service and the CLI and would appreciate someone posting which questions during setup I should answer yes and no to and how to get the gromacs core. Thanx for helping me muddle through this until I get the hang of it

 

[DAPUNISHER]

Ahh I see I'll have to use a program like folding spy to monitor progress, but what to enter when setting up the CLI and how to get the gromacs core are my real issues......

 

[alnitak]

DAPUNISHER, first welcome to the team! Are your machines running 24/7?

I don't use the CLI version, so I will have to let others help you configure the team number, but I can help with your question about the GROMACS core.

There is nothing special you need to do to get a particular core. When your client requests a work unit from the F@H servers the client will check whether the appropriate core is available on your machine and if not it will be automatically downloaded. Various proteins need various cores, and core updates come out every so often, so you can end up with multiple EXEs in your F@H directory. There is no way to control which work units you will get assigned, but it does seem that if you use -advmethods you are much more likely to get a GROMACS WU.

My GUI version looks like this:

"C:\Program Files\Folding@Home\winFAH.exe" -advmethods


If you can stay logged on 24/7 you might as well run the GUI version, it sounds easier to configure (there is a dialog box to put in the team number, for example).

Anyway, look forward to you popping up on the team stats!

 

[Slider76]

dapunisher, i installed the GUI version and then later swithed to the console version with out removing the GUI version and it automatically detected the settings i had in the GUI. perhaps this might be an easy way for you to get the console version working.

 

[DAPUNISHER]

Thanks guys, I'll give the GUI a try then.

 

[Reel]

In running the CLI, you need to run it once by hand so that it writes a settings file. This is where you put in the username and team ID (and a few other advanced settings you may want to look at if you are a confident computer user). If your settings are wrong, delete the client.cfg file and it will allow you to re-enter the settings. After you run it once and goes and downloads the WU, then quit out of the CLI and start the FireDaemon service. At that point, you should be on auto-pilot.

 

[DAPUNISHER]

Originally posted by: ReelC00L
In running the CLI, you need to run it once by hand so that it writes a settings file. This is where you put in the username and team ID (and a few other advanced settings you may want to look at if you are a confident computer user). If your settings are wrong, delete the client.cfg file and it will allow you to re-enter the settings. After you run it once and goes and downloads the WU, then quit out of the CLI and start the FireDaemon service. At that point, you should be on auto-pilot.

I did that and it seemed to work fine, it also ran as a service when I rebooted to make sure it worked no problemo I should have read about needing another program to monitor progress as I think that is what had me messed up. I also didn't realize that I couldn't pick the core that's used with a particular WU so now that I have a better grasp of the particulars I'll be all set to go here in about 10days, thanx again

 

[Reel]

excellent, looking forward to seeing you on the stats board.