Using Win2k SR-4 (on Athlon XP3200), trying to install 5.2.2 it starts the install then partway through says it can\'t find BOINC.msi and asks me to tell it where it is. It creates a large (6391kB) .msi file with a name like 3547a6.msi in my temp directory, but if I try to use this instead (even if I rename it to BOINC.msi) the installer says it\'s not a valid installation file. Could this be because my temp directory (and indeed my home directory ) is on a second partition called u:? The installer should be able to cope- but can it?

EDIT: I don\'t think it\'s to do with the temp directory because I tried it again in the \'administrator\'account which is totally standard and got the same problem. And the md5 checksum on the .exe file I downloaded was correct so it\'s not corrupt.

Anyone have any ideas?

BTW, if already crunching a model using 4.45, if I install 5.2.2 will it continue with the same model? Or would I have to wait for this one to finish? (I have a backup of the whole 4.45 Boinc directory from before I started trying to upgrade- If it trashed the model I was planning to uninstall and roll back...)

Chris

---

I had no problems installing 5.2.2 on Win2k Chris, so that\'s unlikely to be the problem.

Do you have modified Access Control Lists? One of Microsoft\'s October patches can cause problems with MSI if you do. It\'s all detailed in this Knowledgebase article.

The error you describe doesn\'t match the one described in the article, but you might just be seeing another manifestation.

Your model should continue without any problems after installing 5.2.2

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

Another thing that it may be is a previous install did not clean up after itself properly. Rebooting and deleteing the contents of the temp folder may get things cleared out so that the new install will work.

---

BOINC WIKI

BOINCing since 2002/12/8

I had a similar problem on one PC, with it moaning that it couldn\'t find uninst.isu (I think that was the name). Eventually I fixed it by going into the registry and deleting the value referencing it. Dirty I know, but it worked. If you do this, back up the registry first of course, and also worth using a registry cleaner afterwards - I use Registry Mechanic.

Brian

---

Brian

I stumbled across this note while experiencing the same problem. I had 4.45 installed and could not get the 5.2.X install to get past the \"bionic.msi not found error\". Looking in the registry, indeed, the original install location for 4.45 was in the C:\\WINDOWS\\Downloaded Installations\\<some key> directory that no longer existed but was being referenced in the \"not found\" message.

The solution I found was to find the original distribution for 4.45 and re-run it. This will prompt you to either remove or repair. You can feel safe in choosing remove as it should leave your work units alone. This gets the registry properly cleaned up without resorting to manual editing.

At this point, the install of 5.2.X went exactly as expected.

As I have seen this in a couple of other forums with no resolution, I will drop a bug report into the BOINC team so they can take a look at it.

Hope this helps!

--Jon