Well thanks to Bobs dedication and stickling for procedures I was able to duplicate it perfectly! (unlike putting my machines on another account! )

Anyways both my i7 860 and 920 now have the same WUs and are now crunching these . I made a few changes to Bobs procedure though see bold below (I never could follow the rules! )

Quote Originally Posted by 123bob View Post
OK, I did it.

Here's how.

The 860 rig is the "host" machine.
The 920 is the "client" or "target" machine.

1. I suspended crunching on both. (activity - Suspend and Network Activity Suspended)

2. Aborted the current running WUs (Yes, I tried REAL hard not to scream... (This really pained me too! But better aborting them than losing them completely least this way the server will give it out to someone else!)

3. I aborted all "waiting to run" WUs on the 860 rig, except for 24 HFCC WUs. These are the test WUs.

4. "Updated project" so the queue was cleared. Only 24 units sitting there.

5. I aborted ALL the WUs on the 920 rig. (With the same screaming as above. I think the rig screamed louder though....) (This is where I changed tactic and simply put BOINC in activity - Suspend and Network Activity Suspended. Then exited/closed Boinc and made a copy of the Original files and then deleted the contents of the BOINC folder, pasted the 24WUs BOINC folder from the host and presto on starting BOINC it had the same WUs)

6. "Updated project" so the entire queue was cleared. No WUs in this rig. (No need for this step if you follow my suggestion above)

7. I copied the entire "BOINC" folder, under the app data folder on the 860 rig, on to a USB stick.

8. I made a backup of the BOINC folder of the original 920 rig so I can recover it later, I hope.....

9. I copied the BOINC folder from the 860 rig into the app data folder of the 920 rig.

10. I disconnected the network cable from both rigs. (Suspend network activity)

11. Rebooted the 860 rig and resumed crunching. It started on the test units. (No reboot just run BOINC again)

12. Rebooted the 920 rig, it then showed the test WUs. Ran benches, which turned out the same as reported before, then resumed. It is now crunching test WUs.