Do I have to enable the test app to get workunits? Or will the production application be replaced with the new application? If yes - when?

It should automatically download for you.

I guess this makes the issue of whether the WUs are reported fast enough for the science moot at this time until the work generator can keep up with the tremendous gain in efficiency. :)

ATM the new work waiting server is keeping up with the demand OK. But this is for those who have D/Led the Milksop fast client.

The real problem may occur when Dave, and the Admins, release the new client based, to some extent, on Milksop's work. All the community will move across eventually and the demand will be from everyone, not just the ones using the current fast client (just a few).

I wonder what proportion of the crunching community is actually currently using the fast client?

Btw. as it is now possible again, I've updated my profile.
The files linked there contain a fixed app_info.xml.

Or as a short cut:
application for Windows 32 and 64Bit versions
application for Linux 32 and 64Bit versions

Do I need to buy a fire extinguisher for my apartment?

Yes, all humans should have one.

All WU's in progress for this rig should be recycled asap. Motherboard failure. Gigabyte GA P35-DS3L (refurb) from NE. Melted components near 4 pin power connector. Health of remaining components TBD. If there is any good news, I was granted an RMA for credit. Crunch on.

Thanks to all who got the Server back!

Voltron

wow...Gigabytes are usually pretty stable. I usually go with Asus or Abit myself.

I've heard of about a dozen newer Gigabyte boards that have caught fire or had melting where the MOSFETS are. It was always with boards that where overclocked. I don't know what caused this one.

I'll be adding extra cooling on my Asus MOSFETS soon.

In recent memory I have not been a very staunch defender of project decisions. But, there are cases where short deadlines are needed for the project to accomplish its goals. The fact that these deadlines conflict with your needs as a participant is unfortunate and not necessarily a bad design choice.

It just means that you, like all participants, has to decide if the project's parameters meets your capabilities.

There are a half a dozen projects that I wish I could contribute to ... but I cannot because they don't have a version for OS-X ... and that cuts most of my processing power right out. And so, I have to suffer ...

If you do not have "always on" Internet, then this may not be a project that is suitable for your systems.

At the moment, I have been toying with this project and a couple of others on my Mac Pro and with my Cable modem always on ... well, I am constantly seeing large shifts in work and fast turn-around on the tasks issued ... well, there is this one CPDN task that JUST WON'T FINSIH ... 1,000 hours to go ... :)

As John has mentioned there is the one minor issue with BOINC's design that can also cause problems ...

But, I don't suppose any of this is going to make you feel better about the deadlines ...

And projects with short deadlines, participants with fast machines and always on Internet are ideally suited for BOINC ... were they not having a minor issue with the system I would still be blowing through tasks for this project ...

What about shrinking the deadline a bit. BOINC can be very casual about reporting work if the deadline is a long ways away. Somewhat tighter deadlines seem to be what the project needs. If you really generate the next round from the current round, I would suggest something like 25 or 26 hours. This gives at least some intermittently connected users to do some work. If you connect by hand and typically do it when you get home from work or some such, 24 hours exactly is a pain as you have to report just a few minutes earlier each day.