Posts by James Cridland

1) Questions and Answers : Preferences : Keep Work for xx Days not Working Correctly? (Message 2110) Posted 30 Aug 2004 by James Cridland Post: > One of the features of 4.xx is pre-emptive scheduling, which will allow BOINC > to switch projects every hour. This means you will be able to do work for > other projects while still working on the big WUs CPDN has. As soon as the > other projects come online with the new CC, we shall see how well this works. > :) Now that SETI have upgraded to v 4, I've today successfully downloaded a SETI work unit to go with my CPDN one. BOINC temporarily stopped my CPDN unit, and is currently chomping through a small SETI unit. Once it's finished, I'm presuming it'll go back to the CPDN unit again.
2) Questions and Answers : Windows : New BOINC version wiped out previous data and won\'t run other projects (Message 2095) Posted 29 Aug 2004 by James Cridland Post: FYI, Seti have just converted over to v4 of the main BOINC core client. Instead of getting a 'you need to use v3.02' message, I'm now getting a 'no work available' message (as I'd expect, since everyone's changing over today).
3) Questions and Answers : Preferences : Multi-project preferences (Message 2027) Posted 28 Aug 2004 by James Cridland Post: Now, then: I\'m running Seti and Predictor, and also climateprediction. Each of them is set for 33% of my processor time. It strikes me that when a CP work unit will take my little laptop 90 days to complete (ack!), then it\'ll not manage to get any work done on Seti or Predictor in the meantime. And, since I\'ve said I want to share 33% of my processor time between these projects, does that mean I\'ll not work on another CP work unit until a further 180 days after I report it back again? Or will it be a bit cleverer than that, and stop chomping my CP work unit for a bit, so it can chomp through a Seti/Predictor unit? All academic until Seti/Predictor move up to Boinc v4, but I\'m curious to know what might happen. James (I do have faster machines, too, y\'know!)