Thanks for this, it helped me quite a bit when I got my 2nd system running tonight and I was trying to connect remotely from my daily driver. After entering the password in FAHControl -> Configure -> Connection and Remote Access, then restarting the client: Voila! Remote connection established!Finally, got the slot configuration nailed down after trial and error and most of a day. I kept going to the WEBControl and pressing the Stop Folding button. That only pauses the slots. It doesn't actually stop the fahclient process which means when you click the Start Folding button it just reactivates the slots. It doesn't re-read the config.xml. I also edited the config.xml while the slots were paused, then when I issued the stop for the fahclient it over writes the config.xml at shutdown so all my changes were gone. Lesson learned, if you edit the config.xml file, stop the fahclient process and then do the editing.
Yes, if you can get the FAHControl app working.Is there a way to see folding tasks run on each computer like in BOINC?
We can't all run server farms. Like I always say, every credit counts and we value the small crunchers as well as the large! I'm looking forward to getting back on Folding as soon as we get through our WCG work!From now on I have only two machines: one Dell Desktop (four CORE), running Windows 10, focused on WCG (mainly OPN) and a Dell Desktop (octa CORE with a NVIDIA GPU card), running Windows 10 and FAH 7.6.21. Stay strong, people, and may God bless us all!