I recently had problems with Outlook completing its Send/Receive cycle with BOINC/Seti running. When BOINC is exited, everything runs fine. I'm running Outlook 2002, SP2.

I ran into this with Classic Seti running as a service. Outlook was set up on an Exchange server and set up for offline use. During the Send/Receive cycle the offline address book and messages would be updated. This update runs as a low priority process so that it will not interfere (too much) with your other activities. Both Classic Seti and Boinc\Seti run as a low priority process. A low priority process will give up CPU to another process that is running anywhere above low priority, but not to another low priority process. I was using the third-party Seti Service utility to run Classic Seti, and they had built in a configuration option to pause or stop whenever another process of your choice ran. Once I told Seti Service to pause whenever Outlook ran my Send/Receive problem went away.

With BOINC\Seti the problem surfaced again. I switched my offline folder sync to only take place at logon/logoff to get around it. Later, I upgraded to Outlook 2003 and found it isn't a problem any more.

<FONT face="Courier New"> </FONT>

I've noticed that Outlook will hang almost any program whether SETI (Classic or BOINC) is running or not. It's just Outlook that's screwed up.