I signed up to this just over a week ago and it still hasn't done anything. I also signed up to malariacontrol.net at the same time and it's already done loads, so it's not a problem with BOINC. If it were a problem with the firewall or my BOINC preferences, malariacontrol.net wouldn't work either, right?

Check on your account page that you have all types of model enabled. - If you have just signed up you probably do. also check the server status link on the right hand side of this page, you will see there is not much work going @ the moment. If your computer is on 24 hours a day it is likely to pick up some work soon. It is also worth going into tools > computing options > Network preferences and setting the number of days work to fetch @ once up to the maximum of 10.

Within 24 hours unless the servers run out of tasks completely you should get some work.

Dave

I think the most likely problem is that there are more computers requesting work than work units available @ the moment and that until another large batch of units are released it is going to be hit and miss getting work - if there are no units at the time your computer sends a request for work then you wait I think an hour before it requests again.

Dave's last post is probably correct. The research teams obviously don't have much to release at the moment. (Probably have a huge backlog of results to process) You can always check what tasks are available by clicking on 'Server Status' in the RH column. (There are 3 at the moment)
Dave's also correct in mentioning the 1 hour delay between automatic requests.
You could always set the project to 'no new tasks' and then when a task is available, reset to 'get new tasks. That's what I'm doing at the moment - I just do a daily check on 'Server Status'. That way you only request a task when one is available.

Welcome to the project, Peter.

Dave and David offered good advice (though in my display the options appear in a blue box on the left side of the page).

If accustomed to hours-long projects, you're in for a surprise here. For machines running 24/7, CPDN work takes days to weeks, depending on model type. (They've been chopped-up -- they used to run for months and, on some computers, exceeded a year.)

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.