yeah, crunching on my first 2 betas

I figured as much. When I first saw your "beta going out" message about 10 minutes after it was posted, I started bumping my queue up from .1 to .15 to .20, etc. and didn't manage to get any this time.

I thought it might have been a client version issue.

I'll try to be more attentive in the future.

Well I'm doing my part to be sure all get a beta this round as I only snagged one:
BETA_ erlc_ a058_ pe0000_ 0-- and it looks like a good one with a BOINC ETA of 22+ hours but likely sooner

I ended up with 24 beta's the first one went out as a error, it looks like they will take 11hrs each, only one of my machines got them, my dual core. the way I got so many is, when I read that they were planning on sending out some beta's in 24-48hrs, I created a new profile for my fastest computer I have it connect every .1 days, I set the buffer to 9 days, I deselected my current project and selected 1 that is intermittent. and made sure the beta option is selected. and I just have been watching the beta threads waiting for a announcement, and when one came I just kept on clicking on the update button in the boinc.

There's no client limitation, but the 750MB RAM requirement for WUs which use 30MB physical RAM is rather restrictive. (... and, I would think, means that a proportion of machine types may not be in the beta, which may defeat the purpose of a beta test.)