Admin, I need advice. I am about to upgrade host 105273.
26 May 2005 23:09:28 UTC
Topic 189240
(moderation:
105273 will go from socket A to socket 754 this weekend. I plan on a serious remake. I am running it dry of completed WU's and would like to know if there is a procedure I should follow to minimize penalties to me and the project when I come back as an A64. I do not want any more work sent to the previous incarnation, and plan to install 4.19 and reattach to Einstein after a clean install of XP. The rig will get a new PS, Vid card, 1 gig of ram, and mobo/proc. My best guess at this point is to upload completed WU's until the new 14.8 meg work schedule begins to download and then disconnect the lan cable. Seems crude, but there is an arms race. I have read that reducing your drive space for the project in preferences can prevent new work. I am concerned about potential impact on my other rigs if I do this. Aviso Por Favor.
Regards-tweakster
Admin, I need advice. I am about to upgrade host 105273.
)
Aviso Por Favor.
Regards-tweakster
1.) Determine which preferences are in use for the box from your computers page (home/work/school/---=default)
2.) Edit those preferences and set the "Leave at least" to a value larger than your HDD size.
3.) From the box, hit update to get the new prefs.
4.) Disable network access.
5.) Edit the prefs and set the "Leave at least" back to it's normal value.
6.) Wait for all work to be complete, do not re-enable network access before that.
7.) Once all work is complete and ready for upload, repeat step 2.
8.) Enable network access
Your box will upload and contact the server for new work, but will receive the message "not enough disk space" and no work will be sent.
9.) After all uploads are complete, hit update to report the results.
10.) Disable network access and detach from the project.
11.) Repeat step 5.
When you attach again with the new hardware, you will be given a new host id corresponding to your newly built and super slick A64.
Post again if unclear.
I need at least two more
)
I need at least two more helpful posts to confirm this information. There has to be an easier way to add horsepower to this project. Seems like cruncher upgrading was never in the minds of the project gurus. "Solid State physics" Of course. Is there any other? Thanks Ralic; waiting for confirmation from those who "been there, done that" .
Thanks for the post. Without confirmation, the legacy hard drive goes in the freezer. The SATA drive gets a new Host ID and I trash the remaining customers.
Regards: tweakster
I need at least two more
)
I need at least two more helpful posts to confirm this information. There has to be an easier way to add horsepower to this project. Seems like cruncher upgrading was never in the minds of the project gurus. "Solid State physics" Of course. Is there any other? Thanks Ralic; waiting for confirmation from those who "been there, done that" .
Thanks for the post. Without confirmation, the legacy hard drive goes in the freezer. The SATA drive gets a new Host ID and I trash the remaining customers.
Regards: tweakster
This is what I did with a box that had been crunching for a while but was now to be delivered to a person who was not interested in crunching.
Just before switching off, I shut down and uninstalled BOINC and moved the entire residue of the BOINC directory to a pen drive. I had been building a new box anyway with a similar but different speed processor (Sempron 2400+ compared to XP2000+) and a different socket A motherboard. After a fresh install of windows, I inserted the pen drive and copied the BOINC directory into place. I then reinstalled BOINC which then found all the E@H stuff already there. Processing simply continued with the same computer ID and the same work as before. The process was so painless that I didn't even write it down.
This was all done about 2 months ago using 4.19. I am speaking from memory but I don't recall any problems whatsoever. However, I may have just been lucky, so all standard disclaimers should be regarded as applicable to the above information. Use at your own discretion and risk.
Cheers,
Gary.
Tweakster, the thing is: you
)
Tweakster, the thing is: you are changing your motherboard and CPU, so no matter what and how many answers you request of people, your new PC will get a new host ID. Simple as that.
You are going from a socket A PC to a socket 754. Your penalty will be that whatever amount of credits you have at your present PC will stay at that and you'll start from zero at everything with the new PC. No way around it.
BOINC checks the hardware, remember? Those benchmarks when you first start up BOINC? Presto, answered.
I need at least two more
)
I need at least two more helpful posts to confirm this information.
S'ok, no offence, you don't know me.
There has to be an easier way to add horsepower to this project.
With the newer 4.4x series client there is, just select project and "No new work" button. I'm operating under the assumption that because you referred to installing 4.19 that it is also the version you're currently running and hence the drawn out procedure.
You also refer to minimizing project penalties, and this procedure will do that for you. If you'd showed no concern for the project, you could have been advised to just detach the project.
Thanks Ralic; waiting for confirmation from those who "been there, done that" .
You're welcome, and I've "been there, done that" more times than I can remember.
Anyways, I am among the first to advocate safety in all aspects, but while you're waiting for someone else to confirm it, you may want to take a look at this thread over at CPDN Decommissioning a machine
Oh, and this one too Can I gracefully leave?
When I have done upgrades in
)
When I have done upgrades in the past, where I add a new MB and CPU is to:
1 copy off the BOINC Folder ...
2 install hardware
3 FORMAT C:
4 install Windows
5 copy BOINC Folder back
6 Install BOINC over the old version (to add the keys etc.)
7 Finish WIndows installation and updates/SP ...
This way I only lose the time where I am doing basic installs ...
ralic, Paul d, Ageless, Gary;
)
ralic, Paul d, Ageless, Gary; Thanks for your excellent help. I propose to exit Boinc and burn the folder to CD. I will then "gut the fish" and proceed with my hardware duties. After the clean install of the OS plus AV plus updates from MS, I will copy boinc back to the C drive from the CD. three questions; My codes should already be there, once I establish a shortcut on the desktop should't Boinc just fire up? I don't have it set to start at boot. Btw, this rig is running the ugly 4.25 version. Who approved that? Am I missing anything? Thanks again for your help.
regards-tweakster
1: stop BOINC 2: Make a
)
1: stop BOINC
2: Make a backup of the BOINC directory
3: Rebuild your system
4: Reinstall Windows
5: Copy the BOINC folder back into Program FIles
6: Install desired version of BOINC over the copied directory
7: If you keep the same Windows sub version (XP->XP, 2000->2000) your HOST_ID will not change following this procedure. If you 'upgrade' from XP to XP x64 your HOST_ID will change.
Join team BOINCstats
ralic, Paul d, Ageless, Gary;
)
ralic, Paul d, Ageless, Gary; Thanks for your excellent help. I propose to exit Boinc and burn the folder to CD. I will then "gut the fish" and proceed with my hardware duties. After the clean install of the OS plus AV plus updates from MS, I will copy boinc back to the C drive from the CD. three questions; My codes should already be there, once I establish a shortcut on the desktop should't Boinc just fire up? I don't have it set to start at boot. Btw, this rig is running the ugly 4.25 version. Who approved that? Am I missing anything? Thanks again for your help.
regards-tweakster
Should work just fine.
BOINC WIKI
1: stop BOINC 2: Make a
)
1: stop BOINC
2: Make a backup of the BOINC directory
3: Rebuild your system
4: Reinstall Windows
5: Copy the BOINC folder back into Program FIles
6: Install desired version of BOINC over the copied directory
7: If you keep the same Windows sub version (XP->XP, 2000->2000) your HOST_ID will not change following this procedure. If you 'upgrade' from XP to XP x64 your HOST_ID will change.
A slight change to #7: If you keep the same windows sub version the host id will most likely not change. If you change the sub version the host id will most likely change. In either case the BOINC client may decide to do the less likely way for no easy to spot reason.
BOINC WIKI
BOINCing since 2002/12/8