Hi,

Picked up only 3 and all look good:
1 Valid (I7 - Vista Business 32)
1 PV (I7 - Vista Ult 64) 1 wingman waiting, 1 In Progress
1 In Progress (C2D E6750 - XP Pro) a little over 1/2 way done

Picked up 2 units and both are now Aprobación Pendiente.
System: Vista Business

One thing. I had to stop the normal units to start the betas. They weren't high priority. Are they no longer priority jobs??

Edit: update: one is valid now. No problems with my units!

The main parameters of your BOINC client triggering high priority or not for a task are the "Connect to network about every xx days" and the "Switch between applications every: yy minutes".
When the sum of both (plus probably some safety constant) is greater than the time remaining to the task's deadline then the high priority mode is raised immediately. This was usually the case when the repair and beta WUs had a 2-day deadline. Now that they have a 4-day deadline immediate high priority is less probable.
If you run WCG only you may decide to increase the "switch applications" parameter to make repair and beta WUs trigger high priority again immediately after downloading.

Obviously high priority can also be triggered by global workload considerations in your BOINC client but this is a different matter.

Cheers. Jean.

A nice side effect, if only crunching for WCG, is that chances to get a server abort get smaller. My single Beta (as far as I am aware) in this run went fine, but because of the "Initial Replication: 3" and "Quorum: 2" settings I noticed that one slow returner had his Beta "Server aborted" meaning (s)he did not start to crunch before the two other replications already validated.

The only things lost in that case were some bandwidth and the chance to get some extra Beta time. With the settings as suggested by Jean, chances are that there would not have been time to send a "server abort".