Endless "connecting...."

[BMD]

Honestly, I searched for the forum for an answer before posting this...

My computer (HP Pavilion dv7 Notebook PC, Windows 7) crashed (blue screen). It restarted fine. I restarted FAH (I use console mode). My old work unit was gone, and the status was "connecting" (local Connecting 127.0.0.1:36330).

That went on for hours (OK, not "endless", but still).

I decided to uninstall, delete all data (including registry refs. to FAH/folding), and reinstall.

I had been using 7.1.52, but I saw there was a new version, 7.2.9. So I downloaded and installed that. Same result: connecting, for several hours.

Any ideas?

Thanks,
Brian

[bollix47]

Welcome to the folding support forum Brian.

Could you please post the contents of log.txt using the Code tags in Full Editor.

You should be able to find it in your Data Directory:

Click on Start>All Programs>FAHClient>Data Directory

[BMD]

Thanks for the quick reply!

I actually don't have a directory called Data Directory. All I have under FAHClient is:

/themes
FAHControl.db
config.xml
sample-config.xml

And config.xml contains:

<?xml version="1.0"?>
-<config>
<!-- Created by Installer -->
<user v="Brian_M_Delaney"/> <team v="195315"/> <passkey v="[my passkey]"/> <gpu v="true"/> <smp v="true"/> </config>

[bollix47]

Just to be clear Data Directory is not a directory per say but rather a menu item that should take you to
c:\users\[your user name]\AppData\Roaming\FAHClient assuming you used defaults when installing.

When you say "I use console mode" what exactly are you entering or clicking on to start folding?
Have you tried opening FAHControl? In Preferences is the box next to Autostart under Local Client checked?
Where are you seeing the "connecting" message?
Do you have a dos-like window open for FAHClient after starting?
When installing did you ask that FAH be installed as a service?

Sorry about all the questions but they are necessary in order to get a clear picture of what you're experiencing.

Since you're running on a Notebook you might want to set the client up to run just SMP or GPU but not both. You may be running into a heat problem.

[BMD]

Problem solved! Windows firewall was blocking access.

What I did was uninstall (checking "Data" to uninstall that as well), and then reinstalled, but this time chose the default install option (before I'd been choosing "Custom" install). As before, I'm using both SMP and GPU (I like the heat: my apt. is too cold!). I saw the orange "connecting" as before, but this time, within 5-10 seconds, I was asked by Windows Firewall (I think that was it -- some program asked me this) whether I wanted to allow FAH to access the Internet. That didn't happen the other times.

I think I misspoke in saying "... console mode". I start the program by clicking on an icon on my desktop. (Actually, now that I've installed it using the default settings, maybe it was installed as a service?)

Anyway, everything's working fine now. Thanks again!

[codysluder]

Do you happen to remember which options you picked when you installed the version that didn't work? Default options seem to work and many who modify the options seem to have trouble. Maybe there's a way to assist people like you to avoid bad choices.

[BMD]

I don't remember exactly but I don't think it was anything strange. When I clicked on "custom", I may even have simply left all the preset choices as they were. (I typically chose the custom install option when installing software, just to see what changes are going to be made to my computer.)

Let's see, I can reinstall it and see.

Ah, yes, I chose all the default options, EXCEPT, I chose:

start manually

and

I unclicked "Automatically start FAHControl at login time".

[codysluder]

With those two settings, you would probably be responsible for starting both FahClient and FahControl.

I think there's a setting in FahControl that enables it to start FahClient if it's not already running. Was that setting unchecked? If FahClient wasn't started or starting, you'd get the CONNECTING status.

[BMD]

I'm not sure whether it was checked. (It is now.) Maybe that was the problem.