Hmmmm... Good news and bad, first the RamIdle thing doesn't steal cycles from the DNet client when it's not doing anything (at least not from the latest DNet client), you can config it to get your ram back to a certain level, in steps of X MB per Y mins, no matter how much ram it frees up tho' (at least whether it was 5MB or 2MB at a time) doesn't matter it seems... it uses 4 secs of CPU time everytime (on a PIII 933 with 384MB ram)
For an ordinary user this seems like a very sweet proggie since you can also configure it to not free up ram if your cpu usage is higher than XX% (85% is default), but to get it to work with any distcomp client you'll have to disable that feature, and when it frees up ram you lose cycles...
You don't have to let it auto reclaim RAM tho' so I guess it can still be put to good use ... or if you give it a long interval you won't lose many cycles...
That's what I've found the brief time I've tried it now... (20mins)...
With love and respect your fellow TA member
Two-Face