You can only do this when you move the complete BOINC directory (or Data directory in case of BOINC 6) with all sub-directories to the new PC, while the new PC must be using the same operating system platform and have the same CPU manufacturer as the old PC had.

So... Can do:
Windows 2000 -> Windows XP
Intel P4 -> Intel Core2

Can't do:
Windows XP -> Linux
Intel -> AMD

It also depends on which projects you are attached to, if they are updated enough to allow the above. In any case, all your work is registered to the PC that downloaded it, that same PC should upload it. The PC is registered at the project under the hostID. When you change CPU or OS, you will get a brand new hostID, to which all that work isn't registered, so it won't upload/report it to that one. Lost time and work.

If the OSes and CPUs don't match your best bet is to run out your cache on the present PC and if that's not possible, to abort all the work you have in progress and start anew on the other system.

After you moved the directory, you should of course install BOINC on the new system, pointing to the directory you just moved to install BOINC in.

Thanks. The problem is that the old PC will be "recycled" for another user, and BOINC will certainly be removed at this time. So I can't wait until they've finished then upload them. So I guess the WUs might as well be aborted when the PC goes away.

Yes, it's a known issue.

As you noticed, it happens when benchmarks are aborted because an application that has to be removed from memory failed to respond to the quit request within the 10 second interval that the BOINC core client allows. The problem is that the delayed quit response is never acted on and the core client keeps the application marked as running. If memory serves me right things do sort themselves out if the core client decides to schedule another result. It affects applications that have sequences of calculations that are indivisible (e.g. CPDN post-processing) most frequently.

It was first raised on the development mailing list more than 2 years ago by Chris Sutton and myself. I can remember raising it on the list at least twice since then with suggested fixes.

Edit: just checked and the 10 second limit is still in place for 5.10.*.

Just one other thing, hoping not to expose my ignorance too much :) What does Wiki stand for?

Quoted from Wikipedia.org: "The word wiki is a shorter form of wiki wiki (weekie, weekie) which is from the native language of Hawaii (Hawaiian), where it is commonly used as an adjective to denote something "quick" or "fast" (Hawaiian dictionary). In English, it is an adverb meaning "quickly" or "fast".

The first wiki, WikiWikiWeb, is named after the "Wiki Wiki" line of Chance RT-52 buses in Honolulu International Airport, Hawaii. It was created in 1994 and installed on the web in 1995 by Ward Cunningham, who also created the Portland Pattern Repository."

Take a full backup of the Boinc folder (with Boinc shut down) and copy it to the same location on another PC. Then just resume running. It'll phone home the results.

It's a complication that the other PCs you have to chose from also run Boinc, you'd need to move their installations to one side temporariliy.

It's important that you have the permission of anyone whose PC you use, i.e., your work needs to be happy that Boinc is running. I have heard of someone going to court through using a work PC.

...
I understand that if you suspend BOINC, that your monitor will power down at the end of the timeout?

Yes ... all is normal, and between the time the screensaver is enabled and when the monitors are supposed to power down, I see the "bouncing BOINC".

When you're working with BOINC, is it set to run always, or only when your computer is idle? And is that videocard really a card, or an embedded videochip on the motherboard?

I have it set to 'Activity=>Run based on preferences" ... without knowing what the preferences are. BOINC provides "Advanced=>Options" but I don't see screensaver options.

However, the screensaver setup offers "settings", for which "go to blank screen" was disabled, and "minutes until blank" set for 5 minutes. I will try enabling the "blank screen" and see what happens.

You have installed the latest drivers for your videocard and if appropriate for your monitor?

Yes ... It's up to date (according to Dell's support).

I don't think wildcards can be used... but the name of the other PC shouldn't change. So why not use that one in the remote_hosts.cfg file?

My first download for the seti project worked fine. It was processed and sent back. Now I have about 20 files that have downloaded and have been processed but keep failing. The upload starts and the Speed starts at about 0.10 KBps and the progress will get just past 2% and then it will fail and be set to retry in about 2 hours. I've tried retrying them manually with same result. Anything I can do?

Ken

nedsran-cdl,

I don't have the answer to your problem, as I have no experience with VPN. I can, however, steer you to what will most likely be a work-around. I'm sure that Task Manager has a listing on the Processes tab that controls your VPN, though I don't know which particular process. There is something called Process Explorer available (free, GoogleSearch for it) which will tell you what each process running is related to. I think that once you know which one works your VPN that you can exit the process and then restart it, allowing you to log on and connect again.

Here's hoping that someone will come along with a better solution.

OK I hope BOINC's weightings are longterm. I wanted SETI to get exclusive use of 1 CPUCore and The rest to share the 2nd (50/25/25). If SETI runs out of stuff and the server is broken then Einstein gets to monopoize a CPU while LHC/Climate shares the 2nd 50/50. Definitly looks like it don't work work that way.

Unfortunately I'm not likely to get into work for some time, so I won't be able to update the software.

You can TRY using BOINCView to attach to work instead of BOINC Manager. I don't know if that will make any difference, but it seems to work "locally" for multiple Windows computers regardless of BOINC versions... (I only have one PC, rest are Macs, so I haven't used it much.)

I suggest to update the remote client to a newer version just like your local client - does 4.25 has the password authentication actually?
As you have already set a password in gui_rpc_auth.cfg, you could start the remote client with parameter "-allow_remote_gui_rpc". The IP check will be disabled and that will allow you to connect from everywhere without the need of knowing the address but the password.