I believe he has fixed this since, but will comment anyway. On Wed, Sep 07, 2005 at 05:34:04PM +0000, Bob wrote: > Matthew Toseland <[EMAIL PROTECTED]> writes: > > > Are you sure you are talking about the same Freenet we are? Please check > > http://freenetproject.org/ > > > > On Sun, Sep 04, 2005 at 10:34:48PM -0500, Andy Doucette wrote: > > > Dear Freenet Support Community, > > > > > > I have been a happy freenet user for several weeks now. Today, my > > > freenet broke. While my freenet server was running in the background, I > > > accidentally did something that produced a blue screen of death. It had > > > to do with moving a TV window from one monitor to the other, producing > > > some sort of fault in my video card driver. My computer restarted, and > > > I have not been able to connect to the freenet network ever since. What > > > do you think could be wrong? Thanks for your help. > > > > > > ~Andy > > Assuming that this is in relation to freenet; I assume you're running it on > windows? I'm not really familiar with how it works on that platform but a > couple > of things come to mind : > > - Lock files. On *nix a "lock.lck" file gets written to the main freenet > directory on startup, to prevent more than one instance being run at a time. > In > the event of a crash though it wouldn't get deleted and would prevent the node > restarting. So see if you have something like that in c:\Program Files\Freenet > and delete it if so.
True, but we don't lock by its existance; we lock by a file lock on it. So if it dies the lock should go away even if the file doesn't. > > - Inconsistent datastore versus index. I've never seen a node not cope with > this > by fixing the index but perhaps it can happen. If the above doesn't help try > renaming (location of your freenet store)\index to something else, hopefully > this will rebuild the index if that's the problem. I've seen reports of it happening, and stuff getting deleted. > > - If neither of those help, look at (freenet directory)\freenet.log and > hopefully it will tell you what the problem is. Unless you have turned logging > off :) One possibility is that freenet is needing a huge amount of RAM at > startup (so you need to increase the JavaMem size in Flaunch.ini), this is a > known issue for some users on *nix ... > > Bob -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
signature.asc
Description: Digital signature
_______________________________________________ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
