I run several ubuntu/windows dual-boot systems on which I have installed boinc. Because the ubuntu installs are not used with great frequency, boinc projects installed on them tend to not get completed before they time-out. Infact, I've removed boinc from the ubuntu instillations for this very reason.

I was wondering if there was some way to get the windows/ubuntu instillations to process the same projects?

Thanx

Bryan

I run several ubuntu/windows dual-boot systems on which I have installed boinc. Because the ubuntu installs are not used with great frequency, boinc projects installed on them tend to not get completed before they time-out. Infact, I've removed boinc from the ubuntu instillations for this very reason.

I was wondering if there was some way to get the windows/ubuntu instillations to process the same projects?

Thanx

Bryan

I had a similar problem where I had an XP boot and a VISTA boot and I felt bad that once I stuck with VISTA that the XP boinc projects would never get serviced. I found it useful to spend some time at Carolyn's Clinic where they offer treatment for boinc addition ;-)

I was wondering if there was some way to get the windows/ubuntu instillations to process the same projects?

Not possible as BOINC projects register which hostID tasks are sent to. Another host can easily do the work (with some difficulty of moving the complete BOINC data directory to and fro), but the host that downloaded the work must also upload it.

So in the end it's more of a hassle than it's useful.

---

I was wondering if there was some way to get the windows/ubuntu instillations to process the same projects?

Not possible as BOINC projects register which hostID tasks are sent to. Another host can easily do the work (with some difficulty of moving the complete BOINC data directory to and fro), but the host that downloaded the work must also upload it.

So in the end it's more of a hassle than it's useful.

Not strictly true. Work downloaded to a host with a particular host ID has to be uploaded from a host with the same host ID - but since the host ID can travel between different physical hardware in the BOINC Data folder, that in itself isn't a problem.

BeemerBiker could set up 2 copies of BOINC, with the program file installations in the appropriate program folders for each of the two Windows installations, but the data folder on a shared drive/partition visible to both OSs - perhaps a FAT32 disk, so that no pesky security descriptors could prevent access.

That won't work for Bryan, because he can't use the same applications in Linux and Windows: client_state.xml would have to be rebuilt every time the OS changed. The 'shared (multi-visible) data folder' idea can only work for compatible platforms: I wouldn't even use it for win-32 + win-64 unless I knew that every project in the shared installation sent 32-bit apps to 64-bit clients.

Thanx for the replies. This is what I expected, but a guy can hope...

...BTW, if any boinc programmers happen to have some time not needed to deal with real issues, this would be a feature some of us would enjoy.

Bryan

Thanx for the replies. This is what I expected, but a guy can hope...

...BTW, if any boinc programmers happen to have some time not needed to deal with real issues, this would be a feature some of us would enjoy.

Bryan

+1 :)

And what about such scenario:
suspend network connection before rebooting to different OS. Process taks under another OS but use network connection only from the same OS each time - will it work?
(Vista x86 /Server2008 x64 for example (all apps x86 ) )

---