user id's should not match!
csimon
Acadiana Icrontian
This concerns Folding@home.
Those of you who use ghost (or simular) or duplicate your registry's on more than one computer should check your logs to make sure that you don't have duplicate user id's. If you do then let me know because something can be done to dramatically improve your output!
thanks
csimon
Those of you who use ghost (or simular) or duplicate your registry's on more than one computer should check your logs to make sure that you don't have duplicate user id's. If you do then let me know because something can be done to dramatically improve your output!
thanks
csimon
0
Comments
If you have matching user id's you need to stop the client ...edit the registry by deleting the UserID registry (see below) and restart the client ...stanford will reassign a new user ID which will be different.
Do not attempt this if you are not familiar with editing the registry.
Good find. You pick it up in another forum, or did it dawn on you?
Production has been dwindling for the past few months especially since the ghost.
I wonder who's watching over jumpin_jacks farm?
I fold as jdii1215, team 93. Both machines have THAT set of info. But, since I did not ghost, Stanford's download server sent me a different hash code when I configured each instance(think "downloaded client"). Thus the Client UID was unique for each machine and things worked, and both machine's outputs are credited right to "my" user name and team. Essentially, this becomes a client signature or CLIENT UID with a hash of all the above being made. Hash in this case, is a hex conversion of folding name, Team code, and download instance code. Thus, folding can adjust to individual machines and give machines the WUs best suited to each individual folding machine that is acting as a client for Folding's distributed network.
User Name is not ALL of what user ID the way csimon is talking about it means, and I think some newer folks might misunderstand. Like miinkie might have-- user name is NOT Client UID, each client(software run on a box to fold that manages folding on the flding box's end of things, ie CLIENT) individually needs a code unto itself. Yes, you can use same user name and team, just get clients for each box separately as individiual downloads or do as csimon said if you must ghost.
Folding, for one week, thought I had three CPUs folding, but what happened was on one box where I had turnin problems I had redownloaded the whole CLIENT software twice in one week. This did not fix other things, and folding's end had to fix what I ended up reporting to them in PMs to Vijay for forwarding to the net admin folks.
SIDE NOTE: In my case, was an end to end port to port connect problem-- could get a to server connect in 1/100th the time it took (iterative pinging to server via tracerouting was 1/100th the time it took to get a port connect on accepting server for more than 4 of foldings servers) to negotiate a port connect when any server one of my boxes was trying to turn in to was busy handing out new WUs beyond a certain load point. Now, if I get both boxes overlapping simultaneous connects, both WUs get turned in and I get two different WUs, one per box and credit for both turnins. Do not know exactly why, thankful it just works now. At a guess, some servers were not virtualizing port 8080 connects, or not handing off to other servers to take\accept WUs when busy.
John.
Then there is an icon with blue circles and lines with binary codes for Data, and the type is REG_BINARY. It has 5 groups of characters for its NAME, with 8-4-4-4-12 characters.
Which is the one I need to edit? I can check this against both computer that I currently have folding and change one of them.
Do I just delete it and then delete and reload folding@home and it'll fix itself? What do I need to do to get results from both computers?