Shareaza

I have been following all the posts about connection problems with GNUTELLA1 for the past month and I keep wondering is the system still working or is it DEAD?

the gnutella1 network is still alive - once you get connected everything works fine(for a while) - but I think shareaza is maybe having problems communicating with GWCs

I noticed my 64bit Shareaza wasn't connecting to G1 also so I started looking around and found the solution.

In Shareaza Settings, Advanced change the Discovery.EnableG1GWC item to True. Discovery of G1 hosts will start immediately when you click Apply (assuming you have G1 discovery services registered).

My guess is it was due to testing. I imagine the developers turn off various components while testing others and possibly someone forgot to re-enable it during the build.

wow, i have been having this issue for months and got zero replies when i posted about it. when i go to shareaza settings i don't see an advanced option.

hooray! thank you kindly

thx!! hope developers sees this topic

Thanks to pokerfan! GNUTELLA1 is alive and well on my system

I was having the same problem as well. That fixed it, so thanks.

This does not work for me, I pass all connection tests, Discovery.EnableG1GWC is true/enabled and G2 connects along with eDonkey but G1 & DC++ do not connect. I have "connected" everything in the Host Cache (only says eDonkey though) I also Query all the links in the discovery services... why won't they connect?!

Discovery.EnableG1GWC True instead of False

Was it really that simple !? Yes! On 2 different computers.

Unbelievable !!

Come on dear developers !
I really admire your effort, and have deep respect for your time investment in this project.

But this is a bit

If so many people have troubles with this, why not a new fixed release ?
Is it so much work to release a corrected version?
For my and other "Just Users" understanding, how much time/work is it to change a corrected beta to real version?

Maybe it was fixed in a beta, but my experience is that Beta's are running slower and sludgier because of the extra code. And that they are not adviced.
Should we try beta's more often?

This code is a part of Shareaza since 25.06.2007 (implemented by ale5000).

Hmm... Shareaza always prefer G1 UDP-caches and "Discovery.EnableG1GWC" option enables G1 WEB-caches using. At current time no G1 UDP-caches exist.

UPD: Fixed in r9216.

I had to take some time to see what you mean:
So this parameter Discovery.EnableG1GWC has been False for a long time, and it tells Aza to use UDP caches.
These caches seem to be gone and that is the real problem.

Changing it to true is actually a workaround, using an alternative cache-system.

BTW My problem of sometimes very slow G2 connecting is now also fixed with this parameter.

I have tried using Shareaza 2.6 (32 bit) quite a few times and was despairing of it, even removing and reinstalling it a few times. I tried following the advice posted here for Gnutella1 etc re "Enable G1GWC" etc and it solved the problem instantly. I now finally have connections for G1 & G2 but not for edonkey and DC++. Many thanks for the helpful advice on this. However, any advice out there for how to connect to edonkey & DC++? Would be much appreciated.Thanks

Thanks raspopov, but I tried F8 for eDonkey and Host Cache opened up but it seems to be empty. Can't be right surely? Should there be things listed there? Are more steps required to connect to eDonkey? I'm a fairly inexperienced user so any step by step description is much appreciated. Thanks