Hi all,
Had the below error show up.
I initially DLd 3 WU, the first 2 bombed, I aborted the 3rd.. I then detached, re-attached, then DLed 11 new ones.

Every one of them went south..

Boinc mgr is 6.2.18

Free disk is 88g
Used by boinc is 4.81
Use at most 100g
Leave 0
Use up to 50% disk
Leave apps in memory.
Only other project (which was suspended was CPDN at 55% @1004 hrs (do not want to loose this)


mike

(extra blank lines removed)
<core_client_version>6.2.18</core_client_version>

A few questions that may help pin down the problem:

The odd thing is that I had successfully finished 3 models a few days ago, and a couple before that, (cant remember the version off hand, only 1 wu at a time) with no issues. I am attached to 7 projects but am not running then all. (I NNT the projects, and have a small buffer so as to not have to worry about having too much (Yea, I know boinc manages it, but I want to make sure everything gets doone quickly).
When you mentioned boinc dividing the disk space, I am wondering if I had the non active projects suspended, which I ususally have done in the past..
I will retry after I get thru the SIMAP run (this is why I keep the tasks low), making sure my buffer is small so as hopefully not grab 11 tasks


Thanks

Mike

Another question that may help pin down the problem:

Did you have graphics enabled at any time during those runs? When I run minirosetta 1.58 for RALPH@home, it completes successfully if I never enable graphics, but fails if I have graphics enabled for a short time during the run.

Hi all,
Had the below error show up.
I initially DLd 3 WU, the first 2 bombed, I aborted the 3rd.. I then detached, re-attached, then DLed 11 new ones.

Every one of them went south..

Boinc mgr is 6.2.18

Free disk is 88g
Used by boinc is 4.81
Use at most 100g
Leave 0
Use up to 50% disk
Leave apps in memory.
Only other project (which was suspended was CPDN at 55% @1004 hrs (do not want to loose this)


mike

(extra blank lines removed)
<core_client_version>6.2.18</core_client_version>

A few questions that may help pin down the problem:

Are you able to find BOINC 6.2.28, and willing to upgrade to it? That's the only version I have used since 5.10.45, and I don't have that problem.

Have you gone to any extra effort to tell BOINC that it could use more virtual memory than the default?

Have you gone to any extra effort to tell your copy of Windows to allow a bigger swap file than the default?

How many BOINC projects do you have your BOINC Manager set up to recognize? I've seen some so far rather indistinct signs that BOINC divides the disk space it is allowed to use into equal sections for each BOINC project it recognizes before it starts dividing those sections into smaller subsections for each workunit. Therefore, if one BOINC project is heavy on disk space use, workunits for that project might run out of disk space even if some other BOINC project doesn't need all that is reserved for it.

Does this site tell you how much memory your machine has now and what the maximum for that model of computer is?

http://www.crucial.com/

I had problems getting my dual-core CPU to run two Rosetta@home workunits at the same time back when I had only 1 GB of memory to share between Vista and the two workunits, so I ordered an upgrade to the 2 GB maximum my model of computer can handle; now I can run two such workunits at once even while typing this.