On the current second partition on my current drive, drive F:, I am having a configuration problem.

I am using BOINC Manager 6.10.58 there.

On another partition, drive C:, I have for 6.10.58, apparently C:\Programfiler\BOINC, C:\Programfiler\BoincLogX and C:\Programfiler\SMV (for Seti@home-MapView).

I still have an older version of BOINC Manager (5.10.30) residing in F:\Programfiler\BOINC(1), but it is of not too much use anymore and I am in the process of getting rid of it right now.

In order to access these applications, these icons (as well as program folders) are located on the Start-menu.

Possibly the icons can be found on my desktop as well and also on my Quick-Start-menu (those icons located to the right of the Start-button at the bottom of the Windows XP desktop and belongs to my local user name, otherwise 'All Users').

Some of this should be running as well in F:\Documents and Settings\Programdata\BOINC .

But I do not have this stuff located there. Instead it lies in
F:\Documents and Settings\All Users\Application Data\BOINC Data .

Blame an older installation other than 6.10.58 or 5.10.30 for this, perhaps?`

Maybe 6.2.19 (which I did not like too much), or maybe 6.6.36 (which was quite a bit better, not too much different than 6.10.58).

I did a re-install of BOINC Manger (not un-installing the older version first, but otherwise exiting it completely first).

Also I did the same for BoincLogX.

Right-clicking BoincLogX and choosing Setup BoincLogX, in the first box 'Directories', I can see it labeled
F:\Documents and Settings\All Users\Application Data\BOINC Data.

And as I am writing on this stuff, I am able to see that I of course am able to change that directory to the correct one that I will be going to be using.

Problem halfway solved, but I already re-started BOINC Manager and attached to PrimeGrid and was about to do the same for this project.

I will have to re-do it. Bummer me!

I also notice the following:

For BOINC Manager 6.10.58, when the CUDA-option is not set, the Manager thinks that I am having only two processors, rather than the eight that I am in fact having.

Anyway, four cores, if I am not wrong, each of them capable of running two tasks (simultaneously).

So, therefore, first running on one PrimeGrid task and a Seti@home task which I got a little later (waiting in the queue, but not too long), I had to activate the CUDA-option in order to get the other 6 or more tasks that I should have.

Perhaps this has been corrected in the most recent versions of BOINC Manager?

I still do like BOINC Manager 6.10.58.

If you want to move your BOINC data directory:

• uninstall BOINC (that won't delete any currently downloaded tasks)
  
• copy (move) the BOINC data directory to where you want it
  
• reinstall BOINC using advanced mode (third screen) and point the installer to the new data directory
  
• restart BOINC (should continue where it left off)
  

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

You know, most people use just a single installation. I suppose if you keep creating multiple accounts to get around bans than this sort of thing can happen.

Currently, I have 4 PCs running BOINC (Seti, LHC, Einstein and Climate Prediction) with each unit using its own program and data directory. Would it be possible (advisable) to place the data directory in a common location and have all PCs draw from that source?

Secondly, 2 of the 4 units are x64, whilst the other 2 are x32, so could I have those pairs share a common program directory, say BOINC64 and BOINC32 respectively?

---

Would it be possible (advisable) to place the data directory in a common location and have all PCs draw from that source?]

In network storage, you mean? Not advisable, since all those PCs will write their own version of the client_state.xml file to that one directory, nothing even said about all the slot directories that will clash.

No, not possible at this time, or when possible, totally not advisable.
But why? What's wrong with leaving it on the systems?

Secondly, 2 of the 4 units are x64, whilst the other 2 are x32, so could I have those pairs share a common program directory, say BOINC64 and BOINC32 respectively?

Again, why?
This time it's not possible, since BOINC (and its installer) writes things about itself to the registry, something it won't do when it's started from over the network.

---

Would it be possible (advisable) to place the data directory in a common location and have all PCs draw from that source?]

In network storage, you mean? Not advisable, since all those PCs will write their own version of the client_state.xml file to that one directory, nothing even said about all the slot directories that will clash.

I have been thinking about trying to use a common data/subdirs in a dual boot situation.

Would that be possible? There would be no i/o clash since only one os would be active.

The first obstacle I see is one os is WinXP 32-bit and the other is Win7 Ultimate 64-bit, so app names in app_info.xml could be a problem.

Any thoughts??? Anyone.

Lt

edited...

App versions is the least of your problems, as again both BOINC versions will write their own client_state.xml file to that directory. There can only be one of most all BOINC's active files. It will also clash with slot directories.

On top of all of that, work downloaded by one machine must also be uploaded by that machine, as it's registered to that machine's hostID.

---

App versions is the least of your problems, as again both BOINC versions will write their own client_state.xml file to that directory. There can only be one of most all BOINC's active files. It will also clash with slot directories.

On top of all of that, work downloaded by one machine must also be uploaded by that machine, as it's registered to that machine's hostID.

It would only be one machine using seperate drives. The necessary BOINC files would reside on a data drive either os could access. But only one os would ever be running BOINC at a time.

Lt

edited...

App versions is the least of your problems, as again both BOINC versions will write their own client_state.xml file to that directory. There can only be one of most all BOINC's active files. It will also clash with slot directories.

On top of all of that, work downloaded by one machine must also be uploaded by that machine, as it's registered to that machine's hostID.

It would only be one machine using seperate drives. The necessary BOINC files would reside on a data drive either os could access. But only one os would ever be running BOINC at a time.

Lt

edited...

Unfortunately, dual boot does not work with a shared directory in many situations as the executable for linux and windows are not the same. When you booted in linux after using windows, the executable would be wrong and would crash.

---

BOINC WIKI

I do expect to run into unexpected problems and plan on making backups from the start. Should probably even disconnect BOINC from the internet to keep the servers out of the mix until each os can run BOINC successfully - assuming that can/will happen.

Lt

Great!!!

________________________
Awnings

I have been thinking about trying to use a common data/subdirs in a dual boot situation.
Would that be possible? There would be no i/o clash since only one os would be active.
The first obstacle I see is one os is WinXP 32-bit and the other is Win7 Ultimate 64-bit, so app names in app_info.xml could be a problem.

I do it now successfully for WinXP 32-bit + Vista 32-bit
BOINC installed in Vista, then RegEdit info transferred to WinXP
[HKEY_LOCAL_MACHINE\SOFTWARE\Space Sciences Laboratory, U.C. Berkeley\BOINC Setup]

On the same multi-boot system I was unable (3 years ago) to do this for WinXP 32-bit + Vista 64-bit
(I had trouble to resolve something about directory permissions, I don't know if I can do it now, I didn't reboot in Vista 64-bit for years)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Thanks for your input, BilBg!

This job is still on the 'things to try' list.


Lt