I know there is nothing you can do, but it is unfortunate that when the outage occured it seems my client thinks at some point it reported 10 results back which are not showing.

Exactly how BOINC thinks it uploaded resutls to the project is quite beyond me and I was supprised when the units disappeared out of the client after they had stacked up. I am presuming this would be a BOINC client issue rather than a GPUGrid project issue.

Not sure if the same occured to others and therefore if it is just bad luck for me or if there is a pattern.

Ahh well c'est la vie, onwards and upwards.

I know there is nothing you can do, but it is unfortunate that when the outage occured it seems my client thinks at some point it reported 10 results back which are not showing.

Exactly how BOINC thinks it uploaded resutls to the project is quite beyond me and I was supprised when the units disappeared out of the client after they had stacked up. I am presuming this would be a BOINC client issue rather than a GPUGrid project issue.

Not sure if the same occured to others and therefore if it is just bad luck for me or if there is a pattern.

Ahh well c'est la vie, onwards and upwards.

BOINC client uploads them and checks for errors etc. It then reports the work which get an acknowledgement from the server that it has received it. This gets logged into the database on the server side and the BOINC client will delete the wu from your end.

If their server crashed some time after that their latest backup may not have that database entry and so its quite possible its been restored back. I'm sure GDF will advise in due course.

---

BOINC blog

There showing:-

517973 378984 10 Apr 2009 13:33:03 UTC 14 Apr 2009 7:49:01 UTC Over No reply

There is also a bug in many of the version 5 BOINC clients that will do this to you. I lost about 6-10 Einstein tasks go bye-bye on me when EaH went off-line a week or so ago with the disk crash. So, you can be caught on both sides.

This is one reason to upgrade the client, of course the fact that new bugs are introduced means that it is dancing in a minefield and it is just a question of which bug set will you live with. But this is one of the reasons that I had been trying to get people at least up to 6.5.0 ...

The question is if 6.6.20 is good enough to replace all of the past or not. Because it takes a time for many bugs to be cleanly identified it is too soon to tell for sure.

Thanks Paul.

Alas I am on 6.6.20 which I'm not sure is a good or bad thing other than to say so far I have had no other issues at all.

lol at the analogy I used Tango through a minefield in the past myself.

well i am satisfied enough with 6.6.23 at the moment it runs steady and i only see some minor bugs
i am surprised that it runs fairly smooth on my machine and laptop so i guess for now is a good choice to run if you have problems with older ones