The CPU console will only run on one core. You need to run 2 instances to get both cores running. So, running one instance with default settings should work.
As far as the switches are concerned, I only use -advmethods and -forceasm.
Thanks for the info. Wasn't sure if you were supposed to specify which core to run on.
I'm not sure why you need to have it wait 30 minutes? It starts when you stop using the CPU, and it stops (right away) when you use the CPU again. It has been shown that running F@H in the background all the time slows you down by about 0.01%.
Well for a couple of reasons. First, I don't want another window to deal with, and installing it as a service is complicated. (Don't you have to do more than say yes when it asks?) Secondly, my CPU is so slow, that anything less than 100% may not be worth the time.
As for the batch file, I copied the F@H exe's location and used the "-local" arguement. But F@H starts running in the location of the .bat file! So it starts by asking me my user name etc. I'm confused!
I thought the local arguement fixed this. Even without local, it still starts from the directory the bat file is in. How do I fix this?
And in the second line of the .bat file, I have the location of the GPU client. It fails to run at all. If it matters, I have quotes around the locations.
Thanks everyone! (I seem to have the most F@H problems