F@H folks, I require assistance!

Cuhulainn

Senior member
Jan 26, 2006
365
0
0
I screwed up the initial installation of the GPU client, and cannot figure out how to get back to the advanced options that I was presented with when I first installed it ( I need to change the computer ID to two, I think). I've tried deleting and reinstalling, but that interface never comes back. Please advise! Is there a way to change it at this point?


Thanks in advance!

:beer:
 

CupCak3

Golden Member
Nov 11, 2005
1,318
1
81
you can either edit the client.cfg w/ a text editer or start F@H again w/ the -config or -configonly flags


:)
 

Cuhulainn

Senior member
Jan 26, 2006
365
0
0
Originally posted by: CupCak3
you can either edit the client.cfg w/ a text editer or start F@H again w/ the -config or -configonly flags

Okay, I've done that, and now all I get are early unit ends. Over and over again. I adjusted the core voltage to 1.4v as suggested in the GPU client thread, but the problem persists. Any suggestions?

:confused:

 

GLeeM

Elite Member
Apr 2, 2004
7,199
128
106
F@H does not recommend editing the client.cfg file any other way than by configuring the client. It might be better to delete the file instead of editing it.

Notepad, if set to wrap text, adds formatting and can cause problems with files like this.

In each folding directory I make a special "configonly" shortcut so I can easily enter config again (make sure to stop the client before configuring).
 

CupCak3

Golden Member
Nov 11, 2005
1,318
1
81
Originally posted by: GLeeM
Notepad, if set to wrap text, adds formatting and can cause problems with files like this.

whooops.... good to know!
 

chris huff

Member
Sep 8, 2006
71
0
66
Originally posted by: GLeeM
F@H does not recommend editing the client.cfg file any other way than by configuring the client. It might be better to delete the file instead of editing it.

Notepad, if set to wrap text, adds formatting and can cause problems with files like this.

In each folding directory I make a special "configonly" shortcut so I can easily enter config again (make sure to stop the client before configuring).

Thanks for your patience with me.

I have just installed the client version, but want to change a couple of the options.

I'm unsure how to run -config.

I know in the old dos stuff, if you wanted to run an option, you type fah.exe -config

I don't know how to do that in XP.

I've tried looking around the folding site, but I guess I need a "Console for Dummies" or something.

Thanks for all your help.

***edit***

I am having issues with F@H not giving Kaspersky enough cpu time to complete scans. I checked the process priority and Folding is at lowest and KAS is at normal. - Anything I'm missing?
 

natethegreat

Senior member
Dec 5, 2004
899
0
0
Make sure to stop the client before reconfiguring.

From the folder that you installed F@H into do these steps:

1) Right-click the F@H-Console and select "create shortcut"

2) Right-click the new shortcut and select "properties"

3) In the box labeled "target" add a space and -configonly to the end of the path. Mine looks like this: "C:\F@H 1\FAH504-Console.exe" -configonly

4) Click the "general" tab at the top of the properties window and rename the shortcut to "config"

5) Click "apply" and then "ok" to finish creating the shortcut.

Hope this helps :)
 

Insidious

Diamond Member
Oct 25, 2001
7,649
0
0
In windows XP:

First you stop the folding service;

Start -> control panel -> Performance and Maintenance -> Administrative Tools -> Services -> highlite FAH service and then click on the Stop service link

Now run a batch file to re-start FAH with the options you want. Here's what I use to configure:



cd c:\Scott\Folding at Home CPU 1
fah504-console.exe -local -configonly

You can put whatever switches in it you like

-Sid

PS: OK so I type slowly... at least slower than Nate :p

 

natethegreat

Senior member
Dec 5, 2004
899
0
0
Originally posted by: Insidious
PS: OK so I type slowly... at least slower than Nate :p
I would have been done sooner but for some reason my post didn't get put up the first time I hit reply :roll:

p.s. I don't type, I hunt and peck :laugh:

 

chris huff

Member
Sep 8, 2006
71
0
66
Thanks for the quick replies.

When I was setting up the client, it asked how much memory to tell it I had. I said 256meg (I have 1gig). I noticed it is only using 5-10meg now, where it was using 120 on the GUI.

Did I limit it to the smaller wu's by doing this? I was going to change it back to 1gig to see what happens with the next unit.
 

GLeeM

Elite Member
Apr 2, 2004
7,199
128
106
Originally posted by: chris huff
Thanks for the quick replies.

When I was setting up the client, it asked how much memory to tell it I had. I said 256meg (I have 1gig). I noticed it is only using 5-10meg now, where it was using 120 on the GUI.

