I ran into a problem I thought I should report (and this seems like the place to do it) with the new 5.10.x builds. Our machines at the office are, at the moment, all using BOINC 5.8.16 and using SOCKS proxy settings to relay through SOCKSPuppet to WCG (because BOINC doesn't do NTLM so HTTP proxy is out). This configuration works fine. I recently brought a Vista Business x64 machine online for testing purposes in our network, and I installed BOINC 5.10.6 for Windows x64 beta on it. Install completed successfully, I went in and specified the SOCKS proxy, and then tried to attach to the project. It didn't work. The message center revealed nothing in particular of any interest, and from what I could tell monitoring my SOCKSPuppet proxy, it never received any traffic at all from BOINC 5.10.6 on the Vista x64 machine. I reinstalled, etc, triple checked my proxy entry, etc, nothing. After an hour I uninstalled it and tried 5.8.16 (which of course runs in 32 bit emulation in WOW), and to my surprise, it attached to the WCG project immediately and began downloading work.

I have not had the ability to try and duplicate this issue again. 5.10.7 (and all the 5.10.x builds) has worked fine on my Vista x64 Ultimate home machine, but there is no proxy that BOINC has to use for that.

I will try my best to try and test this on an alternate Vista x64 machine, but in the meantime if anyone else with a similar config feels up to testing it out and reporting in, that might be helpful too. :)

By the way, I'm a fairly recent convert from the UD client. BOINC is amazing when compared to that, keep up the great work folks.

Thanks for the report Bill.

I sent it to the alpha list.

You may want to subscribe.

http://www.ssl.berkeley.edu/mailman/listinfo/boinc_alpha

---

Kathryn :o)

Thanks for the report Bill.

I sent it to the alpha list.

You may want to subscribe.

http://www.ssl.berkeley.edu/mailman/listinfo/boinc_alpha

You're welcome. I will look into subscribing to the list, and if I discover any additional info on this I will be sure to post here. Thanks!

Thanks for the report Bill.

I sent it to the alpha list.

You may want to subscribe.

http://www.ssl.berkeley.edu/mailman/listinfo/boinc_alpha

FYI I was able to duplicate this problem upgrading a client from 5.8.16 to 5.10.7 32 bit as well on Windows XP SP2. Following upgrade, BOINC cannot use the SOCKS proxy at all, and looking at the logs on the SOCKS proxy, I see no evidence that BOINC even made an effort to connect to it.

FYI I was able to duplicate this problem upgrading a client from 5.8.16 to 5.10.7 32 bit as well on Windows XP SP2. Following upgrade, BOINC cannot use the SOCKS proxy at all, and looking at the logs on the SOCKS proxy, I see no evidence that BOINC even made an effort to connect to it.

Same with me, when I upgraded to the official 5.10 build I lost both SOCKS and HTTP proxy support on a Vista Business 32bit and XP SP2 system. Is there any way to fix this?