The .ini files
When mldonkey gets started the first time, a lot of files get created. This page will explain what all these files are about:
For every network mldonkey can connect to it creates a .ini file to store some values:
stores values for the audiogalaxy network. Mldonkey does not support this network anymore. So this is not created anymore...
stores values for the Direct Connect network.
stores general mldonkey values, as well as values for the edonkey2000 and overnet network. This is the main configuration file.
stores the sources that you can connect to.
stores md4-hash of all files that are being downloaded
stores the names and IPs of the friends
stores values for the limewire aka gnutella network.
stores values for the openFT (the main protocol for giFT) network.
stores values for the Open Napster network.
stores your custom search queries.
stores values for the edonkey-server, that is integrated in mldonkey.
stores a list of servers you can connect to.
Stores md4-hashes and filenames of files you share
stores values for the Soulseek network.
Those files are all in text format. When using a file from another mldonkey version, missing parameters will take their default value, and unrecognized parameters will be discarded (removed). This is almost always harmless, so you can switch from a version of mldonkey to another by just replacing the executable files (cores, GUIs,...) _-- is it also true of GUI lists (gui_donkey_options_panel, gui_overnet_options_panel,...), may I miss some interface changes if I don't clear them between updates ? /Pango_
NOTE: Because those files are periodically overwritten with updated data when the core is running, you need to stop the core before modifying them. Almost all settings can also be modified on the fly using the mldonkey set command.