Steveleg is making a wise and proper choice.

The only reason I am using anything beyond that is because I wanted the controls on the screen saver that allow me to show only the BOINC screen saver and what projects and work units are running.

This way, I can just glance at the monitor and know what is going on. This is not available on 6.10.18, and apparently only started with 6.10.25, yet another build that went to the build graveyard.

I thought all the WCG projects were 32 bit, so why would it matter if the BOINC agent was 64 or 32 bit? Aren't both versions multi-core aware?

This is using 6.10.43 from what I read. I don't think this addresses any of the problems I recently had in moving from 6.2.28 to 6.10.18. Is there any warning about changes in perhaps a file format between these two releases?

dkt,

It's a head scratcher but to me it's either a bug or a precautionary feature since the data directory part is from 6.2.28 in a separate store away from the C:\program filesxxx structure.

Under the following conditions things may still be recoverable.

1. The 6.10.18 install got a new device ID. Looks like that happened.
2. The C:\ProgramData\BOINC exists and has not been touched since upgrading from 6.2.28 (The message log start up section of 6.10.18 will tell what that data_dir path is.

If so:

a. Stop work fetch when running 6.10.18 and abort all tasks, or finish them.
b. exit BOINC completely.
c. Make a backup of the data_dir that 6.10.18 is looking at.
d. Copy the complete 6.2.28 data_dir as presumed to be per point 2. to that of the 6.10.18 install's data_dir
e. Start BOINC service again.

No guarantees, but the device might take on the ID of the old install and or erase the tasks and declare them aborted or something to that effect.

If too much effort, let it be and the tasks that were assigned to 6.2.28 will expire in time.

PS: In principle far as WCG project is concerned all files for tasks/science applications are same, 32 bit, but the 64 bit 6.10.18 install could just be assuming that the science apps have to be re-retrieved in 64 bit version which there are at other projects... i.e. the old data files were just plain cleaned out.

Hmm, looks like v6.2.28, then this version was uninstalled as part of the installation of new BOINC-version, also moved the data-directory to the "c:\program files (x86)\boinc"-directory. The back-migration should really only happen if computer has previously had v5-client installed, something that clearly isn't the case on your brand-new computer...

But in any case, since v6.2.28 has moved the data-directory to "c:\program files (x86)\boinc", and the 64-bit BOINC-client uses "c:\program files\boinc" instead, it won't see the 32-bit files, and you'll lose anything.

The work-around for anyone upgrading from v6.2.xx 32-bit to 64-bit would be:
1: (optional) Uninstall v6.2.xx-client.
2: Install a 32-bit v6.10.xx-client.
3: Uninstall 32-bit v6.10.xx-client.
4: Install 64-bit v6.10.xx-client.

This work-around will work, since v6.10.xx-client doesn't unneccessarily move the data-directory as older clients did.


As for recovering your lost work, you could finish (or abort) any currently-assigned tasks, uninstall your 64-bit version, delete the data-directory, and afterwards do step 2, 3 and 4 in the list...

But, there is a chance all work will be marked as "bad" when connects to scheduling-server, so in practice it's likely better to just let the tasks time-out and be automatically re-assigned by server.