Did I limit it to the smaller wu's by doing this? I was going to change it back to 1gig to see what happens with the next unit.

I don't know if you limited it to smaller WUs, but you probably did limit it to non-bonus WUs as most of the bonus WUs use over 100MB.

But the memory setting looks like it works which is nice to know! Thanks for the info :)
 

Cuhulainn

Senior member
Jan 26, 2006
365
0
0
Originally posted by: Cuhulainn
Originally posted by: CupCak3
you can either edit the client.cfg w/ a text editer or start F@H again w/ the -config or -configonly flags

Okay, I've done that, and now all I get are early unit ends. Over and over again. I adjusted the core voltage to 1.4v as suggested in the GPU client thread, but the problem persists. Any suggestions?

:confused:

So... as I was asking before I got threadjacked, any suggestions to this problem?
 

CupCak3

Golden Member
Nov 11, 2005
1,318
1
81
Originally posted by: Cuhulainn
Originally posted by: Cuhulainn
Originally posted by: CupCak3
you can either edit the client.cfg w/ a text editer or start F@H again w/ the -config or -configonly flags

Okay, I've done that, and now all I get are early unit ends. Over and over again. I adjusted the core voltage to 1.4v as suggested in the GPU client thread, but the problem persists. Any suggestions?

:confused:
It sounds like you may have some system instability... download prime95, run two instances and start the "stress test" Let this run for 12 hours or so.
So... as I was asking before I got threadjacked, any suggestions to this problem?
 

CupCak3

Golden Member
Nov 11, 2005
1,318
1
81
everytime i read your thread title, all i can think of is super troopers...


BEAR!.... BEARFOCKER!..... Do you need help?! .... Do you NEED assistance?!


ahhh I love that movie :D :D :D
 

Cuhulainn

Senior member
Jan 26, 2006
365
0
0
Originally posted by: CupCak3
Originally posted by: Cuhulainn
Originally posted by: Cuhulainn
Originally posted by: CupCak3
you can either edit the client.cfg w/ a text editer or start F@H again w/ the -config or -configonly flags

Okay, I've done that, and now all I get are early unit ends. Over and over again. I adjusted the core voltage to 1.4v as suggested in the GPU client thread, but the problem persists. Any suggestions?

:confused:

So... as I was asking before I got threadjacked, any suggestions to this problem?
It sounds like you may have some system instability... download prime95, run two instances and start the "stress test" Let this run for 12 hours or so.

I ran for 12+ hours when I did my overclock. Orthos blended test. It's rock solid.
 

Cuhulainn

Senior member
Jan 26, 2006
365
0
0
Originally posted by: CupCak3
everytime i read your thread title, all i can think of is super troopers...


BEAR!.... BEARFOCKER!..... Do you need help?! .... Do you NEED assistance?!


ahhh I love that movie :D :D :D

Team RamRod. Say it! Team RamRod!

 

Insidious

Diamond Member
Oct 25, 2001
7,649
0
0
I troubleshoot for a living. Not PCs except in the rare occasion, but the principle stays the same.

Start with the assumption that something is wrong. (otherwise, why troubleshoot at all?)

So, now you've tested and believe your system is stable, OK... time to move on to something else.

Remove all traces of F@H from your computer. Remember, F@H has to be NOT running while you uninstall and then erase directories.

Next, read the installation guide(s). Use MDE's guide, read the FAH site looking for instructions, google, etc....

Now, try a fresh install with all you have learned.

Resist the temptation to believe the software doesn't work. It does. For nearly a half-million PCs to date.

Lot's of patience, don't get discouraged. Try and try again if necessary. you'll get it :thumbsup:

-Sid
 

Cuhulainn

Senior member
Jan 26, 2006
365
0
0
Originally posted by: Insidious
I troubleshoot for a living. Not PCs except in the rare occasion, but the principle stays the same.

Start with the assumption that something is wrong. (otherwise, why troubleshoot at all?)

So, now you've tested and believe your system is stable, OK... time to move on to something else.

Remove all traces of F@H from your computer. Remember, F@H has to be NOT running while you uninstall and then erase directories.

Next, read the installation guide(s). Use MDE's guide, read the FAH site looking for instructions, google, etc....

Now, try a fresh install with all you have learned.

Resist the temptation to believe the software doesn't work. It does. For nearly a half-million PCs to date.

Lot's of patience, don't get discouraged. Try and try again if necessary. you'll get it :thumbsup:

-Sid

