Shouldn't be too long now! It's been running fine on my machine for about a week now, although its only setup initially to sort out -12 and -529697949 errors. For me, I get about 10 of these a week (-12 and -529697949) - but it finds, cleans and re-assigns them to the CPU with no problems. I am looking to add -177 and other types of errors bit by bit. You will be handy, because you have a Fermi setup (and when your setup goes wrong, in the usual 'Toxic way', it doesn't do it on a small scale)!

. All I need now is a willing volunteer who is running 2 or more GPUs, 1 Fermi and 1 lnon-Fermi jobbie......
I would also like to find a couple of people who are running Windows XP 32 bit......
To complete the first release ready for testing, I need to implement a section of code that extracts the version numbers of the GPU app and CPU app that are being used. I can't assume someone has an app_info.xml file, or that it is in a clean state - so all information has to come from client_state.xml. At the moment, these values are hard-coded, which is no good good for general distribution or for maintenance-free code. However, I did finally figure out how I can get the required info last night, so I just have to implement that in a reasonably efficient way.