I just got a replacement hard drive for my computer and installed seti@home. I have merged the old work units with the ones that I got in this installation, but I want to download that work to complete them (the old work has not expired). Can this be done?

You must copy the full "BOINC" folder in the "C:\ProgramDATA" directory over the new installation of BOINC.

---

Thanks, I'll give that a try

Yes, it can be done, while resend lost tasks is off, a double reporting of a completed task, and asking for work on the 2nd/3rd/4th etc attempt will trigger the server to do resend lost tasks.

Claggy

Do I have to wait the 5 minutes between update requests?

Do I have to wait the 5 minutes between update requests?

No, But the server will only resend 20 tasks at a time.

Claggy

Do I have to wait the 5 minutes between update requests?

No, But the server will only resend 20 tasks at a time.

Claggy

Actually, I've found that the minimal 5 minute interval is necessary. Otherwise, only the task reporting happens. The scheduler refuses to send any tasks if the last request was too recent.

I am doing something wrong: I hit the "Update" button numerous times and it says scheduler request completed, but the old tasks aren't coming.

I am doing something wrong: I hit the "Update" button numerous times and it says scheduler request completed, but the old tasks aren't coming.

It's not as simple as just hitting the "Update" button. As Claggy said, it first requires "a double reporting of a completed task". If you're not doing that each time, it won't fool the scheduler into sending the lost tasks.

There have been a couple threads on this topic earlier in the year. Specifically you could take a look at my post in Message 1798083, as well as a couple of links mentioned in that post.

OK, I think I can do that. Wish me luck; and I'll post my result here.

OK, I think I can do that. Wish me luck; and I'll post my result here.

