[QUOTE=Aramis Wyler;334360]Do we need to put our gpu72 password and username into the ProxyUser and ProxyPass entries when we change ProxyHost?[/QUOTE]

Nope.

And good question -- I'll add that to the FAQ post.

Ok, I can't figure out the work assignment rules.
The default for my PrimeNet account is LL, and all of my AVX capable boxes are set so all threads' worktypes are LL.
GPU72 shows all but one as being set to WMS; I am getting DC assignments.
I wonder what my non-AVX (currently ECM) boxes will get?

Is there some setting I don't know about?

[QUOTE=sdbardwick;337979]Is there some setting I don't know about?[/QUOTE]

Please see Q7 and A7 (which I just added) in the FAQ post above.

This has been talked about before elsewhere, but it should have been there as well.

Apparently you need to either individually set all worker windows to the same worktype or use the "All Workers" setting for the change to be effective. After the change is recorded on GPU72, you can then restore the threads to different worktypes which will be respected for assignments (at least for the LL/DC types I tested).

[QUOTE=sdbardwick;338024]Apparently you need to either individually set all worker windows to the same worktype or use the "All Workers" setting for the change to be effective. After the change is recorded on GPU72, you can then restore the threads to different worktypes which will be respected for assignments (at least for the LL/DC types I tested).[/QUOTE]

OK, thanks for that report.

I'll go through the logs (all Proxy messages are recorded for analysis) and see if there's a bug in my code, or if this is simply the nominal behavior in the API exchanges between Prime95/mprime and Primenet.

Edit: Just saw your edit... It will be the same behavior for all worktypes.

Damn, one really needs to wrangle with the worker settings to get the correct type of work (LL vs. DC), even when GPU72 says LL, and all worker threads are set to LL. I kept getting DCs until I changed workers to different types, communicated, changed types again, communicated, and finally set to same type and communicated.

For reference in the logs look at computers i7-2600K and Jupiter-3570K.
i5-2500k-test logs probably show the quickest resolution: Change a worker to DC, communicate, change the other worker to DC, communicate, use All Workers to change both to LL.

Edt: Forgot to mention that the CPUs with only one worker window behave better, IIRC.

[QUOTE=sdbardwick;338056]Damn, one really needs to wrangle with the worker settings to get the correct type of work (LL vs. DC), even when GPU72 says LL, and all worker threads are set to LL. I kept getting DCs until I changed workers to different types, communicated, changed types again, communicated, and finally set to same type and communicated.[/QUOTE]

Same thing happened to me a few months back when I set up a new laptop. It seemed mysterious until I changed worktypes as you described.

I'm done. Keep getting DCs rather than LL on random machines despite the same machines getting LL assignments previously. This just adds administrative overhead...

I'm almost afraid to mention this and tempt fate, but I think I've finally gotten away from unwanted DC assignments. For the longest time I had been doing a work around on my third P-1 worker: moving assignments from other workers to avoid automatic assignments on #3. A few weeks back I went through a hardware shakeup which included a CPU change from a PhenomII x6 to an FX-8350 x8. That setup has run long enough for a number of automatic fetches through GPU72, and worker 3 has received only P-1's (so far.) :smile:

A minor observation: I noticed that gimps.gpu72.com formats assignment keys differently (uppercase vs lowercase) for GPU72-owned assignments vs passthrough requests. Assignments that GPU72 is interested in are returned in all-lowercase, and requests that are passed through to PrimeNet get all-uppercase assignment keys. For example:[code]Pfactor=bb266817ed297ce1e1fbb1079b0df7__,1,2,61559999,-1,73,2
Pfactor=741879D85394BC94352CE0C5EA0E50__,1,2,80015017,-1,73,2[/code]Not that it really makes any difference, just an observation.

GPU on a Mac
 

Is there anyone running a gpu on a Mac at present at GPU72?

Could do with a hand getting mine set up

Thanks