Right, in CVS is now an updated source and binary for freenet.exe. It reads "fservecli" from flaunch.ini instead of "fserve" as suggested. I've also updated the flaunch.ini file in CVS to reflect this, ready for the next release
The non-GUI node does indeed use less RAM. Windows users will be able to sleep happily now :) The new freenet.exe has been thoroughly tested using the latest JRE2 version 1.3, as well as jview. It all works a treat. Sebastian - i **think** I've managed to reproduce the problem you described as "the non-GUI node causing freenet.exe to report it isn't running when it is". There seems to be a bit of an issue with using wjview.exe in this version - the node no longer responds to WM_CLOSE meaning restarting the node is achieved using TerminateProcess ... Then the node cannot be restarted again automatically. So for example, when you hit Configure, the node is stopped but not automatically restarted. Remedy - just popup the menu and click Start Freenet and it'll get going again. Real remedy - Don't use wjview. Note here that freenet.exe is reporting the node isn't running when it **isn't** ... I haven't yet got it to report that the node isn't running when it IS. Let me know how you did this and I'll try and find a fix,
