Sorry for the large quote, but I see the following in all of my returned results:

<core_client_version>5.10.13</core_client_version>
<![CDATA[
<stderr_txt>
reading parameters file: parameters.txt
APP: astronomy reading volume from file: volume.txt
APP: astronomy reading integral checkpoint file
APP: astronomy read integral checkpoint finished
APP: astronomy integral checkpointing
APP: astronomy integral checkpoint done
APP: astronomy integral checkpointing
APP: astronomy integral checkpoint done
APP: astronomy integral checkpointing
APP: astronomy integral checkpoint done
APP: astronomy integral checkpointing
APP: astronomy integral checkpoint done
APP: astronomy integral checkpointing
APP: astronomy integral checkpoint done
APP: astronomy integral checkpointing
APP: astronomy integral checkpoint done
APP: astronomy reading likelihood checkpoint file
APP: astronomy read likelihood checkpoint finished
APP: astronomy likelihood checkpointing
APP: astronomy likelihood checkpoint done


**********
**********

Memory Leaks Detected!!!

Memory Statistics:
0 bytes in 0 Free Blocks.
166 bytes in 4 Normal Blocks.
12916 bytes in 8 CRT Blocks.
0 bytes in 0 Ignore Blocks.
0 bytes in 0 Client Blocks.
Largest number used: 6413860 bytes.
Total allocations: 11300360 bytes.

Dumping objects ->
c:researchboinc_samplesastronomyparameters.c(168) : {400115} normal block at 0x02E851C0, 64 bytes long.
Data: < m5 ?| -@> 17 A0 6D 35 EB 8C E6 3F 7C 80 EE CB 99 05 2D 40
{55} normal block at 0x01D550F0, 12 bytes long.
Data: <X> C K > 58 3E D5 01 B8 43 D5 01 90 4B D5 01
c:researchboincapiboinc_api.c(160) : {50} normal block at 0x01D52960, 4 bytes long.
Data: < > 00 00 EB 01
c:researchboinclibparse.c(142) : {49} normal block at 0x01D528D8, 86 bytes long.
Data: < <color_scheme>T> 0A 3C 63 6F 6C 6F 72 5F 73 63 68 65 6D 65 3E 54
Object dump complete.


</stderr_txt>
]]>


It's the "memory leaks detected" part which concerns me....


TTFN - Pete.

Odd, thought we had fixed all those. What OS/architecture are you running?

How about to allow only >5.5.1, this will reduce some of 5.5.0 unofficial clients?

I wouldn’t much like that: I’m running (stock) v5.4.9, and because of the problems I’ve had with later versions on another Mac, I’m very reluctant to upgrade this one. It makes appropriate claims as requested by the SETI@home apps, for example, as do all versions since 5.2.6 or thereabout.

I would rather see the work replicated, which serves as a deterrent to a variety of abuses. Fixed credit might be a simpler solution at the back end—I guess they have their reasons for the quorum of one— which I’d be perfectly happy with as long as it’s roughly in line with the nominal benchmarks or cross-project average.

The reason we have a min quorum of 1 is that our search method is highly resistent to failures/bad results, so theres really not much reason to replicate work. We're also very alpha at the moment so we're working on a simple validator and figure out some credit strategies that will hopefully make everyone happy. We might bump the quorum up to 2 in the future, but right now it's more useful to us to have as many results back as possible (good or not).

Actually my other pc's do show up. However there are several WUs listed on my account that are not on my pc.
http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=104679
http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=104735
http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=104855
http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=103982
http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=104860
http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=106539
http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=106540

None of these are on any of my computers.