On Wed, 07 Dec 2005 21:19:20 GMT, Josef W. Segur
<jsegur@frontiernet.net> wrote:

You don't, it's a parameter at the scheduler which requires your system
to report 67108864 bytes of memory or more before it will send you any
work.

The memory amount is read by BOINC each time it starts, so you can't
accomplish anything by exiting BOINC and modifying a file. Mac and Sun
systems report all installed memory. Windows reports installed memory
less any which has been taken by the BIOS to hold code from ROM. Linux
reports installed memory less what is needed by the OS.

It is possible that reconfiguring the BIOS to run itself and any video ROM
code from ROM rather than the faster RAM would make the difference.

The enhanced version of setiathome will probably come out of beta test
fairly soon, and I think the best chance of getting the memory limit
reduced will be at that time. I suggested something like 56 MB in one
of the beta test <URL: http://setiweb.ssl.berkeley.edu/beta/ > forum
threads not too long ago. Eric Korpela is basically alone on SAH
development now, he's aware of the issue but it's unlikely to be a high
priority for him.

Well done with this answer, but it is totally wrong (though I don't
think the answer is down to you).  This is NOT a SETI problem, but a
problem with the new BOINC client (I'm running 5.2.6).  Up until
Monday of this week I was running Windows 2k on an Athlon 2400 system
with 512Mb memory and a 40Gb partition (which was never allowed to get
below 500Mb free), and SETI kept giving me that 64Mb error message
since I upgraded BOINC 5.2.6.

Now, for other reasons, I had to reformat my HDD and decided to use
Win XP Pro (as I'm a computer engineer going for MCSE qualification
soon and need to be up-to-date).  My HDD is now relatively virgin, has
28.5Gig free on the HDD, Task Manager is reporting 120Mb free memory
and I still get the following log when I start BOINC up:

08/12/2005 17:24:53||Starting BOINC client version 5.2.6 for
windows_intelx86
08/12/2005 17:24:53||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
08/12/2005 17:24:53||Data directory: C:\Program Files\BOINC
08/12/2005 17:24:53||Processor: 1 AuthenticAMD AMD Athlon(tm) XP 2400+
08/12/2005 17:24:53||Memory: 511.48 MB physical, 1.22 GB virtual
08/12/2005 17:24:53||Disk: 40.05 GB total, 28.52 GB free
08/12/2005 17:24:53|climateprediction.net|Computer ID: 88336;
location: ; project prefs: default
08/12/2005 17:24:53|SETI@home|Computer ID: 485059; location: home;
project prefs: default
08/12/2005 17:24:53||General prefs: from SETI@home (last modified
2004-08-21 12:54:55)
08/12/2005 17:24:53||General prefs: no separate prefs for home; using
your defaults
08/12/2005 17:24:53||Remote control not allowed; using loopback
address
08/12/2005 17:24:54|climateprediction.net|Sending scheduler request to
http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
08/12/2005 17:24:54|climateprediction.net|Reason: To fetch work
08/12/2005 17:24:54|climateprediction.net|Requesting 604800 seconds of
new work
08/12/2005 17:24:58|climateprediction.net|Scheduler request to
http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
08/12/2005 17:24:58|climateprediction.net|Message from server: No work
sent
08/12/2005 17:24:58|climateprediction.net|Message from server: (there
was work but you don't have enough disk space allocated)
08/12/2005 17:24:58|climateprediction.net|Message from server: No disk
space (YOU must free 69.1 MB before BOINC gets space). Review
preferences for maximum disk space used.
08/12/2005 17:24:58|climateprediction.net|No work from project
08/12/2005 17:25:03|climateprediction.net|Deferring communication with
project for 23 hours, 59 minutes, and 54 seconds
08/12/2005 17:25:03|SETI@home|Sending scheduler request to
http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
08/12/2005 17:25:03|SETI@home|Reason: To fetch work
08/12/2005 17:25:03|SETI@home|Requesting 604800 seconds of new work
08/12/2005 17:25:08|SETI@home|Scheduler request to
http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
08/12/2005 17:25:08|SETI@home|Message from server: No work sent
08/12/2005 17:25:08|SETI@home|Message from server: (there was work but
you don't have enough disk space allocated)
08/12/2005 17:25:08|SETI@home|Message from server: No disk space (YOU
must free 69.1 MB before BOINC gets space). Review preferences for
maximum disk space used.
08/12/2005 17:25:08|SETI@home|No work from project
08/12/2005 17:25:14|SETI@home|Deferring communication with project for
23 hours, 59 minutes, and 54 seconds

Now note

i) 08/12/2005 17:24:58|climateprediction.net|Message from server:
(there was work but you don't have enough disk space allocated)
08/12/2005 17:24:58|climateprediction.net|Message from server: No disk
space (YOU must free 69.1 MB before BOINC gets space). Review
preferences for maximum disk space used.

ii) 08/12/2005 17:25:08|SETI@home|Message from server: (there was work
but you don't have enough disk space allocated)
08/12/2005 17:25:08|SETI@home|Message from server: No disk space (YOU
must free 69.1 MB before BOINC gets space). Review preferences for
maximum disk space used.

Both error messages the same, and I've not changed settings for BOINC
or the projects since I started running BOINC back in March/April, but
now I don't have sufficient resources available.

I've always supported SETI@home since I joined in February 2000, and
was certainly not blinkered when it came to the new BOINC version to
the project, but I think Berkley have bitten off more than they can
chew with this project if two seperate projects are complaining that a
(relatively) new computer is not capable of running their work.  I
have better things to do with my time and resources than to mess
around with something I do as a volunteer.

Berkeley, get your act together before you loose suppoerters!

Andy