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 nf.Configuration file: eMule uses preferences.ini but aMule uses nf.The bad is still to come.Ĭonfiguration Files NOT Automatically Imported shareddir.dat paths of shared directories, but it is only compatible with eMule when using aMule for Windows.key_index.dat, load_index.dat, nodes.dat, preferencesKad.dat and src_index.dat are Kademlia files.cryptkey.dat and preferences.dat, they uniquely identify you to other clients, so you can keep credits to their side.addresses.dat contains a list of URLs from where aMule will download t files to merge with its current t file.ipfilter.dat and ipfilter_static.dat, which contain the IP denied to connect/share files with you.t and staticservers.dat, it contains the saved eMule servers.t, it's where AICH hashes of shared files are stored.t, it's where details about the downloaded files are stored, the ones printed in green when searched again. ![]() When you download some from a client, you'll store in this file how much you have got, so you can promote that client when it will be in your upload queue. Many files are read and correctly imported into aMule among them there are: Good, so let's look further.Ĭonfiguration Files Automatically Imported So the easy step is to copy the files from the eMule's configuration directory to aMule's. 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\\Application Data\aMule directory in Windows. In eMule, these files are stored under config directory. There are two important parts in eMule: the configuration files and temp/shared files. Searching around the web you will find a lot of people saying the migration is easy: do not believe them! ) Or better, it's easy because the temporary file format is compatible, but if we are talking about configuration files, then things are different.įollow my notes below about the migration from eMule to aMule of all my downloads. This quickly became the de facto standard "donkey" client for Linux.ĮDonkey2000 is now almost dead, and even charges for a professional version of its client. ![]() 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. A multi p2p network program, mlDonkey added support to eMule's network later lMule was renamed to xMule. ![]() ![]() The Linux community started developing a Linux client able to connect to eMule's network: lMule was born. After an initial study phase, eMule developers decided to create a new p2p network leaving eDonkey2000 network alone. Soon the eDonkey2000 guys started criticising eMule, blaming constant slowdowns in the P2P network on the large number of eMule clients. Many client versions came up with patches and new code. Its source code was open, so anyone able to program could read it and modify it, and so they did. Some coders, unsatisfied by that client, started developing a new one, called eMule. 3.2 Configuration Files NOT Automatically ImportedĮDonkey2000 was born some years ago and its great protocol, ed2k became the Olympian of file sharing programs.3.1 Configuration Files Automatically Imported.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |