"I got", but I'm curious how many times on how many devices you rattled the update button?

<ot> rattled > Rattles: (Think that was a German band, not an indication of my age and my past whereabouts :-)

edit: yes indeed http://www.youtube.com/watch?v=WKd8zm-q6OM

The Witch</ot>

I know, that there are still some resends around.
However, does the team already have a result of the beta test?
Are there major issues to be addressed that may lead to another round of beta test for this project or can it be started after some final preparations?

I forgot, but I'm sure it was answered in this thread some dozen questions up... have to run now.

... and ran back... 8 klicks.

No, but there was a suggestion to get a message in the client message log once a device is deemed reliable.

Till then, I watch my queue sideways and when seeing a task that's with a rush deadline on a production task, <= 4 days, then that's the word the device is below 0.2%.

"Close to zero" does not exist. The rating never goes below 0.1%... you'll be checked all through your crunching career.

They only go to devices that return work routinely within 48 hours from receipt. All these fantastics schemes thought up to get A type or rush or whatever are just that... it's like Catweazle's alchemy **. Running a 0.1 day cache allows to increase it to 2 days to quickly load up on whatever 'precious' and not jeopardize the R++ rating when returning to normal crunching cycle. Running 0.1 days is good for 2.4 hours server outage at least, but practically since all running jobs have 1 backup if a jobs has < 2.4 hours left, the cache is probably worth the time those ready to start jobs take. At any rate, I run with 0.9 days and a short scheduled connect of 1 hour a day. The current researches are not going away for at least the next 6 months.

Edit: ** Sorry could not resist, but my own alchemy works best, for me :P