Are we talking about setting up FahMon?

 

I suspect you are running the clients both using the service and by clicking the EXE. This is not good as they will conflict with each other and slow down work. The service should be the only client running. One of the great things about the service is that you shouldn't have any DOS boxes while the client is running.

Open up Task Manager and find the FAH502-Console.exe processes. Look in the user name column (if you don't have the user name column go to View > Select Columns and turn it on.) If a client was started by the service, it should have SYSTEM in the user name column. If it was started separately by you, it should have your username.

What do you have?

 

When all your FAH installations are up and running execute FahMon from any direcotry, it does not have to be the same one as the FAH one. When you're at the main FahMon window right click in the upper left frame and click "Add a new client". Name the client (it can be anything) and browse to the location of the console. It should now load up when you click on the entry for that client. It's not exciting to watch as it moves through the work very slowly. It's just to see what it's doing; it's not entertainment.

Also, what machine is this that you've got 3 consoles running? If it's a Hyperthreaded Xeon box like mine you'll discover that if you allow -advmethos for all of then it hurts performance by saturating the system bus talking to the RAM. Also be sure to keep each console in a SEPARATE directory. Otherwise it gets confused looking for work files and will fail to work. You must also have a unique Machine ID number for each console or only one will run. I use one through 4 but you can use anything you want just as long as a number is not duplicated in the same system.

Oh, and you're not being a pain, we love to do this sort of stuff (at least I do).

 

How many times did you run and set up the console? One is running as a system service and the other is running locally. If they're actualloy both the same program (the smae file being executed) it won't work. If you want another client so that both CPUs get used, you'll have to copy FAH502_console.exe to a DIFFERENT directory and configure it again. It's the same deal as before, just in a different spot. Once that's done exit out of all the console windows and open up services.msc. FInd the FAH entry(ies) and click Start. That should push the CPU to 100%



EDIT: If the console has just started a WU FahMon won't be able to predict when it'll be done. Give it a bit of time to establish a pattern.

 

OK... as you have a dual-processor machine, two FahCore_78s taking 50% CPU each is what you should have. But it looks like one of them is being started by the service and the other directly through a DOS box. What you need is two separate services running.

I don't have any experience with setting that up as I don't have a dual-CPU system, but you may be able to help, Billy? I suspect you can create the second service just like you did the first, except with the client in a different folder.

 

Exactly. For instance, I put the first client in a folder called C:/Fold/1 The second gets a copy of the console in a different folder called C:/Fold/2. To set it up it's exactly the same procedure as setting up one, including the registry edits for things like -forceasm, -verbosity 9, and -advmethods. The only difference is that you must enter the advanced options and change the second installation's Machine ID to some number not equal to 1.

 

It's very good. Now to use the other CPU you must copy FAH502_console.exe to a different folder (it can be a subfolder of what you're already suing). Run it again, exactly as you did to the first, but in the end change the machine ID to 2. When it finishes with the configuration press Ctrl C to exit the command window. Open up services.msc and start the FAH service there that is not funning. You can then make your batch files to turn on and off the Folding processes.

 

When you turn in your first WU you'll appear on the stats pages.

Give FahMon a bit of time to figure out how long it is going to take to finish the work. It hasn't enough checkpoints to establish a rate of completion yet.

 

I leave mine (about 30 of them) on 24/7 whenever possible. The computer doesn't get too much computing done when it's off.

 

When the client detects instability it will disable SSE/SSE2/SSE3 optimizations in those WUs that use such assembly optimizations. -forceasm tells it never to turn them off.

 

No worries... as Billy said, we kinda enjoy it

As long as possible I try and keep this machine on as close to 24/7 as I can, but it's in my bedroom and sometimes I can't sleep through the noise so I have to turn it off sometimes for a few hours.

 

Indeed, it actaully helps keep up my project dolphin scores