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?
I have successfully ported the systray tool from asm to C, and added a very useful feature whereby, if the node does not run correctly, the icon flashes to warn that something is wrong. I noticed during the 0.3.8.1 problems that you can use the systray icon to Start Freenet and from that point it thinks it's running - even if it isn't. Not ideal. My fix is to, after executing "java.exe Freenet.node.Node", wait on the process object that you get back. If the object ever gets signalled it means the process has died unexpectedly. I do handling around Stop, Shutdown, etc. and it all seems to work I'll be thinking about checking this stuff into cvs pretty soon, so i'll be talking to Sebastian to integrate any changes he may have made. Who/where should I go to get authorisation to check things into Contrib/wininstall ? Dave _______________________________________________ Devl mailing list Devl at freenetproject.org
