David McNab <[EMAIL PROTECTED]> writes: > 1) What's the proper way to detect the presence of Freenet on Windows? > Is there a fixed, stable registry key location for example? > ick, I doubt it. Fred itself doesn't touch the registry.
> 2) If Freenet is installed, what's the proper way to determine if it is > running, and how to access it? Does the FCP port get written to a > registry key? Or does the client winstaller need to parse freenet.ini? > FCP should *always* be on port 8481. It's possible, but *strongly* discouraged, to change this to a different port. Just assume a running freenet node will be listening on this port. > 4) What other issues should a client-writer be aware of when writing a > winstaller so that it can *reliably* auto-detect, auto-download and/or > auto-start Freenet? > I can't think of any problems for the detection. Downloading and starting freenet is a bit wacky under windows still, though. I guess running the winstaller should be enough to get things installed, and I don't know the best way to start it. Maybe there could be a command line argument to the winstaller to run the node owhen the install completes. Thelema -- E-mail: [EMAIL PROTECTED] Raabu and Piisu GPG 1024D/36352AAB fpr:756D F615 B4F3 BFFC 02C7 84B7 D8D7 6ECE 3635 2AAB _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
