WTF? my F@H config reset somehow

[lobadobadingdong]

just noticed my F@H config on my fastest cruncher reset to anonymous with no team ID. I've been wondering why daily output has dropped so much the last couple of days.

anyone ever have this happen before?

 

[Khyron320]

It happened to me and i have no idea why

 

[GLeeM]

anyone ever have this happen before?

I haven't, but this is a good heads up for everyone to check their rigs!
Check the FAHlog.txt file for a line that looks like this:
[21:34:13] - User name: GLeeM (Team 198)
lol, but with your user name

Are you using the new V5? And if so, the console or the GUI?
Maybe this is something we can figure out.

Thanks

 

[lobadobadingdong]

I'm using the v4.00 GUI.

It's the only machine I've noticed that did this, but one of my crunchers isn't at my house (my wifes pc at her office) I'll have to check it in a few days to be sure.

 

[ProviaFan]

That's weird, I don't know why that would happen.

Just checked my systems, though, and they all are ok now.

 

[GLeeM]

The GUI stores some information in the registry. (This is the reason that when using a console on a computer that has had the GUI installed must use the -local flag)

It also keeps some info in the "client.cfg" file. Which they say is not editable. It needs to be changed by the client.

I know that with the console if you delete this file the next time you start the console it will enter config mode with blank defaults.

If you use the -config flag and the client.cfg file is OK, the prompts will suggest your user name and team name that are in the client.cfg file.

I can't remember how config works with the GUI.

Could the config file have been deleted or the GUI been re-configured?

 

[lobadobadingdong]

I haven't touched it, only thing I can figure is that I had to do a hard reset the other day because windows locked up while switching users one day. (which in and of itself was a little strange)

 

[GLeeM]

If the client had the client.cfg file open when the computer locked up it may have gotten corrupted then.

The GUI must make a new default client.cfg file and continue on its merry way, leaving you at unawares.

The console begins in config mode if the client.cfg file is missing.