Questions and Answers :
Windows :
Workunit there but CPDN grabbed a new one...
Message board moderation
Author | Message |
---|---|
Send message Joined: 31 Aug 04 Posts: 1 Credit: 585,966 RAC: 0 |
I upgraded my boinc software and copied out the Projects folder, slots folder and teh .xml files before I upgraded. After I installed the newer version, I copied the files back... When BOINC restarted it grabbed a new workunit.... My old work unit files are still there.... How can I get boinc to reattached the old workunit.. I was a couple timesteps from being finished... I could have waited but I have seen a lot of people talk about upgrading boinc and moving workunits to different machines without too much difficulity.... Any ideas... how to reattached my old workunit files..... Thanks, Pete |
Send message Joined: 7 Aug 04 Posts: 2183 Credit: 64,822,615 RAC: 5,275 |
What version did you upgrade from? If 4.05, I think the CPDN client was upgraded from 4.03 to 4.04 for any version of BOINC after 4.05. If that's the case, I believe that upgrading the CPDN client will download a new workunit, while upgrading BOINC without upgrading the CPDN client will not, say from 4.09 to 4.13. |
Send message Joined: 31 Aug 04 Posts: 13 Credit: 134,268 RAC: 0 |
i have the same problem...i am trying to move a run on my home computer to work and cant get boinc to recognize the old model. i copy /projects, /slots, and all the cpdn .xml type files. then copy straight to boinc folder on work machine. when started, boinc manager just sits there. if i use the installer to "repair" it downloads another model so i have to detach before it crunches. boinc 4.25 at work model ran on 4.25 at home p.s. can the /locale stuff except for default language be deleted safely? |
©2024 cpdn.org