Nice! Today I learned that trying to install the BOINC Manager without network connectivity = fail. Had to wait for my Internet connection to come back online before I could get any version of the BOINC Manager to load my existing projects and work. If I temp'd the data directory away it loaded up fine, and would even do so with my projects (all cleared, "initializing") but no version would load with my current work load until my 'net was back.

Played with 6.6.36 a bit, but the fact all the MW units "run" the timer up w/o actually running messes things up a whole bunch. Estimating 40+ minutes on every WU means I was constantly having to force the next batch of MW work to start as the manager didn't want to start such long WUs. Back on 6.4.7 and tampering with settings more hehe.

---

Yeah, I've been with BOINC from the Start when the SETI Pre BETA/Pre Public was started & I have never understood why you had to have a Internet Connection for BOINC to work. My feelings are if there's work in the Caches BOINC should be able to run the work Internet Connection or no Internet Connection. Actually it can if you the "Network activity suspended: before you turn off the BOINC Client.

Anyway the following commands have worked for me running 4/3 or 4/6 depending on the Amount of Single Core ATI Cards I have on a Quad Core PC. For my i7 I just changed the <avg_ncpus>0.01 to <avg_ncpus>0.04 to get 8 Reg Wu's running & 6 Milkyway Wu's running. Maybe it was pointed out before & I missed it as my Settings are basically Default except for the <avg_ncpus> but for the last 24 hr's I've been running with those Settings in the Application File & as far as I know the Milkyway Wu's haven't gone into a waiting to run mode yet. At least I haven't seen them go into that mode anyway.

I'm running Win XP Pro / SP2 & BOINC Client v6.6.20 / ATI Driver v8.12 & Single Core Sapphire 4870's across the Pharm: I'll be messing with some X2's later today to see if the same settings work, I figure I'll need to modify them somewhat for X2's ...

<avg_ncpus>0.01</avg_ncpus>
<max_ncpus>1</max_ncpus>
<cmdline>n3 w1.0</cmdline>

Are you still using 6.6.36?

I've tried everything from 0.3 to 0.01 and only 0.01 made a difference, and that wasn't a good change (all MW WUs trying to run at once, to the point of shutting down all but 1 CPU app). Still don't quite understand what this value is really doing in terms of scheduling.

I've got mine set to .2 so that 5 WUs will flag "running," but it doesn't seem to have any impact on scheduling at all. I am finding out, however, that Enigma (which I'm only running because it's the KWSN project of the month) doesn't play well with MW (or QMC, since every single QMC WU that ran with Enigma running hit 100% and then failed computation). The wrapper doesn't update progress and timers very often and it tends to make the manager panic a lot that WUs are going to run-over their predicted time. I've had to "kick-start" MW several times tonight.

---

interesting how differed WUs clash
I have been running 7 climateprediction WUs and 6 MilkWay WUs at once for the last 2 days. have been getting 120000 to 140000 credts a day.
By decrasing the resources for MW WUs to 12% seems to keep everything in sync.
Always have plenty of WUs and minimal overflow, 18 tasks at a time.
thinking of getting a another 4870x2, should double my work.
still using BOINC 6.6.36
Ross

---

Are you still using 6.6.36?

No, running 6.6.20 since a few days ago ...