>From "Dave Hooper" <[EMAIL PROTECTED]>
>I recently 'upgraded' to 0.3.8.1 - i did this by completely demolishing my
>node and starting from scratch.  Probably not ideal, but hey, I wanted a
>clean install.
>Despite the already documented problems with Freenet_setup0.3.8.1.exe
>doing -classpath instead of /cp, I noticed that freenet.ini isn't getting
>the "services.fproxy.port=8081" text added to it.  This is the profile
>string used by the systray tool to load the gateway right?  So i get just
>http://localhost:
>And unsuprisingly that doesn't work.   But I thought freenet.ini was created
>by the node itself not by the installer - is something broken in the node's
>initialisation code?
>

No, there's a java setup utility that gets run by the installer that creates 
the initial freenet.ini, which doesn't run because of the -cp issue.  you can 
create a valid freenet.ini by rightclicking on hops, selecting 'configure', 
clicking ok, and shutting down and restarting the node... at least that worked 
for me.

--
Benjamin Coates


_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/devl

Reply via email to