I'm having a problem with the CPID that is currently showing on my account at Milkyway; cpid ending in ".....6blC".
For some reason this cpid refuses to migrate into the correct "CPID" at Boincstats; 3617b699c88dc109cfad443c0168912a.
Is there anyway the erroneous CPID can be "over-ridden" or corrected at your project. I would really like to get back on-line with "Milkyway" as I have to suspend the project while trying to resolve the "split CPID" issue at Boincstats.

hmmm...youre going to have to give me more information on this as i am not familiar with CPIDs. What would you want it to be overridden to...and are others migrating as you say...or are they the same both places?

---

Dave Przybylo
MilkyWay@home Developer
Department of Computer Science
Rensselaer Polytechnic Institute

Mr/Mrs/Ms, Butts, I see your similar post over at Orbit.

It can take a couple 2-3 days for the CPID to link up properly. Each detachment resets the clock (I think). Patience has been the only thing required (well, patience and having the exact same email addy at each project). I know of no way to force them to sync up.

hope this helps
tony

---

Mr/Mrs/Ms, Butts, I see your similar post over at Orbit.

It can take a couple 2-3 days for the CPID to link up properly. Each detachment resets the clock (I think). Patience has been the only thing required (well, patience and having the exact same email addy at each project). I know of no way to force them to sync up.

hope this helps
tony

thank you astro for your response in this matter.

---

Dave Przybylo
MilkyWay@home Developer
Department of Computer Science
Rensselaer Polytechnic Institute

your welcome. I am starting to doubt the "detachment" resetting the clock...bit. All that a user can so is:

1. ensure same email addy at all projects (the email addy is THE unique account identifier)

and

2. wait

your welcome. I am starting to doubt the "detachment" resetting the clock...bit. All that a user can so is:

1. ensure same email addy at all projects (the email addy is THE unique account identifier)

and

2. wait

The user also needs to ensure that there is a path from server to client to server that covers all projects. The simplest way of doing this is to have a single computer that is attached to all projects. But schemes such as computer 1 attached to projects A and B, and computer 2 attached to projects A and C will work as long as project A has the oldest join date. There is a fix that is upcomming that will fix this so the CPIDs will synchronize even if the project with the most recent join date is the one that is in common.

---

BOINC WIKI