Hi!
The WUs have a protein number, like p638, and a Run_xx, Clone_xx, Gen_xx, number. If both WUs have the same run, clone, gen numbers then you do need to make sure that you have started the client with the -local switch and make sure that each client has a unique MachineID.
I make a shortcut to FAH4Console.exe and in the Target box of the properties dialog for that shortcut I add the switches I want. After the quote mark add a space, a dash (-), and then the word local. This is what mine looks like: -local -verbosity 9 -forceasm -advmethods
verbosity 9 makes reading the FaHlog.txt file easier, forceasm forces the client to keep using advanced code if the computer crashes, advmethods doesn't do much good anymore but I still try it sometimes.
To make sure that each client has a unique MachineID look at FaHlog.txt files from each folder that contains FAH4Console.exe. Near the beginning there will be a line with MachineID. The number can be any number 1 through 8. So you could run F@H on an eight proc rig!
I hope this helps you, if not post back.
Edit: Just saw your other post. I would delete everything from one of the folders (after stopping clients). Download another console and make sure to change MachineID to 2, during the configuration. The first one should be the default 1. And use a shortcut with the -local switch as in above.
It's exciting watching your fast climb up the ranks
