fordyce0593 wrote:I think this is correct. Everything is running smoothly since two hours.
Yes, that is correct.
fordyce0593 wrote:Thanks to you all, you are really efficient.
You're welcome!
art_l_j_PlanetAMD64
Over 1.04 Billion Total Points
Over 185,000 Work Units
Over 3,800,000 PPD
Overall rank (if points are combined) 20 of 1721690
In memory of my Mother May 12th 1923 - February 10th 2012
If you have any idea how you got two copies of FAHControl & FAHClient to start at exactly the same time, we might be able to figure out a way to prevent that from happening to somebody else. Nevertheless, the important thing is that you've got it working correctly now.
One copy is launched automatically on booting.
I suppose I lauched the second one inavertently.
I did that in the past with the previous version of FAH, however I was immediately warned that "another version is running".
In this case the safety, if any, has not worked properly.
I am sure no second occurence was visible in the task bar.
By the way FAH is running smoothly since yesterday.
I have been so happy to get such a nice and efficient help.
Thanks to all.
Fordyce
fordyce0593 wrote:One copy is launched automatically on booting.
I suppose I lauched the second one inavertently.
I did that in the past with the previous version of FAH, however I was immediately warned that "another version is running".
In this case the safety, if any, has not worked properly.
I am sure no second occurence was visible in the task bar.
By the way FAH is running smoothly since yesterday.
I have been so happy to get such a nice and efficient help.
Thanks to all.
Fordyce
Thank you very much for your help, this is good information on an important problem with dual FAHClient/FAHControl being launched!
art_l_j_PlanetAMD64
Over 1.04 Billion Total Points
Over 185,000 Work Units
Over 3,800,000 PPD
Overall rank (if points are combined) 20 of 1721690
In memory of my Mother May 12th 1923 - February 10th 2012
I got this when I clicked on the FAH client button which opened the web client and then windows finished loading the regular client at the same time. Killing the web client version in task manager fixed it up immediately.
I normally recommend that you choose to use EITHER WebControl or FAHControl (the one designed for experts). Perhaps that choice needs to be made at install time to avoid conflicts like the one you mention.