Well, that happens if we don't see each others posts before we have finished posting :D
Better redundant information than no information.
But I might be annoyed enough to do a FAQ entry I can point to next time ::)
____________
A person who won't read has no advantage over one who can't read. (Mark Twain)

I suspect there are exactly three persons that know how the AP validator works (i.e. what parameters are checked with what error levels): Josh, Eric and Joe.

I know roughly what is checked on MB - number and type of signals and some scores attached to the individual signals. With MB any tasks that has more than 50% match to the canonical one will be valid. I would assume it works similarly for AP.

The number and type of signals found by those three closely related apps was the same, so something in the score must have been too different - beyond our ability to check, that is in the uploaded result file, not in stderr.

Why you are repeatedly coming up inconclusive against r1316 might need investigation.

I see. So no one else can see any reason either. r1316 is the most widely used version out there, it would stand to reason that version would show up most. The other versions aren't even close. You might want to check on some of those Inconclusive Hosts that are using r1316, some of them have a history. So, after over 2000 Valid results somehow this one, which is pretty close to the other Barts card in the Workunit, is deemed Invalid.
Interesting.

But if you want the x64 version, the one in that download directory is broken. There are numerous regular posters around here who have a copy of the x64 version, including me (I got it from someone a few months ago myself). PM if interested.
____________
Linux laptop:
Record uptime: 1484d 22h 42m
Ended due to UPS failure, as discovered 14 hours later

It is beginning to be a pain. I have 170 waiting on one machine. Then you have little incidents where three different hosts, using three different versions of the software, all arrive at the same general results yet the one using the most recent software is marked as 'Invalid'. Not very encouraging...

Someone care to explain why that was marked as Invalid?

The only thing I see it's the Boinc version.
You have .52 they have .28

Tim

That is of no consequence to the validity of results.

Boinc only provides the infrastructure - what task is run when, what project to contact for tasks, for how much work to ask, etc. the science is all done by the respective applications. If something goes wrong there, the app is at fault not boinc. [the only exception that springs to mind being the problem that AP may not get boinc 'suspend' orders under some circumstances, that's something where the API is probably involved - that's the bit that handles communication between boinc and the apps]

Yeah, one would think it's like that... apparently it's not that simple. As you see, some versions of BOINC combined with some versions of nVidia drivers can cause issues even on CPU-only projects.
____________.

So this is really cool. I was looking through my tasks and looked at the two most-recent that I reported, and I was a _2 on both of them.. and _0 and _1 are the same for both. Two back-to-back APs with the same three wingmates.

The statistics on that happening must be somewhere between "unlikely" and "remote," but it happened anyway.
____________
Linux laptop:
Record uptime: 1484d 22h 42m
Ended due to UPS failure, as discovered 14 hours later

I'm still using Squid in Ubuntu for my Windows Downloads.
If it ain't broke...

I did try the RFC1323 option in Windows and it seems to replicate what I had with using Squid as a proxy. Squid may be slightly better overall, though I am wary of having a single point of failure for BOINC transfers, so I did revert to direct connections once I confirmed the RFC1323 option works.
____________
Soli Deo Gloria

Across 9 rigs, I have 1794 WUs cached out of a possible 1800, so no outstanding problems here either.
____________
***************************************
I am still the kittyman.
Accept no imitations.

I like that, for the first time in months the Panic thread if quiet, i belive is due the TCP bug fix is working fine on all who use it, who no and have windoes hosts, must try. Tanks to the one who discovered/share that with us.
____________