I just installed rosetta. It downloaded a WU and processed it, and then uploaded the results (with some prodding from me--status of the WU looked weird and inconsistent with the messages I was seeing).

Now it will not download a new WU.

I am using MAC OS X Tiger (latest rev.)

Are there any known issues with the combo?

The result showed up fine, was successful, got credit... no known issues beyond Mac version of Rosetta app being slower than Windows version, but it gives more credit, so...

Are you running another project? If so, is the resource share for Rosetta "very low" compared to it? Normally, not downloading a result is because you owe a "debt" to the other project that is larger than your cache size. (Or the other project is in danger of missing a deadline.) If you select Rosetta in the Projects tab and hit "update" and are told "not requesting new work" in the Messages tab, then it's a debt issue. If you're told anything else, paste the messages in here, and we'll see if we can help!

---

Thanks, Bill. Suspending Seti did the trick. They are having some network problems and I had some work for Seti stacking up.

---

Suspending Seti did the trick.

Great! We just discovered (thanks to this current upload problem) that "Uploading" work is still counted as being "present" on the system in some BOINC versions. "Downloading" work _must_ count as being "present", as it could arrive any moment. When neither uploads nor downloads are working well for a project, suspending it is about the only way to make everything else run semi-normally.

Even when it _is_ all running fine, if your cache is small (as is recommended) don't be too surprised to find no work on hand for one project or the other at times. The resource shares are met "in the long run", but not "minute by minute", and it's not unusual to go a few hours without a result from one project being present. If it's a full day, I'd start to get concerned. (Assuming SETI and Rosetta - other projects, other rules... CPDN in particular.)

---

Even when it _is_ all running fine, if your cache is small (as is recommended) don't be too surprised to find no work on hand for one project or the other at times. The resource shares are met "in the long run", but not "minute by minute", and it's not unusual to go a few hours without a result from one project being present. If it's a full day, I'd start to get concerned. (Assuming SETI and Rosetta - other projects, other rules... CPDN in particular.)

If I may add something here, running a very skewed resource share will also throw things off a bit. I run Rosetta 99% and a couple of others to fill the 1% for when Rosetta is down. Those low share projects can go for a week at a time or longer without seeing a WU.

---

If I may add something here, running a very skewed resource share will also throw things off a bit. I run Rosetta 99% and a couple of others to fill the 1% for when Rosetta is down. Those low share projects can go for a week at a time or longer without seeing a WU.

Very true - I had "assumed" a 50:50 split. My bad.

---