Folding Forum

spazzychalk wrote:new install of windows

If you didn't export the Pandegroup registry key from the old Windows OS installation and import it to the registry in the new Windows OS installation, or clone the old HDD, you in fact did get a new F@H User ID number issued to you when you restarted the F@H client. When ever you start any F@H client, one of the first things it does is check your Windows registry for a F@H User ID number. If there isn't any, the client will get a new one and your processor count will go up temporarily. PG never reissues your old User ID back to you. In Windows, simply changing the Machine ID number in any of your clients will also make your CPU count go up temporarily. There are no ifs, and, or maybes. This is how it works. This doesn't apply to Mac OS X, or Linux clients as they store the User ID number in a file called machineindependent.dat in the F@H folder.

ok. except that didnt happen. its been uploading without increasing the processor count. only possibility may be because the installation came from a factory image cd with all prgrams and all their crap loaded on it? maybe its maintaining. the same windows codes from the image

NO! A factory image would NOT come with a FAH ID already in the registry. The only way for it to get there is for the fah client to put in there when the client is first run. (or if you import that number manually, but since you didn't do that, ignore this part).

This is becoming a bit of a goose chase. Go to each of your clients. Write down the FAH ID and the Machine ID for each. Double check the user name and team # for each one while you're at it. Then post those here. Then a ModAdmin can check to see which one hasn't uploaded in the last 7 days. They don't go missing. It just doesn't work like that.

i was thinking the windows ID #s may be the same because of it. where do i find those #s

spazzychalk wrote:i was thinking the windows ID #s may be the same because of it. where do i find those #s

Look about one page from the top of FAHlog.txt. You'll find your User Name and Team No. as well as the User ID and the Machine ID. Then go back to the chart I provided and check them off, one by one.

The 2 items in RED from the fahlog.txt file for each client!

[16:25:37] - Ask before connecting: No
[16:25:37] - User name: xxx (Team xx)
[16:25:37] - User ID: 7390C3E168052248
[16:25:37] - Machine ID: 1


4 pages of postings to find a missing ID that isn't really missing? Just hasn't reported in the last 7 days because it's either slow or a long work unit? Really?

for quite a while it was missing at the beginning of the thread. as these things do it evolved into a topic of everyone on my team having their processor count doubled, then i swapped hard drives on my duo core with a fresh install of windows but no reinstall of folding just copy/paste and when the client finished it didnt get a new processor count or machine ID. anyway, just had a revelation. the dos client didnt register a new machine ID to the new windows install because it was .... a ---DOS--- client. i only said dos client 100 times in this discussion. if thats really the reason im gonna feel prett ydumb for saying it over and over and not even realizing it

spazzychalk wrote:i swapped hard drives on my duo core with a fresh install of windows but no reinstall of folding just copy/paste and when the client finished it didn't get a new processor count or machine ID.

This is just semantics. No matter how you did it, it was a new install of F@H. When you started the client it didn't find the User ID in the registry because you didn't export it, so it downloaded a new one. It doesn't matter which client you use, all F@H clients for Windows use the same User ID in the registry. Your CPU page shows 13 different User ID + Machine ID combinations going back to 3/23/09, but you seem to be ignoring that fact. Your not running 13 clients are you?

For reference, that console client NOT a DOS client. It won't run under DOS v6. You must have Windows XP or newer for the v6.x fah client, and the Console client simply uses the command line interface, it's not really using DOS files to run. That's why the console client is sometimes abbreviated as the CLI client (command line interface). Not abbreviated as the DOS client. There is a big difference.

ChelseaOilman wrote:Your CPU page shows 13 different User ID + Machine ID combinations going back to 3/23/09, but you seem to be ignoring that fact. Your not running 13 clients are you?

see above where i mentioned everyone on my teams # of processors going way up at the same time.

Let's stick with specific details. Please define "way up." Or stick with your specific situation. Solve one problem at a time. Thanks.

bruce wrote:

spazzychalk wrote:i was thinking the windows ID #s may be the same because of it. where do i find those #s

Look about one page from the top of FAHlog.txt. You'll find your User Name and Team No. as well as the User ID and the Machine ID. Then go back to the chart I provided and check them off, one by one.

Have you done this yet?

Or, if it's easier, provide a list of the last WU that was successfully completed by each of your clients (including the one that's "missing")

We've had 28 posts and we are no closer to a solution than we were when you started the topic. We'd really like to help you, but if we're not getting anywhere because you're unwilling to do your part in diagnosing this problem I'm going to close this discussion.