..and a recent escapee from Science United. How do I get work to process. I get "Communication deferred ..." in the BOINC Manager, so I must be doing something wrong. Or they may be on Xmas holiday. I "think" I've set up the PC so that it is Visible to you folks. Any and all help welcome!

..and a recent escapee from Science United. How do I get work to process? I get "Communication deferred ..." in the BOINC Manager, so I must be doing something wrong. Or they may be on Xmas holiday. I "think" I've set up the PC so that it is Visible to you folks. Any and all help welcome!

First, take a look at the Activity menu in Boinc Manager and, in the 3 areas, make sure the 2nd of each group of 3 is selected
That is:
Run based on Preferences
Use GPU based on Preferences
Network Activity based on Preferences

Most particularly that "Suspend Network Activity" is NOT selected

Select Rosetta@Home under the Projects tab of the Boinc Manager, then click update
Next, take a look at "Event Log" under the Tools menu of Boinc Manager, select the lines reported from that manual update and post what it shows.

It might look something like this:

23/12/2025 02:12:01 | Rosetta@home | update requested by user
23/12/2025 02:12:06 | Rosetta@home | Sending scheduler request: Requested by user.
23/12/2025 02:12:06 | Rosetta@home | Not requesting tasks: don't need (CPU: job cache full; NVIDIA GPU: no applications)
23/12/2025 02:12:07 | Rosetta@home | Scheduler request completed
23/12/2025 02:12:07 | Rosetta@home | Project requested delay of 31 seconds

Or perhaps like this:

23/12/2025 01:05:21 | Rosetta@home | Sending scheduler request: To fetch work.
23/12/2025 01:05:21 | Rosetta@home | Requesting new tasks for CPU
23/12/2025 01:05:22 | Rosetta@home | Scheduler request completed: got 1 new tasks
23/12/2025 01:05:22 | Rosetta@home | Project requested delay of 31 seconds

After you do those things and post back here, the solution might become apparent - no point guessing at this stage

NB: You've obviously registered on the website here, but is it too obvious to ask if you added the project (Tools menu, Add Project...) in the Boinc Manager with the exact same name and password as well?

---

I set up the Activities as you requested.

Here is the Event Log you requested;

12/23/2025 5:31:12 AM | Rosetta@home | update requested by user
12/23/2025 5:31:15 AM | Rosetta@home | Sending scheduler request: Requested by user.
12/23/2025 5:31:15 AM | Rosetta@home | Requesting new tasks for CPU and NVIDIA GPU and Intel GPU
12/23/2025 5:31:16 AM | Rosetta@home | Scheduler request completed: got 0 new tasks
12/23/2025 5:31:16 AM | Rosetta@home | Server error: feeder not running
12/23/2025 5:31:16 AM | Rosetta@home | Project requested delay of 3600 seconds

Thank you for your help!

P.S. --Everything is same Name and same Password.

Please check the following:
https://boinc.bakerlab.org/rosetta/hosts_user.php (From: Computers on this account -> View)
Which operating system is displayed?
Mine says “Alpine Linux” even though I have WIN 10. That's probably my problem.
However, I can't change that. Deleting and adding the PC doesn't change anything. I don't get any tasks. Same message: “Feeder not running.”

hi, try to look a this https://boinc.bakerlab.org/rosetta/forum_thread.php?id=6893&postid=113258#113258

some add to do in host file ^^

I set up the Activities as you requested.

Here is the Event Log you requested;

12/23/2025 5:31:12 AM | Rosetta@home | update requested by user
12/23/2025 5:31:15 AM | Rosetta@home | Sending scheduler request: Requested by user.
12/23/2025 5:31:15 AM | Rosetta@home | Requesting new tasks for CPU and NVIDIA GPU and Intel GPU
12/23/2025 5:31:16 AM | Rosetta@home | Scheduler request completed: got 0 new tasks
12/23/2025 5:31:16 AM | Rosetta@home | Server error: feeder not running
12/23/2025 5:31:16 AM | Rosetta@home | Project requested delay of 3600 seconds

Thank you for your help!

P.S. --Everything is same Name and same Password

Great. You're calling for tasks properly, but the Server you've been pointed to was changed about 9 months ago. There's no way you could know.

First thing to say, none of this is your fault. Everyone's had to sort this out at one time - old users and new.
Second, click this link and make the edit described in my post there.
Hopefully this solves your problem.
On the plus side, tasks are available to grab right now, so you should get some.

---

Thank you Sid Celery !

I modified my Hosts. It looks like this now;

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
#Rosetta@home
128.95.160.156 boinc-files.bakerlab.org
128.95.160.156 bwsrv1.bakerlab.org

Is this the way it should look?

Thank you Sid Celery !

I modified my Hosts. It looks like this now;

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
#Rosetta@home
128.95.160.156 boinc-files.bakerlab.org
128.95.160.156 bwsrv1.bakerlab.org

Is this the way it should look?

Yes, exactly that, and I now see that 2 tasks have arrived on your computer.
Success - away you go.

---

Thank you for the help!

Yes, exactly that, and I now see that 2 tasks have arrived on your computer.
Success - away you go.

Thank you for the help!

And they have now timed out with no response.



The default processing time for a Rosetta Task is 8 hours.
The deadline is within 3 days.

If you set your computer to suspend BOINC work with user activity- it will take much longer than 8 hours to actually return the work.
If you set the computer to suspend BOINC work if non-BOINC CPU activity is more than xxx%, it will take much longer than 8 hours to actually return the work.
If the computer only spends a few hours a day running, it will take much longer than 8 hours to actually return the work.


In your account, Computing preferences (or on the BOINC Manager if you set them locally).

Use at most 50% of the CPUs

You're running a low performance CPU laptop- this will help limit the temperature. Reduce the number if it's still too hot, increase it if the cooling is up to it.

Use at most 100 % of CPU time

The lower this value, the longer it takes to complete work.

Suspend when computer is in use

should not be selected.

Suspend when non-BOINC CPU usage is above --- %

should be left blank.
You're only using half (or less) of your cores/threads, so there's no need to suspend BOINC work when the computer is doing other things.

          Store at least 0.25 days of work
Store up to an additional 0.01 days of work

You can increase the "Store at least" value to 1 or 2 if you feel the need, but not until you have returned at least 10 or more Valid results.
Give BOINC a chance to figure out just how long it takes your system to return work before increasing the cache.

---

Grant
Darwin NT

Thanks for the help. I'm dropping Rosetta@home. I was unaware that I would have to let the PC run constantly. Off to other things.

Thanks for the help. I'm dropping Rosetta@home. I was unaware that I would have to let the PC run constantly. Off to other things.

It doesn't need to run constantly, but it does need to run long enough each day in order to do 8 hours of processing and return it before the deadline which is 3 days. If you choose to use different setting to the ones i posted, it can take longer than 8 hours to process a Task, even if that is all the system is doing.
The target Runtime can be set longer or shorter than the default 8 hours.

Other projects have longer & shorter processing times, but many of them have longer deadlines so you can do less work each day and still complete the Task before the deadline.

---

Grant
Darwin NT