@Kalessin
Look at this WU 4817265. Log:

<core_client_version>6.4.5</core_client_version>
<![CDATA[
<stderr_txt>
Chess960athome Wrapper (build 22; 200607120205) starting

Preparing input file
Using slot ID 1 for engine name
Preparing launcher
launch.bat: glaurung < input > ../../projects/www.chess960athome.org_alpha/chess960_34243_108_3_0
Copying Glaurung dependencies
Retval for kpk.bin: 0
Retval for glaurung: 0
Ready to launch launcher
Could not open result file for status
Application exited. Processing output files
All done.

</stderr_txt>
]]>
Validate state Valid
Claimed credit 0.666926621602751
Granted credit 0.750744425691028
application version 1.01

Got credit too. The problem is the chess app.

There was a similar problem before caused by missing libraries.
last part of the thread
old thread

A few but not all of those hosts are mine.

A few...good joke!

If you look at the total results from this host for example

http://www.chess960athome.org/alpha/show_host_detail.php?hostid=62024

You will see most WU's are inline with what they should be, but a very few that are overclaiming.

Good joke again. The normal claim at chess is from 0.8 to 1.9 only in exceptions the claim is higher than 2. Your host has not one claim lower than 4.80.
If thats what should be.....?

These WU's were frozen, and hung the CPU and GPU - but the timer was still running on both projects. Rebooting or restarting BOINC fixed the issue.
As with a few of the other hosts.

I think the major problem is not the 56er claim but all those claims that are constantly at least double or thrice the normal. So you take care always to get the second highest claim. Which is the gain with overclaiming with this quorum.

However, I can only run this project on Win32 bit boxes, and don't have any Win32 boxes that don't have ATI/GPU cards not attached except one:

http://www.chess960athome.org/alpha/show_host_detail.php?hostid=62013

Just checking this particular host
http://www.chess960athome.org/alpha/show_host_detail.php?hostid=62026
Also with a ATI/GPU attached, - has had 2 WU stuck with running time of over 2.5 hours, and 0% CPU usage being used for all WU's in process. With time to complete still increasing. Obviously stuck, and has been stuck for at least 18 hours or more from what I can tell. - The MW WU's are frozen as well. Go figure.

I am sorry for that. These situation are always very stressing.

The problem I see it is that this app does not play well with ATI/GPU.

I don't know about that, my ATI/GPU/MW host had none of these problems, always claimed normally. No irregular stopping anywhere. Only did these Chess WUs get into panic-mode and made MW stop until no chess WUs were there any more. That is the reason, why it does not do chess anymore. I had hanging WUs only with the linux hosts.

So exactly what is the problem. Even if they overclaim on this project, the quorum granted credit corrects that issue.

Getting funny again.
Yes, you will never receive what you claimed (as your hosts are the highest claiming all around), but as mentioned above you make sure always to receive the second highest claim. That increases the creditgain by about 20-30%!

But even so, MUCH MORE serious issue than a couple overclaiming hosts and a credit cop is the fact that this project is screwing up my other projects hanging my hosts.

Sorry for that again, especially for the credit cop. Still, I have not seen any of them around, only someone who doesn't like those overclaimers, who put their interest above that of all the other normal claimers.

As far as your outrages claim that 6.4.5 is a known cheating BOINC client, I guess you should notify the BOINC developers of that - because last time I checked, 6.4.5 is a stock client.

Read again: 6.4.5 is not overclaiming, but there does exist a client, that is overclaiming and calls itself 6.4.5 also. I think you should know of it.

And I don't know which one of those you do use, and I don't care, as long as you play fair. But always claiming double, thrice or tenfold increasing your output by about 25% is not something in the category of playing fair.

And as you well enough know the boinc developers cannot and will not control this kind of cheatery.

That makes it even more disgusting when it is used in a project that has no means to control this by itself.