After battling the Firewall / BOINC interaction for months, it dawned on me a few days ago, that my specific firewall Kerio PF, requires the specific linking of the science background with both BOINC.exe and BOINCMgr.exe ON TOP of the port permissions of 443+31416 (superseeding 1043). A different place in the firewall software actually specifically permits packets to pass or not pass between 2 processes like coming from 'wcg_faah_autodock_5.09_windows_intelx86'

Whilst it came all natural in UD, where the science has an 'exe' extension, never a squeek from the firewall after grants, the once packaged for BOINC don't **. As the firewall is set to list only exe files, you actually have to type *.*, which unfortunately throws up a forest of files, obscuring the trees needed. After setting the packet permission links, for 2 days now the BOINCmgr.exe has not had the random freeze (science continues), requiring me to apply the temporary fix of closing the firewall and restarting......it at times probably overwhelmed by multiple communications request atop the BOINCMgr.exe every second contacting of BOINC.exe / science (so goes the story in some Firewall support forums).

Anyway, a verbose lead up to my request: Would it be possible to give the future sciences the exe extension for assisting in reducing the firewall configuration oversights for WinOsses, or would this conflict with the running of these on other OSses or even BOINC as a multi project manager?

** The BOINC science package/part, in fact on the inside has the same exe name as those for UD. Oddly as previously commented elsewhere, the version number in one is lower, than the version number on the outside?

thx,