PDA

View Full Version : Command Line eDonkey


View Full Version : Command Line eDonkey


GoldenTequila
November 5th, 2002, 05:43 PM
Hello. I just started using Command Line eDonkey since I had a crashing problem with both eDonkey and eMule. Someone said he didn't have any problems with Command Line eDonkey (CLeD). Well, so far, it hasn't crashed on me, but I'm not sure if it's really working either. Here is the thing. I am behind a firewall. When I used eDonkey and eMule. I used HttPort to bypass the firewall. I'm trying to do the same thing with CLeD, but I don't know what the command key to do it on Command Line. I tried "Port 127.0.0.1:1080" (port # : sets the port that you listen for other clients on. Takes effect upon
restart.), but I'm not sure if it is recognized as SOCKS 4 by CLeD and if it's really going through my HttPort. The other thing is the traffic indicator of HttPort stays white, which means no traffic is active. But, then, my CLeD IS connected to servers and displays user # and files. I can perform search too, and get a descent result. download lists do show the availability of each DL. (if it's found a user with a complete file, etc. Displayed in %). From my experience, they pretty much indicate that.... OMG, never mind. I just checked my CLeD, and it's downloading now! :) Well, if you have a problem with eDonkey, eMule, or Overnet, it might be a good idea to try CLeD. CLeD doesn't have any GUI requirements, graphic complication, etc, which some people suspect are the causes of known problems such as crash or sudden shut-down. In other words, CLeD is like you are using a skeleton of eDonkey. Because it doesn't have any living tissues like organs, it doesn't get sick. (I don't know how good this analogy is lol...) Even if you are not familiar with Command Prompt, don't hesitate to try CLeD cuz' it's really simple. Whenever you are lost, you can just type "?", and it will give you all the keys you need. Happy Sharing :)