Jep :
Matthew Toseland :
On Friday 31 December 2010 20:39:13 Jan wrote:
Jep :
[nothing connects]
1317/1318 may help.
Doesn't look that way.
Disconnected for 20 hours now and manual update an hour ago to 1318 has
changed only the number at the fproxy page.
Kinda lame to reply to my own message but since there appeared no other...
Because it sometimes works better, I start Freenet using 'services.msc'.
Trying that, I noticed name and location of 'freenetwrapper.exe' as well
as the location of 'wrapper.conf' have changed but not the registry key
pointing to them.
Result is that the wrapper can not be started from 'services', and also,
when it is started in another manner, the services pane thinks the
service is still stopped.
Maybe the installer, the uninstaller or both don't edit the registry
correctly.
On uninstall, a lot of rubble is left.
Created hardlinks to these two files in the by the system expected
folders, and now it is possible again to start FN from the services window.
Yes, hardlinks are possible with that stupid xp.
It has NOT helped to connect to strangers, my node is still offline but
I figure you want to know.
The old pathname of the wrapper was
\Freenet\bin\wrapper-windows-x86-32.exe
and the new:
\Freenet\wrapper\freenetwrapper.exe
Old location of the config file:
\Freenet\wrapper.conf
New:
\Freenet\wrapper\wrapper.conf
Can it be this confusion of file locations is written to ini files, too?
Or somehow elsewise preventing my node from connecting?
Fproxy looks completely normal.
_______________________________________________
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
