Evening Area51!
Downloading now, will be using windows 7 ultimate 64 bit edition gtx480 and seti 6.10.58
Well, that'll be the first acid test - a Fermi card! The code should handle that fine. All we will need is for you to generate some -12 or a -529697949 errors. This script handles just those two error types at the moment. I am wrestling with my brain to figure out -177 aborts. Having had a 'true' -177 abort with a real run-a-way task, I know I can't make assumptions about how to handle them. But I do have a plan!
It doesn't matter how long it takes for you to generate errors - honest! You don't even have to know if you've generated them. The idea is that the script is run just prior to upload - it then tells you if you've got any GPU errors it can fix, and re-assign to the CPU. I will be including a doco' that describes the intended method of operation etc. etc. The script is quite 'chatty' - this is more to help me find any problems it may have.
I will be writing a second far simpler bulk cleaning script for when people need to clean up a big FUBAR - perhaps by over-cooking an OC, or like you, when a shed load of -177's turn up because the server had a headache when it tried to figure out how long it was going to take to complete a task etc. This is a much simpler thing, as I just have to identify the screwed tasks, and re-set them back to their 'normal' values. However, for now, we will stick with this first script and see how we go.
Once you have finished the PERL install, you need to open a command line prompt. Do:
Start | All Programs | Accessories | Command Prompt
Then, type:
perl -v
You should get some blurb about 'This is perl v5.10.1' ..... etc. If you get this, you're "OK to go" (where did that come from?

)!!!
Anyway, thanks for agreeing to test this, and if you don't get the perl message as described above, just let me know!