Hello. I posted the message below to the seti@home message board and thought it might help out some others. It is in response to a user who was having trouble with BOINC after upgrading to IE7.

Thanks,

Bill

----------

Hello. I also had a problem with BOINC after the latest round of Microsoft security updates (which I applied today). These "urgent updates" included the installation of IE7. After uninstalling BOINC (v 4.45) and then re-installing BOINC (v 5.4.11), the problem disappeared.

Some details:

After applying the updates (and rebooting), the BOINC Manager (which had worked rock-solid for over a year) told me that it "failed to connect". I stopped BOINC and restarted it and got the same error. It looked like the status (in the lower-right corner of the BOINC Manager) was saying "connecting to localhost" before popping up the "failed to connect" error message. I have not changed any BOINC settings in a really long time (and I do not have IIS installed on this machine).

In any case, I also tried rebooting, but I continued to get the "failed to connect" message. I then uninstalled BOINC (v 4.45) and then re-installed (v 5.4.11). Everything then started working again. I didn't even have to reconfigure the SETI@home project. Everything just started working.

Strangely, a few days ago, I applied the Microsoft updates to another machine running BOINC and it did not appear to have any of these same problems.

So, perhaps you can try the uninstall/reinstall approach.

Good luck,

Bill B.
Atlanta, GA

Update:

It appears that my installing BOINC 5.4.11 has started causing another problem. I am now getting an IRQL_NOT_LESS_OR_EQUAL blue screen of death message upon restart/shutdown of the machine.

This problem went away after uninstalling BOINC 5.4.11. Unfortunately, I tried re-installing the older version (4.45), but it still does not work with those other MS updates.

So, unfortunately, I guess I'll need to keep BOINC off of this machine until a solution is found.

Any ideas would be greatly appreciated.

Thanks,

Bill

Have you tried the 5.7.3 development code? I am running it with IE7 without problems.

---