Page 1 of 1

Bit of a problem.

Posted: Fri Mar 14, 2014 9:44 pm
by TheHiding
Ok, so F@H stopped launching for me.
It would pop up in task manager then close out immediately. Never came up in the sys tray.

After messing about a bit, I decided to reinstall it.
Left the data directory in place. Same problem after reinstall.

Moved the data directory to a new location. F@H started up normally, asked for config info. Name, team, pass key etc.
Shut F@H down copied the old config in, and it wouldn't launch again. Deleted the config and let it create a new one, entered all my info again.

It's folding new WUs now, but I'd like to finish the other ones that I copied out to the new location if that's possible.
I've got it set to finish both WU right now. Do I just need to copy the '00' and '01' folders from the 'work' folder back to the proper location once the current units are done or is there more to it?

Can I do just the CPU (00) folder when that one is done? And then the GPU(01) when that one finishes?

Re: Bit of a problem.

Posted: Fri Mar 14, 2014 9:57 pm
by PantherX
Welcome to the F@H Forum TheHiding,

Unfortunately, it isn't that easy to transfer WUs. Given that it is all on the same system, you can do the following only if the old configuration and the new configuration is 100% identical. If there is a mis-match, especially in the Slots, the WUs could be dumped.
Old location -> D:\Folder\FAHClient
New location -> C:\Folder\FAHClient

Now, once all the WUs have finished, you exit FAHClient to ensure that it isn't running at all. You then delete all the files in the new location and then cut/paste the files from the old location to the new location. Be careful since this will override you configuration and if the old one is incorrect, this may not work.

Re: Bit of a problem.

Posted: Fri Mar 14, 2014 10:23 pm
by TheHiding
Well, not going to put the old config back, as that seemed to be what was stopping the program from running at all.

Re: Bit of a problem.

Posted: Sat Mar 15, 2014 12:14 am
by bruce
One way to make sure that FAHClient starts and then dies immediately is to edit config.xml manually and make a syntax error. That's why we insist that you use FAHControl to make all changes to the configuration.

(It might be other things, too.)

Re: Bit of a problem.

Posted: Sat Mar 15, 2014 2:13 am
by P5-133XL
I would suggest that you shut down the folding client; delete the config.xml; and then restart the folding client. The client will simply create a new config.xml with new slots and default settings.

Re: Bit of a problem.

Posted: Sun Mar 16, 2014 6:21 am
by TheHiding
bruce wrote:One way to make sure that FAHClient starts and then dies immediately is to edit config.xml manually and make a syntax error. That's why we insist that you use FAHControl to make all changes to the configuration.

(It might be other things, too.)
Ya, I never even looked at any of the files involved with the program until after it wouldn't run, so my situation would fall in the other things.