I've now done all of this, and I still can't figure out what I've done wrong. The result is the same, early unit ends over and over again. Here is a sceenshot of my configuring the GPU client. Have I made any mistakes? This is now the only F@H client on my computer.

Anybody see what I'm doing wrong? Or should I just switch back to my CPU client and be happy with that? I'd like to run both, but I can't figure this out!
 

Insidious

Diamond Member
Oct 25, 2001
7,649
0
0
The only thing I see different than I would have chosen is the CPU priority. I use 'idle'. But I really don't see how that would cause you any difficulty.

Does F@H give any guidance about what ATI drivers are supported? I guess since you are using the GPU client, I would try an un-install and then re-install of your video card drivers prior to the (next) F@H install. I'm not familiar with ATI stuff, but don't they have a tool to remove all their drivers? If you use it, be sure to delete any associated directories after it runs if it leaves any behind. (I suggest running in safe-mode for the un-install)

-Sid
 

CupCak3

Golden Member
Nov 11, 2005
1,318
1
81
indeed, which drivers are you using? 6.10s working great here. I woudlnt' touchthe 6.12s though, that may be your problem..
 

Athlex

Golden Member
Jun 17, 2000
1,258
2
81
Originally posted by: Cuhulainn
I've now done all of this, and I still can't figure out what I've done wrong. The result is the same, early unit ends over and over again. Here is a sceenshot of my configuring the GPU client. Have I made any mistakes? This is now the only F@H client on my computer.

Anybody see what I'm doing wrong? Or should I just switch back to my CPU client and be happy with that? I'd like to run both, but I can't figure this out!

I see two differences in your setup from my GPU client setup-

1. I'm running the GPU client at idle priority instead of low. This shouldn't matter, but Windows' task scheduler is a bit iffy sometimes.
2. It looks like you took the default 'no' answer to -advmethods. IIRC, this option just allowed amber-core WUs to be downloaded on P4 machines, but it may also need to be enabled for FahCore_10 (GPU) WUs to work.

As far as drivers are concerned, the GPU FAQ says that only Catalys v6.5 and 6.10 are supported, but I've been running 6.11 on Windows 2000 for a couple of days with no issues.
 

Cuhulainn

Senior member
Jan 26, 2006
365
0
0
Originally posted by: Athlex
Originally posted by: Cuhulainn
I've now done all of this, and I still can't figure out what I've done wrong. The result is the same, early unit ends over and over again. Here is a sceenshot of my configuring the GPU client. Have I made any mistakes? This is now the only F@H client on my computer.

Anybody see what I'm doing wrong? Or should I just switch back to my CPU client and be happy with that? I'd like to run both, but I can't figure this out!

I see two differences in your setup from my GPU client setup-

1. I'm running the GPU client at idle priority instead of low. This shouldn't matter, but Windows' task scheduler is a bit iffy sometimes.
2. It looks like you took the default 'no' answer to -advmethods. IIRC, this option just allowed amber-core WUs to be downloaded on P4 machines, but it may also need to be enabled for FahCore_10 (GPU) WUs to work.

As far as drivers are concerned, the GPU FAQ says that only Catalys v6.5 and 6.10 are supported, but I've been running 6.11 on Windows 2000 for a couple of days with no issues.

Thanks to all for the help so far, but...

I've now installed the 6.10 drivers, tried changing all of the recommended settings, and I'm *still* getting EUEs over and over. I've fired up the CPU client again just so I can keep contributing, but I'd still like to get this figured.

Any more suggestions??

:confused:
 

Athlex

Golden Member
Jun 17, 2000
1,258
2
81
Originally posted by: Cuhulainn
Any more suggestions??
:confused:

What kind of video card are you running the client on? X1900, X1950, X1800 (XT/XTX/Pro/GTO)? Brand?
I can check some other DC forums to see if anyone is having similar troubles with the same card.
 

Cuhulainn

Senior member
Jan 26, 2006
365
0
0
Originally posted by: Athlex
Originally posted by: Cuhulainn
Any more suggestions??
:confused:

What kind of video card are you running the client on? X1900, X1950, X1800 (XT/XTX/Pro/GTO)? Brand?
I can check some other DC forums to see if anyone is having similar troubles with the same card.

It's the ATI x1900xt Crossfire edition (just the one card, though)
 

GLeeM

Elite Member
Apr 2, 2004
7,199
128
106
Finally found the name of that file!

Do a search on your hard drive for a file named: d3dx9_30.dll

The client needs this file. It missing has been a problem for others.

Could you post some of your log file (probably named FAHlog.txt or something close to that). It could help us troubleshoot.