It involves once you have a task ready to report, suspending network activity, and setting NNT, shutting down Boinc, saving a copy of the client_state.xml,
Starting Boinc, reporting the completed task, (*) shutting down Boinc, eithier restoring the saved client_state.xml (while incrementing the <rpc_seqno>number</rpc_seqno> by 2,
Or by restoring the <file> x2, <workunit> and <result> entries of the ready to report result into your existing client_state.xml,
Then starting Boinc, unsetting NNT, and network activity and asking for work
(* you can preselect the device that gets the lost wu's by selecting your project preferences to only ask for work for a particular device)

Here's an example of the entries that will need to be restored, (each in their respective (setiathome) portion of the client state.xml):

<file>
<name>31dc10aa.10522.11110.15.42.76</name>
<nbytes>365935.000000</nbytes>
<max_nbytes>0.000000</max_nbytes>
<md5_cksum>995498cfe5b13bbf9c85e92ce96dd3de</md5_cksum>
<status>1</status>
<download_url>http://boinc2.ssl.berkeley.edu/sah/download_fanout/396/31dc10aa.10522.11110.15.42.76</download_url>
</file>

<file>
<name>31dc10aa.10522.11110.15.42.76_1_0</name>
<nbytes>20907.000000</nbytes>
<max_nbytes>65536.000000</max_nbytes>
<md5_cksum>e6eaf4fba274f6403ff308acabadeee6</md5_cksum>
<status>0</status>
<uploaded/>
<upload_url>http://setiboincdata.ssl.berkeley.edu/sah_cgi/file_upload_handler</upload_url>
</file>

<workunit>
<name>31dc10aa.10522.11110.15.42.76</name>
<app_name>setiathome_v8</app_name>
<version_num>800</version_num>
<rsc_fpops_est>27722956047859.894531</rsc_fpops_est>
<rsc_fpops_bound>554459120957197.937500</rsc_fpops_bound>
<rsc_memory_bound>33554432.000000</rsc_memory_bound>
<rsc_disk_bound>33554432.000000</rsc_disk_bound>
<file_ref>
<file_name>31dc10aa.10522.11110.15.42.76</file_name>
<open_name>work_unit.sah</open_name>
</file_ref>
</workunit>

<result>
<name>31dc10aa.10522.11110.15.42.76_1</name>
<final_cpu_time>19116.990000</final_cpu_time>
<final_elapsed_time>21797.129266</final_elapsed_time>
<exit_status>0</exit_status>
<state>5</state>
<platform>x86_64-pc-linux-gnu</platform>
<version_num>800</version_num>
<final_peak_working_set_size>41734144</final_peak_working_set_size>
<final_peak_swap_size>53440512</final_peak_swap_size>
<final_peak_disk_usage>32101</final_peak_disk_usage>
<stderr_out>
<![CDATA[
<stderr_txt>
Not using mb_cmdline.txt-file, using commandline options.

Build features: SETI8 Non-graphics FFTW FFTOUT JSPF SSSE3 64bit
System: Linux x86_64 Kernel: 3.13.0-92-generic
CPU : Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz
2 core(s), Speed : 1333.000 MHz
L1 : 64 KB, Cache : 2048 KB
Features : FPU TSC PAE APIC MTRR MMX SSE SSE2 HT PNI SSSE3

ar=0.415240 NumCfft=198813 NumGauss=1137712906 NumPulse=226354770964 NumTriplet=452745632668
In v_BaseLineSmooth: NumDataPoints=1048576, BoxCarLength=8192, NumPointsInChunk=32768
Linux optimized setiathome_v8 application
Version info: SSSE3xjf (Intel, Core 2-optimized v8-nographics) V5.13 by Alex Kan
SSSE3xjf Linux64 Build 3306 , Ported by : Raistmer, JDWhale, Urs Echternacht

Work Unit Info:
...............
Credit multiplier is : 2.85
WU true angle range is : 0.415240
Pulse: peak=4.375068, time=64.63, period=1.326, d_freq=1420738678.58, score=1.01, chirp=-11.796, fft_len=128
Pulse: peak=4.388912, time=64.63, period=1.326, d_freq=1420738691.38, score=1.013, chirp=-12.779, fft_len=128
Spike: peak=24.04922, time=33.55, d_freq=1420745567.71, chirp=-12.8, fft_len=128k
Spike: peak=26.71989, time=33.55, d_freq=1420745567.7, chirp=-12.805, fft_len=128k
Spike: peak=24.0386, time=33.55, d_freq=1420745567.71, chirp=-12.807, fft_len=128k
Spike: peak=26.17782, time=33.55, d_freq=1420745567.69, chirp=-12.809, fft_len=128k
Spike: peak=25.39719, time=33.55, d_freq=1420745567.71, chirp=-12.811, fft_len=128k
Triplet: peak=11.10577, time=101.3, period=5.384, d_freq=1420745379.43, chirp=-87.489, fft_len=64
Triplet: peak=11.59668, time=101.3, period=5.384, d_freq=1420745385.84, chirp=-90.438, fft_len=64
Triplet: peak=11.94316, time=101.3, period=5.384, d_freq=1420745392.35, chirp=-93.386, fft_len=64

Best spike: peak=26.71989, time=33.55, d_freq=1420745567.7, chirp=-12.805, fft_len=128k
Best autocorr: peak=17.79475, time=33.55, delay=5.6584, d_freq=1420741764.76, chirp=-12.599, fft_len=128k
Best gaussian: peak=3.749324, mean=0.5467027, ChiSq=1.346167, time=84.72, d_freq=1420742160.72,
score=-0.4069557, null_hyp=2.191392, chirp=-83.956, fft_len=16k
Best pulse: peak=4.388912, time=64.63, period=1.326, d_freq=1420738691.38, score=1.013, chirp=-12.779, fft_len=128
Best triplet: peak=11.94316, time=101.3, period=5.384, d_freq=1420745392.35, chirp=-93.386, fft_len=64


Flopcounter: 38528944614795.328125

Spike count: 5
Autocorr count: 0
Pulse count: 2
Triplet count: 3
Gaussian count: 0
Time cpu in use since last restart: 19116.7 seconds
20:50:59 (12117): called boinc_finish(0)

</stderr_txt>
]]>
</stderr_out>
<ready_to_report/>
<completed_time>1469130669.031838</completed_time>
<wu_name>31dc10aa.10522.11110.15.42.76</wu_name>
<report_deadline>1473343613.000000</report_deadline>
<received_time>1468691148.374173</received_time>
<file_ref>
<file_name>31dc10aa.10522.11110.15.42.76_1_0</file_name>
<open_name>result.sah</open_name>
</file_ref>
</result>

Claggy

Well, I went through the process but instead of shutting down BOINC I hit the "red X" in the upper right corner, which closes most other software but not BOINC. (I knew that, but it slipped my mind) Anyway, it didn't work, so I'll let these units expire and be sent to someone else. Thanks everyone for your help.

Well, I went through the process but instead of shutting down BOINC I hit the "red X" in the upper right corner, which closes most other software but not BOINC. (I knew that, but it slipped my mind) Anyway, it didn't work, so I'll let these units expire and be sent to someone else. Thanks everyone for your help.

Tsk, tsk. A Jedi master who gives up so easily. Whatever is the galaxy coming to? ;^)

Well, I went through the process but instead of shutting down BOINC I hit the "red X" in the upper right corner, which closes most other software but not BOINC. (I knew that, but it slipped my mind) Anyway, it didn't work, so I'll let these units expire and be sent to someone else. Thanks everyone for your help.

Tsk, tsk. A Jedi master who gives up so easily. Whatever is the galaxy coming to? ;^)

I'm a faux Jedi Master who is frustrated with the chore of getting my replacement hard drive back to the state it was in before the original drive imploded (BOINC and the old WU's are low priority, but at least it's running). When my E-mail, security software, financial software, cloud storage, music program, etc. are up to speed, I may revisit this.

The hard drive was down for a month while the warrantee review and drive replacement (in Ohio no less) was done, so some of those WU's will be expired soon anyway.

Again, thanks for your help.