Files Used
02.05.2004 16:10

During eMule's runtime quite some files are used or created on first start. Most of them are created in eMule's config folder, others reside in the temporary directory as specified in the Preferences or directly in eMule's installation directory.

o
Known.met
The Known.met saves all files eMule knows of whether they are shared files or files currently in the download list. For every file information like file size, path to the file, hash sets, hash values and some statistics are saved.
o
Clients.met
This file stores all users who have credits with your eMule
o
Server.met
Contains all known servers.
o
Emfriends.met
If users are add to the friends list they are stored in this file.
o
Preferences.ini
Saves all options set in the preferences dialog and information about visual details like column size etc.
o
Fileinfo.ini
Comments or Ratings for your own shared files.
o
Category.ini
Stores the settings of your categories like name, comment and colour coding.
o
Ipfilter.dat
This file contains the IP ranges and access levels to be filtered by the IP Filter. Also see Preferences -> Security
o
Onlinesig.dat
The Online Signature is a small file which contains the server eMule is connected to and up- and download statistics. Maybe used for IRC scripts or signature images.
o
Preferences.dat
Saves the user hash. This is a value calculated at eMule's first start and is used to identify this client in the network. Used for credit system and friends.
o
Sharedir.dat
Holds all paths to shared directories.
o
Staticservers.dat
Static servers never change their IP and are theoretically always online in the network. These servers can be added to staticservers.dat by the context menu (right mouse button) of the server list. See also Preferences -> Server
o

Adresses.dat
eMule updates its server list at startup if valid addresses to server.mets are provided in this file. Preferences -> Server offers a button to edit this list and the option for updating at start up. The file may contain multiply entries (one each line) but only the first address to deliver a valid server.met is used.

o
AC_SearchStrings.dat
Each search string that has been used is recorded and an auto completing is offered if a new search matches previous ones.
o
AC_ServerMetURLs.dat
Same file as the the one above. The only difference is that this one is used to store entered URL to server.met files. Mind that many sites regularly change their addresses to the server.mets.
o
Cryptkey.dat
It contains the unique 384 bit private RSA key of your client
o
eMule.tmpl
The *.tmpl files are required for the Webinterface. They define layout and options of the displayed pages.
o
xx.part
Part files are unfinished downloads. eMule is able to download from more than one user at the same time, so the *.part files always have the size of finished download. Missing parts are simply filled with zero.
o
xx.part.met
Every *.part file has a corresponding *.part.met file. To identify a download in the network and to check for errors each download is divided in about 9 MB parts. For each part a so called hash value is calculated. Then a new hash value is created of the complete set of these part hashes. This information together with the file name and the status of the hashes are stored in the *.part.met files.
o
xx.part.met.BAK
A backup of the *.part.met files is created as it is very bad if such a file gets corrupted by a crash. See Troubleshooting for help, if your downloads vanish due to corrupted *.part.met files.
o
eMule.log
Saves the output of the Log window in the Server pane if the appropriate option in Preferences -> Extended is turned on
o
eMule_Debug.log
Saves the output of the Debug window in the Server pane if the appropriate option in Preferences -> Extended is turned on

Applies to version: .29b +
Last update on: 2003-06-20 by Monk