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?
Bit of a problem.
Moderators: Site Moderators, FAHC Science Team
-
- Site Moderator
- Posts: 6986
- Joined: Wed Dec 23, 2009 9:33 am
- Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB
Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400 - Location: Land Of The Long White Cloud
- Contact:
Re: Bit of a problem.
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.
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.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Re: Bit of a problem.
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.
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.)
(It might be other things, too.)
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
- Posts: 2948
- Joined: Sun Dec 02, 2007 4:36 am
- Hardware configuration: Machine #1:
Intel Q9450; 2x2GB=8GB Ram; Gigabyte GA-X48-DS4 Motherboard; PC Power and Cooling Q750 PS; 2x GTX 460; Windows Server 2008 X64 (SP1).
Machine #2:
Intel Q6600; 2x2GB=4GB Ram; Gigabyte GA-X48-DS4 Motherboard; PC Power and Cooling Q750 PS; 2x GTX 460 video card; Windows 7 X64.
Machine 3:
Dell Dimension 8400, 3.2GHz P4 4x512GB Ram, Video card GTX 460, Windows 7 X32
I am currently folding just on the 5x GTX 460's for aprox. 70K PPD - Location: Salem. OR USA
Re: Bit of a problem.
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.
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.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.)