Big Thanks Rusty....
unfortunately I've hit a snag - it seems I can't edit the "Services" part of the registry.. so I've given up on running it as a service and I'll just run it from a script and/or "Startup" (just run it when a user logs in).
But now.. and this is the bit which makes me absolutely mad.. I can't get two instances to run.
From what I see I need to create two separate directories with one copy of the fah3console.exe in each. Then I run "fah3console -config" in one dir to create the config file. I use machineid=1 for this.. then I copy it to the second fah dir and in that config file I change machineid to 2.
Great so far, just like it says in the FAQ
. Note I didn't just copy an installed directory over, I haven't done what is says not to do here
. So, I've just two dir, each with a fah3console.exe, each with a client.cfg, differing by MachineID.
Now if I run one ("C:\dir1\> fah3console -local"), it works. Now if I start the second ("C:\dir2\> fah3console -local") the client.cfg of that instance ("C:\dir2\client.cfg") gets overwritten with some simple three line (incorrect) config. Once I replace C:\dir2\client.cfg and run it ("C:\dir2\> fah3console -local") then the config of the first one gets overwritten.
ARGH! I've browsed the web a bit (I gave up after an hour of fiddling) and it seems to me that the Stanford FAQs, "fah3console --help" and the few posts I've found regarding client.cfg are all about as useful as a serious heart attack.
Oh.. and one other problem.. I looked at the logs and it seems I have about 10 WUs (from running the graphical version) ready for upload but they cannot be uploaded... I'm connecting through a proxy server but I know that it's worked in the past.. and now after fiddling with the console clients it doesn't. I don't think this problem is specific to this dual CPU box though - another single CPU box hasn't been able to send WU either. I've tried three proxies. I checked the status of the server and supposedly they work.. but when I telnet to them (on port 8080) it connects and then just disconnects.
This whole F@H things is really infuriating with the really poor documentation and debugging features ("-verbosity 9" is useless).
Any ideas? am I missing something obvious? I'm pretty sure I've tried all combinations but maybe I've missed something.
BTW.. if I'm behind a proxy running two separate (say single CPU machines for now) F@H hosts then I don't need to fiddle machineid for each do I?
Thanks and sorry for the general grumpy tone,
PS One last Q.. if I copy the "work" directory from the PCs which cannot return the results to a computer at home, which repeatedly has successfully returned results then will it work? Or do the files in "work" have something specific to the machine the were computed on?