I found BOINC to be a little restrictive when trying this. The registry got very confused. Due dates of 1900 were common.

On the other hand, the UD version works very well for this type of application, called "sneakernetting", or walking your file back and forth on a floppy disk. Just copy everything in the prime directory where UD.EXE is located. These days, with USB ports, walking it back and forth on a flash drive has been even more reliable.

The add-on product UDMonitor can manage multiple slots. It takes a certain amount of concentration to keep from getting messed up since UDMonitor swaps the main directory in/out with various cache slots. That way, the internet computer and remote computer can BOTH be working on separate UD workunits. Good luck.

UDMonitor has one caveat. Since it was originally written for grid.org, it must be started with the WCG bat file to make it run for the WCG version.

Maybe you didn't catch that, O.

I did try testing the idea of moving files from computer to computer with BOINC and the registry got messed up on one or the other computers.

Since we still have an UD option here, running it that way works a lot better for swapping workunits from 1 or more remotes. I think it's because the UD install is simpler. If you don't want it any more, it can simply be deleted.

Naturally you can't run UD and BOINC simultaneously on the same computer. Just run one or the other. I still have both around, and ran some UD workunits last winter when the BOINC server was down 3 days in a blizzard.

As a minimum I'd set up UDMonitor with one cache slot for the internet computer and the second slot designated for the remote computer.

Try that way for awhile.

The remote computer doesn't have to have UDMonitor unless you want to stack up more than one workunit at a time. If so, match slots on the remote and internet computer to keep it straight.

Sneakernetting is one of the few places where the UD version still has an advantage.

On the down side, WCG will not be getting any more United Devices versions. At least one of the upcoming projects will be BOINC only. More computers now are dual core or quad core, which BOINC can take advantage of. That eventually will be much better than babysitting with a single core remote. Start BOINC and walk away.

Regrettably, the structure is such that part of the project file management is in files stored with the BOINC program, so only moving the project files is not an option. The one process working is to make sure you get the complete BOINC program with sub directories. AND, please make sure all the clocks (Time+Date) on all the machines between which you transfer the files are in sync. Minimises chance of work getting misdiagnosed as late or damaged. BOINC hates for clocks to be adjusted backwards when it is running, forward by small steps is not an issue.

Somewhere I read that if you have the machines on a LAN you can make a local time server. Since there is file transfer, albeit via a USB key, you could as well connect via Ethernet. Disconnect the router or modem while doing that.

Somewhere i flicked out a 13 step process of doing this.... might expand on that and put it in the Start Here FAQ as it does come up semi-frequently.