Hoping somone can quickly help me out.

Long story short, lost internet access at home, and will likely be out at least another week.

Had both a desktop and laptop running Rosetta when this happened.

Still before deadlines.

Able to bring laptop to library to use their internet access.

Rosetta completed wu does not seem to want to upload. In Boinc Manager, "Status" says "uploading".

Any ideas on how I can return these results?

(I assume desktop results will have to be transferred to laptop, and somehow "trick" Boinc into thinking the laptop completed them, but what do I know,lol!)

Thanx!

Hoping somone can quickly help me out.

Long story short, lost internet access at home, and will likely be out at least another week.

Had both a desktop and laptop running Rosetta when this happened.

Still before deadlines.

Able to bring laptop to library to use their internet access.

Rosetta completed wu does not seem to want to upload. In Boinc Manager, "Status" says "uploading".

Have you tried telling it to re-try the transfer?

Go to the transfers tab (in the 'advanced' view, if you have the newer version of the manager), highlight one of the files, click Retry Now (or some such, I am typing this from memroy). This may be enought to get it going, or if not repeat for all other files.

Any ideas on how I can return these results?

(I assume desktop results will have to be transferred to laptop, and somehow "trick" Boinc into thinking the laptop completed them, but what do I know,lol!)

Assuming everything is on windoze, and assuming you can connect the desktop to the laptop via windows networking, proceed as follows

1. copy the desktop BOINC folder to somewhere on the laptop that is close to the laptop BOINC folder without actually overwriting it. If you have the default install then the folders will be at C:Program FilesBOINC in each case. So for example copy

\DesktopProgram FilesBOINC to \laptopProgram FilesBOBO

The copy may involve internal copies on one or both machines to get the file to a shared part of your drive, depending on how you have the windows networking set up.

You can safely leave BOINC running on the laptop while doing this, but make sure BOINC is stopped on the desktop or you will transfer an inconsisten set of files.

2. At the library, start BOINC as usual, and upload and report all laptop work. If you want to do this once a week till your connection comes back, allow it to download new work, and wait till all the transfers are complete. If you don't want to have to do this exercise once a week, then make sure you have set Don't Fetch Work or whatever it is called.

3. When all transfers are complete, stop BOINC.

4. Rename the BOINC folder to something else, say BOLAP.

5. Rename BOBO to BOINC.

6. Start BOINC

7. Repeat as for 2. The work willl be identified with the desktop hostid, but the machine info will get reported as for the laptop. If the server gets confused it may give you a new hostid, and in this case it may or may not refuse to accept the work. However I have never had any probls with this. As in 2, decide whether you want to download new work to be done on the desktop, or do you want to rest the desktop till the proper connection comes back. Before doing the update you will have set Allow Work Fetch or Don't Fetch Work as appropriate.

8. Stop BOINC.

9. Rename BOINC to BOBO

10. Rename BOLAP to BOINC.

11. Restart BOINC if req'd.

12. If you downloaded work for the desktop, delete the original BOINC folder from the desktop and copy BOBO back onto it.

13. If you did not download new work for the desktop, reset every project to make it forget the files it still thinks need to be downloaded.


I have almost done this sequence, but for a single desktop and with a USB drive instead of a laptop. It worked for me.

Final thoughts

Returning Linux results from a windows machine will not work on this technique, or vice versa. But different versions of the same family (eg win2k and winXP) worked fine. It would be sensible, if possible, to have the same version of BOINC on both machines in case there are registry issues with version changes. With any luck you already do have. If not then you are going to have to update one of the boxes - possible by bringing the install file home on the laptop...

Good Luck!
River~~

---

@River - Thanx. I'll give it a try. Just want to avoid wasted crunching.

Any ideas on how I can return these results?

(I assume desktop results will have to be transferred to laptop, and somehow "trick" Boinc into thinking the laptop completed them, but what do I know,lol!)

Didn't seem to work. Don't understand why, everything you said made sense. Lost about two hours of Rosetta work on my laptop,

Probably gonna hafta lug the desktop over to my brother's, and borrow his internet connection.

I understand that this situation is not common, but if there had been an easy way to transfer files back and forth on my laptop from a public library internet connection to my desktop at home without an internet connection, I probably could have completed 2 weeks of Rosetta crunching.

Not a great loss, but if it was not too complicated, I would have made the effort to transfer files back and forth to my destop to keep Rosetta going.

Guess my AMD A64 gets a two week vacation...

@River - Thanx. I'll give it a try. Just want to avoid wasted crunching.

Any ideas on how I can return these results?

(I assume desktop results will have to be transferred to laptop, and somehow "trick" Boinc into thinking the laptop completed them, but what do I know,lol!)

Didn't seem to work. Don't understand why, everything you said made sense.

I don't *know* why it didn't work either, but looking at your computers my best guess would be that the difference between a 64 bit cpu and a 32 bit cpu might be enough to make the server smell a rat.

Bad luck, and nice try is the only other thing I can say.

The reason it is not made easy to do this is that in the early days of classic Seti people used to use variations of this for cheating, and even tho that would not work any more for other reasons, by the time the door had shut on that cheat the devs had locked themselves into the current strategy.

Yet another example of the well known observation that a few bad apples can spoil a whole barrel or [insert your simile here]

R~~

I got an AMD 64bit -so if you get to England!!!!
Woud do my credits no harm.

---

@River - Thanx for the effort, and background info.

@Michael.L - Would love to head over, but alas I think my deadlines on those wu's have now expired. Maybe next time I can send some credit your way!

I got an AMD 64bit -so if you get to England!!!!
Woud do my credits no harm.

@River - Thanx for the effort, and background info.

@Michael.L - Would love to head over, but alas I think my deadlines on those wu's have now expired. Maybe next time I can send some credit your way!

I got an AMD 64bit -so if you get to England!!!!
Woud do my credits no harm.

Note that Rosetta will credit you for returned work well after the deadline - the deadlines set are more of an advisory thing than a cut-off, and to make sure that other projects with short deadlines don't sideline Rosetta forever.

If the work has not been crunched, don't start it after the deadline, but if it has already been crunched, it is certainly worth tryont to retuen in the 'offical' way once your normal connection is restored.

R~~