FAQ

last update: 08/25/2002

If you are complete new to the eDonkey-network you should read the official FAQ first. This faq is only additional and eMule specific.

1. General

 2. Using eMule

3. Features

If you have a questions which is not answered here, mail me and I'll add it to this FAQ.

 

1. General

1.1 What is eMule?
eMule is a filesharing client based on the eDonkey2000 protokoll. This means you are able to connect to official eDoneky2000 clients and eDoneky2000 clients can connect to emule. If you want to know more about eDonkey2000 visit the official homepage.

1.2 Does eMule support OverNet?
No, not yet.

1.3 Does eMule enforce uploading like eDonkey does?
Yes. Upload is needed to keep the network alive. However I know that it is possible to modify eMule and avoid any upload (just like you can modify the official ED2K Client). That's why eMule tries to make uploading fairer and raise the upload-acceptance. A client based credit system is in planing and will be introduced soon. That means that if you are downloading X MBs from a client, this client will be remembered and the next time he wants to download from you he gets a higher priority (->and if you are uploading you get a higher priority if you want to download something).

 

2. Using eMule

2.1 What do the colors on the progress bar mean?

progress bar for downloading files:

  • black: parts you have already downloaded
  • yellow: parts you are currently downloading.
  • blue: part you need to download, which is available (the more blue the more common)
  • red: part you need to download, which was not found yet.
  • green: total progress. When this progress bar is full the file is complete

progress bar for source clients:

  • black: this part is available
  • green: this part is available but you have downloaded it already
  • grey: this part is NOT available

 

3. Features

This part explains already implemented features and what they do :)

3.1 Intelligent Corruption Handling (ICH)
the goal of this feature is to reduce the amount of data you need to redownload due to corrupted parts. In the first version it reduces the average (re)download size of corrupted parts form 10 MB (one full part) to 5-6 MB. How does it work: When a part is corrupted emule marks it as corrupted and removes it (just like ED2K). In 99.9% of this cases only some bytes or blocks are wrong. So eMule checks after each block which is retransfered if the part is still corrupted and if not it re-adds the part to the file. That means chances are that you only have to redownload 10KB but it could also happen that you need to redownload 9,9 MB - depending on where the corruption is. In later versions eMule will be able to request additional hashs from other eMule-clients and reduce the amount of data you need to redownload to 5-10%.

3.2 Autoupdate serverlist
If you activate this (on your preferences screen) emule will download a new serverlist at startup. You can set the downloaddress in "adresses.dat" (open it with notepad and paste the URL - ATM only the top URL is used, later you can add aditional mirrors). ocbMaurice's serverlist is used as pre-setting. You might want to change this to your favorite serverlist.