In case you're not subscribed to the cvs mailing list, I've recently checked in a minor (but significant) change to the freenet systray app.
1. If FProxy is enabled in config (i.e. freenet.ini) then fcpproxy is NOT loaded on systray startup. This appears to solve the "FProxy sometimes works / sometimes doesn't" bug on Windows. 2. If FProxy is not enabled in config then fcpproxy IS loaded on systray startup (but with a hidden window, so you can't accidentally close it and wonder why your freenet proxy no longer works) 3. If fcpproxy was loaded, and the node is then stopped or exited, then fcpproxy is also shut down. I may later make the necessary tweaks that ensure fcpproxy is also shut down if the node is stopped non-cleanly (i.e flashing systray icon, "Freenet Is Having Problems", should also cause fcpproxy to shut down). Basically, I've made fcpproxy just as 'hidden' as FProxy. Naturally, if fcpproxy was not installed, then it won't be run (so you'll either have to use FProxy, or no proxy, no change there) Dave _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
