I just 'evolved' to 1.4.5.0 and when I closed Gnucleus and started it up again, it would crash on every attempt to use it. This is running on Win2k. I experimented with blocking certain ports, and I seem to have got it to run smoothly by blocking ports 80, and 6660-7000 (irc), I didn't see why it connected to an irc server on startup anyhow.
If you experience the same problem, try this.

Hrm.. thats interesting. Are you running a multi-processor system by any chance?

You've tipped me off that it is maybe the chat thread code causing the problem for win2k users.

No, single processor pII system. On Win2k Pro btw.

I released a test on http://www.gnucleus.net , try it, email me what happens.

The exact same thing happens to me right away everytime I start gnucleus, in windows 2000, and I am using dual p3 700s. I hope you get it fixed soon. I don't want to use another client, gnucleus is my fav.

I should also mention that I am behind a linux router using iptables for NAT. This may be causing a problem, no? The older versions worked great before and my network has remained unchanged.

Updated exe does not crash. I removed blocks from ports 80, and irc ports, started up Gnutella twice, and experienced no crashes. However, I restored the original exe afterward, kept the port blocks down, and ran IT twice... and still no crashes. So this seems to be inconclusive in my case. Perhaps it is a strictly immediate-post-evolve problem...

My machine is a single CPU (P3) running NT4. I've been having crashes too.

I evolved to 1.4.5 and started crashing a few seconds after startup. I tried the test release #2 but it still crashes.

I download 1.4.3 again, removed 1.4.5 and installed 1.4.3, and it STILL crashes? Whatever 1.4.5 is doing, it's leaving it there even after it's gone apparently. I will do a reboot and try 1.4.3 again and see what happens.

This may be a network thing

I have a similar problem when trying to use gnucleus on win98 on my university network I think ports might be blocked or a cleaver firewall or somthing.

I've tried lots of gnutella clients none of which worked, however gnucleus was the only one which crashed.

I found that if I stopped it from trying to connect really quick it didn't crash, but if I then tried to connect it would crash.

Hi,

I had the same problem and this method usually works. When you run Gnucleus, go to preferences before it crashes. Disable "Connect automatically at startup" and reduce the number of min and max connections to 1 or 2. Then run Gnucleus again. Connect by clicking to "Add" button and then increase the numbers of min and max connections slowly.

Gnucleus used to crash at startup every time I run it, and I was able to run it with this method. Just give it a try.

If this hint is useful, please read my question at the follwing link and please help me if you know about it.


http://www.gnutellaforums.com/showth...&threadid=5126


Thank you.

Solid