> 1 a) if you try to import/export references in a location with spaces in the > path, like "C:\test freenet\pippo.ref" or "C:\mickey mouse.ref", the process > fails!
Argh. Sounds like I wrote that bug. > 1 b) if you try to import/export references in a good location accordingly > to point 1a, but you have J2RE installed in a location with spaces in the > path, like "C:\program files\jre\bin\...", the process fails too! Argh. Sounds like I wrote that bug too. > 2) if you make manual changes to freenet.ini, like > "services=fproxy,nodeinfo,console,nodestatus", an after that you use the > nodeconfig program, you may loose some setting... like > "services=fproxy,nodeinfo," Fair point. Which specific changes get lost when you run NodeConfig (is it just the services= key or is there more?). NodeConfig only knows how to deal with the fproxy and nodeinfo services. I probably ought to make it pass through anything it doesn't understand and let the user edit that from NodeConfig too. (In fact I'll probably just add it to the Unknown Settings dialog off of the Serious Geeks Only tab) > and now the wish... :) > Is possible to start freenet node as a WinNT service? Do a quick search on the freenet developers' archive, someone was talking about this just the other day. It's not hard to write a simple NT Service wrapper for freenet.exe, but I haven't had the time to do it and no-one else has done it yet either. However there's seemingly loads of third-party tools that let you run generic .exe applications as services. Not quite as good or flexible as having freenet actually running as a service but pretty close. d _______________________________________________ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
