Thread 'dualboot machines: same work units in both partitions????'

Message boards : BOINC Manager : dualboot machines: same work units in both partitions????
Message board moderation

To post messages, you must log in.

AuthorMessage
Profilellagos

Send message
Joined: 8 Mar 07
Posts: 35
Chile
Message 9494 - Posted: 10 Apr 2007, 21:47:37 UTC

Hi,

I have a laptop with dual boot... Win XP (on C:) and 2k3 (on E:)... I have boinc installed in both partitions, independently from each other.

Since I have been working lately in the office, so the work done has been from the w2k3 partition. When I go home and go into the wxp partition, all work units reported as 'expired' and so, I deleted them all and lost all those cpu time (and score!).

So, is there any way to have the project folder shared between partitions and opsys? I am even planning to install linux or solaris10 for i386 soon...

Regards,

Leo
ID: 9494 · Report as offensive
ProfileJord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15561
Netherlands
Message 9496 - Posted: 10 Apr 2007, 22:13:31 UTC

Just install BOINC in the same directory for all the operating systems you use.
You can still lose work though, if you don't switch between the OSes often enough.

But if you just install BOINC for all OSes in e.g. C:\BOINC, then all will run from there.
ID: 9496 · Report as offensive
Profilellagos

Send message
Joined: 8 Mar 07
Posts: 35
Chile
Message 9498 - Posted: 10 Apr 2007, 22:50:05 UTC - in response to Message 9496.  

Thanks! but my point was to not lose work... so, let's say I install boinc for the first time in wxp, under c:\boinc, attach all projects, run a few days...

then, I install w2k3 in e:, but I install boinc in the same c:\boinc...

will this second install recognize my previous work? I mean, will it add all my projects automagically, and will it start working after finishing the install process???

Or, shall it start blank, so I have to re-attach to all projects, and re-download new work, when I already have a lot half-way???

Regards,

Leo
ID: 9498 · Report as offensive
ProfileJord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15561
Netherlands
Message 9499 - Posted: 10 Apr 2007, 22:56:38 UTC - in response to Message 9498.  

will this second install recognize my previous work? I mean, will it add all my projects automagically, and will it start working after finishing the install process???

It won't recognize the work you are doing under the other OS, but the account_*.xml files should take care of your computer auto-attaching to all the projects. Just for each OS with its own host ID.

So your best course of work is to use a low connect to in your preferences and possibly, before you go switch OSes, put BOINC on No New Tasks and run the cache dry, upload & report. That way you won't lose work.
ID: 9499 · Report as offensive
Nicolas

Send message
Joined: 19 Jan 07
Posts: 1179
Argentina
Message 9500 - Posted: 10 Apr 2007, 23:57:15 UTC

Don't rely on projects having cross-platform checkpoints!
ID: 9500 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5129
United Kingdom
Message 9502 - Posted: 11 Apr 2007, 7:33:30 UTC

Do you have (or could you make) a third 'data' partition visible to both OSs? Or are you saying that the same C:\BOINC folder is visible all the time, whichever OS is in control?

Provided you do have a single folder which is visible all the time, and both OSs are flavours of Windows, you should be able to install BOINC to the common repository from both OSs, and crunch the same WUs with the same apps in either mode. Wouldn't work for a Linux/Windows dual boot, though.
ID: 9502 · Report as offensive
Profilellagos

Send message
Joined: 8 Mar 07
Posts: 35
Chile
Message 9510 - Posted: 11 Apr 2007, 14:10:11 UTC - in response to Message 9503.  

Thanks a lot for all your responses... it seems boinc manager is not yet ready to multiboot, although, I'd like to see that in an upcoming release.

In one of my previous laptop (a few years ago), I had seti@home installed three times (under winxp, win2k, and linux)... however, there was no "too late" warning with that program, so I could run any OS for a month, then the next one for another week, and so on, and never lose any work unit or score.

Maybe some admin here could put this feature into the wish list ????

at least for win flavors, it should be able, if installed in the same folder as an existing version, to recognize the existing projects AND work units and continue with those...

Regards,

Leo
ID: 9510 · Report as offensive
ProfileKSMarksPsych
Avatar

Send message
Joined: 30 Oct 05
Posts: 1239
United States
Message 9511 - Posted: 11 Apr 2007, 14:12:04 UTC

Projects set deadlines. They're not set by the BOINC core client.

Deadlines range from hours (some resends from PrimeGrid) to a year or more (CPDN).
Kathryn :o)
ID: 9511 · Report as offensive
clownius

Send message
Joined: 17 Feb 07
Posts: 35
Australia
Message 9537 - Posted: 12 Apr 2007, 5:31:03 UTC

One issue i can see with this is its going to be a lot of work. When i change Linux kernels it often decides its a new machine and i haven't lost work yet but expect i would and thats basically the same OS. Projects use different app for different OS's due to different things being supported by the different OS. Imagine someone trying to make the same science app do the same thing on Win98 and Vista. Everything would have to be dumbed down to 98 standards.
A lot of projects don't support more than the current 'doze platforms XP and some Vista so i cant see them making the app support 9x and Vista.
I know those are two very closely related Operating Systems yes but im certain things that worked on Vista don't always work on XP or the other way around otherwise you wouldn't need to dual boot anyway and this is the same problem thats going to go on with the science apps.
ID: 9537 · Report as offensive

Message boards : BOINC Manager : dualboot machines: same work units in both partitions????

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.