I plan to upgrade my pc in the future with an Athlon XP 3000+ cpu. The rest of the hardware will remain the same. Can I continue my current work unit in this case, or will CPDN not recognize it as the same pc?

In my opinion your PC is identivied over your IP address, but nevertheless behind this Ip stands your PC(CPU,...). I'm not sure but I think you should only to have to run a benchmark and then all should work!But I'm not sure at all!!!

Simply make an backup of BOINC and have a try ;-).

Greetings from Germany!
Basti

> I plan to upgrade my pc in the future with an Athlon XP 3000+ cpu. The rest of
> the hardware will remain the same. Can I continue my current work unit in this
> case, or will CPDN not recognize it as the same pc?
>

you shouldn't have any problems...


Your PC is identified by your hostid...
<img border="0" height="80" src="http://11730.cpdn.sig.boinc.dk?188">

it should be fine, the next time BOINC runs benchmarks you'll see the updated numbers for your CPU etc.

That's great, then I don't have to wait a month until my current workunit finishes before I can upgrade.

Thanks for the help!

I've upgraded several boxes over time and have had no problems.. an OS change, now that's an issue....

Just in case the comp would be recognized as a different one, you can click on "merge computers", so no problem at all. But just a CPU upgrade won´t change anything in that aspect.

&gt; Just in case the comp would be recognized as a different one, you can click on
&gt; "merge computers", so no problem at all. But just a CPU upgrade won´t change
&gt; anything in that aspect.
&gt;
In fact, I just up-graded my entire computer and switched from a 2.2 Ghz chip to a HT 3.6 Ghz chip. I copied my old hard drive to my new hard drive, and then copied the Boinc folder to its place in the program folder. I downloaded the newest version of Boinc and the thing worked! It picked up my old WUs from SETI, LHC, and CPDN and started happily crunching away. So, I have to think that a "mere" CPU change won't have an adverse effect.

Good luck.

Mark

I upgraded from an Intel 2.0GHz to a 3.2GHz HT with no problems, then I changed from W2K or XPSP2 again with no problems. BOINC and CPDN were fine...happy days.

Live long and crunch!

<a href="http://www.boinc.dk/index.php?page=user_statistics&amp;project=sah&amp;userid=31411"><img border="0" height="80" src="http://31411.sah.sig.boinc.dk?188"></a>BOINC Beta

I've been running with the new cpu for a couple weeks now, and indeed there have been no problems whatsoever. Well, except it got a little too hot in the beginning, forcing me to buy a bigger cooler. But now it works perfectly :-)

Hm, so you're saying a new Motherboard, new HDD and (in case of a new Linux Distribution and a fresh Installation) consequently a new Kernel Version wouldn't make CPDN discard its current work ?

This Idea has been worrying me ever since.
___________________________________________
<p>Scientific Network : <a href="http://www.falconfly.de/network.htm">36200 MHz «» 8204 MB «» 815.0 GB</a> </p>

&gt; Hm, so you're saying a new Motherboard, new HDD and (in case of a new Linux
&gt; Distribution and a fresh Installation) consequently a new Kernel Version
&gt; wouldn't make CPDN discard its current work ?
&gt;
&gt; This Idea has been worrying me ever since.

Why should it? In my case I went from a 2GHz cpu with my system on W2K to a 3.2GHz cpu with my system on XPSP2. As I had the same HDD all I had to do was re-install BOINC and it picked up from where it left off as BOINC does not delete the existing directory, it just updates the relevant files where client_state.xml is not one of them. As I said....happy days.

Then my wife went and moved the case 6 inches while she was cleaning up and accidently hit the reset key, which caused major problems with BOINC. Lost all references to all projects, even the client_state_prev.xml file was stuffed. Bugger. Overall the machine hasn't been the same since. I haven't been able to stay online for more than 5 minutes (dial-up / remote host disconnects) which is causing multiple failures while trying to re-attach to cpdn (sorry guys, I think I've wiped about 6 wu's over the past few days - if only BOINC would remember where it was upto and continue downloading from where it left off!).

<a href="http://www.boinc.dk/index.php?page=user_statistics&amp;project=sah&amp;userid=31411"><img border="0" height="80" src="http://31411.sah.sig.boinc.dk?188"></a>BOINC Beta