Excellent. Thanks for that. I will be updating my experiment log tomorrow. I have noticed a number of things, none particulaly damaging, but sufficiently odd to be note worthy. I will post here once I have done the updates.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

I have updated the experiment log with some observations. They are all in a section at the bottom, after the original conclusion.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Adrian
About: zero disk space on SETI.
BOINC has a problem with \"0\". Try \"0.0\"

Okay Les, I\'ll try an experiment. I have set it to zero, (integer), and expect all projects to continue. Then I\'ll set it to 0.0 and see that they all complain. Will update the experiment log and report back once I have done so.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Experiment log.

Summary, it would seem that the representation of zero is not a factor. Integer or real versions are accepted at some sites and ignored at others.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

@adrianxw

I think the reason new host-ids were created is because the scheduler keeps track of the number of times the client has contacted the server, and if the number is less than the expected, it assigns a new host-id (i remember reading this somewhere on the BOINC site

on a site note i must congratulate you on a very well documented and explained article on your site, if only all instructions were as easy to follow as your example :p

Lee

a potentially much simpler solution would be to periodically drain work for all other projects, make a backup of the whole BOINC folder (which would only contain the CPDN work) then resume and continue crunching

to restore i think it would just be a case of draining the work queues again and copying the whole BOINC folder backup to the \"live\" location (C:\\Program files\\BOINC)

correct me if i missed something

yes this takes longer than a \"stop, backup, restart\" type backup, but i think it\'d be much cleaner, and therefore safer, with fewer things to worry about, there\'s less to go wrong :)

thoughts please

Lee

a potentially much simpler solution would be to periodically drain work for all other projects, make a backup of the whole BOINC folder (which would only contain the CPDN work) then resume and continue crunching

Sounds right to me. But it does make the whole process of backing up a more drawn out process as you say, and I\'m wondering how many people will do it often enough. We all know how important it is to take regular backup of all our important files, but how many actually do it?

---

We all know how important it is to take regular backup of all our important files, but how many actually do it?

I\'ll be the first to hold my hand up in shame lol

been months since i\'ve done a system backup nevermind anything else