eDonkey users...

[Pastore]

Does it ever take you an extremely long time to connect to servers? I have been letting it connect now for half an hour and it just keeps saying it can't connect, and tries another.

 

[b0red]

connect to AdaNET server

click on it rapidly

eventually u'll get in

 

[neomits]

I use emule


I think its more user friendly

 

[murphy55d]

agreed. i like eMule better.

 

[Pastore]

Originally posted by: b0red
connect to AdaNET server

click on it rapidly

eventually u'll get in

I don't have AdaNET in my server list.

 

[Pastore]

I am an idiot.

 

[b0red]

AdaNET is 195.112.128.222

 

[Pastore]

bored, how do I get it to stop trying to connect to the servers automatically? When I click on the AdaNET server it says already trying to connect.

 

[murphy55d]

I think you need to unclick stay connected in the preferences.

not 100% tho.

 

[Yossarian]

Originally posted by: neomits
I use emule


I think its more user friendly

 

[fleshconsumed]

Beast1284
What's the last time you updated your serverlist? You should update it at least once a day to get some fresh servers...

If the server has free slots and is not overloaded (CPU wise ie has some hardware resources to spare), then connect time should be less than 4-5 seconds...

 

[b0red]

ya...and dont click on connect...

just click on server name

click AdaNET 50times...i'm sure u'll get in 😱

biggest server i believe...40K users

 

[Pastore]

Originally posted by: fleshconsumed
Beast1284
What's the last time you updated your serverlist? You should update it at least once a day to get some fresh servers...

If the server has free slots and is not overloaded (CPU wise ie has some hardware resources to spare), then connect time should be less than 4-5 seconds...

I have tried updating the server list but I don't think I have up to date URLs because it says it failed.

 

[abaez]

go to the edonkey forums and update to maurices serverlist... he updates it all the time need to replace your server.met

 

[Pastore]

Originally posted by: abaez
go to the edonkey forums and update to maurices serverlist... he updates it all the time need to replace your server.met

blah, did that and still can't get anything to connect.

 

[manly]

Originally posted by: neomits
I use emule


I think its more user friendly

What about downloading throughput in emule vs. edonkey?

The main problem I see with edonkey is that while my uploading is always around my preset cap (64 kbps), the download usually lags around 20 kbps. I believe it has something to do with the maximum connections setting being a critical shared resource.

There should be separate connection queues for uploading and downloading, but it seems like if a lot of people are leeching from you, it restricts your ability to download from available sources as well. I haven't seen any source code, but from the behavior of the edonkey client, I've drawn that conclusion. It seems to me that the edonkey network favors network files propogation over a balanced upload/download experience in a particular client.

 

[crab]

11/24/02 22:10:23: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:10:24: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:10:26: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:10:28: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:10:29: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:10:30: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:10:36: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:10:38: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:10:38: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:10:40: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:10:40: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:10:42: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:10:42: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:10:44: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:10:45: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:10:46: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:10:47: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:10:49: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:10:49: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:10:51: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:10:51: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:10:53: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:10:53: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:10:55: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:10:56: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:10:57: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:10:58: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:00: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:00: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:02: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:02: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:04: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:05: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:06: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:07: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:08: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:09: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:11: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:11: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:13: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:14: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:15: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:16: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:18: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:18: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:20: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:20: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:22: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:22: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:24: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:25: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:26: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:27: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:29: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:29: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:30: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:32: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:32: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:34: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:35: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:36: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:37: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:38: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:39: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:41: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:42: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:43: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:44: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:46: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:46: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:48: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:48: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:50: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:51: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:52: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:53: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:55: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:55: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:57: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:57: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:11:59: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:11:59: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:12:01: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:12:01: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:12:03: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:12:04: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:12:05: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:12:06: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:12:07: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:12:08: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:12:10: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:12:10: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:12:12: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:12:12: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:12:14: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:12:14: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:12:16: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:12:16: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:12:18: adaNET (195.112.128.222:4661) appears to be dead.
11/24/02 22:12:19: Connecting to adaNET (195.112.128.222:4661)...
11/24/02 22:12:20: adaNET (195.112.128.222:4661) appears to be dead.

 

[gump47371]

Emule works ok, I personally (in the minority, I know) like Overnet. Still in testing phases, so not perfect, but near.

 

[crab]

Finally got in, but I can't beleive the queues... 🙁

 

[manly]

Is emule a complete drop-in replacement for edonkey?

Specifically, can it be pointed to the same temp/partials directory that edonkey uses and pick up from there without corruption (obviously you can only run one client at a time).

 

[ajskydiver]

Manly: Yes, emule will work with the donkey's or overnet's files without any problems...

~AJ

 

[Yossarian]

emule is so much faster than edonkey it's ridiculous

 

[Pastore]

eMule doesn't work with sharereactor does it?

 

[manly]

eMule seems to work better than eDonkey.

But every so often, it experiences a long pause in operation where the application is completely unresponsive, but not locked. It's not hashing or completing a file, so I don't know what the problem is.

While the UI is better designed, the layout is too cramped for 800x600.

Also, I don't know if this is normal or not, but I have 1000 clients on queue. That seems to be a much bigger number than I used to see with eDonkey.

 

[Yossarian]

Originally posted by: Beast1284
eMule doesn't work with sharereactor does it?

it does