The motherboard on one of my machines died this weekend. Due to Berkley's electrical problems I still have 12 completed WUs waiting to upload on this box. I did manage to copy the BOINC directory to a flash drive before the machine died completely. If I copy this directory to another machine and run BOINC, will the results be accepted by SETI?

> The motherboard on one of my machines died this weekend. Due to Berkley's
> electrical problems I still have 12 completed WUs waiting to upload on this
> box. I did manage to copy the BOINC directory to a flash drive before the
> machine died completely. If I copy this directory to another machine and run
> BOINC, will the results be accepted by SETI?
>
NO, each workunit is tied to a specific machine and any other machine that either processes it or returns it will result in no credits being issued. A cache is "in the works" but who knows when, what with al lthe other issues going on right now.

---

Bummer :(
I thought that is what would happen. I might try it anyhow as the WUs will be well overdue by the time I can get the parts and recap the motherboard. I have another box with the same hardware & OS installed, only difference is the amount of RAM. I won't get credit for them anyway if I upload them after the machine is repaired.

> Bummer :(
> I thought that is what would happen. I might try it anyhow as the WUs will be
> well overdue by the time I can get the parts and recap the motherboard. I have
> another box with the same hardware & OS installed, only difference is the
> amount of RAM. I won't get credit for them anyway if I upload them after the
> machine is repaired.

It all depends on how long it takes for the machine to get repaired -- if it's fixed in a couple of days, you'll likely still get credit.

... and if it's going to take a couple of weeks, try putting them on another machine and see what happens -- nothing ventured, nothing gained.

---

> The motherboard on one of my machines died this weekend. Due to Berkley's
> electrical problems I still have 12 completed WUs waiting to upload on this
> box. I did manage to copy the BOINC directory to a flash drive before the
> machine died completely. If I copy this directory to another machine and run
> BOINC, will the results be accepted by SETI?

That answer is incorrect.

You MAY upload results from a different machine but not from another host.

What do I mean by this?

If machine #1 breaks down, and machine #2 is already a host for a given project...you cannot copy the result files to the project directory of machine #2. This will not work.

If machine #1 breaks down...
A. and you stop any BOINC software running on machine #2. (if there is one)
B. and you move the machine #2 boinc directory to some backup location. (so there is no longer a folder where BOINC used to be)
C. and you copy the entire BOINC directory and subdirectories from the HDD of machine #1
D. to the same folder path location BOINC used to be on machine #2
E. and you launch (double click) the boinc_gui executable from the newly copied directory
F. It should begin running on machine #2.

You should tell the copied boinc not download more WUs. The newer client (4.2x) can do this when told to "phaseout" a project (you may have to use boincview to tell it so). Or you can change the venue (general, home, work, school) that the boinc host belongs to so that it won't get more. (ie change max HDD for that venu to 1 megabyte, or similar)

> That answer is incorrect.
>
> You MAY upload results from a different machine but not from
> another host.
>
> What do I mean by this?
>
> If machine #1 breaks down, and machine #2 is already a host for a given
> project...you cannot copy the result files to the project directory of
> machine #2. This will not work.
>
> If machine #1 breaks down...
> A. and you stop any BOINC software running on machine #2. (if there is one)
> B. and you move the machine #2 boinc directory to some backup
> location. (so there is no longer a folder where BOINC used to be)
> C. and you copy the entire BOINC directory and subdirectories from the HDD of
> machine #1
> D. to the same folder path location BOINC used to be on machine #2
> E. and you launch (double click) the boinc_gui executable from the newly
> copied directory
> F. It should begin running on machine #2.
>
> You should tell the copied boinc not download more WUs. The newer client
> (4.2x) can do this when told to "phaseout" a project (you may have to use
> boincview to tell it so). Or you can change the venue (general, home, work,
> school) that the boinc host belongs to so that it won't get more. (ie change
> max HDD for that venu to 1 megabyte, or similar)
>
>

Thank you.
If I cannot get the new capacitors in time I will give this a try.

To keep it from downloading any new WUs, I am guessing I should also edit the global_prefs.xml file before starting the client. True?

> That answer is incorrect.
>
> You MAY upload results from a different machine but not from
> another host.
>
> What do I mean by this?
>
> If machine #1 breaks down, and machine #2 is already a host for a given
> project...you cannot copy the result files to the project directory of
> machine #2. This will not work.

You could probably save the files from one host, replace them with files from the other host, and then upload?

---

> You could probably save the files from one host, replace them with files from
> the other host, and then upload?

Most probably.

Anyway, what I did recently and no project I take part in complained is that I changed one computer with a new one. The same OS, but different hardware (faster :) ). I installed boinc client (of newer version), copied all other files (project and slot directories plus all xml files) and voila, I have the same host (acording to project stats) with different hardware.

No problems at all.

---

Metod ...