.... and no work was sent.

The machine actually does have 512MB of memory but 32MB of that is shared video memory. This machine does nothing but crunch. The 469221376 bytes of memory is fully available to Rosetta all the time.

Is there any possibility of relaxing the memory requirement a bit to take into account machines like mine or is that 500MB requirement firm ?

Thanks for listening ... my other 9 machines are doing just fine.

---

I've noticed that this memory "error" comes up only rarely on my computers with only 256 megs of memory. The message says "out of work" but they very quickly get work again on their own.

---

... but they very quickly get work again on their own.

So far mine has not, on its own. It will when I punch the "update" button but until then it sits and sucks its thumb. It runs "headless" so I only notice the delay when I check my stats and find that it has not reported in a day or so.

Not a crisis but if it's an easy fix then my vote is in.

---

... but they very quickly get work again on their own.

So far mine has not, on its own. It will when I punch the "update" button but until then it sits and sucks its thumb. It runs "headless" so I only notice the delay when I check my stats and find that it has not reported in a day or so.

Not a crisis but if it's an easy fix then my vote is in.

But it will when you leave BOINC alone. Look at your Projects tab. It says communications is deferred. When that timer runs out, BOINC will reconnect and you'll get more work.

BOINC knows what it's doing, and I've learned to trust it. It doesn't need pesky humans hitting the UPDATE button. As long as you have another project on that computer you'll be fine.

.... and no work was sent.

The machine actually does have 512MB of memory but 32MB of that is shared video memory. This machine does nothing but crunch. The 469221376 bytes of memory is fully available to Rosetta all the time.

Is there any possibility of relaxing the memory requirement a bit to take into account machines like mine or is that 500MB requirement firm ?

Thanks for listening ... my other 9 machines are doing just fine.

If all you use the machine for is crunching, you could lower the video memory in BIOS so it only uses 8Mb and leaves the rest for SETI.

.... and no work was sent.

The machine actually does have 512MB of memory but 32MB of that is shared video memory. This machine does nothing but crunch. The 469221376 bytes of memory is fully available to Rosetta all the time.

Is there any possibility of relaxing the memory requirement a bit to take into account machines like mine or is that 500MB requirement firm ?

Thanks for listening ... my other 9 machines are doing just fine.

If all you use the machine for is crunching, you could lower the video memory in BIOS so it only uses 8Mb and leaves the rest for SETI.

I was going to suggest that, but then I realized that this doesn't actually help, as the requirement is 512MB, so with 512MB of RAM, any subtraction from that would mean less than 512MB. Adding a small stick of memory may work tho'.

--
Mats

---

Thank you for your replies and suggestions.

Unfortunately the machine only has 2 memory slots so adding an extra stick isn't on. I might be able to move some memory around between machines but am generally loath to do that as there is always the risk of something going "poof" on one of the memory sticks. I am usually fairly careful .. but based on experience .. not consistently so. DDR memory isn't as cheap as it once was.

I think that I will just suck it up and let it run Seti as a backup task to Rosetta. If I stumble across a cheap video card I will throw that in and disable the onboard video.

I don't share Matts faith in Boinc knowing what it's doing but do agree that it is "much improved".

Thanks again for your help...

---

I don't share Matts faith in Boinc knowing what it's doing but do agree that it is "much improved".

BOINC is awesome. Once I forgot to set my alarm clock and BOINC woke me up so I wouldn't be late!

BOINC is awesome.

Agreed. BOINC has replaced the TV as primary babysitter at my house. It also occassionally cooks dinner and does the laundry when I run out of socks.

---

... I don't share Matts faith in Boinc knowing what it's doing but do agree that it is "much improved".

Thanks again for your help...

I would say boinc does know what it is doing, that is different to the users knowing what boinc is doing.

for the fit and forget people, boinc runs fine (normally ;-) But for people that like to have a look at things boinc doesn't, by default, tell you a lot about what it is actually doing.

If it just crunches and it can be accesed over a network, you should be ale to disable the onboard graphics and let it boot. Then use Remote desktop (if using Win2k/XP Pro + on it) or VNC to use it.
If you don't actually need to use it then use BoincView to monitor and change boinc settings, you could even use BoincManager but I find it easer to use BoincView for this sort of thing

---

Team mauisun.org

If it just crunches and it can be accesed over a network, you should be ale to disable the onboard graphics and let it boot. Then use Remote desktop (if using Win2k/XP Pro + on it) or VNC to use it.
If you don't actually need to use it then use BoincView to monitor and change boinc settings, you could even use BoincManager but I find it easer to use BoincView for this sort of thing

I have a computer sitting in the corner of a room. It doesn't have a monitor, keyboard, or mouse - just a power cord and a network cable. It just runs BOINC on Windows 2k. I haven't had to touch that computer in over a month - BOINC runs perfectly on its own. I know it's running successfully because I see completed work units in my Rosetta profile.

BOINC is awesome.

Agreed. BOINC has replaced the TV as primary babysitter at my house. It also occassionally cooks dinner and does the laundry when I run out of socks.

Sounds like there've been improvements--maybe I'll upgrade. I don't know, though, I've been running rev 3.x for so long I'm really attached to it.
OSF

---

dag
--Finding aliens is cool, but understanding the structure of proteins is useful.

.... and no work was sent.

The machine actually does have 512MB of memory but 32MB of that is shared video memory. This machine does nothing but crunch. The 469221376 bytes of memory is fully available to Rosetta all the time.

Is there any possibility of relaxing the memory requirement a bit to take into account machines like mine or is that 500MB requirement firm ?

Thanks for listening ... my other 9 machines are doing just fine.

If all you use the machine for is crunching, you could lower the video memory in BIOS so it only uses 8Mb and leaves the rest for SETI.

I was going to suggest that, but then I realized that this doesn't actually help, as the requirement is 512MB, so with 512MB of RAM, any subtraction from that would mean less than 512MB. Adding a small stick of memory may work tho'.

--
Mats

Almost all of my dedicated "crunch" computers use "onboard" video which means they have slightly less than 512Mb....they still run Rosetta.

Almost all of my dedicated "crunch" computers use "onboard" video which means they have slightly less than 512Mb....they still run Rosetta.

There have been some issues with machines not getting work. And it apparently has something to do with the new class of WUs that require 512MB. So he was just asking if the requirement could be dropped to say 480MB instead, then he could still crunch the "big" WUs.

I'm still not clear how the scheduler works and why people have trouble getting the WUs that CAN run on the 256MB systems.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

My host celeron 500 Win98 w/256Mram hasn't had an error in a coons age(during entire recording period with started Aug 18th, so it was sometime before that). So, it's done atleast 102 wus successfully in a row. The first 90 were with the default "run time" setting and the last 12 were with the 24 hour setting. Of course, this puter is setting in a corner with only the power cable and network cable attached, so I don't use it for anything else that take up memory or otherwise contribute to the goofing up. Note: no screensaver either of course.

This old laptop sits in a corner of my work area in the basement and crunches Rosetta 24/7 with 192MB. Only refused a WU twice. Last time was 6 days ago but still got one soon after. It ran through CASP 7 with no problems.

192MB

This old laptop sits in a corner of my work area in the basement and crunches Rosetta 24/7 with 192MB. Only refused a WU twice. Last time was 6 days ago but still got one soon after. It ran through CASP 7 with no problems.

192MB

Yeah, I've noticed that RAM issues aren't that big of a deal if it's a computer you're not using for your own stuff. If the computer is just sitting there doing BOINC then you're fine.