I use a trick: when i know that my pc will be on for a several days , i just change to 10 days of amount of work and it downloads several WUs. Works fine

---

By your command !!!

Changing the number of CPUs (2 to 4) will affect the amount of WU download after the change? The amount of WUs and deadline it will be the same?

Yes changing # of CPUs will effect number of tasks the machine will download from that point forwards. Actually BOINC will adjust how much it gets based on the performance of the machine on a regular basis.
The deadline is set when you download the tasks. So it will remain unchanged.

If you upgrade a machine or move all of the work to a faster one it is no problem at all. BOINC will adjust what goes on without any user intervention. Normally it does this on the slower/cautious side. If you normally have 10-15 tasks in your cache and then move form 2 to 4 CPUs it isn't necessarily going to double the tasks in the queue.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the BP6/VP6 User Group today!

Changing the number of CPUs (2 to 4) will affect the amount of WU download after the change? The amount of WUs and deadline it will be the same?

The BOINC core client asks for work in seconds, so doubling the number of CPUs will double the amount it asks for. The servers will send about twice as many WUs in response. Deadlines won't change, they're simply a time limit for each WU which is set by adding the maximum duration set by the splitter to the time when the task is sent to a host.

                                                                   Joe

Changing the number of CPUs (2 to 4) will affect the amount of WU download after the change? The amount of WUs and deadline it will be the same?

---

By your command !!!

When moving work from one machine to another:
1) Any work that has not been processed will run fine.
2) If you are running the same applications the tasks that are in process will run fine.
3) Older applications run fine on newer hardware. If you want to change to a different application I suggest suspending any unprocessed tasks & finishing ones that are partially done. Then change the applications & unsuspend the tasks.

I have had a few invalid for partly processed tasks. Only when I moved work from one machine to another & changed the application. Like SSE2 x86 to SSSE3 x64.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the BP6/VP6 User Group today!

I've never had a validation problem when moving the entire BOINC Data directory from one computer to another (don't do much GPU crunching though). I'm sure they would have validated normally.

Since I transfered my Hard Drive from my dead computer to this other computer, Different machine specs , Duel core instead of single , ETC. will the wu's i had on the other machine still validate , or will they be invalid or error out ?

shoild i run them or just abort them ?

I see you've aborted them, you could have run the CPU tasks. It's just as if you had upgraded the existing system; as long as the same applications will work BOINC is happy. The servers think you still have some GPU tasks. If they're not ghosted and you're going to try to get that set up in the new machine BOINC will hold them until the hardware is ready.

                                                                   Joe

should i run them or just abort them ?

Abort them all then click the Projects find Seti@Home select it with 1 left click so theirs a blue line. Now in the left hand pane click Update

OK, I aborted all tasks and did update...

at least they can be re-scheduled now...

---

should i run them or just abort them ?

Abort them all then click the Projects find Seti@Home select it with 1 left click so theirs a blue line. Now in the left hand pane click Update

---

Since I transfered my Hard Drive from my dead computer to this other computer, Different machine specs , Duel core instead of single , ETC. will the wu's i had on the other machine still validate , or will they be invalid or error out ?

shoild i run them or just abort them ?

---