All 3 are 6.2.28, and i downloaded them within 50 seconds - so it's probably the same wingman. None of the _2 wingmen have reported yet, my replications are now past checkpoints 4 at 25% progress, no errors or security alerts (of which i have never seen one since using Win 7 firewall).

edit: Also, watch your caches. The estimated time on my client are getting lower and lower for some reason (might be because of heavy heat throttling yesterday, but not sure). I expect the new tasks to take ~3.5 hours, the estimated run times are now 57 minutes, already have 21 CFSW tasks on an 8-thread machine with 0.01 cache.

The mix of old app tasks with new app tasks is likely reducing the mean projected time for any received after the science app update. You can always hack the DCF back to 1.000000 if you like (at full own risk).

--//--

We updated the estimated flops for workunits that had not sent out results yet as we released the new app version. However, there was a gap of about 10-15 minutes between the release of the new app version and the results. Additionally, if you are assigned repair jobs, you will get the old estimated flops.

What's this mean:

2012-06-08 19:49:54	World Community Grid	Message from server: No tasks are available for the applications you have selected.
2012-06-08 19:49:54	World Community Grid	Message from server: This computer has finished a daily quota of 2 tasks

This Win7 x64 dual core machine's actually fetched 4 of the 6.11 app work units, so far.

Ubuntu x64 dual core grabbed 31 and is freely downloading more.
CentOS x64 quad core grabbed 45 and is saying it's finished a daily quota of 5 tasks (SIC).

While the newer optimization is much faster it seems that XP still suffers from the same issue as the old app. It takes more than twice as long to do a WU on XP as it does on Win7 with the same hardware. Is it because XP is 32 bit and Win7 is 64 bit?