[Bobibutu]

One of my laptops started processing work units slower.

Looking at the hidden processes running after a restart shows FahCore_82.exe running and I have not yet launched the client. CPU usage 98%

Launching the client the console opens and starts processing ...

Looking at the hidden stuff again shows 2 Cores running @ 49%

I'm thinking of trashing one of them but hate to loose the WU.

Any thots? Running XP

[Drango]

Just a bump to let you know you made the "big board" and your first WU has been reported. WU-Hoooooo.

http://folding.extremeoverclocking.com/user_list.php?s=&a=2&t=36120

And a big warm welcome to all the other new members! (I don't know everyones Freeper name.) "lrenh" is an animal with 9 CPUs folding! Fold on!

[HangThemHigh]

Is one of the two processes the GUI version and one the console version? The instructions warn against that.

Or do you have two copies of the console version running in different directories?

If it's the latter case, I'd just let it run until it finshed a work unit and then trash the one that finished first.

[SC Swamp Fox]

Are you running the console version of the program?

I'm not an expert...but it sounds like you have FAH setup to run as a service, so it starts on system start-up. When you launch the console manually you are running it a second time. If you only have one FAH program and folder, you are working on the same WU twice, at about half speed. I can't imagine this is a good thing.

If you run the console as a service you don't have to (shouldn't) launch the progarm manually. To check the status of the program, look at the FAHlog file or UnitInfo file. The log file contains all of the text you usually see in the console window.