Closing the F@H Console

[asterasy]

Is there some kind of special way to do this? Because I lost 45 steps on one of my 1500000 projects today when I restarted my computer, and want to know how to prevent that from happening in future.

[Xantor]

It's because the console saves your work in between certain intervals of time. You should go into the console and change the option "Interval, in minutes, between checkpoints". Set it to 3 (minutes). Now, your work will be saved every 3 minutes. Good luck :)

[bobletman]

I tend to make it save my work every 10 minutes. But 45 steps is a lot what was your previous save interval?

[peti1212]

I tend to make it save my work every 10 minutes. But 45 steps is a lot what was your previous save interval?

Does it have any advantage if you make it save later instead of 3 minutes?

[Xantor]

Does it have any advantage if you make it save later instead of 3 minutes?
I guess it puts less stress on your processor. I haven't investigated how much ressources folding takes when saving yet.

Back to the first question, I think the console is suppose to save the WU whenever it exits. I am guessing that it was stopped abruptly and so it was not able to save the WU. The proper (probably full-proof) way to shut down the console would be to go into Services (services.msc) and stop "FAH********"

[werty316]

Its save the progress of your WU everytime the interval checkpoint passes, just reconfigure it to 3 mins and you should be fine.

Lowering the interval checkpoint time to 3 mins would put just as much stress on the calculation time if it were set to 15 mins since all that is written is the progress of the current WU.

[asterasy]

It saves on an interval of 15minutes, it was saving properly. However, I closed it down by pressing the 'X' on the console window (I guess that's considered closing it abruptly). And then when I got back into windows and re-opened the console, it gave me a 'FILE_IO_ERROR' message. Was I supposed to stop the FAHCore in Services before I restarted my computer?
And my previous save was about 10 minutes prior to restarting, so, probably still at 45 steps.

[werty316]

If you have it running as a service you wouldn't see a window of the console.

[asterasy]

Is it supposed to open a console by itself on startup if I have it running as a service? Because mine doesn't : /

[werty316]

Is it supposed to open a console by itself on startup if I have it running as a service? Because mine doesn't : /
If its set as a service, yes. If its not set as a service you either have to open it manually everytime you reboot or create a shortcut in the "startup" folder so the console(s) windows open automatically whenever you reboot your computer.

[Xantor]

Closing the console via the window isn't good for it I think. I use it as a service (type yes in the options) and I haven't had any problems so far. When running as service, a window of the console will not appear. It will run in the background

[asterasy]

Alright, so I don't need to worry about the console not showing up. Awesome.

[Xantor]

Alright, so I don't need to worry about the console not showing up. Awesome.
:keepfolding:

[srpeters18]

I'm not running it as a service either, but I figured out yesterday that instead of just closing the window, if you CTRL+C it, it pops a message at the bottom of the console (too fast to read it) but it doesn't tell me it was closed abruptly and I don't lose any work.

[Xantor]

Can't say anything about that. I have not tried myself. :icon_tiphat:

[werty316]

I'm not running it as a service either, but I figured out yesterday that instead of just closing the window, if you CTRL+C it, it pops a message at the bottom of the console (too fast to read it) but it doesn't tell me it was closed abruptly and I don't lose any work.
"CTRL+C" is a keyboard shortcut to close a window and its the same thing as pressing the "X" on a window. It makes no difference which method you use.

[srpeters18]

It does, in windows. In a command prompt, it works just like it used to in DOS. Just like when you ping an IP with the -t switch it will just keep going until you press CTRL+C, won't close the window, just return you to the prompt. When I close the console window the the "X" the next time I start it tells me that it was shut down improperly and its resuming from the last save point. When I do CTRL+C, I don't get that error upon relaunch and it will tell me I am so many steps in, usually an odd number because it actually saves it when you exit. :wink:

[asterasy]

Yea, that happens to me too srpeters. Ctrl+C works like a charm though.

[werty316]

I've never had any problems using either method.