EDIT: Double Post

---

- - - - Rusty - - - -



DC-Vault
Team Ninja's DC-Vault Click Link Here

Your account shows two computers. As long as you have one project in common between them you can attach the slower computer to projects with WU short run times and the faster one for the longer running WU. This should shorten the time it takes to bring things in sync. Once the projects all have a common CPID you can go back to running one project at a time.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

Depending on server settings you may just be able hit update and change your CPID, it will take at least two per project though (P#1, P#2, P#1, P#2). If the servers are not set for that you will have to report or be assigned tasks for the communication to count towards syncing your CPID.

I strongly advise running multiple projects per host on a permanent basis to weather server problems. You can use the standard venues to set different backup projects on up to 4 hosts and achieve nearly the same result as running one project per host. If you use BAM! you can set different resource shares on an unlimited number of hosts.

Your host speed is acceptable for running multiple projects. I have a 650mhz host that runs 10 projects without problems. The BOINC cient may not get work from all of them at the same time though (that 650mhz host normally has work from about 3-4 projects at a time).

---

BOINC WIKI

BOINCing since 2002/12/8

Russ,

This should work. Attach Leiden Classical to all your computers and process 2 WU. These are usually short. (Or use another if they have shorter times). On the one that is Leiden Classical put the next shorter WU project. That should sync you up if the emails are the same.

David

---

Or better yet, Pirates. I don't think you even have to do a WU for it to sync up just so long as you have a common project attached to all computers.

---

Flip, it's only a P4, I will take all of a month to do some of the units, especailly CP

In that case, pick a project (preferably one with shorter-than-average tasks) to attach all your hosts to. You can give it a very low resource share, because the host that’s already dedicated to it, having no other projects, will run it at 100% regardless. That way the others will only interrupt their ‘main’ project once in a while. Once the ‘common’ project has registered all your hosts, your CPID should get synched up.

P.S. You can ‘mix & match’ this strategy with the all-projects-on-one-host strategy however is most convenient, as long as there are enough overlaps to make a continuous thread of connections, direct or indirect—what a mathematician might call “a connected graph”.

---