Hi Folks,

I am using Windows Vista Home Premium Service Pack 2, and BOINC version 6.6.38.

It seems that I have installed the BOINC software okay. The problem I have stems from my attempting to attach to a third project. I identified myself but provided the wrong password for my account. I did receive a message to resend my password but I cannot find a way to do so. This is because the BOINC Manager at the 'Projects' tab cycles through the appearance of my selected projects and a blank page.

How should I proceed?

Which project is this at?

---

Cosmology@Home

Okay, go to http://www.cosmologyathome.org/get_passwd.php and use the top option.

Alternatively you can log in with your account key, which can be found in the account_www.cosmologyathome.org.xml file in your BOINC Data directory. Copy the number between the <authenticator></authenticator> tags into the bottom option on that page.

Make sure that once you have logged in, that you set your password again.

---

Thanks, I now have a new password for my account (as an aside, I did know my password; I had failed to use it).

I have rebooted my computer. The BOINC Manager now presents me with these messages:

15/10/2009 12:29:57 Starting BOINC client version 6.6.38 for windows_intelx86
15/10/2009 12:29:57 log flags: task, file_xfer, sched_ops
15/10/2009 12:29:57 Libraries: libcurl/7.19.4 OpenSSL/0.9.8k zlib/1.2.3
15/10/2009 12:29:57 Data directory: C:\ProgramData\BOINC
15/10/2009 12:29:57 Running under account Andrew
15/10/2009 12:29:57 Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU E7300 @ 2.66GHz [x86 Family 6 Model 23 Stepping 6]
15/10/2009 12:29:57 Processor features: fpu tsc pae nx sse sse2 pni mmx
15/10/2009 12:29:57 OS: Microsoft Windows Vista: Home Premium x86 Edition, Service Pack 2, (06.00.6002.00)
15/10/2009 12:29:57 Memory: 3.25 GB physical, 6.68 GB virtual
15/10/2009 12:29:57 Disk: 288.02 GB total, 253.71 GB free
15/10/2009 12:29:57 Local time is UTC +1 hours
15/10/2009 12:29:57 No CUDA-capable NVIDIA GPUs found
15/10/2009 12:29:57 No coprocessors
15/10/2009 12:29:57 Not using a proxy
15/10/2009 12:29:57 rosetta@home URL: http://boinc.bakerlab.org/rosetta/; Computer ID: 1079169; location: (none); project prefs: default
15/10/2009 12:29:57 Einstein@Home URL: http://einstein.phys.uwm.edu/; Computer ID: 1886387; location: home; project prefs: default
15/10/2009 12:29:57 Cosmology@Home URL: http://www.cosmologyathome.org/; Computer ID: 41701; location: (none); project prefs: default
15/10/2009 12:29:57 rosetta@home General prefs: from rosetta@home (last modified 06-Jun-2009 20:15:07)
15/10/2009 12:29:57 rosetta@home Host location: none
15/10/2009 12:29:57 rosetta@home General prefs: using your defaults
15/10/2009 12:29:57 Preferences limit memory usage when active to 2493.95MB
15/10/2009 12:29:57 Preferences limit memory usage when idle to 2992.74MB
15/10/2009 12:29:57 Preferences limit disk usage to 20.00GB
15/10/2009 12:29:57 Running CPU benchmarks
15/10/2009 12:29:57 Suspending computation - running CPU benchmarks
15/10/2009 12:29:57 Cosmology@Home [error] File params_092809_220101_2.ini has wrong size: expected 1911, got 0
15/10/2009 12:29:57 Cosmology@Home Started download of params_092809_220101_2.ini


There is a greater context to this: I did uninstall/delete BOINC Directory/reinstall, several times. I am sorry now, but I did lose projects' data. I'm guilty of impatience and incompetence.

After starting the Manager connects to the client but then clears the listing of Projects under the Projects tab.

By going back to version 6.2.28 of BOINC, my computer is now crunching for my selected projects.

...
15/10/2009 12:29:57 Cosmology@Home [error] File params_092809_220101_2.ini has wrong size: expected 1911, got 0
...

That's a known bug in the Cosmo project (server side!) and has nothing to do with the BOINC client version.

It happens with all resent workunits. The second (and each following) delivered result is damaged.

Unfortunately each error result and each result not returned in time produces 4 results with download failure, so sometimes you get several download failures in a row.

Just retry until you get a "fresh" result :-)