Stats have me totall confused

OK, then it looks like it is the average daily amount of credit you are receiving from that project from all your machines that are registered with that project. As I said, nothing to do with crunch times for individual results.

When you say, "time setting for tasks", are you referring to the website general preference setting called "switch between applications every XX minutes"? If you are you should realise that the default value of 60 minutes is fine for 99.9% of situations. It's not something you would normally even bother about. It's certainly not something you would need to micromanage.

All that setting does is tell BOINC when it should check to see if there is a more deserving task that needs to run rather than the current one. If there is not, the current one will simply continue. If there is, BOINC will suspend the current task for now and resume crunching on the more deserving task. If you set that interval to a large value like 240 minutes, you are effectively allowing a task that doesn't deserve to be running at the moment to continue for longer than it really should before being suspended. It's probably better to let BOINC do these checks every 60 minutes by leaving the default alone and not fiddling with things.

You should have no problem if you set up 3 to 5 projects on each PIII and give those projects reasonable resource shares. Leaving the resource share of each project at the default value of 100 would be wise until you learn more about how things work. Then you could give one project more and another one less if you so desired. The thing you shouldn't do is set up 5 projects per machine and make the resource shares something like 100/1/1/1/1. BOINC would handle it but it might not be very pretty!! :).

BOINC is a complex piece of software that really does work well at the default settings. Unless you really understand what you are doing, it's much safer to leave the defaults largely alone.

Lets assume you were supporting 4 projects each with the default 100 resource share. The sum of those 4 values is 400. Any one project deserves to get 100/400, ie 25% of the available cpu cycles. If one project has already had 25.001% of those cycles then it no longer deserves to get any more time for the moment. There would have to be at least one other project whose share was less than 25% since the total cannot exceed 100%. At any given point in time the most deserving project will be the one whose actual cpu usage is the lowest when referenced to the share that it is entitled to.

A more complex example. Let's assume 4 projects A, B, C, D (all with current tasks on board) whose shares are 100, 200, 50, 150 respectively. You should be able to confirm that project C is entitled to 10% of the available cycles and project B is entitled to 40%. Lets assume that project B is currently running and that BOINC's record of CPU usage for the 4 projects is 20.5%, 38.2%, 10.3% and 31.0% respectively. If the "switch between applications every XX minutes" interval has just expired, which project will BOINC allow to run next?

You're welcome!

PS: You need to allow the system to organise your quoting for you :)

Next time you respond to a message, pay close attention to the way the quote tags work and how they are nested. If you want to break up a single quoted block into multiple sections, just add your own /quote where you want a quoted block to finish and insert an extra opening quote where you want the next bit to start. Click on the "Use BBCode tags ..." link next to the message composition box when you are creating a reply to see more examples of what you can do. Be careful not to insert any new response text in between the opening and closing quote tags or else you'll really confuse your audience :).

Please realise that I'm deliberately leaving out the square braces in the above examples so that the system doesn't try to interpret them as real quote tags.

EDIT: When you are responding to a fairly lengthy message, it's always appreciated by your audience if you delete out of the quoted blocks the stuff that is not relevant to your current message. As an example, have a look at how much of your previous message actually made it into this particular response. If you have an afterthought, just edit your message to add it in like I have here rather than creating an extra full message. If your afterthought is more than one hour later you will need a new message.