Migrate from eMule to aMule-tw

From AMule Project FAQ
Revision as of 05:18, 2 January 2010 by Mstar (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

English] | 正體中文

本頁是介紹如何將 eMule 原有的設定檔、暫存檔轉移至 aMule 使用。


eDonkey2000 was born some years ago and its great protocol, ed2k became the Olympian of file sharing programs.

Some coders, unsatisfied by that client, started developing a new one, called eMule. Its source code was open, so anyone able to program could read it and modify it, and so they did. Many client versions came up with patches and new code. Soon the eDonkey2000 guys started criticising eMule, blaming constant slowdowns in the P2P network on the large number of eMule clients. After an initial study phase, eMule developers decided to create a new p2p network leaving eDonkey2000 network alone. It was a success.

The Linux community started developing a Linux client able to connect to eMule's network: lMule was born. A multi p2p network program, mlDonkey added support to eMule's network; later lMule was renamed to xMule. But the winner is yet to come.

xMule got a few coders but a project started ramping up: try to port the changes from eMule to a Linux client: aMule was born. This quickly became the de facto standard "donkey" client for Linux.

eDonkey2000 is now almost dead, and even charges for a professional version of its client.

因為 aMule 跟 eMule 淵源很大,所以很多 eMule 的設定檔可以直接餵給 aMule,相關積分都可以繼續使用,不必重新養起


In eMule, these files are stored under config directory. In aMule, instead, the configuration files are stored under ~/.aMule directory (Linux) or in the ~/Library/Application Support/aMule directory (Mac), or, for example in the C:\Documents and Settings\<username>\Application Data\aMule directory in Windows. So the easy step is to copy the files from the eMule's configuration directory to aMule's. Good, so let's look further...


以下設定檔可直接從 eMule 複製至 aMule 的目錄 ~/.aMule/ 下使用:

That's the good news. The bad is still to come...


  • Configuration file: eMule uses preferences.ini but aMule uses amule.conf.
  • Categories: They are the tabs separating files in the download list; in eMule they are written in the file Category.ini but aMule writes them down into amule.conf.
  • eMule's shareddir.dat file is not compatible with aMule when switching to any aMule not running in Windows, since paths are so different. In this case, aMule will automatically generate this file once you set in Preferences the directories you want to share.
  • Some files in eMule's config directory are not used by aMule: AC_BootstrapIPs.dat, AC_IPFilterUpdateURLs.dat, AC_SearchStrings.dat, AC_ServerMetURLs.dat, fileinfo.ini, k_index.dat, preferencesK.dat, s_index.dat, statistics.ini and webservices.dat. Most of the above files come from old eMule installations and are now deprecated.

部份 eMule 的設定經處理後仍可移至 aMule 使用:


This command line should help you generate the categories information from eMule's Category.ini file (put the command on the same line):

grep -E "^\[Cat|^Title|^Incoming|^Comment|^Color|^a4afPriority" Category.ini | sed 1,6d | sed 's/#/\\#/g' | sed 's/&/\\&/g' | sed 's/a4afPriority/Priority/g'

This escapes even # and & characters, because I've got them in my Category.ini file; maybe there will be other chars to be escaped that have to be included in the script (edit this article, if it is the case). The script deletes the first 6 rows, that is the first category, since it's a dummy one: that category is the first one in eMule, which contains all/uncategorized/etc files; aMule has its "all" tab and do not need this entry. Cut&paste the script's result into amule.conf.

Under [General] in amule.conf, you have to define a variable count (or change its value if already defined) with value:

echo `grep -c "^\[Cat" Category.ini` -1 | bc

This variable holds the number of tabs to display: note that even if you have imported 10 categories, but leave count=1, only one category will be displayed.

At the end, the categories configuration in amule.conf should look like:


Note: If you import the categories before importing the temp files, they will be classified as in eMule.


eMule's statistics are available in two different files: preferences.ini and statistics.ini. I found statistics in the latter file more up-to-date than the ones in the former file.

Looking into statistics.ini you'll find that all statistics are under Statistics tag. Even inside amule.conf there exists this tag, so the logic conclusion is to copy from span statistics.ini to amule.conf. In this last file, there are two keys, MaxClientVersions and DesktopMode, that should not be deleted.

Note: Sadly, very few values get imported: seems only downloaded and uploaded bytes. Maybe it's not the right place where I've written those keys, or maybe aMule uses other ones. Only using aMule will reveal it.


Configurations not yet imported are the program strictly ones. They are, for example, about the TCP and UDP port to use, Incoming and Temp directories, network limits and so on.

Since they are very client-specific and important for its correct behavior, I suggest to redefine them by the Preferences aMule form. Maybe it would be long and boring, but done it once, they will last forever, almost.

If you're really brave, you can try to import directly some keys from preferences.ini to amule.conf, but then don't argue if it doesn't work.


eMule 下已抓到一半的暫存檔可直接給 aMule 使用,aMule 重新計算完 hash 值後就會繼續抓剩下的部份。可以在 aMule 設定暫存檔資料夾至 eMule 的、也可以複製出來讓 aMule 使用。

唯一問題是:若反過來把 aMule 的暫存檔給 eMule 使用,則英文之外的檔案名稱都會變成亂碼,需要重新命名;但都可正常傳輸無誤。