[QUOTE=kladner;309538]I guess this is as good a place as any to note that a DC I had in progress was finished by[CODE]25838287No factors below2^69
P-1B1=285000, B2=3633750
Verified LL232B4614879A8803 by "Anthony Lieuallen"
Verified LL232B4614879A8803 by "jg5" on 2012-08-28
AssignedDouble-checking to "ktony" on 2012-08-21
Historyno factor for M25838287 from 2^67 to 2^68 [mfaktc 0.19 barrett76_mul32] by "GIMPS Visualization" on 2012-08-21
Historyno factor for M25838287 from 2^68 to 2^69 [mfaktc 0.19 barrett76_mul32] by "Carsten Kossendey" on 2012-08-21
History232B4614879A88__ by "jg5" on 2012-08-28[/CODE]I'm not sure what motivates someone to poach DCs.:no:

EDIT: My thanks again to chalsall for the refinements on the Assignments page of GPU72. The warning of a completed assignment at least allowed me to cut my losses.[/QUOTE]
Yes, yours and dozens more in the 24-25M range. He's been busy.

DC count discrepancy
 

368 on the Overall DC workers report
398 on my personal stats page (I.e. When I click on my name on the Overall chart.
The list of completions shows 368.

I checked a few others; some match, some don't including yours, though I have the biggest difference.

Aha! I feel happy others have this problem too :razz: Chalsall has me on ignore list (:smile: methink :whistle:)

[QUOTE=petrw1;314751]368 on the Overall DC workers report
398 on my personal stats page (I.e. When I click on my name on the Overall chart.
The list of completions shows 368.

I checked a few others; some match, some don't including yours, though I have the biggest difference.[/QUOTE]

:bump:

[QUOTE=petrw1;315531]:bump:[/QUOTE]

OK, OK... I'll look into it.

It will be a Stupid Programmer Error.

I am running P95 with three workers, all set for P-1. This worked fine when I had two workers, but now I keep getting DC assignments on the third worker. Since I am minus a GPU right now (RMA), I am not doing any LL or DC work.

This continued accumulation of DCs is troubling. I have not unreserved any, since I don't want them lost to GPU72 (I'm using the proxy to get assignments.) I now have seven of them, and I expect it to be two to three weeks before I can hope to get the other GPU back.

My GIMPS account has two CPUs listed, though they are the same machine. The second instance of P95 is set for DCs as it is only used to get CUDALucas assignments. The primary instance is set for all P-1.

This would not be a problem if I were at full crunching strength. As it is, I would really like for it to stop. Any suggestions would be welcome!

Have you opened the workers configuration and set that worker to P-1?

[QUOTE=flashjh;317299]Have you opened the workers configuration and set that worker to P-1?[/QUOTE]

Yes. On the main instance of P95 all three workers are set to P-1, as they are on PrimeNet. As mentioned, I only fire up the other instance to get CuLu assignments. It is set for DC both locally and on PrimeNet.

[QUOTE=kladner;317301]Yes. On the main instance of P95 all three workers are set to P-1, as they are on PrimeNet. As mentioned, I only fire up the other instance to get CuLu assignments. It is set for DC both locally and on PrimeNet.[/QUOTE]

It's strange you'd get assignments for a worker that isn't doing anything. In your worker windows, how many do you have it set for?

[QUOTE=flashjh;317302]It's strange you'd get assignments for a worker that isn't doing anything. In your worker windows, how many do you have it set for?[/QUOTE]

The main instance (P-1) has three worker threads set accordingly. The "slave" instance has one worker set for DC.

[QUOTE=kladner;317304]The main instance (P-1) has three worker threads set accordingly. The "slave" instance has one worker set for DC.[/QUOTE]
Can you post a screen shot? Is there a reason you can't just not run the DC instance until you want more exponents?