How could it be unsafe?
hmm... it's been around a day that I have been running this program, but it's not showering anything when I look at my User stats. Does it take awhile to update or something?
@Godwynn.
I'd give the WU a bit of time yet, they often take a while before giving you a sensible finish date. If you want a better estimate now, have a look at your log and see how long it takes for each step and multiply up by the remaining steps to get the time to finish. If your worried about the laptop 10 hours a day etc you could drop the max processor usage down from 100%, if you do this and want an eta on the current work unit though you'll have to factor it into your calculations.
There should be a log file somewhere called FAHlog.txt. Mine is in the same folder as the rest of my FaH software. If you open that in Notepad you should be able to tell whether FaH is doing anything and what progress it's making.
Here's mine currently (the SMP client isn't very good at writing to the log, so you sometimes get broken lines of text):
Spoiler :
[07:49:58] Project: 2605 (Run 15, Clone 256, Gen 16)
[07:49:58]
[07:49:58] Entering M.D.
[07:50:15] - Starting from initial work packet
[07:50:15]
[07:50:15] Project: 260Entering M.D.
[07:50:15] ne 256, Gen 16)
[07:50:15]
[07:50:15] Entering M.D.
[07:50:21] mdrunner cpfilename:
[07:50:22] g local files
[07:50:22] Extra SSE boost OK.
[07:50:22] ocal files
[07:50:22] Extra SSE boost OK.
[08:01:58] local files
[08:01:58] Completed 5000 out of 500000 steps (1 percent)
[08:13:52] Writing local files
[08:13:52] Completed 10000 out of 500000 steps (2 percent)
[08:25:30] Writing local files
[08:25:30] Completed 15000 out of 500000 steps (3 percent)
[08:37:07] Writing local files
[08:37:07] Completed 20000 out of 500000 steps (4 percent)
[08:48:44] Writing local files
[08:48:44] Completed 25000 out of 500000 steps (5 percent)
[09:00:20] Writing local files
[09:00:21] Completed 30000 out of 500000 steps (6 percent)
[09:12:15] Writing local files
[09:12:16] Completed 35000 out of 500000 steps (7 percent)
[09:23:57] Writing local files
[09:23:57] Completed 40000 out of 500000 steps (8 percent)
[09:35:35] Writing local files
[09:35:35] Completed 45000 out of 500000 steps (9 percent)
[09:47:13] Writing local files
[09:47:14] Completed 50000 out of 500000 steps (10 percent)
[09:58:51] Writing local files
[09:58:52] Completed 55000 out of 500000 steps (11 percent)
[10:10:43] Writing local files
[10:10:43] Completed 60000 out of 500000 steps (12 percent)
[10:22:21] Writing local files
[10:22:21] Completed 65000 out of 500000 steps (13 percent)
[10:34:00] Writing local files
[10:34:00] Completed 70000 out of 500000 steps (14 percent)
[10:45:39] Writing local files
[10:45:39] Completed 75000 out of 500000 steps (15 percent)
[10:57:18] Writing local files
[10:57:18] Completed 80000 out of 500000 steps (16 percent)
You can see that in my case it's doing 1% of the WU every 12 minutes or so. The full 100% should therefore be done in 20 hours.
You add the -local flag to the client that you want to run in a different directory from what you originally installed it in, usually the second client you install. It then takes the settings from the directory it is run from (ie: locally) rather from the original folding at home directory.
It doesn't hurt to put it on the first one as well, but I don't think it is essential.
When you first run the second client, run it with -configonly as well as -local. It will then allow you to set it up, including Machine ID and exit before downloading a WU. This will allow you to check that you've entered everything correctly including team name etc before starting a WU.
The easiest way to add these flags is to copy the shortcut that you use to start folding and add the flags in that.
PS: if you look you're now back on the EOC results page
I use Windows ME. This is my shortcut. Right click on it and choose properties then add the flag to the target line.
Ignore the vertical line before the -local flag - that's just the cursor...