Kevin - I have now aborted all those on my fast machines which have had a high proportion of errors relating to the upload size issue, and have left the others to run them.....I don't know if they are going to be penalised as a result, but I would be grateful if you could check and raise the download limits again if required

I don't know if this observation is of use to you or not, but I will mention anyway:

I have noticed that on a quad core that generally 2 out of the 4 running WU's have high memory useage and Page Faults, and at the same time 2 of the 4 end up with the restarting 'DLL Initialisation' error messages in Boinc and then result in the upload size error......I can't tell from Task Manager if the 2 showing this are the same 2 that have the DLL/upload size error messages, but I'm wondering if these are in some way related?

I see that work units running as high priority occasionally. They should be able to send them out that way, no?

High priority is only driven by a short deadline and a client scheduler that puts them ahead in the queue. The present have 8 hour deadline, so they will always jump the queue.

Probably you occasionally get a repair job, but if you run on the verge of over buffering, meaning e.g. stocking 10 days and queuing jobs with 10 days deadline, your hosts are also bound to cycle in and out of high priority. The minimum safety BOINC uses is 24 hours so with a 10 day deadline the buffer on 24/7 should not exceed e.g. 8 days. The queue volume is automatically adapted for part time crunchers through the active_frac factor and the result duration correction factor

Expect you know already, but others may not, reading this stuff.

[added: Are these labelled as such.... don't know, likely, but you'd recognise them by short deadline and runtime of 1 hour anyhow.]

A quick update for the techs on the final old Rice WU's that have gone through:

I have watched closely the progress of these remaining old wu's, and the ones that error due to the data size error seem to have 2 issues whilst in progress prior to completion.......they all get the DLL Initialization errors AND have high Memory usage/leakage - so it seems in my case at least they are linked in some way.

Perhaps once the memory leakage issue is resolved then these DLL Initialization errors may disappear too

Yes you will get credit as long as they validate, and I imagine they will. We have seen one batch validate so far, we are awaiting more batches to have a quorum which may start soon.

-Uplinger