AMule Project FAQ - User contributions [en]

Configure

2005-08-29T11:22:09Z

83.42.86.182:

{| width="90%" align="left"
|
== Introduction ==

''configure'' configures [[aMule]] to adapt to many kinds of systems.

Its purpose is to make it easy to port it to many platforms and to compile it and use it in all platforms in the very same way.

You can set lots of parameters in it to adapt it to your system and to tweak its features.

'''NOTE:''' This article is focused in [[aMule]]'s ''configure''. Other ''configure'' scripts work in a similar way, but their options will differ. This article might be useful for them as well, but have in mind that they might have options not listed here and lack some listed here too.

== Main usage ==

Its usage is ''./configure [OPTION]... [VARIABLE=VALUE]...''

So, as you can see, you can define its behaviour both through [[#Options|options]] and through [[#Variables|variables]]

== Options ==

You can define one or more options. The available options in [[aMule]]'s ''configure'' are listed below. To better understand their meaning, they have been grouped into several tables with options which affect the behaviour of ''configure'' in a similar way.

Please note that ''configure'' will (in most cases) not complain if you enter an invalid option or variable. So make sure you enter the options correctly (no typos) or they will have no effect and configure won't behave in the way you expected.

=== Main options ===

These options should exist in any ''configure'' script around the world. They won't run the ''configure'' script to configure your application's compilation, but only output information you might need.

{| border=1
|+ Basic options
|''-h'' or ''--help'' || This will display a help message summing up all ''configure'' options
|-
|''--help=short'' || This will display a help message summing up all ''configure'' options specific to this application (doesn't display generic configure options)
|-
|''-V'' or ''--version'' || This will display the version information
|}

=== Non-compilation common options ===

These options should also exist on any ''configure'' script around the world. They will set some non-compilation related preferences.

{| border=1
|+ Options directly related to the ''configure'' script
|''-q'' or ''--quiet'' or ''--silent'' || Do not print the `checking...' messages, only the final summed up ouput
|-
|''--cache-file=FILE'' || Store the checkings' ouputs in '''FILE''' in a script format, so you can reuse without the need to rerun ''configure'' (read the cached file for more information)
|-
|''-C'' or ''--config-cache || Same as ''--cache-file=config.cache''
|-
|''-n'' or ''--no-create || Just run ''configure'', but do not create any files
|-
|''--srcdir=DIR'' || Look for the sources in '''DIR'''. By default, the ''configure'' dir or its parent (''../'')
|}

=== Common options ===

These options should also exist on any ''configure'' script around the world. This time, these ones will affect the compilation of the application, so be careful when using them. You should take a close look at the application's ''README'' document (if available) if you want to use any of them (and even if you don't, still take a look at it, since you might '''have''' to use some).

{| border=1
|+ Installation directories options
| ''--prefix=PREFIX'' || Set where to install architecture-independent files (data) in '''PREFIX'''. By dafault, this is set to ''/usr/local''
|-
| --exec-prefix=EPREFIX || Set where to install architecture-dependent files (mainly binaries) in '''EPREFIX'''. By default, this is set to the same value as '''PREFIX'''.
|}

{| border=1
|+ Advanced installation directories options
| ''--bindir=DIR'' || Where to store user executables. By default, '''''EPREFIX'''/bin''
|-
| ''--sbindir=DIR'' || Where to store system administrator executables. By default, '''''EPREFIX'''/sbin''
|-
| ''--libexecdir=DIR'' || Where to store program executable. By default '''''EPREFIX'''/libexeec''
|-
| ''--datadir=DIR'' || Where to store read-only architecture independent data. By default, '''''EPREFIX'''/share''
|-
| ''--sysconfdir=DIR'' || Where to install read-only single-machine data. By default, '''''PREFIX'''/etc''
|-
| ''--sharedstatedir=DIR'' || Where to store modifiable architacture-independent data. By default '''''PREFIX'''/com''
|-
| ''--localstatedir=DIR'' || Where to store modifiable single-machine data. By default, '''''PREFIX'''/var''
|-
| ''--libdir=DIR || Where to search libs object code libraries. By default, '''''EPREFIX'''/lib''
|-
| ''--includedir=DIR'' || Directory containing the [http://en.wikipedia.org/wiki/C_programming_language C] header files. By default, '''''PREFIX'''''/include''
|-
| ''--oldincludedir=DIR'' || Directory containing [http://en.wikipedia.org/wiki/C_programming_language C] header files for non-GCC. By default, ''/usr/include''
|-
| ''--infodir=DIR'' || Where to store info and documentation files. By default, '''''EPREFIX'''/info''
|-
| ''--mandir=DIR'' || Where to store man pages. By default, '''''EPREFIX'''/man
|}

{| border=1
|+ General rule to program enabling and dirs specification
| ''--program-prefix=PREFIX'' || Prepend '''PREFIX''' to installed program names
|-
| ''--program-suffix=SUFFIX'' || Append '''SUFFIX''' to installed program names
|-
| ''--program-transform-name=SUBST'' || Run ''[http://www.gnu.org/software/sed/sed.html sed] '''SUBST''''' on installed program names
|}

{| border=1
|+ General rule to enabling or disabling features (sometimes it enables or disables the compilation of a program)
| ''--disable-FEATURE'' || Do not include '''FEATURE'''. Equivalent to ''--enable-'''FEATURE'''=no'' (see below)
|-
| ''--enable-FEATURE'' || Include '''FEATURE'''. Equivalent to ''--enable-'''FEATURE'''=yes'' (see below)
|-
| ''--enable-FEATURE=VALUE'' || Include '''FEATURE''' and specify it's value to '''VALUE'''. The meaning of the value should be explained in the ''configure --help'' output of the script
|}

{| border=1
|+
| ''--without-PACKAGE'' || Do not use '''PACKAGE'''. Equivalent to ''--with-'''PACKAGE'''=no'' (see below)
|-
| ''--with-PACKAGE'' || use PACKAGE. Equivalent to ''--with-'''PACKAGE'''=yes'' (see below)
|-
| ''--with-PACKAGE=VALUE'' || Use '''PACKAGE''' and set its value to '''VALUE'''
|}

{| border=1
|+ System specifications
| ''--build=BUILD'' || Configure for building on '''BUILD''' platform. By default, it guesses the platform it is being run on
|-
| ''--host=HOST'' || Cross-compile to build programs to run on '''HOST''' platforms. By default, same as '''BUILD'''
|-
| ''--target=TARGET'' || Configure for building compilers for '''TARGET''' platfroms. By default, same as '''HOST'''
|}

=== Very-common options ===

In most ''configure'' scripts you will also be able to use these options.

{| border=1
|+ Quite common compiler options
| ''--with-gnu-ld'' || Use the [http://www.gnu.org/software/binutils/manual/ld-2.9.1/ld.html GNU ld] as linker, without testing if it is the default linker in the system
|}

{| border=1
|+ X directory specifications
| ''--with-x'' || Use the [http://www.xfree86.org X Window System]
|-
| ''--x-includes=DIR'' || '''DIR''' contains [http://www.xfree86.org X]'s include files
|-
| ''--x-libraries=DIR'' || '''DIR''' contains [http://www.xfree86.org X]'s libraries
|}

=== [[aMule]] options ===

The following options are specific to [[aMule]]'s ''configure'' script. They will allow you to enable and disable them, so you should really take a look at them or you might sadly find out you lack things you would like to have in your [[aMule]] system ;-)

{| border=1
|+ Developer options
|-
| ''--enable-maintainer-mode'' || Activate some extra instructions only useful for developers (and totaly non-recommended to normal users)
|-
| ''--disable-dependency-tracking'' || Makes the application compile faster, but causes problems if you change the source code and try to compile again. Dependency tracking allows the make process to know which things to rebuild when something changes. If you do not plan to compile the application again with those same sources, you can safely use this option
|-
| ''--enable-dependency-tracking'' || Keep track of the dependencies so that on next build, only changed files will be recompiled. It slows down the compilation a little. This is the default
|-
| ''--enable-ccache'' || Enable [http://ccache.samba.org ccache]. This will make following compilations faster since only the non-modified bits of code will be recompiled. If you don't plan to compile [[aMule]] very often, don't enable this, since it takes longer to compile on the first compilation and it requires lots of disk space
|-
| ''--enable-profile'' || Enable code profiling (which allows to see how much time and resources are spent on each part of the code, though it will make [[aMule]] run much slower, so, in most cases, don't use it). The output file is ''gmon.out'' and can be viewed with ''gprof''. For more information, ''man [http://www.cs.utah.edu/dept/old/texinfo/as/gprof_toc.html gprof]'' and ''man [http://gcc.gnu.org gcc]'' (in the man pages of ''[http://gcc.gnu.org gcc]'', search for the command line option ''-pg'')
|}

{| border=1
|+ Compilation tweaks
| ''--disable-debug'' || Disables outputing information of the application execution. This information is useful to track bugs, so you might not want to use this option or you will not be able to report bugs properly
|-
| ''--enable-optimize'' || Optimizes the code to run (a little) faster. Using this option will not allow you to create useful bug reports so you might not want to enable it
|-
| ''--enable-optimise'' || Same as ''--enable-optimize'', but is deprecated (it is still there for backwards compatibility only)
|-
| ''--disable-rpath'' || Do not write the libraries' path into the binary. Useful only if you plan to move the binary to other systems or if you move your libraries often. Only use it if you know what you're doing, since it will make [[aMule]] run slower
|-
| ''--enable-static'' || Creates statically linked executables, which means that they will need no libraries since any needed library will be included in the executable file. The executable might run faster, and will be easily portable between systems using the same platform, but will be incredibly bigger in size
|}

{| border=1
|+ Compilation of external libraries
| ''--disable-embedded_crypto'' || Do not use [[aMule]]'s cryptography code, instead, use external libraries' code. This option is not recommended and it could possibly break the compilation
|-
| ''--disable-gsocket'' || Do not use [[aMule]]'s ''gsocket.c'' implementation. Do not use it unless you are '''very''' sure of what you are doing! (On [[wxWidgets]] 2.4, the default ''gsocket.c'' code gives [[Low ID]]s on restart)
|-
| ''--disable-nls'' || Do not use [http://www.vitavoom.com/postgresql-docs/nls.html Native Language Support]. This way [http://www.gnu.org/software/gettext gettext] won't be required, but translations will be disabled
|}

{| border=1
|+ Compilation hardcodings
| ''--disable-systray'' || Do not include a SysTray into the [[aMule]] build. Only [[wxWidgets]] 2.4.2 users with no [http://www.gtk.org GTK] should use it. Others should disable SysTray in [[aMule]]'s preferences
|-
| ''--enable-utf8-systray'' || Use [http://www.unicode.org UTF-8] encoded strings in [[aMule]]'s SysTray. Only affects [[wxWidgets]] 2.4
|-
| ''--enable-kad-compile'' || Compile the [[Kademlia]] code
|}

{| border=1
|+ [[aMule]] binaries selection
| ''--disable-monolithic'' || disable building of the [[aMule|monolithic aMule]] app. This is normally not recommended, unless you really know what you are doing (e.g. to compile only the [[aMuled|daemon]])
|-
| ''--enable-amule-daemon'' || Compile [[aMuled|aMule daemon]]
|-
| ''--enable-amulecmd'' || Compile the [[aMuleCMD|aMule command line client]]
|-
| ''--enable-amulecmdgui'' || Compile [[aMuleCMDDLG|aMule command line client (GUI version)]]
|-
| ''--enable-webserver'' || Compile [[aMuleWeb|aMule's WebServer]]
|-
| ''--enable-webservergui'' || Compile [[aMuleWebDLG|aMule's WebServer (GUI version)]]
|-
| ''--enable-amule-gui'' || Compile [[aMuleGUI|aMule remote GUI]]
|-
| ''--enable-cas'' || Compile [[CAS|C aMule Statistics]]
|-
| ''--enable-wxcas'' || Compile [[wxCAS|aMule GUI Statistics]]
|-
| ''--disable-ed2k'' || Don't compile [[ed2k command|aMule's ed2k links handler]]
|-
| ''--enable-alc'' || Compile [[aLinkCreator|aMuleLinkCreator GUI version]]
|-
| ''--enable-alcc'' || Compile [[aLinCreatorConsole|aMuleLinkCreator for console]]
|}

{| border=1
|+ Configure tweaks
| ''--disable-gtktest'' || Do not try to compile a test [http://www.gtk.org GTK] (either [http://www.gtk.org GTK]1 or [http://www.gtk.org GTK]2 depending on your system's configuration) program to see if your system has a proper [http://www.gtk.org GTK] configuration. This will make the ''configure'' script run a (very) little faster, but you should still not use it unless you know what you are doing, since the ''configure'' script could miss some tests.
|}

=== [[aMule]] compilation settings ===

This options are specific to [[aMule]]'s configure script, but they are not directly related to [[aMule]]. They just tell were some libraries or headers are located in your system, so that [[aMule]] can find them when compiling. Use them if you have those files in non-standard paths or when you know what you are doing.

To better understand these options, take a look at the [[#Common options|common options]] chapter in this article.

{| border=1
|+ [http://www.gzip.org/zlib zLib]
| ''--with-zlib=PREFIX'' || Look for [http://www.gzip.org/zlib zLib] files in '''PREFIX'''
|}

{| border=1
|+ [http://curl.haxx.se Curl]
| ''--with-curl-config=CONFIG'' || '''CONFIG''' is the path of ''curl-config''
|}

{| border=1
|+ [http://www.boutell.com/gd LibGD]
| ''--with-gdlib-prefix=PREFIX'' || Look for [http://www.boutell.com/gd LibGD] files in '''PREFIX'''
|-
| ''--with-gdlib-exec-prefix=PREFIX'' || Look for GDLib libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-gdlib-exec-prefix''
|-
| ''--with-gdlib-config=CONFIG'' || '''CONFIG''' is the path of ''gdlib-config''
|}

{| border=1
|+ [http://www.libpng.org LibPNG]
| ''--with-libpng-prefix=PREFIX'' || Look for [http://www.libpng.org LibPNG] files in '''PREFIX'''
|-
| ''--with-libpng-exec-prefix=PREFIX'' || Look for [http://www.libpng.org LibPNG] libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-libpng-exec-prefix''
|-
| ''--with-libpng-config=CONFIG'' || '''CONFIG''' is the path of ''libpng-config''
|}

{| border=1
|+ [[wxWidgets]]
| ''--with-wx-prefix=PREFIX'' || Look for [[wxWidgets]] files in '''PREFIX'''
|-
| ''--with-wx-exec-prefix=PREFIX'' || Look for [[wxWidgets]] libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-wx-exec-prefix''
|-
| ''--with-wx-config=CONFIG'' || '''CONFIG''' is the path of ''wx-config''
|}

{| border=1
|+ [[wxBase]]
| ''--with-wxbase-prefix=PREFIX'' || Look for [[wxBase]] files in '''PREFIX'''
|-
| ''--with-wxbase-exec-prefix=PREFIX'' || Look for [[wxBase]] libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-wxbase-exec-prefix''

|-
| ''--with-wxbase-config=CONFIG'' || '''CONFIG''' is the path of ''wxbase-config''
|}

{| border=1
|+ [http://www.gtk.org GTK]
| ''--with-gtk-prefix=PREFIX'' || Look for [http://www.gtk.org GTK] (not [http://www.gtk.org GTK]2) files in '''PREFIX'''
|-
| ''--with-gtk-exec-prefix=PREFIX'' || Look for [http://www.gtk.org GTK] (not [http://www.gtk.org GTK]2) libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-gtk-exec-prefix''
|}

{| border=1
|+ [http://www.openssl.org/docs/crypto/crypto.html Crypto++]
| ''--with-crypto-prefix=PREFIX'' || Look for [http://www.openssl.org/docs/crypto/crypto.html Crypto++] files in '''PREFIX'''
|}

{| border=1
|+ [http://www.gnu.org/software/libiconv LibIConv]
| ''--with-libiconv-prefix=PREFIX'' || Look for [http://www.gnu.org/software/libiconv LibIConv] files in '''''PREFIX'''/include'' and '''''PREFIX'''/lib''
|-
| ''--without-libiconv-prefix'' || Don't search for [http://www.gnu.org/software/libiconv LibIConv] in includedir and libdir
|}

{| border=1
|+ [http://www.gnu.org/software/gettext gettext]
| ''--with-included-gettext'' || Use the [http://www.gnu.org/software/gettext GNU gettext] library included in the ''intl/'' directory instead of the system's. This is only for strange systems where [http://www.gnu.org/software/gettext gettext], for some reason, will not handle [[aMule]]'s catalog files
|}

{| border=1
|+ [http://gnuwin32.sourceforge.net/packages/libintl.htm LibIntl]
| ''--with-libintl-prefix=PREFIX'' || Look for [http://gnuwin32.sourceforge.net/packages/libintl.htm LibIntl] files in '''''PREFIX'''/include''' and '''''PREFIX'''/lib''''
|-
| ''--without-libintl-prefix'' || Don't search for [http://gnuwin32.sourceforge.net/packages/libintl.htm LibIntl] in includedir and libdir
|}

{| border=1
|+ [http://ccache.samba.org ccache]
| ''--with-ccache-prefix=PREFIX'' || Look for [http://ccache.samba.org ccache] files in '''PREFIX'''
|}

== Variables ==

Before you take a look at the [[#Variables and what they mean|variables and what they mean]], you must take a look at the two variable [[#Usage types|usage types]] available.

=== Usage types ===

You can either use [[#Environment variables|environment variables]] or you can [[#Configure variables|enter variables directly into the ''configure'' command]].

==== Environment variables ====

If you plan to use environment variables, you will affect the behaviour of ''configure'' and any other program you run in that same shell until you end your session. You must set them '''before''' running configure. To set them, run

export ''VAR=VALUE'''

where ''VAR'' is the name of the environmental variable and ''VALUE'' is it's value.

==== Configure variables ====

If you don't want to use environment variables, you can pass them into the ''configure'' command, this way:

configure VAR=VALUE

where ''VAR'' stands for the variable name and ''VALUE'' is its value.

=== Variables and what they mean ===

Do '''NOT''' touch these variables if you don't know what you are doing!

This are some of the most commonly used variables for ''configure'':

{| border=1
|+ Variables
| ''CC'' || [http://en.wikipedia.org/wiki/C_programming_language C] compiler command to use
|-
| ''CXX'' || [http://en.wikipedia.org/wiki/C_Plus_Plus C++] compiler command to use (e.g. ''[http://gcc.gnu.org g++]'')
|-
| ''CPP'' || [http://en.wikipedia.org/wiki/C_programming_language C] preprocessor command to use
|-
| ''CFLAGS'' || [http://en.wikipedia.org/wiki/C_programming_language C] compiler flags
|-
| ''CXXCPP'' || [http://en.wikipedia.org/wiki/C_Plus_Plus C++] preprocessor command to use
|-
| ''CXXFLAGS'' || [http://en.wikipedia.org/wiki/C_Plus_Plus C++] compiler flags
|-
| ''LDFLAGS'' || Linker flags. Usually used to specify additional library directories (e.g. ''LDFLAGS="-L/usr/lib"'')
|-
| ''CPPFLAGS'' || [http://en.wikipedia.org/wiki/C_programming_language C]/[http://en.wikipedia.org/wiki/C_Plus_Plus C++] preprocessor flags (e.g. ''CPPFLAGS="-I/usr/include"'')
|}

== More information ==

This article is mainly an explanation (dummy-proof) of the output of ''configure --help''.

Anyway, it could (rarely) be out of date. So, if there's something you want to do with ''configure'' that is not listed here, run ''configure --help'' and see if it is listed there.

Of course, you can always take a look at the [http://www.airs.com/ian/configure GNU configure page].
|
|}

Configure

2005-08-29T11:16:13Z

83.42.86.182:

{| width="90%" align="left"
|
== Introduction ==

''configure'' configures [[aMule]] to adapt to many kinds of systems.

Its purpose is to make it easy to port it to many platforms and to compile it and use it in all platforms in the very same way.

You can set lots of parameters in it to adapt it to your system and to tweak its features.

'''NOTE:''' This article is focused in [[aMule]]'s ''configure''. Other ''configure'' scripts work in a similar way, but their options will differ. This article might be useful for them as well, but have in mind that they might have options not listed here and lack some listed here too.

== Main usage ==

Its usage is ''./configure [OPTION]... [VARIABLE=VALUE]...''

So, as you can see, you can define its behaviour both through [[#Options|options]] and through [[#Variables|variables]]

== Options ==

You can define one or more options. The available options in [[aMule]]'s ''configure'' are listed below. To better understand their meaning, they have been grouped into several tables with options which affect the behaviour of ''configure'' in a similar way.

Please note that ''configure'' will (in most cases) not complain if you enter an invalid option or variable. So make sure you enter the options correctly (no typos) or they will have no effect and configure won't behave in the way you expected.

=== Main options ===

These options should exist in any ''configure'' script around the world. They won't run the ''configure'' script to configure your application's compilation, but only output information you might need.

{| border=1
|+ Basic options
|''-h'' or ''--help'' || This will display a help message summing up all ''configure'' options
|-
|''--help=short'' || This will display a help message summing up all ''configure'' options specific to this application (doesn't display generic configure options)
|-
|''-V'' or ''--version'' || This will display the version information
|}

=== Non-compilation common options ===

These options should also exist on any ''configure'' script around the world. They will set some non-compilation related preferences.

{| border=1
|+ Options directly related to the ''configure'' script
|''-q'' or ''--quiet'' or ''--silent'' || Do not print the `checking...' messages, only the final summed up ouput
|-
|''--cache-file=FILE'' || Store the checkings' ouputs in '''FILE''' in a script format, so you can reuse without the need to rerun ''configure'' (read the cached file for more information)
|-
|''-C'' or ''--config-cache || Same as ''--cache-file=config.cache''
|-
|''-n'' or ''--no-create || Just run ''configure'', but do not create any files
|-
|''--srcdir=DIR'' || Look for the sources in '''DIR'''. By default, the ''configure'' dir or its parent (''../'')
|}

=== Common options ===

These options should also exist on any ''configure'' script around the world. This time, these ones will affect the compilation of the application, so be careful when using them. You should take a close look at the application's ''README'' document (if available) if you want to use any of them (and even if you don't, still take a look at it, since you might '''have''' to use some).

{| border=1
|+ Installation directories options
| ''--prefix=PREFIX'' || Set where to install architecture-independent files (data) in '''PREFIX'''. By dafault, this is set to ''/usr/local''
|-
| --exec-prefix=EPREFIX || Set where to install architecture-dependent files (mainly binaries) in '''EPREFIX'''. By default, this is set to the same value as '''PREFIX'''.
|}

{| border=1
|+ Advanced installation directories options
| ''--bindir=DIR'' || Where to store user executables. By default, '''''EPREFIX'''/bin''
|-
| ''--sbindir=DIR'' || Where to store system administrator executables. By default, '''''EPREFIX'''/sbin''
|-
| ''--libexecdir=DIR'' || Where to store program executable. By default '''''EPREFIX'''/libexeec''
|-
| ''--datadir=DIR'' || Where to store read-only architecture independent data. By default, '''''EPREFIX'''/share''
|-
| ''--sysconfdir=DIR'' || Where to install read-only single-machine data. By default, '''''PREFIX'''/etc''
|-
| ''--sharedstatedir=DIR'' || Where to store modifiable architacture-independent data. By default '''''PREFIX'''/com''
|-
| ''--localstatedir=DIR'' || Where to store modifiable single-machine data. By default, '''''PREFIX'''/var''
|-
| ''--libdir=DIR || Where to search libs object code libraries. By default, '''''EPREFIX'''/lib''
|-
| ''--includedir=DIR'' || Directory containing the [http://en.wikipedia.org/wiki/C_programming_language C] header files. By default, '''''PREFIX'''''/include''
|-
| ''--oldincludedir=DIR'' || Directory containing [http://en.wikipedia.org/wiki/C_programming_language C] header files for non-GCC. By default, ''/usr/include''
|-
| ''--infodir=DIR'' || Where to store info and documentation files. By default, '''''EPREFIX'''/info''
|-
| ''--mandir=DIR'' || Where to store man pages. By default, '''''EPREFIX'''/man
|}

{| border=1
|+ General rule to program enabling and dirs specification
| ''--program-prefix=PREFIX'' || Prepend '''PREFIX''' to installed program names
|-
| ''--program-suffix=SUFFIX'' || Append '''SUFFIX''' to installed program names
|-
| ''--program-transform-name=SUBST'' || Run ''[http://www.gnu.org/software/sed/sed.html sed] '''SUBST''''' on installed program names
|}

{| border=1
|+ General rule to enabling or disabling features (sometimes it enables or disables the compilation of a program)
| ''--disable-FEATURE'' || Do not include '''FEATURE'''. Equivalent to ''--enable-'''FEATURE'''=no'' (see below)
|-
| ''--enable-FEATURE'' || Include '''FEATURE'''. Equivalent to ''--enable-'''FEATURE'''=yes'' (see below)
|-
| ''--enable-FEATURE=VALUE'' || Include '''FEATURE''' and specify it's value to '''VALUE'''. The meaning of the value should be explained in the ''configure --help'' output of the script
|}

{| border=1
|+
| ''--without-PACKAGE'' || Do not use '''PACKAGE'''. Equivalent to ''--with-'''PACKAGE'''=no'' (see below)
|-
| ''--with-PACKAGE'' || use PACKAGE. Equivalent to ''--with-'''PACKAGE'''=yes'' (see below)
|-
| ''--with-PACKAGE=VALUE'' || Use '''PACKAGE''' and set its value to '''VALUE'''
|}

{| border=1
|+ System specifications
| ''--build=BUILD'' || Configure for building on '''BUILD''' platform. By default, it guesses the platform it is being run on
|-
| ''--host=HOST'' || Cross-compile to build programs to run on '''HOST''' platforms. By default, same as '''BUILD'''
|-
| ''--target=TARGET'' || Configure for building compilers for '''TARGET''' platfroms. By default, same as '''HOST'''
|}

=== Very-common options ===

In most ''configure'' scripts you will also be able to use these options.

{| border=1
|+ Quite common compiler options
| ''--with-gnu-ld'' || Use the [http://www.gnu.org/software/binutils/manual/ld-2.9.1/ld.html GNU ld] as linker, without testing if it is the default linker in the system
|}

{| border=1
|+ X directory specifications
| ''--with-x'' || Use the [http://www.xfree86.org X Window System]
|-
| ''--x-includes=DIR'' || '''DIR''' contains [http://www.xfree86.org X]'s include files
|-
| ''--x-libraries=DIR'' || '''DIR''' contains [http://www.xfree86.org X]'s libraries
|}

=== [[aMule]] options ===

The following options are specific to [[aMule]]'s ''configure'' script. They will allow you to enable and disable them, so you should really take a look at them or you might sadly find out you lack things you would like to have in your [[aMule]] system ;-)

{| border=1
|+ Developer options
|-
| ''--enable-maintainer-mode'' || Activate some extra instructions only useful for developers (and totaly non-recommended to normal users)
|-
| ''--disable-dependency-tracking'' || Makes the application compile faster, but causes problems if you change the source code and try to compile again. Dependency tracking allows the make process to know which things to rebuild when something changes. If you do not plan to compile the application again with those same sources, you can safely use this option
|-
| ''--enable-dependency-tracking'' || Keep track of the dependencies so that on next build, only changed files will be recompiled. It slows down the compilation a little. This is the default
|-
| ''--enable-ccache'' || Enable [http://ccache.samba.org ccache]. This will make following compilations faster since only the non-modified bits of code will be recompiled. If you don't plan to compile [[aMule]] very often, don't enable this, since it takes longer to compile on the first compilation and it requires lots of disk space
|-
| ''--enable-profile'' || Enable code profiling (which allows to see how much time and resources are spent on each part of the code, though it will make [[aMule]] run much slower, so, in most cases, don't use it). The output file is ''gmon.out'' and can be viewed with ''gprof''. For more information, ''man [http://www.cs.utah.edu/dept/old/texinfo/as/gprof_toc.html gprof]'' and ''man [http://gcc.gnu.org gcc]'' (in the man pages of ''[http://gcc.gnu.org gcc]'', search for the command line option ''-pg'')
|}

{| border=1
|+ Compilation tweaks
| ''--disable-debug'' || Disables outputing information of the application execution. This information is useful to track bugs, so you might not want to use this option or you will not be able to report bugs properly
|-
| ''--enable-optimize'' || Optimizes the code to run (a little) faster. Using this option will not allow you to create useful bug reports so you might not want to enable it
|-
| ''--enable-optimise'' || Same as ''--enable-optimize'', but is deprecated (it is still there for backwards compatibility only)
|-
| ''--disable-rpath'' || Do not write the libraries' path into the binary. Useful only if you plan to move the binary to other systems or if you move your libraries often. Only use it if you know what you're doing, since it will make [[aMule]] run slower
|-
| ''--enable-static'' || Creates statically linked executables, which means that they will need no libraries since any needed library will be included in the executable file. The executable might run faster, and will be easily portable between systems using the same platform, but will be incredibly bigger in size
|}

{| border=1
|+ Compilation of external libraries
| ''--disable-embedded_crypto'' || Do not use [[aMule]]'s cryptography code, instead, use external libraries' code. This option is not recommended and it could possibly break the compilation
|-
| ''--disable-gsocket'' || Do not use [[aMule]]'s ''gsocket.c'' implementation. Do not use it unless you are '''very''' sure of what you are doing! (On [[wxWidgets]] 2.4, the default ''gsocket.c'' code gives [[Low ID]]s on restart)
|-
| ''--disable-nls'' || Do not use [http://www.vitavoom.com/postgresql-docs/nls.html Native Language Support]. This way [http://www.gnu.org/software/gettext gettext] won't be required, but translations will be disabled
|}

{| border=1
|+ Compilation hardcodings
| ''--disable-systray'' || Do not include a SysTray into the [[aMule]] build. Only [[wxWidgets]] 2.4.2 users with no [http://www.gtk.org GTK] should use it. Others should disable SysTray in [[aMule]]'s preferences
|-
| ''--enable-utf8-systray'' || Use [http://www.unicode.org UTF-8] encoded strings in [[aMule]]'s SysTray. Only affects [[wxWidgets]] 2.4
|}

{| border=1
|+ [[aMule]] binaries selection
| ''--disable-monolithic'' || disable building of the [[aMule|monolithic aMule]] app. This is normally not recommended, unless you really know what you are doing (e.g. to compile only the [[aMuled|daemon]])
|-
| ''--enable-amule-daemon'' || Compile [[aMuled|aMule daemon]]
|-
| ''--enable-amulecmd'' || Compile the [[aMuleCMD|aMule command line client]]
|-
| ''--enable-amulecmdgui'' || Compile [[aMuleCMDDLG|aMule command line client (GUI version)]]
|-
| ''--enable-webserver'' || Compile [[aMuleWeb|aMule's WebServer]]
|-
| ''--enable-webservergui'' || Compile [[aMuleWebDLG|aMule's WebServer (GUI version)]]
|-
| ''--enable-amule-gui'' || Compile [[aMuleGUI|aMule remote GUI]]
|-
| ''--enable-cas'' || Compile [[CAS|C aMule Statistics]]
|-
| ''--enable-wxcas'' || Compile [[wxCAS|aMule GUI Statistics]]
|-
| ''--disable-ed2k'' || Don't compile [[ed2k command|aMule's ed2k links handler]]
|-
| ''--enable-alc'' || Compile [[aLinkCreator|aMuleLinkCreator GUI version]]
|-
| ''--enable-alcc'' || Compile [[aLinCreatorConsole|aMuleLinkCreator for console]]
|}

{| border=1
|+ Configure tweaks
| ''--disable-gtktest'' || Do not try to compile a test [http://www.gtk.org GTK] (either [http://www.gtk.org GTK]1 or [http://www.gtk.org GTK]2 depending on your system's configuration) program to see if your system has a proper [http://www.gtk.org GTK] configuration. This will make the ''configure'' script run a (very) little faster, but you should still not use it unless you know what you are doing, since the ''configure'' script could miss some tests.
|}

=== [[aMule]] compilation settings ===

This options are specific to [[aMule]]'s configure script, but they are not directly related to [[aMule]]. They just tell were some libraries or headers are located in your system, so that [[aMule]] can find them when compiling. Use them if you have those files in non-standard paths or when you know what you are doing.

To better understand these options, take a look at the [[#Common options|common options]] chapter in this article.

{| border=1
|+ [http://www.gzip.org/zlib zLib]
| ''--with-zlib=PREFIX'' || Look for [http://www.gzip.org/zlib zLib] files in '''PREFIX'''
|}

{| border=1
|+ [http://curl.haxx.se Curl]
| ''--with-curl-config=CONFIG'' || '''CONFIG''' is the path of ''curl-config''
|}

{| border=1
|+ [http://www.boutell.com/gd LibGD]
| ''--with-gdlib-prefix=PREFIX'' || Look for [http://www.boutell.com/gd LibGD] files in '''PREFIX'''
|-
| ''--with-gdlib-exec-prefix=PREFIX'' || Look for GDLib libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-gdlib-exec-prefix''
|-
| ''--with-gdlib-config=CONFIG'' || '''CONFIG''' is the path of ''gdlib-config''
|}

{| border=1
|+ [http://www.libpng.org LibPNG]
| ''--with-libpng-prefix=PREFIX'' || Look for [http://www.libpng.org LibPNG] files in '''PREFIX'''
|-
| ''--with-libpng-exec-prefix=PREFIX'' || Look for [http://www.libpng.org LibPNG] libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-libpng-exec-prefix''
|-
| ''--with-libpng-config=CONFIG'' || '''CONFIG''' is the path of ''libpng-config''
|}

{| border=1
|+ [[wxWidgets]]
| ''--with-wx-prefix=PREFIX'' || Look for [[wxWidgets]] files in '''PREFIX'''
|-
| ''--with-wx-exec-prefix=PREFIX'' || Look for [[wxWidgets]] libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-wx-exec-prefix''
|-
| ''--with-wx-config=CONFIG'' || '''CONFIG''' is the path of ''wx-config''
|}

{| border=1
|+ [[wxBase]]
| ''--with-wxbase-prefix=PREFIX'' || Look for [[wxBase]] files in '''PREFIX'''
|-
| ''--with-wxbase-exec-prefix=PREFIX'' || Look for [[wxBase]] libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-wxbase-exec-prefix''

|-
| ''--with-wxbase-config=CONFIG'' || '''CONFIG''' is the path of ''wxbase-config''
|}

{| border=1
|+ [http://www.gtk.org GTK]
| ''--with-gtk-prefix=PREFIX'' || Look for [http://www.gtk.org GTK] (not [http://www.gtk.org GTK]2) files in '''PREFIX'''
|-
| ''--with-gtk-exec-prefix=PREFIX'' || Look for [http://www.gtk.org GTK] (not [http://www.gtk.org GTK]2) libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-gtk-exec-prefix''
|}

{| border=1
|+ [http://www.openssl.org/docs/crypto/crypto.html Crypto++]
| ''--with-crypto-prefix=PREFIX'' || Look for [http://www.openssl.org/docs/crypto/crypto.html Crypto++] files in '''PREFIX'''
|}

{| border=1
|+ [http://www.gnu.org/software/libiconv LibIConv]
| ''--with-libiconv-prefix=PREFIX'' || Look for [http://www.gnu.org/software/libiconv LibIConv] files in '''''PREFIX'''/include'' and '''''PREFIX'''/lib''
|-
| ''--without-libiconv-prefix'' || Don't search for [http://www.gnu.org/software/libiconv LibIConv] in includedir and libdir
|}

{| border=1
|+ [http://www.gnu.org/software/gettext gettext]
| ''--with-included-gettext'' || Use the [http://www.gnu.org/software/gettext GNU gettext] library included in the ''intl/'' directory instead of the system's. This is only for strange systems where [http://www.gnu.org/software/gettext gettext], for some reason, will not handle [[aMule]]'s catalog files
|}

{| border=1
|+ [http://gnuwin32.sourceforge.net/packages/libintl.htm LibIntl]
| ''--with-libintl-prefix=PREFIX'' || Look for [http://gnuwin32.sourceforge.net/packages/libintl.htm LibIntl] files in '''''PREFIX'''/include''' and '''''PREFIX'''/lib''''
|-
| ''--without-libintl-prefix'' || Don't search for [http://gnuwin32.sourceforge.net/packages/libintl.htm LibIntl] in includedir and libdir
|}

{| border=1
|+ [http://ccache.samba.org ccache]
| ''--with-ccache-prefix=PREFIX'' || Look for [http://ccache.samba.org ccache] files in '''PREFIX'''
|}

== Variables ==

Before you take a look at the [[#Variables and what they mean|variables and what they mean]], you must take a look at the two variable [[#Usage types|usage types]] available.

=== Usage types ===

You can either use [[#Environment variables|environment variables]] or you can [[#Configure variables|enter variables directly into the ''configure'' command]].

==== Environment variables ====

If you plan to use environment variables, you will affect the behaviour of ''configure'' and any other program you run in that same shell until you end your session. You must set them '''before''' running configure. To set them, run

export ''VAR=VALUE'''

where ''VAR'' is the name of the environmental variable and ''VALUE'' is it's value.

==== Configure variables ====

If you don't want to use environment variables, you can pass them into the ''configure'' command, this way:

configure VAR=VALUE

where ''VAR'' stands for the variable name and ''VALUE'' is its value.

=== Variables and what they mean ===

Do '''NOT''' touch these variables if you don't know what you are doing!

This are some of the most commonly used variables for ''configure'':

{| border=1
|+ Variables
| ''CC'' || [http://en.wikipedia.org/wiki/C_programming_language C] compiler command to use
|-
| ''CXX'' || [http://en.wikipedia.org/wiki/C_Plus_Plus C++] compiler command to use (e.g. ''[http://gcc.gnu.org g++]'')
|-
| ''CPP'' || [http://en.wikipedia.org/wiki/C_programming_language C] preprocessor command to use
|-
| ''CFLAGS'' || [http://en.wikipedia.org/wiki/C_programming_language C] compiler flags
|-
| ''CXXCPP'' || [http://en.wikipedia.org/wiki/C_Plus_Plus C++] preprocessor command to use
|-
| ''CXXFLAGS'' || [http://en.wikipedia.org/wiki/C_Plus_Plus C++] compiler flags
|-
| ''LDFLAGS'' || Linker flags. Usually used to specify additional library directories (e.g. ''LDFLAGS="-L/usr/lib"'')
|-
| ''CPPFLAGS'' || [http://en.wikipedia.org/wiki/C_programming_language C]/[http://en.wikipedia.org/wiki/C_Plus_Plus C++] preprocessor flags (e.g. ''CPPFLAGS="-I/usr/include"'')
|}

== More information ==

This article is mainly an explanation (dummy-proof) of the output of ''configure --help''.

Anyway, it could (rarely) be out of date. So, if there's something you want to do with ''configure'' that is not listed here, run ''configure --help'' and see if it is listed there.

Of course, you can always take a look at the [http://www.airs.com/ian/configure GNU configure page].
|
|}

Configure

2005-08-29T11:13:56Z

83.42.86.182: wrong description

{| width="90%" align="left"
|
== Introduction ==

''configure'' configures [[aMule]] to adapt to many kinds of systems.

Its purpose is to make it easy to port it to many platforms and to compile it and use it in all platforms in the very same way.

You can set lots of parameters in it to adapt it to your system and to tweak its features.

'''NOTE:''' This article is focused in [[aMule]]'s ''configure''. Other ''configure'' scripts work in a similar way, but their options will differ. This article might be useful for them as well, but have in mind that they might have options not listed here and lack some listed here too.

== Main usage ==

Its usage is ''./configure [OPTION]... [VARIABLE=VALUE]...''

So, as you can see, you can define its behaviour both through [[#Options|options]] and through [[#Variables|variables]]

== Options ==

You can define one or more options. The available options in [[aMule]]'s ''configure'' are listed below. To better understand their meaning, they have been grouped into several tables with options which affect the behaviour of ''configure'' in a similar way.

Please note that ''configure'' will (in most cases) not complain if you enter an invalid option or variable. So make sure you enter the options correctly (no typos) or they will have no effect and configure won't behave in the way you expected.

=== Main options ===

These options should exist in any ''configure'' script around the world. They won't run the ''configure'' script to configure your application's compilation, but only output information you might need.

{| border=1
|+ Basic options
|''-h'' or ''--help'' || This will display a help message summing up all ''configure'' options
|-
|''-V'' or ''--version'' || This will display the version information
|}

=== Non-compilation common options ===

These options should also exist on any ''configure'' script around the world. They will set some non-compilation related preferences.

{| border=1
|+ Options directly related to the ''configure'' script
|''-q'' or ''--quiet'' or ''--silent'' || Do not print the `checking...' messages, only the final summed up ouput
|-
|''--cache-file=FILE'' || Store the checkings' ouputs in '''FILE''' in a script format, so you can reuse without the need to rerun ''configure'' (read the cached file for more information)
|-
|''-C'' or ''--config-cache || Same as ''--cache-file=config.cache''
|-
|''-n'' or ''--no-create || Just run ''configure'', but do not create any files
|-
|''--srcdir=DIR'' || Look for the sources in '''DIR'''. By default, the ''configure'' dir or its parent (''../'')
|}

=== Common options ===

These options should also exist on any ''configure'' script around the world. This time, these ones will affect the compilation of the application, so be careful when using them. You should take a close look at the application's ''README'' document (if available) if you want to use any of them (and even if you don't, still take a look at it, since you might '''have''' to use some).

{| border=1
|+ Installation directories options
| ''--prefix=PREFIX'' || Set where to install architecture-independent files (data) in '''PREFIX'''. By dafault, this is set to ''/usr/local''
|-
| --exec-prefix=EPREFIX || Set where to install architecture-dependent files (mainly binaries) in '''EPREFIX'''. By default, this is set to the same value as '''PREFIX'''.
|}

{| border=1
|+ Advanced installation directories options
| ''--bindir=DIR'' || Where to store user executables. By default, '''''EPREFIX'''/bin''
|-
| ''--sbindir=DIR'' || Where to store system administrator executables. By default, '''''EPREFIX'''/sbin''
|-
| ''--libexecdir=DIR'' || Where to store program executable. By default '''''EPREFIX'''/libexeec''
|-
| ''--datadir=DIR'' || Where to store read-only architecture independent data. By default, '''''EPREFIX'''/share''
|-
| ''--sysconfdir=DIR'' || Where to install read-only single-machine data. By default, '''''PREFIX'''/etc''
|-
| ''--sharedstatedir=DIR'' || Where to store modifiable architacture-independent data. By default '''''PREFIX'''/com''
|-
| ''--localstatedir=DIR'' || Where to store modifiable single-machine data. By default, '''''PREFIX'''/var''
|-
| ''--libdir=DIR || Where to search libs object code libraries. By default, '''''EPREFIX'''/lib''
|-
| ''--includedir=DIR'' || Directory containing the [http://en.wikipedia.org/wiki/C_programming_language C] header files. By default, '''''PREFIX'''''/include''
|-
| ''--oldincludedir=DIR'' || Directory containing [http://en.wikipedia.org/wiki/C_programming_language C] header files for non-GCC. By default, ''/usr/include''
|-
| ''--infodir=DIR'' || Where to store info and documentation files. By default, '''''EPREFIX'''/info''
|-
| ''--mandir=DIR'' || Where to store man pages. By default, '''''EPREFIX'''/man
|}

{| border=1
|+ General rule to program enabling and dirs specification
| ''--program-prefix=PREFIX'' || Prepend '''PREFIX''' to installed program names
|-
| ''--program-suffix=SUFFIX'' || Append '''SUFFIX''' to installed program names
|-
| ''--program-transform-name=SUBST'' || Run ''[http://www.gnu.org/software/sed/sed.html sed] '''SUBST''''' on installed program names
|}

{| border=1
|+ General rule to enabling or disabling features (sometimes it enables or disables the compilation of a program)
| ''--disable-FEATURE'' || Do not include '''FEATURE'''. Equivalent to ''--enable-'''FEATURE'''=no'' (see below)
|-
| ''--enable-FEATURE'' || Include '''FEATURE'''. Equivalent to ''--enable-'''FEATURE'''=yes'' (see below)
|-
| ''--enable-FEATURE=VALUE'' || Include '''FEATURE''' and specify it's value to '''VALUE'''. The meaning of the value should be explained in the ''configure --help'' output of the script
|}

{| border=1
|+
| ''--without-PACKAGE'' || Do not use '''PACKAGE'''. Equivalent to ''--with-'''PACKAGE'''=no'' (see below)
|-
| ''--with-PACKAGE'' || use PACKAGE. Equivalent to ''--with-'''PACKAGE'''=yes'' (see below)
|-
| ''--with-PACKAGE=VALUE'' || Use '''PACKAGE''' and set its value to '''VALUE'''
|}

{| border=1
|+ System specifications
| ''--build=BUILD'' || Configure for building on '''BUILD''' platform. By default, it guesses the platform it is being run on
|-
| ''--host=HOST'' || Cross-compile to build programs to run on '''HOST''' platforms. By default, same as '''BUILD'''
|-
| ''--target=TARGET'' || Configure for building compilers for '''TARGET''' platfroms. By default, same as '''HOST'''
|}

=== Very-common options ===

In most ''configure'' scripts you will also be able to use these options.

{| border=1
|+ Quite common compiler options
| ''--with-gnu-ld'' || Use the [http://www.gnu.org/software/binutils/manual/ld-2.9.1/ld.html GNU ld] as linker, without testing if it is the default linker in the system
|}

{| border=1
|+ X directory specifications
| ''--with-x'' || Use the [http://www.xfree86.org X Window System]
|-
| ''--x-includes=DIR'' || '''DIR''' contains [http://www.xfree86.org X]'s include files
|-
| ''--x-libraries=DIR'' || '''DIR''' contains [http://www.xfree86.org X]'s libraries
|}

=== [[aMule]] options ===

The following options are specific to [[aMule]]'s ''configure'' script. They will allow you to enable and disable them, so you should really take a look at them or you might sadly find out you lack things you would like to have in your [[aMule]] system ;-)

{| border=1
|+ Developer options
|-
| ''--enable-maintainer-mode'' || Activate some extra instructions only useful for developers (and totaly non-recommended to normal users)
|-
| ''--disable-dependency-tracking'' || Makes the application compile faster, but causes problems if you change the source code and try to compile again. Dependency tracking allows the make process to know which things to rebuild when something changes. If you do not plan to compile the application again with those same sources, you can safely use this option
|-
| ''--enable-dependency-tracking'' || Keep track of the dependencies so that on next build, only changed files will be recompiled. It slows down the compilation a little. This is the default
|-
| ''--enable-ccache'' || Enable [http://ccache.samba.org ccache]. This will make following compilations faster since only the non-modified bits of code will be recompiled. If you don't plan to compile [[aMule]] very often, don't enable this, since it takes longer to compile on the first compilation and it requires lots of disk space
|-
| ''--enable-profile'' || Enable code profiling (which allows to see how much time and resources are spent on each part of the code, though it will make [[aMule]] run much slower, so, in most cases, don't use it). The output file is ''gmon.out'' and can be viewed with ''gprof''. For more information, ''man [http://www.cs.utah.edu/dept/old/texinfo/as/gprof_toc.html gprof]'' and ''man [http://gcc.gnu.org gcc]'' (in the man pages of ''[http://gcc.gnu.org gcc]'', search for the command line option ''-pg'')
|}

{| border=1
|+ Compilation tweaks
| ''--disable-debug'' || Disables outputing information of the application execution. This information is useful to track bugs, so you might not want to use this option or you will not be able to report bugs properly
|-
| ''--enable-optimize'' || Optimizes the code to run (a little) faster. Using this option will not allow you to create useful bug reports so you might not want to enable it
|-
| ''--enable-optimise'' || Same as ''--enable-optimize'', but is deprecated (it is still there for backwards compatibility only)
|-
| ''--disable-rpath'' || Do not write the libraries' path into the binary. Useful only if you plan to move the binary to other systems or if you move your libraries often. Only use it if you know what you're doing, since it will make [[aMule]] run slower
|-
| ''--enable-static'' || Creates statically linked executables, which means that they will need no libraries since any needed library will be included in the executable file. The executable might run faster, and will be easily portable between systems using the same platform, but will be incredibly bigger in size
|}

{| border=1
|+ Compilation of external libraries
| ''--disable-embedded_crypto'' || Do not use [[aMule]]'s cryptography code, instead, use external libraries' code. This option is not recommended and it could possibly break the compilation
|-
| ''--disable-gsocket'' || Do not use [[aMule]]'s ''gsocket.c'' implementation. Do not use it unless you are '''very''' sure of what you are doing! (On [[wxWidgets]] 2.4, the default ''gsocket.c'' code gives [[Low ID]]s on restart)
|-
| ''--disable-nls'' || Do not use [http://www.vitavoom.com/postgresql-docs/nls.html Native Language Support]. This way [http://www.gnu.org/software/gettext gettext] won't be required, but translations will be disabled
|}

{| border=1
|+ Compilation hardcodings
| ''--disable-systray'' || Do not include a SysTray into the [[aMule]] build. Only [[wxWidgets]] 2.4.2 users with no [http://www.gtk.org GTK] should use it. Others should disable SysTray in [[aMule]]'s preferences
|-
| ''--enable-utf8-systray'' || Use [http://www.unicode.org UTF-8] encoded strings in [[aMule]]'s SysTray. Only affects [[wxWidgets]] 2.4
|}

{| border=1
|+ [[aMule]] binaries selection
| ''--disable-monolithic'' || disable building of the [[aMule|monolithic aMule]] app. This is normally not recommended, unless you really know what you are doing (e.g. to compile only the [[aMuled|daemon]])
|-
| ''--enable-amule-daemon'' || Compile [[aMuled|aMule daemon]]
|-
| ''--enable-amulecmd'' || Compile the [[aMuleCMD|aMule command line client]]
|-
| ''--enable-amulecmdgui'' || Compile [[aMuleCMDDLG|aMule command line client (GUI version)]]
|-
| ''--enable-webserver'' || Compile [[aMuleWeb|aMule's WebServer]]
|-
| ''--enable-webservergui'' || Compile [[aMuleWebDLG|aMule's WebServer (GUI version)]]
|-
| ''--enable-amule-gui'' || Compile [[aMuleGUI|aMule remote GUI]]
|-
| ''--enable-cas'' || Compile [[CAS|C aMule Statistics]]
|-
| ''--enable-wxcas'' || Compile [[wxCAS|aMule GUI Statistics]]
|-
| ''--disable-ed2k'' || Don't compile [[ed2k command|aMule's ed2k links handler]]
|-
| ''--enable-alc'' || Compile [[aLinkCreator|aMuleLinkCreator GUI version]]
|-
| ''--enable-alcc'' || Compile [[aLinCreatorConsole|aMuleLinkCreator for console]]
|}

{| border=1
|+ Configure tweaks
| ''--disable-gtktest'' || Do not try to compile a test [http://www.gtk.org GTK] (either [http://www.gtk.org GTK]1 or [http://www.gtk.org GTK]2 depending on your system's configuration) program to see if your system has a proper [http://www.gtk.org GTK] configuration. This will make the ''configure'' script run a (very) little faster, but you should still not use it unless you know what you are doing, since the ''configure'' script could miss some tests.
|}

=== [[aMule]] compilation settings ===

This options are specific to [[aMule]]'s configure script, but they are not directly related to [[aMule]]. They just tell were some libraries or headers are located in your system, so that [[aMule]] can find them when compiling. Use them if you have those files in non-standard paths or when you know what you are doing.

To better understand these options, take a look at the [[#Common options|common options]] chapter in this article.

{| border=1
|+ [http://www.gzip.org/zlib zLib]
| ''--with-zlib=PREFIX'' || Look for [http://www.gzip.org/zlib zLib] files in '''PREFIX'''
|}

{| border=1
|+ [http://curl.haxx.se Curl]
| ''--with-curl-config=CONFIG'' || '''CONFIG''' is the path of ''curl-config''
|}

{| border=1
|+ [http://www.boutell.com/gd LibGD]
| ''--with-gdlib-prefix=PREFIX'' || Look for [http://www.boutell.com/gd LibGD] files in '''PREFIX'''
|-
| ''--with-gdlib-exec-prefix=PREFIX'' || Look for GDLib libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-gdlib-exec-prefix''
|-
| ''--with-gdlib-config=CONFIG'' || '''CONFIG''' is the path of ''gdlib-config''
|}

{| border=1
|+ [http://www.libpng.org LibPNG]
| ''--with-libpng-prefix=PREFIX'' || Look for [http://www.libpng.org LibPNG] files in '''PREFIX'''
|-
| ''--with-libpng-exec-prefix=PREFIX'' || Look for [http://www.libpng.org LibPNG] libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-libpng-exec-prefix''
|-
| ''--with-libpng-config=CONFIG'' || '''CONFIG''' is the path of ''libpng-config''
|}

{| border=1
|+ [[wxWidgets]]
| ''--with-wx-prefix=PREFIX'' || Look for [[wxWidgets]] files in '''PREFIX'''
|-
| ''--with-wx-exec-prefix=PREFIX'' || Look for [[wxWidgets]] libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-wx-exec-prefix''
|-
| ''--with-wx-config=CONFIG'' || '''CONFIG''' is the path of ''wx-config''
|}

{| border=1
|+ [[wxBase]]
| ''--with-wxbase-prefix=PREFIX'' || Look for [[wxBase]] files in '''PREFIX'''
|-
| ''--with-wxbase-exec-prefix=PREFIX'' || Look for [[wxBase]] libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-wxbase-exec-prefix''

|-
| ''--with-wxbase-config=CONFIG'' || '''CONFIG''' is the path of ''wxbase-config''
|}

{| border=1
|+ [http://www.gtk.org GTK]
| ''--with-gtk-prefix=PREFIX'' || Look for [http://www.gtk.org GTK] (not [http://www.gtk.org GTK]2) files in '''PREFIX'''
|-
| ''--with-gtk-exec-prefix=PREFIX'' || Look for [http://www.gtk.org GTK] (not [http://www.gtk.org GTK]2) libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-gtk-exec-prefix''
|}

{| border=1
|+ [http://www.openssl.org/docs/crypto/crypto.html Crypto++]
| ''--with-crypto-prefix=PREFIX'' || Look for [http://www.openssl.org/docs/crypto/crypto.html Crypto++] files in '''PREFIX'''
|}

{| border=1
|+ [http://www.gnu.org/software/libiconv LibIConv]
| ''--with-libiconv-prefix=PREFIX'' || Look for [http://www.gnu.org/software/libiconv LibIConv] files in '''''PREFIX'''/include'' and '''''PREFIX'''/lib''
|-
| ''--without-libiconv-prefix'' || Don't search for [http://www.gnu.org/software/libiconv LibIConv] in includedir and libdir
|}

{| border=1
|+ [http://www.gnu.org/software/gettext gettext]
| ''--with-included-gettext'' || Use the [http://www.gnu.org/software/gettext GNU gettext] library included in the ''intl/'' directory instead of the system's. This is only for strange systems where [http://www.gnu.org/software/gettext gettext], for some reason, will not handle [[aMule]]'s catalog files
|}

{| border=1
|+ [http://gnuwin32.sourceforge.net/packages/libintl.htm LibIntl]
| ''--with-libintl-prefix=PREFIX'' || Look for [http://gnuwin32.sourceforge.net/packages/libintl.htm LibIntl] files in '''''PREFIX'''/include''' and '''''PREFIX'''/lib''''
|-
| ''--without-libintl-prefix'' || Don't search for [http://gnuwin32.sourceforge.net/packages/libintl.htm LibIntl] in includedir and libdir
|}

{| border=1
|+ [http://ccache.samba.org ccache]
| ''--with-ccache-prefix=PREFIX'' || Look for [http://ccache.samba.org ccache] files in '''PREFIX'''
|}

== Variables ==

Before you take a look at the [[#Variables and what they mean|variables and what they mean]], you must take a look at the two variable [[#Usage types|usage types]] available.

=== Usage types ===

You can either use [[#Environment variables|environment variables]] or you can [[#Configure variables|enter variables directly into the ''configure'' command]].

==== Environment variables ====

If you plan to use environment variables, you will affect the behaviour of ''configure'' and any other program you run in that same shell until you end your session. You must set them '''before''' running configure. To set them, run

export ''VAR=VALUE'''

where ''VAR'' is the name of the environmental variable and ''VALUE'' is it's value.

==== Configure variables ====

If you don't want to use environment variables, you can pass them into the ''configure'' command, this way:

configure VAR=VALUE

where ''VAR'' stands for the variable name and ''VALUE'' is its value.

=== Variables and what they mean ===

Do '''NOT''' touch these variables if you don't know what you are doing!

This are some of the most commonly used variables for ''configure'':

{| border=1
|+ Variables
| ''CC'' || [http://en.wikipedia.org/wiki/C_programming_language C] compiler command to use
|-
| ''CXX'' || [http://en.wikipedia.org/wiki/C_Plus_Plus C++] compiler command to use (e.g. ''[http://gcc.gnu.org g++]'')
|-
| ''CPP'' || [http://en.wikipedia.org/wiki/C_programming_language C] preprocessor command to use
|-
| ''CFLAGS'' || [http://en.wikipedia.org/wiki/C_programming_language C] compiler flags
|-
| ''CXXCPP'' || [http://en.wikipedia.org/wiki/C_Plus_Plus C++] preprocessor command to use
|-
| ''CXXFLAGS'' || [http://en.wikipedia.org/wiki/C_Plus_Plus C++] compiler flags
|-
| ''LDFLAGS'' || Linker flags. Usually used to specify additional library directories (e.g. ''LDFLAGS="-L/usr/lib"'')
|-
| ''CPPFLAGS'' || [http://en.wikipedia.org/wiki/C_programming_language C]/[http://en.wikipedia.org/wiki/C_Plus_Plus C++] preprocessor flags (e.g. ''CPPFLAGS="-I/usr/include"'')
|}

== More information ==

This article is mainly an explanation (dummy-proof) of the output of ''configure --help''.

Anyway, it could (rarely) be out of date. So, if there's something you want to do with ''configure'' that is not listed here, run ''configure --help'' and see if it is listed there.

Of course, you can always take a look at the [http://www.airs.com/ian/configure GNU configure page].
|
|}

HowTo compile on Win32 with MinGW

2005-08-29T09:55:21Z

83.42.86.182:

<center><h2>Originally by '''[[User:Madcat|Madcat]]'''</h2></center>

<center>
'''English''' | [[HowTo compile on Win32-de|Deutsch]]
</center>

This wiki page only covers the latest [[aMule_CVS|CVS]] version of [[aMule]], not releases in the 1.x.x or 2.x.x branches.

''For those of you that don't want to compile [[aMule]] from source, there is also the option of the [[Win32_binary|aMule Windows Installer]].''

== Requirements for compiling [[aMule]] ==

You will need the following packages:

*[http://www.microsoft.com/windows Windows] port of [http://gcc.gnu.org GNU C compiler], [http://www.mingw.org MinGW] -> [http://prdownloads.sourceforge.net/mingw/MinGW-4.1.1.exe?download Download (4.1.1)]
*Minimal [http://www.gnu.org GNU] shell for [http://www.microsoft.com/windows Windows], [http://www.mingw.org/msys.shtml MSys] -> [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download Download (1.0.10)]
*Developer toolkit for [http://www.mingw.org/msys.shtml MSys] (for [http://www.gnu.org/software/cvs CVS] & co) -> [http://prdownloads.sf.net/mingw/msysDTK-1.0.1.exe?download Download (1.0.1)]
*[http://www.gnu.org/software/libiconv LibIConv] (required by [http://www.gnu.org/software/gettext gettext]) -> [http://prdownloads.sf.net/mingw/libiconv-1.8.0-2003.02.01-1.exe?download Download (1.8)]
*[http://www.gnu.org/software/gettext GetText] (for [http://www.gnu.org/software/gettext po files], [http://www.gnu.org/software/automake/automake.html autogen.sh], etc) -> [http://prdownloads.sf.net/mingw/gettext-0.11.5-2003.02.01-1.exe?download Download (0.11.5)]
*[http://www.zlib.org zlib] compression library -> [http://www.zlib.net/zlib-1.2.3.tar.gz Download (1.2.3)]
*[http://www.microsoft.com/windows Windows] port of [[wxWidgets]] library (knows as [[wxWidgets|wxMSW]]) -> [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.1.zip Download (2.6.1)]
*[[aMule]]'s latest release sources or [[aMule CVS]] -> [http://dl.amule.org Download aMule]

Also, 800MB-1500MB free space on your hard disk (around 40MB to download the above packages and the rest for temporary compilation files and installations. The amount of space needed will largely depend on the configuration flags you use).

As a reference, the whole compilation process will take around 3 hours on a medium-high resourced computer.

== Installing the Minimal System ==

The first step is to create a [http://www.kernel.org Linux]-like environment, which is required in order to be able to perform the build. This can be done by following these steps '''in this order''':

#Install [http://www.mingw.org MinGW]. Select ''Compact installation'' unless you know what you are doing. When it prompts you for a folder, the default (''C:\mingw'') is slightly messy but the safer selection.
#Install [http://www.mingw.org/msys.shtml MSys]. When it prompts you for the [http://www.mingw.org MinGW] folder, it's very important to specify it correctly. Failure on this step will stop any compilation attempts. If for some reason you fail, install [http://www.mingw.org/msys.shtml MSys] again, or edit the file ''/etc/fstab'' in your [http://www.mingw.org/msys.shtml MSys] environment.
#Install the [http://www.mingw.org/msys.shtml MSys] developer toolkit.
#Install [http://www.gnu.org/software/libiconv LibIConv].
#Install [http://www.gnu.org/software/gettext GetText].

== Compiling the libraries ==

There are two libraries that [[aMule]] will need compiled: [http://www.zlib.org zlib] and [[wxWidgets]].

We will compile them from [http://www.mingw.org/msys.shtml MSys], so just run it. Once you are running [http://www.mingw.org/msys.shtml MSys], you'll be on your home folder. Copy the [http://www.zlib.org zlib] and [[wxWidgets]] files you downloaded above into this folder (something like ''C:\msys\1.0\home\'''user''''').

The steps for compiling them is:

#[http://www.zlib.org zlib]: Uncompress [http://www.zlib.org zlib], cd to the newly created directory and run ''./configure --prefix=/mingw && make && make install''
#[[wxWidgets]]: Uncompress [[wxWidgets]], cd to the newly created directory and run ''./configure --disable-shared --without-checklistbox && make && make install''

If you want to help us developers, you can add ''--enable-debug'' flag to the [[wxWidgets]] configure command, right after ''--disable-shared'', but be warned it will result into an ''aMule.exe'' file bigger than 100MB.

== Compilation ==

Ok, we're all done with the compilation environment. Let's do the last step: compiling [[aMule]].

First of all, extract [[aMule]]'s sources and enter the newly created folder.

The compilation itself is actually just a matter of following the usual method: ''./configure && make''. Use your favorite flags on ''./configure'', for example, ''--disable-debug'' will remove debug info, but will also make it harder for us developers to understand the bugs you might find.

You might want to compile just the remote GUI: the flags would be ''--disable-monolithic --disable-ed2k --enable-amule-gui''

'''Beware:''' The following programs do not work yet on [http://www.microsoft.com/windows Windows]:
*[[aMuled|aMule Daemon]]: Doesn't even compile.
*[[aMuleGUI]]: Fails to communicate with [[aMule]].
*[[aMuleCMD|aMuleCMDDLG]]: Fails to communicate with [[aMule]]. The command-line version, [[aMuleCMD]], still works though.
*[[aMuleWeb|aMuleWebDLG]]: Fails to communicate with [[aMule]]. The command-line version, [[aMuleWeb]], still works though.
*[[ed2k_command|ed2k]]: Fails to send the [[ed2k link]]s to [[aMule]].
*[[CAS]]: Fails to find the [[signature]] file.

'''Note:''' To keep the size of the binnaries down, you can run ''strip'' from within [http://www.mingw.org/msys.shtml MSys].

== Running ==

To run the binnaries we've created you need ''mingwm10.dll''. This file can be found in ''C:\MinGW\bin\mingwm10.dll'' (or whatever path you used to install [http://www.mingw.org MinGW].

You now have to place this file in some place so that the binnaries find it when they are executed. Here you have two options:

#Place it in the same folder where the binnaries are (if you have them spread in several different folders, copy this file once into each folder. Since it is a very small file, it is not much of a loss).
#Place it in ''C:\windows'' or some other any other path where [http://www.microsoft.com/windows Windows] might look for libraries (such as ''C:\Windows\System'' or ''C:\Windows\System32'').

Now... just run your binnaries and have fun with [[aMule]] on your [http://www.microsoft.com/windows Windows] box!

'''Note:''' By default, the binnaries are compiled to ''C:\MSys\1.0\home\'''user'''\amule-2.0.3\src\''.

== Having different languages ==

Now [[aMule]] will be successfully running, but you will not be able to use any other language but default english.

TO be able to choose between any of the lot of languages [[aMule]] is shipped with, from [http://www.mingw.org/msys.shtml MSys] go to [[aMule]]'s extracted folder and then into ''po/'' folder. Something like the following should do it:

cd
cd amule-2.0.3/po

Now install the languages:

make install-data-yes

This language files are now in ''C:\MSys\1.0\local\share\locale'', so exit [http://www.mingw.org/msys.shtml MSys], go to ''C:\msys\1.0\local\share\locale'' and copy that folder to the folder were you are keeping your compiled ''amule.exe'' and ''amulegui.exe'' files.

HowTo compile on Win32 with MinGW

2005-08-29T09:54:27Z

83.42.86.182:

<center><h2>Originally by '''[[User:Madcat|Madcat]]'''</h2></center>

<center>
'''English''' | [[HowTo compile on Win32-de|Deutsch]]
</center>

This wiki page only covers the latest [[aMule_CVS|CVS]] version of [[aMule]], not releases in the 1.x.x or 2.x.x branches.

''For those of you that don't want to compile [[aMule]] from source, there is also the option of the [[Win32_binary|aMule Windows Installer]].''

== Requirements for compiling [[aMule]] ==

You will need the following packages:

*[http://www.microsoft.com/windows Windows] port of [http://gcc.gnu.org GNU C compiler], [http://www.mingw.org MinGW] -> [http://prdownloads.sourceforge.net/mingw/MinGW-4.1.1.exe?download Download (4.1.1)]
*Minimal [http://www.gnu.org GNU] shell for [http://www.microsoft.com/windows Windows], [http://www.mingw.org/msys.shtml MSys] -> [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download Download (1.0.10)]
*Developer toolkit for [http://www.mingw.org/msys.shtml MSys] (for [http://www.gnu.org/software/cvs CVS] & co) -> [http://prdownloads.sf.net/mingw/msysDTK-1.0.1.exe?download Download (1.0.1)]
*[http://www.gnu.org/software/libiconv LibIConv] (required by [http://www.gnu.org/software/gettext gettext]) -> [http://prdownloads.sf.net/mingw/libiconv-1.8.0-2003.02.01-1.exe?download Download (1.8)]
*[http://www.gnu.org/software/gettext GetText] (for [http://www.gnu.org/software/gettext po files], [http://www.gnu.org/software/automake/automake.html autogen.sh], etc) -> [http://prdownloads.sf.net/mingw/gettext-0.11.5-2003.02.01-1.exe?download Download (0.11.5)]
*[http://www.zlib.org zlib] compression library -> [http://www.zlib.net/zlib-1.2.3.tar.gz Download (1.2.3)]
*[http://www.microsoft.com/windows Windows] port of [[wxWidgets]] library (knows as [[wxWidgets|wxMSW]]) -> [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.1.zip Download (2.6.1)]
*[[aMule]]'s latest release sources or [[aMule CVS]] -> [http://dl.amule.org Download aMule]

Also, 800MB-1500MB free space on your hard disk (around 40MB to download the above packages and the rest for temporary compilation files and installations. The amount of space needed will largely depend on the configuration flags you use).

As a reference, the whole compilation process will take around 3 hours on a medium-high resourced computer.

== Installing the Minimal System ==

The first step is to create a [http://www.kernel.org Linux]-like environment, which is required in order to be able to perform the build. This can be done by following these steps '''in this order''':

#Install [http://www.mingw.org MinGW]. Select ''Compact installation'' unless you know what you are doing. When it prompts you for a folder, the default (''C:\mingw'') is slightly messy but the safer selection.
#Install [http://www.mingw.org/msys.shtml MSys]. When it prompts you for the [http://www.mingw.org MinGW] folder, it's very important to specify it correctly. Failure on this step will stop any compilation attempts. If for some reason you fail, install [http://www.mingw.org/msys.shtml MSys] again, or edit the file ''/etc/fstab'' in your [http://www.mingw.org/msys.shtml MSys] environment.
#Install the [http://www.mingw.org/msys.shtml MSys] developer toolkit.
#Install [http://www.gnu.org/software/libiconv LibIConv].
#Install [http://www.gnu.org/software/gettext GetText].

== Compiling the libraries ==

There are two libraries that [[aMule]] will need compiled: [http://www.zlib.org zlib] and [[wxWidgets]].

We will compile them from [http://www.mingw.org/msys.shtml MSys], so just run it. Once you are running [http://www.mingw.org/msys.shtml MSys], you'll be on your home folder. Copy the [http://www.zlib.org zlib] and [[wxWidgets]] files you downloaded above into this folder (something like ''C:\msys\1.0\home\'''user''''').

The steps for compiling them is:

#[http://www.zlib.org zlib]: Uncompress [http://www.zlib.org zlib], cd to the newly created directory and run ''./configure --prefix=/mingw && make && make install''
#[[wxWidgets]]: Uncompress [[wxWidgets]], cd to the newly created directory and run ''./configure --disable-shared --without-checklistbox && make && make install''

If you want to help us developers, you can add ''--enable-debug'' flag to the [[wxWidgets]] configure command, right after ''--disable-shared'', but be warned it will result into an ''aMule.exe'' file bigger than 100MB.

== Compilation ==

Ok, we're all done with the compilation environment. Let's do the last step: compiling [[aMule]].

First of all, extract [[aMule]]'s sources and enter the newly created folder.

The compilation itself is actually just a matter of following the usual method: ''./configure && make''. Use your favorite flags on ''./configure'', for example, ''--disable-debug'' will remove debug info, but will also make it harder for us developers to understand the bugs you might find.

You might want to compile just the remote GUI: the flags would be ''--disable-monolithic --disable-ed2k --enable-amule-gui''

'''Beware:''' The following programs do not work yet on [http://www.microsoft.com/windows Windows]:
*[[aMuled|aMule Daemon]]: Doesn't even compile.
*[[aMuleGUI]]: Fails to communicate with [[aMule]].
*[[aMuleCMD|aMuleCMDDLG]]: Fails to communicate with [[aMule]].
*[[aMuleWeb|aMuleWebDLG]]: Fails to communicate with [[aMule]].
*[[ed2k_command|ed2k]]: Fails to send the [[ed2k link]]s to [[aMule]].
*[[CAS]]: Fails to find the [[signature]] file.

'''Note:''' To keep the size of the binnaries down, you can run ''strip'' from within [http://www.mingw.org/msys.shtml MSys].

== Running ==

To run the binnaries we've created you need ''mingwm10.dll''. This file can be found in ''C:\MinGW\bin\mingwm10.dll'' (or whatever path you used to install [http://www.mingw.org MinGW].

You now have to place this file in some place so that the binnaries find it when they are executed. Here you have two options:

#Place it in the same folder where the binnaries are (if you have them spread in several different folders, copy this file once into each folder. Since it is a very small file, it is not much of a loss).
#Place it in ''C:\windows'' or some other any other path where [http://www.microsoft.com/windows Windows] might look for libraries (such as ''C:\Windows\System'' or ''C:\Windows\System32'').

Now... just run your binnaries and have fun with [[aMule]] on your [http://www.microsoft.com/windows Windows] box!

'''Note:''' By default, the binnaries are compiled to ''C:\MSys\1.0\home\'''user'''\amule-2.0.3\src\''.

== Having different languages ==

Now [[aMule]] will be successfully running, but you will not be able to use any other language but default english.

TO be able to choose between any of the lot of languages [[aMule]] is shipped with, from [http://www.mingw.org/msys.shtml MSys] go to [[aMule]]'s extracted folder and then into ''po/'' folder. Something like the following should do it:

cd
cd amule-2.0.3/po

Now install the languages:

make install-data-yes

This language files are now in ''C:\MSys\1.0\local\share\locale'', so exit [http://www.mingw.org/msys.shtml MSys], go to ''C:\msys\1.0\local\share\locale'' and copy that folder to the folder were you are keeping your compiled ''amule.exe'' and ''amulegui.exe'' files.

Webserver

2005-08-29T09:46:05Z

83.42.86.182:

== Setting up [[aMuleWeb|Webserver]] with [[aMule]] ==

=== [[Webserver-1.2.x|Webserver with aMule 1.2.8 or earlier]] ===

=== Webserver with [[aMule]] 2.0.0-rcX versions ===

*[http://www.gnu.org/software/tar/tar.html Untar] the sources and copy '''''src/aMule.tmpl''''' or in new versions (you are using a ''new version'' if you don't have the file ''aMule.tmpl'' in ''src/'') only the following dir '''''src/webserver/''''' into your '''''~/.aMule/''''' directory. The following (run from the sources directory), should do so:
:''$ cp -r src/aMule.tmpl src/webserver/ ~/.aMule/''

* If you installed [[aMule]] from rpm, then you can do:
:''$ cp /usr/share/amuleweb/aMule.tmpl ~/.aMule/''
:''$ cp -r /usr/share/amuleweb/webserver/ ~/.aMule/''
:'''NOTE''': Note that in current versions (since [[aMule]] 2.0.0) the above step is not necessary (in fact, it is incorrect).

*Go to "Preferences"->"Remote Controls" (in [[aMule]]) and...
**Enable "Accept External Connections".
**Enable "Use TCP ports instead of unix local sockets".
**Enter a password for external connections. If you don't do this, amuleweb will not communicate with amule.

::'''NOTE:''' On some early [[aMule]] 2.0.0-rcX versions the above options weren't available (or didn't work). Use this if you want to run [[aMuled]], too. If you are using such [[aMule]] version and you don't wish to upgrade, then do the following:

:Shutdown [[aMule]] if it is still running.
:Edit your ''~/.eMule'' file, locate the ''[ExternalConnect]'' section and change:
::''AcceptExternalConnections=1'' <-- To enable [[aMule]] listening for [[External Connections]].
::''ECUseTCPPort=1'' <-- To use the [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] port. Very important since [http://www.unix.org Unix] sockets are disabled.
::''ECPassword=ca3c365274907c6fd527068788e14639'' <-- To find the MD5 string for your password, do:
:::''$ echo -n yourpasswordhere | md5sum | cut -d ' ' -f 1''
:::''ca3c365274907c6fd527068788e14639''

::'''NOTE:''' Since [[aMule]] 2.0.0 the ''~/.eMule'' file is now called ''~/.aMule/amule.conf''.

*Restart [[aMule]]

*Go to your "Preferences"->"Remote Controls" (in [[aMule]]) and setup your passwords here for [[External Connections]] and [[aMuleWeb|webserver]] login.
::'''NOTE:''' When you change your [[aMuleWeb|webserver]] and [[External Connections]] ports here, make sure to restart [[aMule]].
::'''NOTE:''' that ''"Enable [[aMuleWeb|Webserver]]"'' has no effect and will be renamed in 2.0.0rc8. [[aMuleWeb|Webserver]] is always enabled as long as you have [[External Connections]] enabled.
::'''NOTE:''' For users running [[aMuled|aMule Daemon]] you have to edit the ''.eMule'' file like shown above. For a way to setup a password check the [[Webserver-1.2.x|1.2.8 aMule HowTo]]. You can still do it in the same way.

*Now you're done! You are ready to run [[aMuleWeb|amuleweb]] and connect to it.

'''[[User:Stefanero|Stefanero]]'''

=== Webserver with [[aMule]] 2.0.0 or later ===

*For users running the monotlithic [[aMule]] application:
**Go to "Preferences"->"Remote Controls" (in [[aMule]]) and...
***Enable "Accept External Connections".
***Enable "Use TCP ports instead of unix local sockets" (This option doesn't exist since version 2.1.0)
***Enter a password for [[External Connections]]. If you don't do this, [[aMuleWeb]] will not communicate with [[aMule]].
::'''NOTE:''' When you change your [[aMuleWeb|webserver]] and [[External Connections]] ports here, make sure to restart [[aMule]].

*For users running the [[aMule|aMule daemon]]:
**Shutdown [[aMule|aMuled]] if it is still running.
**Edit your ''~/.aMule/amule.conf'' file, and locate or create the following lines:
***''[ExternalConnect]'' <- Section header
***''AcceptExternalConnections=1'' <-- To enable [[aMule]] listening for [[External Connections]].
***''ECUseTCPPort=1'' <-- To use the [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] port. Very important since [http://www.unix.org Unix] sockets are disabled.
***''ECPassword=ca3c365274907c6fd527068788e14639'' <-- To find the MD5 string for your password, do:
:::''$ echo -n yourpasswordhere | md5sum | cut -d ' ' -f 1''
:::''ca3c365274907c6fd527068788e14639''
**Restart [[aMule|aMuled]]

'''NOTE:''' In [[aMule]] version 2.0.0 and later you don't need to do any copy/link of [[aMuleWeb|webserver]] files.

Thanks to [[User:Stefanero|Stefanero]], from who I shamelessly stole a lot from his tutorial.

==== Skin support ====

[[aMuleWeb|Webserver]] now looks for its files in a number of places:
*In your home directory: ''$HOME/.aMule/webserver/''[skin name]''/''
*And at it's install location, in this order (by default, ''/usr/local/share/amule/webserver'' if you compiled [[aMule]], or ''/usr/share/amule/webserver'' if you installed it from a package).

Default skin (template) name is 'default'.

If, '''after installing''' [[aMule]], [[aMuleWeb|webserver]] refuses to run because of not being able to load template:
*Please report this situation to us, and then
*Create the directories ''webserver/default'' in the ''.aMule'' subdirectory of your home directory, and copy the contents of the ''src/webserver'' directory there from the [[aMule]] tarball (I mean to ''$HOME/.aMule/webserver/default''). [New record, four 'directory' word in one sentence :)]

'''[[User:GonoszTopi|GonoszTopi]]'''

== Connecting to [[aMuleWeb|amuleweb]] ==

To run [[aMuleWeb]] run '''''amuleweb''''' on a terminal. For more information about running [[aMuleWeb]] check the [[aMuleWeb|aMuleWeb document]].

Once [[aMuleWeb]] is running, open a web browser and connect to:

''http://host:port''

where ''host'' stands for your host's name (try with ''localhost'') and port stands for the [[aMuleWeb]] port ('''NOT''' the [[External Connections]] port).

For example: ''http://localhost:4711''

== Standard ports ==

The ports can be set to anything, but this are the most used (the standard ones):

*[[External Connections]]: 4712
*[[aMuleWeb|amuleweb]]: 4711

Make sure you do not confuse with what each of them is.

== Where to report problems and questions? ==

For Problems or Questions just report on http://forum.amule.org forum or join [[IRC]] channel [irc://irc.freenode.net/amule #amule] at [irc://irc.freenode.net irc.freenode.net]

== Other sources of information ==

Read the [[aMuleWeb]] man page, which is available in English, French, German, Hungarian and Spanish.

HowTo compile on Win32 with MinGW

2005-08-29T08:33:41Z

83.42.86.182:

<center><h2>Originally by '''[[User:Madcat|Madcat]]'''</h2></center>

<center>
'''English''' | [[HowTo compile on Win32-de|Deutsch]]
</center>

This wiki page only covers the latest [[aMule_CVS|CVS]] version of [[aMule]], not releases in the 1.x.x or 2.x.x branches.

''For those of you that don't want to compile [[aMule]] from source, there is also the option of the [[Win32_binary|aMule Windows Installer]].''

== Requirements for compiling [[aMule]] ==

You will need the following packages:

*[http://www.microsoft.com/windows Windows] port of [http://gcc.gnu.org GNU C compiler], [http://www.mingw.org MinGW] -> [http://prdownloads.sourceforge.net/mingw/MinGW-4.1.1.exe?download Download (4.1.1)]
*Minimal [http://www.gnu.org GNU] shell for [http://www.microsoft.com/windows Windows], [http://www.mingw.org/msys.shtml MSys] -> [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download Download (1.0.10)]
*Developer toolkit for [http://www.mingw.org/msys.shtml MSys] (for [http://www.gnu.org/software/cvs CVS] & co) -> [http://prdownloads.sf.net/mingw/msysDTK-1.0.1.exe?download Download (1.0.1)]
*[http://www.gnu.org/software/libiconv LibIConv] (required by [http://www.gnu.org/software/gettext gettext]) -> [http://prdownloads.sf.net/mingw/libiconv-1.8.0-2003.02.01-1.exe?download Download (1.8)]
*[http://www.gnu.org/software/gettext GetText] (for [http://www.gnu.org/software/gettext po files], [http://www.gnu.org/software/automake/automake.html autogen.sh], etc) -> [http://prdownloads.sf.net/mingw/gettext-0.11.5-2003.02.01-1.exe?download Download (0.11.5)]
*[http://www.zlib.org zlib] compression library -> [http://www.zlib.net/zlib-1.2.3.tar.gz Download (1.2.3)]
*[http://www.microsoft.com/windows Windows] port of [[wxWidgets]] library (knows as [[wxWidgets|wxMSW]]) -> [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.1.zip Download (2.6.1)]
*[[aMule]]'s latest release sources or [[aMule CVS]] -> [http://dl.amule.org Download aMule]

Also, 800MB-1500MB free space on your hard disk (around 40MB to download the above packages and the rest for temporary compilation files and installations. The amount of space needed will largely depend on the configuration flags you use).

As a reference, the whole compilation process will take around 3 hours on a medium-high resourced computer.

== Installing the Minimal System ==

The first step is to create a [http://www.kernel.org Linux]-like environment, which is required in order to be able to perform the build. This can be done by following these steps '''in this order''':

#Install [http://www.mingw.org MinGW]. Select ''Compact installation'' unless you know what you are doing. When it prompts you for a folder, the default (''C:\mingw'') is slightly messy but the safer selection.
#Install [http://www.mingw.org/msys.shtml MSys]. When it prompts you for the [http://www.mingw.org MinGW] folder, it's very important to specify it correctly. Failure on this step will stop any compilation attempts. If for some reason you fail, install [http://www.mingw.org/msys.shtml MSys] again, or edit the file ''/etc/fstab'' in your [http://www.mingw.org/msys.shtml MSys] environment.
#Install the [http://www.mingw.org/msys.shtml MSys] developer toolkit.
#Install [http://www.gnu.org/software/libiconv LibIConv].
#Install [http://www.gnu.org/software/gettext GetText].

== Compiling the libraries ==

There are two libraries that [[aMule]] will need compiled: [http://www.zlib.org zlib] and [[wxWidgets]].

We will compile them from [http://www.mingw.org/msys.shtml MSys], so just run it. Once you are running [http://www.mingw.org/msys.shtml MSys], you'll be on your home folder. Copy the [http://www.zlib.org zlib] and [[wxWidgets]] files you downloaded above into this folder (something like ''C:\msys\1.0\home\'''user''''').

The steps for compiling them is:

#[http://www.zlib.org zlib]: Uncompress [http://www.zlib.org zlib], cd to the newly created directory and run ''./configure --prefix=/mingw && make && make install''
#[[wxWidgets]]: Uncompress [[wxWidgets]], cd to the newly created directory and run ''./configure --disable-shared --without-checklistbox && make && make install''

If you want to help us developers, you can add ''--enable-debug'' flag to the [[wxWidgets]] configure command, right after ''--disable-shared'', but be warned it will result into an ''aMule.exe'' file bigger than 100MB.

== Compilation ==

Ok, we're all done with the compilation environment. Let's do the last step: compiling [[aMule]].

First of all, extract [[aMule]]'s sources and enter the newly created folder.

The compilation itself is actually just a matter of following the usual method: ''./configure && make''. Use your favorite flags on ''./configure'', for example, ''--disable-debug'' will remove debug info, but will also make it harder for us developers to understand the bugs you might find.

You might want to compile just the remote GUI: the flags would be ''--disable-monolithic --disable-ed2k --enable-amule-gui''

'''Beware:''' [[aMuled|aMule Daemon]] doesn't work on [http://www.microsoft.com/windows Windows] and might not even compile on some releases.

'''Note:''' To keep the size of the binnaries down, you can run ''strip'' from within [http://www.mingw.org/msys.shtml MSys].

== Running ==

To run the binnaries we've created you need ''mingwm10.dll''. This file can be found in ''C:\MinGW\bin\mingwm10.dll'' (or whatever path you used to install [http://www.mingw.org MinGW].

You now have to place this file in some place so that the binnaries find it when they are executed. Here you have two options:

#Place it in the same folder where the binnaries are (if you have them spread in several different folders, copy this file once into each folder. Since it is a very small file, it is not much of a loss).
#Place it in ''C:\windows'' or some other any other path where [http://www.microsoft.com/windows Windows] might look for libraries (such as ''C:\Windows\System'' or ''C:\Windows\System32'').

Now... just run your binnaries and have fun with [[aMule]] on your [http://www.microsoft.com/windows Windows] box!

'''Note:''' By default, the binnaries are compiled to ''C:\MSys\1.0\home\'''user'''\amule-2.0.3\src\''.

== Having different languages ==

Now [[aMule]] will be successfully running, but you will not be able to use any other language but default english.

TO be able to choose between any of the lot of languages [[aMule]] is shipped with, from [http://www.mingw.org/msys.shtml MSys] go to [[aMule]]'s extracted folder and then into ''po/'' folder. Something like the following should do it:

cd
cd amule-2.0.3/po

Now install the languages:

make install-data-yes

This language files are now in ''C:\MSys\1.0\local\share\locale'', so exit [http://www.mingw.org/msys.shtml MSys], go to ''C:\msys\1.0\local\share\locale'' and copy that folder to the folder were you are keeping your compiled ''amule.exe'' and ''amulegui.exe'' files.

User:GonoszTopi

2005-08-29T07:51:43Z

83.42.86.182:

'''[[aMule]] [[AMule_devs|dev]] ;)'''

Main [[aMule]] concerns:
*[[ECv2]] development.
*[[Bug]] fixing.
*In fact, just about any development.

IRC rules

2005-08-29T07:23:12Z

83.42.86.182:

== Introduction ==

While you stay at our [[IRC]] channels, you '''must''' follow some rules.

Most of them are basic ethic rules which, for some reason, some people fail to understand. Others are not so intuitive. There for, everybody '''must''' read this article '''before''' entering our IRC channel.

Just keep reading.

== What you must do ==

*You must read topic (''/topic #<channel>'') '''before''' saying anything.
*You must read this article from the beginning to the end '''before entering''' the channel. Did I say "read"? I meant "'''understand'''"!
*You must go to #macMule if you want to talk/ask about [[aMule]] on [http://macosx.apple.com MacOS X].
*You must go to #aMule if you want to talk/ask about [[aMule]] on any platform but on [http://macosx.apple.com MacOS X].
*You must speak english in our channels. They are english speaking channels.
*You must look for an answer in [http://forum.amule.org aMule's Forums] and in [[Main Page|this wiki]] before asking anything.
*You must read twice and, before talking, make sure you understand what other people write.
*You must read twice what you write before sending your message.
*You must stay in the channel for at least 30 minutes if you ask something. We hate people who just want their questoins to be answered right after they ask, in 0-time.
*If you want to talk specifically to someone, open a query (''/query <nick>''). Do not flood the channel with your private conversation unless you believe the conversation may make the knowledge of the rest of the people in the channel richer.

== What you must not do ==

*You must not violate any of your contry's laws nor any of the [http://europa.eu.int European Community] laws nor any of the [http://www.firstgov.gov USA] laws nor any of the international laws while staying at any of our channels. Sounds funny? Well, it's not.
*You must not talk about anything that doesn't regard '''directly''' (in the most strict way) to [[aMule]] as an application. Exceptionally, you may ask questions about the [[FAQ_ed2k|ed2k]] and [[Kademlia]] protocols, but an answer is not guaranteed.
*You must not talk, directly or indirectly, about any copyrighted non-free (in the ''beer way'') material.
*You must not talk about any website which breaks any of our channels rules.
*You must not provide any URL which's contents break any of our channels rules.
*You must not provide '''any''' [[ed2k link]].
*You must not do any kind of publicity about anything unless some channel operator allows you to do so.
*Do not flood. Not even a little. More than tree lines in a row will be enough to be considered flooding.
*Don't ask to ask. Just ask!
*You must not ask anything if you haven't at least tried a little to find out the answer on your own. Did I seay "try a little"? I mean "try as hard as you can".
*You must not ask repeatedly for a question. Wait at least an hour before asking again, even if you get answer. Asking the same question using different words won't make the trick either.
*You must not use any ''away message''.
*You must not use any bots in the channels unless some channel operator allows you to do so.
*Do not split whatever you want to say into several different short lines. This is not Instant Messaging. This is IRC. Get used to it.
*You must not use abreviated words or non-standard language.
*You must not type with capital letters nor user more than two exclamation marks in a single line (scream).
*You must not insult, flame, blame, begin a war, fight, etc.
*You may not enter and leave the channel as if you were hiding from someone. Decide whether you want to enter or leave the channel and then do so. Not the other way round.

== What you can do ==

You can do anything you wish as long as it is not forbidden in any rule in this article. Anyway, we'd like to make emphasys in some things which you can do in our channels which are sometimes forbidden in many other channels around:

*You can talk to the [[aMule Team]]. They are the official channels, so the Team is hearing. Just wait some time till they read. And make no doubt they will read you.
*You can stay idle as long as you wish.
*You can answer questions to other people even if they weren't asking you, as long as you know what you are talking about and as long as what you answer is what you really believe to be true/right.

== Suggestions ==

*Try to always ask&answer in an objective way.
*If you ask a question, wait for a few hours for an answer. Most of the time people are idle (not in front of the computer), so it may take long till someone reads your question. Just don't leave that fast.
*If you get an answer don't become sceptic about what you are told. Otherwise just don't ask.
*Use the latest stable [[aMule]] release.
*Distro specific questions, even if regarding [[aMule]], should go the distro's channel or forums. Most surely we won't know the answer.
*Now here is '''The BIG Suggestion (c)''': Think, then act.

== What if a rule is not clear? ==

This rules are made by the channels operators.

The only people who know exactly what they mean are them. You must try to understand what operators think the rules mean. And in case of doubt, just stay silent or ask what is meant.

Channel operators may charge on you if they consider you have broken some rule in the interpretation they, as channel operators, make of the rule. And the interpretation may vary depending on the mood, the phase of the moon, the colour of the clouds or the price of gas and pizza.

== Consequences ==

Anyone who doesn't follow one or more of the above rules will be kicked from the channel.

Anyone repeatedly breaking this rules will have to face a ban. There is no rule for ban periods: it depends on our mood in which we are :->

If someone severely breaks some rule, even if it isn't repeatedly, it could also be punished with a ban.

IPFilter

2005-08-29T06:09:52Z

83.42.86.182:

== Description ==

The [[IP]] Filter blocks traffic from/to IPs and ranges of [[IP]]s with our [[client]]. This means that those [[IP]]s which get blocked will not be able neither to upload to us nor to download from us.

This filter is read from [[ipfilter.dat_file|''~/.aMule/ipfilter.dat'']] which is a file which's contents describes the valid and blocked [[IP]] ranges.

== [[ipfilter.dat file]] ==

The information and details about the [[ipfilter.dat file]] can be found [[ipfilter.dat file|here]].

== Using the [[IP]] Filter in [[aMule]] ==

The ''Access level'' of the [[IP]] filter is selected in [[aMule]] through "Preferences" -> "Security" -> "IP Filtering" -> "Filtering level" (in [[aMule]] versions up to 2.0.0-rc8 it is under "Server", instead of "Security").

'''NOTE:''' [[aMule]]'s ''ipfilter.dat'' file is 100% compatible with [[eMule]]'s ([[eMule]]'s [http://www.methlabs.org/methlabs.htm PeerGuardian] format, which is the most popular. The ''antip2p.txt'' format isn't yet supported).

== [[IP]] Filter sources ==

http://emulepawcio.sourceforge.net/nieuwe_site/Ipfilter_fakes/ipfilter.dat (Last update: 28 August 2005)

http://www.openmedia.info/p27.html (Last update: 30 April 2005)

http://www.emulext.net/seguridad/Mc4TuTi/ipfilter.dat (Last update: February 2005)

http://www.autistici.org/smokingmath/ipfilter.dat (Only filters [[fake]] [[server]]s. Last update: 8 August 2005)
== Hard coded [[IP]] filter in [[aMule]] ==

[[aMule]] has a range of [[IP]]s which it filters by default following the [http://www.rfc-editor.org/rfc/rfc3330.txt RFC 3330] document. This ranges are:

<pre>
Address Block Present Use Reference
----------------------------------------------------------------------
"0.0.0.0/8", // "This" Network [RFC1700, page 4]
"10.0.0.0/8", // Private-Use Networks [RFC1918]
"14.0.0.0/8", // Public-Data Networks [RFC1700, page 181]
"24.0.0.0/8", // Cable Television Networks --
"39.0.0.0/8", // Reserved but subject
// to allocation [RFC1797]
"127.0.0.0/8", // Loopback [RFC1700, page 5]
"128.0.0.0/16", // Reserved but subject
// to allocation --
"169.254.0.0/16", // Link Local --
"172.16.0.0/12", // Private-Use Networks [RFC1918]
"191.255.0.0/16", // Reserved but subject
// to allocation --
"192.0.0.0/24", // Reserved but subject
// to allocation --
"192.0.2.0/24", // Test-Net
"192.88.99.0/24", // 6to4 Relay Anycast [RFC3068]
"192.168.0.0/16", // Private-Use Networks [RFC1918]
"198.18.0.0/15", // Network Interconnect
// Device Benchmark Testing [RFC2544]
"223.255.255.0/24",// Reserved but subject
// to allocation --
"224.0.0.0/4", // Multicast [RFC3171]
"240.0.0.0/4" // Reserved for Future Use [RFC1700, page 4]
</pre>

However, you can un-filter this range of [http://www.faqs.org/rfcs/rfc791.html IP]s by unchecking "Preferences"->"Security"->"IP-filtering"->"Always filter bad IPs" (on [[aMule]] versions up to 2.0.0-rc8, this option can be found in "Preferences"->"Server"->"Always filter bad IPs").

Auxiliary port

2005-08-29T05:59:19Z

83.42.86.182:

#REDIRECT [[How_to_use_auxiliary_server_ports]]

Server.met file

2005-08-29T05:59:01Z

83.42.86.182:

== File ==

'''Name:''' ''server.met''

'''Location:''' ''~/.aMule/''

== Description ==

Binary file containing the list of [[server]]s known to [[aMule]].

Because its in binary format, it must be changed within [[aMule]], or with other appropriate tools.

The format description below is for development information purposes.

== Format ==

=== File Format ===

This file's fields are written in [[little endian]] order.

'''Note:''' All digit fields are unsigned unless stated.

*Met Header (1 Byte): With value ''Ox0E'' or ''OxE0'', and is used in [[aMule]] to check for valid ''server.met'' files
*Server Count (4 Bytes): Lists the number of [[server]]s that follow
*Block of servers: Each [[server]] is constituted by the following fields:
**[[Server]] [[IP]] (4 Bytes): Simply that. The [[server]]'s [[IP]].
**[[Server]] [[Port]] (2 Bytes): Simply that. The [[port]] through which [[aMule]] will connect to the [[server]].
**Tag Count (4 Bytes): Lists the number of [[server]] tags that follows.
**Block of Tags: Each [[server]] can have a list of associated tags with the format bellow.

=== Tags Format ===

==== General tags format ====

There are two tag identifiers: A name (string) and an ID (1 Byte)

Which one is used depends on the tag value type given or on the size of the tag name. If tag name length is ''1'', an ID is used.

*Tag value type (1 Byte)
*Tag name length (2 Bytes)
*Tag name (size given above)
*Tag value length (2 Bytes) (Only when the value is a string)
*Tag value (if the value is a string, it's size is given in the above field. If it is not a string, the size depends on the type of value it is)

==== Tag value types ====

{|
|+ Tag types
| '''Tag type (''Code'')''' || '''Explanation'''
|-
| String (''0x02'') (*) || Defines a string tag.
|-
| Unsigned 32 bits number (''0x03'') || Defines a numeric tag.
|}

'''(*):''' Systems with [http://www.unicode.org Unicode] enabled have the same tag string defined twice, the first in [http://www.unicode.org Unicode], and the second in plain [http://www.asciitable.com ASCII], which will be ignored by [http://www.unicode.org Unicode] enabled [[client]]s, and used by non-[http://www.unicode.org Unicode] ones.

==== Tag IDs ====

{|
|+ Tag IDs
| ''ID ('''code''')'' || ''Tag value type'' || ''Description''
|-
| ServerName (''0x01'') || String || Name of the [[server]]
|-
| Description (''0x0B'') || String || Short description about the server
|-
| Ping (''0x0C'') || Unsigned 32 bits number || Time (in ms) it takes to comunicate with the server
|-
| Fail (''0x0D'') || Unsigned 32 bits number || How many times [[connect]]ing to the server failed
|-
| Preference (''0x0E'') || Unsigned 32 bits number || Priority given to this server among the others (Normal=''0'', High=''1'', Low=''2'')
|-
| DNS (''0x85'') || String || [http://en.wikipedia.org/wiki/DNS DNS] of the server
|-
| Max users (''0x87'') || Unsigned 32 bits number || Maximum number of users the server allows to simoultaneously connect to it
|-
| Soft files (''0x88'') || Unsigned 32 bits number || [[Soft files]] number
|-
| Hard files (''0x89'') || Unsigned 32 bits number || [[Hard files]] number
|-
| Last ping (''0x90'') || Unsigned 32 bits number || Last time the server was [[ping]]ed
|-
| Version (''0x91'') || String / Unsigned 32 bits number || Version and name of the software the server is running to support the [[FAQ_ed2k|ed2k]] [[network]]
|-
| [http://www.ietf.org/rfc/rfc768.txt UDP] flags (''0x92'') || Unsigned 32 bits number || Informs of the actions the server accepts through [http://www.ietf.org/rfc/rfc768.txt UDP] connections. This flags are:
*''0x01'': Get sources
*''0x02'': Get files
*''0x08'': New tags
*''0x10'': Unicode
*''0x20'': Get extended sources info
|-
| Auxiliary [[port]]s list (''0x93'') || String || Some servers have [[How_to_use_auxiliary_server_ports|additional ports]] open for those [[user]]s who cannot connect to the standard one (usually because they have a firewall which tries to stop [[P2P]] connections). This servers tell in this field which additional ports they have open. Each additional port is separated from the others by a coma ('','').
|-
| [[LowID]] [[client]]s (''0x94'') || Unsigned 32 bits number || Number of users connected with a LowID
|}

==== Tag Names ====

{| border=0
|+ There are at the moment two tag names recognized by [[aMule]]:
| width="100px" | ''Tag Name'' || ''Tag Value''
|-
| "files" || Unsigned 32 bits number || Shows the number of [[file]]s registered in the [[server]]
|-
|"users" || Unsigned 32 bits number || Shows the number of [[user]]s registered in the [[server]]
|}

== Example ==

The following is an example file:

''E00200000050EFC86CB80B0C000000020100010A004269472042616E4720390201000B0E0077''
''77772E42694742616E472E746F0305007573657273EF1A010003050066696C657331DC8C0003''
''01000C9C00000003010090332B114303010087E0930400030100888813000003010089102700''
''0002010091040031372E3603010092FB0000000301009474580000428722C64E200C00000002''
''0100011E003E3E3E2A2A2A5757572E534558455345584F5345582E434F4D2A2A2A2020''

Here goes the explanation of the file:

*''E0'' <- Validation initial value
*''02000000'' <- ''2'' servers will be listed (remember its [[little endian]])
*Server #1:
**''50EFC86C'' <- [[IP]]: ''108.200.239.80.'' (remember its [[little endian]])
**''B80B'' <- [[Port]]: ''3000'' (remember its [[little endian]])
**''0C000000'' <- ''12'' tags (remember its [[little endian]])
**Tag #1
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''01'' <- Tag name: ''1'' (Server name)
***''0A00'' <- Tag value length: ''10'' (remember its [[little endian]])
***''4269472042616E472039'' <- Tag value: ''BiG BanG 9'' (server name)
**Tag #2
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''0B'' <- Tag name: ''0B'' (Description)
***''0E00'' <- Tag value length: ''14'' (remember its [[little endian]])
***''7777772E42694742616E472E746F'' <- Tag value: ''www.BiGBanG.to'' (server description)
**Tag #3
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0500'' <- Tag name length: ''5'' (remember its [[little endian]])
***''7573657273'' <- Tag name: ''users'' (this is a string, not a code)
***''EF1A0100'' <- Tag value: ''72431'' (remember its [[little endian]])
**Tag #4
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0500'' <- Tag name length: ''5'' (remember its [[little endian]])
***''66696C6573'' <- Tag name: ''files'' (this is a string, not a code)
***''31DC8C00'' <- Tag value: ''9231409'' (remember its [[little endian]])
**Tag #5
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''0C'' <- Tag name: ''0C'' (Ping)
***''9C000000'' <- Tag value: ''156'' (ping time in ms)
**Tag #6
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''90'' <- Tag name: ''90'' (Last ping)
***''332B1143'' <- Tag value: ''5:10:43 28/08/2005'' (last time the server was pinged)
**Tag #7
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''87'' <- Tag name: ''87'' (Max users)
***''E0930400'' <- Tag value: ''300000'' (max users)
**Tag #8
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''88'' <- Tag name: ''88'' (Soft files)
***''88130000'' <- Tag value: ''5000'' (soft files)
**Tag #9
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''89'' <- Tag name: ''89'' (Hard files)
***''10270000'' <- Tag value: ''10000'' (hard files)
**Tag #10
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''91'' <- Tag name: ''91'' (Version)
***''0400'' <- Tag value length: ''4'' (remember its [[little endian]])
***''31372E36'' <- Tag value: ''17.6'' (version)
**Tag #11
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''92'' <- Tag name: ''92'' ([http://www.ietf.org/rfc/rfc768.txt UDP] flags)
***''FB000000'' <- Tag value (in binnary, only the least valuable byte): ''11111001'' ([http://www.ietf.org/rfc/rfc768.txt UDP] flags: get sources, new tags, unicode, extended sources)
**Tag #11
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''94'' <- Tag name: ''94'' (LowID users)
***''74580000'' <- Tag value: ''22644'' (LowID users)
*Server #2
**''428722C6'' <- [[IP]]: ''198.34.135.66'' (remember its [[little endian]])
**''4E20'' <- [[Port]]: ''8270'' (remember its [[little endian]])
**''01000000'' <- ''1'' tag (remember its [[little endian]])
**Tag #1
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''01'' <- Tag name: ''1'' (Server name)
***''1E00'' <- Tag value length: ''30'' (remember its [[little endian]])
***''3E3E3E2A2A2A5757572E534558455345584F5345582E434F4D2A2A2A2020'' <- Tag value: ''***WWW.SEXESEXOSEX.COM*** '' (server name)

== More ==

For more information on tags used in [[eMule]] [[AMule_files|files]] and protocol, check the [http://hydranode.com/docs/ed2k/ed2k-tag.php ed2k tag documentation] at the [http://hydranode.com Hydranode project].

Ed2k links handling

2005-08-29T05:25:03Z

83.42.86.182:

The way to have [[aMule]] handle your [[ed2k link]]s on your favorite WebBrowser will depend on which WebBrowser you use. So, here's a list of mini-HowTos for each of the most popular WebBrowsers.
Have in mind that everywhere on this document, ''/path/to/ed2k'' should be replaced with ''/usr/local/bin/ed2k'', ''/usr/bin/ed2k'', ''C:\Program Files\aMule\ed2k.exe'' or whatever, depending on your own system's configuration.

As a general idea, in most [http://www.kernel.org Linux] systems, self-compiled [[aMule]]s will install the [[FAQ_ed2k_command|ed2k]] utility in ''/usr/local/bin/ed2k'', while package-installed [[aMule]]s will install it in ''/usr/bin/ed2k''. As an exception, it is known that [http://www.suse.com SuSE] packages install it in ''/usr/local/bin/ed2k''.

== [http://www.microsoft.com/windows/ie Internet Explorer] ==
'''by ''[[User:Jacobo221|Jacobo221]]'''''

Go to "Start" -> "Run" and run "regedit" (without quotes).

Now, in regedit, go to ''HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ed2k\shell\open\command''

'''NOTE:''' It could happen that ''ed2k'' and/or it's subfolders didn't exist. In such case, create them one-by-one by selecting "New" -> "Key" and entering ''ed2k'' or whatever as it's value.

http://www.amule.org/dev-up/ed2k-win1.jpg

Now just double click on "(Default)" (or "(Standad)" or whatever the first value is there) and enter the path to the ed2k application, followed by ''"%1"'' (with quotes), so you should end with some value like ''C:\Program Files\aMule2\ed2k "%1"''.

http://www.amule.org/dev-up/ed2k-win2.jpg

Finally, do the same in ''HKEY_CLASSES_ROOT\ed2k\shell\open\command''

== [http://www.konqueror.org Konqueror] ==
'''by ''gfdsa'''''

''/usr/kde/3.1/share/services'' you can find it by file names ended with ''.protocol'' kinda ''`find /usr -name "*.protocol"`'' or ''`find /opt -name "*.protocol"`'' or even put ''/'' to path if you want.

If the search was successful, create a file named like ''ed2k.protocol'' in
the mentioned directory:

<code>[Protocol] 
exec=/path/to/ed2k "%u" 
protocol=ed2k 
input=none 
output=none 
helper=true 
listing=false 
reading=false 
writing=false 
makedir=false 
deleting=false</code>

Now just restart [http://www.konqueror.org Konqueror].

'''NOTE:''' You might get a security warning. don't worry. it is just warning you that the link is being sent to an external application.

'''NOTE2:''' If after clicking ''OK'' on the security warning the link is still not being sent to [[aMule]], just right-click on the [[ed2k link]] and tell [http://www.konqueror.org Konqueror] to open it in a new window/tab.

== [http://galeon.sourceforge.net Galeon] ==

=== Method 1 ===

In the [http://freshmeat.net/projects/gnomecc GNOME Control Center] go to "Complex" -> "File Types and Programs" -> "Internet Services" -> "Add Service...".

In the protocol filed enter ''ed2k''

In the Program field enter ''ed2k %s''

Unselect "Run in terminal" if it is selected.

Click ''OK'' and you're done!

=== Method 2 ===

Execute the following three commands to create the appropriate ''gconf'' keys:
*''gconftool-2 -t string -s /desktop/gnome/url-handlers/ed2k/command "/usr/local/bin/ed2k %s"''
*''gconftool-2 -t bool -s /desktop/gnome/url-handlers/ed2k/enabled true''
*''gconftool-2 -t bool -s /desktop/gnome/url-handlers/ed2k/needs_terminal false''
Replace "''/usr/local/bin/ed2k''" above with the path and name of the ''ed2k'' executable on your system.

Uninstalling this protocol handler is similarly simple:
*''gconftool-2 -u /desktop/gnome/url-handlers/ed2k --recursive-unset''

== [http://www.opera.com Opera] ==
'''by ''thermoman (Marcel Meckel)'', ''ender'' and ''[[User:Jacobo221|Jacobo221]]''

=== Clean way ===

In [http://www.opera.com Opera] go to ''Tools->Preferences->Paths and Programms->Add...''

In the "Protocol" field enter ''ed2k''

In the "Path" or "Open with another application" field enter ''/path/to/ed2k''

http://www.amule.org/dev-up/ed2k-op.jpg

=== Dirty way ===

If he above instructions didn't work, you can try edit ''/etc/opera6rc'' as root or ''~/.opera/opera6.ini'' as non-root and setting:

''[User Prefs]'' 
''TrustedExternalURLProtocols=ed2k'' 
''[Trusted Applications]'' 
''ed2k=ed2k''

=== Opera 6 bug ===

'''[http://www.opera.com Opera] 6''' doesn't pass complete URL to external programs; only URL without protocol. The way to walk around this follows.

==== [http://www.kernel.org Linux] or some other [http://www.unix.org Unix]-like flavour ====

Create ''amule_submit.sh'' with this content:

<code>#!/bin/sh 
/path/to/ed2k "ed2k://$1"</code>

Now in ''Tools->Preferences->Paths and Programms->Add...->Path'' or in the ''opera6rc'' file change ''ed2k=/path/to/ed2k'' with ''ed2k=/path/to/amule_submit.sh''

==== [http://www.microsoft.com/windows Windows] ====

Create ''amule_submit.bat'' with this content:

''X:\path\to\ed2k.exe "ed2k://%1"''

Change ''ed2k=/path/to/ed2k ed2k://%u'' with ''ed2k=X:\path\to\amule_submit.bat ed2k://%u''

== [http://www.mozilla.org Mozilla] 1.7 (or later) & [http://www.mozilla.org/products/firefox Firefox] 0.9 (or later)==
'''by ''GhePeU'''''

Mozex doesn't work anymore with [http://www.mozilla.org Mozilla] 1.7 and [http://www.mozilla.org/products/firefox Firefox] 0.9. There is an alternate method that seems to be working with both of them:

*Remove [http://mozex.mozdev.org/installation.html MozEx] if installed or at least remove the ed2k input from it (only if [http://mozex.mozdev.org/installation.html MozEx] is installed)

*Insert ''about:config'' in the address bar

*Right click on the list, select '''New''', then '''Boolean'''; insert ''network.protocol-handler.external.ed2k'' as '''Preference Name''' and ''true'' as '''Value'''

*Now another right click, select '''New''' and '''String'''; insert ''network.protocol-handler.app.ed2k'' as '''Preference Name''' and ''/path/to/ed2k'' (path to where the file is installed on your system) as '''Value'''.

http://www.amule.org/dev-up/ed2k-ff9.jpg

== [http://www.mozilla.org/products/firefox Firefox] v0.8 ==

Go to [http://mozex.mozdev.org/installation.html MozEx's WebPage] and install the ''mozex-1.07.xpi'' file.

Restart [http://www.mozilla.org/products/firefox FireFox], go to Edit -> Preferences -> Extensions -> mozex -> Options -> ED2K and set it to ''/path/to/ed2k %r''

Click '''OK''' and you're done.

http://www.amule.org/dev-up/ed2k-firefox.png

http://www.amule.org/dev-up/ed2k-mozex.png

== [http://www.mozilla.org Mozilla] 1.3 to 1.6 & [http://www.mozilla.org/products/firefox Firebird] v0.6 ==
'''by ''DeltaHF'''''

Go to [http://mozex.mozdev.org/installation.html MozEx's WebPage] and install the ''mozex-1.07.xpi'' file.

Restart [http://www.mozilla.org Mozilla]/[http://www.mozilla.org/products/firefox FireBird], go to Edit -> Preferences -> mozex -> ED2K and set it to ''/path/to/ed2k %r''

Click '''OK''' and you're done.

http://www.amule.org/dev-up/ed2k-moz.png

== [http://www.mozilla.org Mozilla] 1.2.1 or earlier ==
'''by ''rpokorny [R. Pokorny]'''''

1) Go to [http://protozilla.mozdev.org/download.html Protozilla's WebPage] 
Choose the version fitting your [http://www.mozilla.org Mozilla]-version and click on '''Install'''. It will auto-install [http://protozilla.mozdev.org Protozilla]. 
Now close [http://www.mozilla.org Mozilla] completely.

Notes for [http://www.kernel.org Linux] and other Unix-like systems users 
- You must have write permission to the [http://www.mozilla.org Mozilla] installation directory. If you've installed [http://www.mozilla.org Mozilla] in ''/usr'', you'll have to be '''root''' probably. 
- The downloadable precompiled version of [http://protozilla.mozdev.org Protozilla] apparently does '''not''' work with [http://www.debian.org Debian]'s [http://www.mozilla.org Mozilla] packages. It '''does''' work together with the precompiled version of 1.2.1 available at [http://www.mozilla.org Mozilla's WebPage] for example (or you can build both [http://www.mozilla.org Mozilla] and [http://protozilla.mozdev.org Protozilla] yourself).

2) This step is only necessary if you had to start [http://www.mozilla.org Mozilla]/[http://www.mozilla.org/products/firefox FireBird]/[http://www.mozilla.org/products/firefox FireFox] as '''root''' in step 1.

As '''root''' do:
''cp -r /root/.mozilla/PROFILENAME/RANDOM.slt/protozilla/ /home/USERNAME/.mozilla/PROFILENAME2/RANDOM.slt/''

This will have copied protozilla-configuration from root's home directory to user's home directory.

''cd /home/USERNAME/.mozilla/PROFILENAME/RANDOM.slt/
chown -R YOURUSER.YOURGROUP protozilla''

This will have changed file-ownership parameters in user's files.

Note: 
'''USERNAME:''' Name of your normal, non-root user. 
'''PROFILENAME:''' Name of the profile you'll want to use. 
'''RANDOM:''' Random alphanumeric string, autogenerated by mozilla. 
'''YOURUSER, YOURGROUP:''' User and group of your normal user. 

3) Setup a protocol-handler for [[ed2k link]]s: 
''cd ~/.mozilla/PROFILENAME/RANDOM.slt/protozilla/protocol''

create a file called ''ed2k.cmd'' with the following content:

''ed2k ed2k:$URI_DATA''

(The file doesn't need to be executable).

Now restart [http://www.mozilla.org Mozilla].

== [http://xray.sai.msu.ru/~karpov/links-hacked Links] ==
(Probably this will work for the usual links and/or [[ed2k link|elinks]], too)

add to ''url.c'' behind the lines about telnet and tn3270:
''--snip''
''{"ed2k", 0, NULL, ed2k_func, 0, 0, 0},''
''--snap''

add to ''links.h'' behind the definitions of /* mailto.c */:
''--snip''
''void ed2k_func(struct session *, unsigned char *);''
''--snap''

add to ''mailto.c'' at the end:
''--snip''
''void ed2k_func(struct session *ses, unsigned char *url)''
''{''
''tn_func(ses, url, options_get("network_program_ed2k"), TEXT(T_ED2K), TEXT(T_BAD_ED2K_URL));''
''}''
''--snap''

add to ''options_register.c'' behind telnet and tn3270:
''--snip''
''register_option_char("network_program_ed2k", TEXT(T_ED2K_PROG),NULL,2);''
''--snap''

add to ''intl/*.lng'' behind
''"T_TN3270_PROG": T_ED2K_PROG, "ed2k program",'' (or whatever that is in your language), behind
''"T_TN3270": T_ED2K, "ed2k",'' and behind
''"T_BAD_TN3270_URL": T_BAD_ED2K_URL'' (I guess you've got the picture)

If you want to automatize this stuff, execute the following commands:
''cd intl''
''for l in *.lng; do''
''cp $l $l.bak''
''cat $l.bak | sed -e "/T_TN3270_PROG*/aT_ED2K_PROG\, \"ed2k program\"\," \''
''-e "/T_TN3270,\ */aT_ED2K\, \"ed2k\"\," \''
''-e "/T_BAD_TN3270_URL*/aT_BAD_ED2K_URL\, \"Bad ed2k url\"\," > $l''
''done''

Anyway, run afterwards before recompiling links-hacked:
''./synclang''
''cd ..''

Now you can compile with
''./configure'' (add your favourite options here) ''&&''
''make &&''
''make install''

Because links somewhat malforms the urls, we need a small bash script handler:
''cat > /usr/bin/ed2k4links.sh << "EOF"''

''#!/bin/bash''

''ed2k $(echo "ed2k://$1" | sed s/_/\|/g)''
''EOF''
''chmod a+x /usr/bin/ed2k4links.sh''

Do not forget to setup links (Options->Network Options->Mail and Telnet Programs) to call our ''ed2k4links.sh'' for [[ed2k link]]s:
''ed2k4links.sh %''

Attention: The Percent Mark is important! Now links should work with [[ed2k link]]s.

== Remotely handling links ==

You can also handle links remotely, which means that you click over an [[ed2k link]] in a browser somewhere in the world and it gets into your home's [[aMule]] queue.

How?

Easy enough: using [[aMuleCMD]] (thanks '''djtm''' for this tip). Instead of using the [[ed2k command]], use the following as the command to use:

''/'''path'''/'''to'''/amulecmd -rh $server -pw $pw -c "Add %u"''

Obviously, you'll have to replace ''$server'' and ''$pw'' with your server's [[IP]] (or [http://www.webopedia.com/TERM/D/DNS.html DNS]) and your [[External Connections]] password.

Please note that the above tip is only available since [[aMule]] 2.0.0rc8.

'''NOTE 1:''' In [http://www.mozilla.org Firefox], it is not possible to start a command with parameters. An easy solution is a shell script with the command described above. You only have to replace %u with $1. This shell script must be executable (chmod +x ed2k.sh) and defined as external ed2k app in Firefox.

'''NOTE 2:''' If you prefer simple tools, try this shell script (for [http://www.kernel.org Linux]) - can be used with the above mentioned tip:

#!/bin/bash
beep -f 100 -l 40 -r2
(sleep 1; echo dllink $1; sleep 2; echo q;) | nc '''''IP''''' '''''PORT'''''
beep -l 15 -r3

''nc'' is [http://netcat.sourceforge.net Netcat], but you can use telnet too (that's a bit simpler in [http://www.cygwin.com Cygwin]), ''beep'' is a simple program for beeping. ''IP'' and ''PORT'' should be replaced with the [[IP address]] and [[port]] of your remote server. That's it.

Ed2k links handling

2005-08-29T05:22:50Z

83.42.86.182:

The way to have [[aMule]] handle your [[ed2k link]]s on your favorite WebBrowser will depend on which WebBrowser you use. So, here's a list of mini-HowTos for each of the most popular WebBrowsers.
Have in mind that everywhere on this document, ''/path/to/ed2k'' should be replaced with ''/usr/local/bin/ed2k'', ''/usr/bin/ed2k'', ''C:\Program Files\aMule\ed2k.exe'' or whatever, depending on your own system's configuration.

As a general idea, in most [http://www.kernel.org Linux] systems, self-compiled [[aMule]]s will install the [[FAQ_ed2k_command|ed2k]] utility in ''/usr/local/bin/ed2k'', while package-installed [[aMule]]s will install it in ''/usr/bin/ed2k''. As an exception, it is known that [http://www.suse.com SuSE] packages install it in ''/usr/local/bin/ed2k''.

== [http://www.microsoft.com/windows/ie Internet Explorer] ==
'''by ''[[User:Jacobo221|Jacobo221]]'''''

Go to "Start" -> "Run" and run "regedit" (without quotes).

Now, in regedit, go to ''HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ed2k\shell\open\command''

'''NOTE:''' It could happen that ''ed2k'' and/or it's subfolders didn't exist. In such case, create them one-by-one by selecting "New" -> "Key" and entering ''ed2k'' or whatever as it's value.

http://www.amule.org/dev-up/ed2k-win1.jpg

Now just double click on "(Default)" (or "(Standad)" or whatever the first value is there) and enter the path to the ed2k application, followed by ''"%1"'' (with quotes), so you should end with some value like ''C:\Program Files\aMule2\ed2k "%1"''.

http://www.amule.org/dev-up/ed2k-win2.jpg

Finally, do the same in ''HKEY_CLASSES_ROOT\ed2k\shell\open\command''

== [http://www.konqueror.org Konqueror] ==
'''by ''gfdsa'''''

''/usr/kde/3.1/share/services'' you can find it by file names ended with ''.protocol'' kinda ''`find /usr -name "*.protocol"`'' or ''`find /opt -name "*.protocol"`'' or even put ''/'' to path if you want.

If the search was successful, create a file named like ''ed2k.protocol'' in
the mentioned directory:

<code>[Protocol] 
exec=/path/to/ed2k "%u" 
protocol=ed2k 
input=none 
output=none 
helper=true 
listing=false 
reading=false 
writing=false 
makedir=false 
deleting=false</code>

Now just restart [http://www.konqueror.org Konqueror].

'''NOTE:''' You might get a security warning. don't worry. it is just warning you that the link is being sent to an external application.

'''NOTE2:''' If after clicking ''OK'' on the security warning the link is still not being sent to [[aMule]], just right click on the [[ed2k link]]s and tell [http://www.konqueror.org Konqueror] to open it in a new window.

== [http://galeon.sourceforge.net Galeon] ==

=== Method 1 ===

In the [http://freshmeat.net/projects/gnomecc GNOME Control Center] go to "Complex" -> "File Types and Programs" -> "Internet Services" -> "Add Service...".

In the protocol filed enter ''ed2k''

In the Program field enter ''ed2k %s''

Unselect "Run in terminal" if it is selected.

Click ''OK'' and you're done!

=== Method 2 ===

Execute the following three commands to create the appropriate ''gconf'' keys:
*''gconftool-2 -t string -s /desktop/gnome/url-handlers/ed2k/command "/usr/local/bin/ed2k %s"''
*''gconftool-2 -t bool -s /desktop/gnome/url-handlers/ed2k/enabled true''
*''gconftool-2 -t bool -s /desktop/gnome/url-handlers/ed2k/needs_terminal false''
Replace "''/usr/local/bin/ed2k''" above with the path and name of the ''ed2k'' executable on your system.

Uninstalling this protocol handler is similarly simple:
*''gconftool-2 -u /desktop/gnome/url-handlers/ed2k --recursive-unset''

== [http://www.opera.com Opera] ==
'''by ''thermoman (Marcel Meckel)'', ''ender'' and ''[[User:Jacobo221|Jacobo221]]''

=== Clean way ===

In [http://www.opera.com Opera] go to ''Tools->Preferences->Paths and Programms->Add...''

In the "Protocol" field enter ''ed2k''

In the "Path" or "Open with another application" field enter ''/path/to/ed2k''

http://www.amule.org/dev-up/ed2k-op.jpg

=== Dirty way ===

If he above instructions didn't work, you can try edit ''/etc/opera6rc'' as root or ''~/.opera/opera6.ini'' as non-root and setting:

''[User Prefs]'' 
''TrustedExternalURLProtocols=ed2k'' 
''[Trusted Applications]'' 
''ed2k=ed2k''

=== Opera 6 bug ===

'''[http://www.opera.com Opera] 6''' doesn't pass complete URL to external programs; only URL without protocol. The way to walk around this follows.

==== [http://www.kernel.org Linux] or some other [http://www.unix.org Unix]-like flavour ====

Create ''amule_submit.sh'' with this content:

<code>#!/bin/sh 
/path/to/ed2k "ed2k://$1"</code>

Now in ''Tools->Preferences->Paths and Programms->Add...->Path'' or in the ''opera6rc'' file change ''ed2k=/path/to/ed2k'' with ''ed2k=/path/to/amule_submit.sh''

==== [http://www.microsoft.com/windows Windows] ====

Create ''amule_submit.bat'' with this content:

''X:\path\to\ed2k.exe "ed2k://%1"''

Change ''ed2k=/path/to/ed2k ed2k://%u'' with ''ed2k=X:\path\to\amule_submit.bat ed2k://%u''

== [http://www.mozilla.org Mozilla] 1.7 (or later) & [http://www.mozilla.org/products/firefox Firefox] 0.9 (or later)==
'''by ''GhePeU'''''

Mozex doesn't work anymore with [http://www.mozilla.org Mozilla] 1.7 and [http://www.mozilla.org/products/firefox Firefox] 0.9. There is an alternate method that seems to be working with both of them:

*Remove [http://mozex.mozdev.org/installation.html MozEx] if installed or at least remove the ed2k input from it (only if [http://mozex.mozdev.org/installation.html MozEx] is installed)

*Insert ''about:config'' in the address bar

*Right click on the list, select '''New''', then '''Boolean'''; insert ''network.protocol-handler.external.ed2k'' as '''Preference Name''' and ''true'' as '''Value'''

*Now another right click, select '''New''' and '''String'''; insert ''network.protocol-handler.app.ed2k'' as '''Preference Name''' and ''/path/to/ed2k'' (path to where the file is installed on your system) as '''Value'''.

http://www.amule.org/dev-up/ed2k-ff9.jpg

== [http://www.mozilla.org/products/firefox Firefox] v0.8 ==

Go to [http://mozex.mozdev.org/installation.html MozEx's WebPage] and install the ''mozex-1.07.xpi'' file.

Restart [http://www.mozilla.org/products/firefox FireFox], go to Edit -> Preferences -> Extensions -> mozex -> Options -> ED2K and set it to ''/path/to/ed2k %r''

Click '''OK''' and you're done.

http://www.amule.org/dev-up/ed2k-firefox.png

http://www.amule.org/dev-up/ed2k-mozex.png

== [http://www.mozilla.org Mozilla] 1.3 to 1.6 & [http://www.mozilla.org/products/firefox Firebird] v0.6 ==
'''by ''DeltaHF'''''

Go to [http://mozex.mozdev.org/installation.html MozEx's WebPage] and install the ''mozex-1.07.xpi'' file.

Restart [http://www.mozilla.org Mozilla]/[http://www.mozilla.org/products/firefox FireBird], go to Edit -> Preferences -> mozex -> ED2K and set it to ''/path/to/ed2k %r''

Click '''OK''' and you're done.

http://www.amule.org/dev-up/ed2k-moz.png

== [http://www.mozilla.org Mozilla] 1.2.1 or earlier ==
'''by ''rpokorny [R. Pokorny]'''''

1) Go to [http://protozilla.mozdev.org/download.html Protozilla's WebPage] 
Choose the version fitting your [http://www.mozilla.org Mozilla]-version and click on '''Install'''. It will auto-install [http://protozilla.mozdev.org Protozilla]. 
Now close [http://www.mozilla.org Mozilla] completely.

Notes for [http://www.kernel.org Linux] and other Unix-like systems users 
- You must have write permission to the [http://www.mozilla.org Mozilla] installation directory. If you've installed [http://www.mozilla.org Mozilla] in ''/usr'', you'll have to be '''root''' probably. 
- The downloadable precompiled version of [http://protozilla.mozdev.org Protozilla] apparently does '''not''' work with [http://www.debian.org Debian]'s [http://www.mozilla.org Mozilla] packages. It '''does''' work together with the precompiled version of 1.2.1 available at [http://www.mozilla.org Mozilla's WebPage] for example (or you can build both [http://www.mozilla.org Mozilla] and [http://protozilla.mozdev.org Protozilla] yourself).

2) This step is only necessary if you had to start [http://www.mozilla.org Mozilla]/[http://www.mozilla.org/products/firefox FireBird]/[http://www.mozilla.org/products/firefox FireFox] as '''root''' in step 1.

As '''root''' do:
''cp -r /root/.mozilla/PROFILENAME/RANDOM.slt/protozilla/ /home/USERNAME/.mozilla/PROFILENAME2/RANDOM.slt/''

This will have copied protozilla-configuration from root's home directory to user's home directory.

''cd /home/USERNAME/.mozilla/PROFILENAME/RANDOM.slt/
chown -R YOURUSER.YOURGROUP protozilla''

This will have changed file-ownership parameters in user's files.

Note: 
'''USERNAME:''' Name of your normal, non-root user. 
'''PROFILENAME:''' Name of the profile you'll want to use. 
'''RANDOM:''' Random alphanumeric string, autogenerated by mozilla. 
'''YOURUSER, YOURGROUP:''' User and group of your normal user. 

3) Setup a protocol-handler for [[ed2k link]]s: 
''cd ~/.mozilla/PROFILENAME/RANDOM.slt/protozilla/protocol''

create a file called ''ed2k.cmd'' with the following content:

''ed2k ed2k:$URI_DATA''

(The file doesn't need to be executable).

Now restart [http://www.mozilla.org Mozilla].

== [http://xray.sai.msu.ru/~karpov/links-hacked Links] ==
(Probably this will work for the usual links and/or [[ed2k link|elinks]], too)

add to ''url.c'' behind the lines about telnet and tn3270:
''--snip''
''{"ed2k", 0, NULL, ed2k_func, 0, 0, 0},''
''--snap''

add to ''links.h'' behind the definitions of /* mailto.c */:
''--snip''
''void ed2k_func(struct session *, unsigned char *);''
''--snap''

add to ''mailto.c'' at the end:
''--snip''
''void ed2k_func(struct session *ses, unsigned char *url)''
''{''
''tn_func(ses, url, options_get("network_program_ed2k"), TEXT(T_ED2K), TEXT(T_BAD_ED2K_URL));''
''}''
''--snap''

add to ''options_register.c'' behind telnet and tn3270:
''--snip''
''register_option_char("network_program_ed2k", TEXT(T_ED2K_PROG),NULL,2);''
''--snap''

add to ''intl/*.lng'' behind
''"T_TN3270_PROG": T_ED2K_PROG, "ed2k program",'' (or whatever that is in your language), behind
''"T_TN3270": T_ED2K, "ed2k",'' and behind
''"T_BAD_TN3270_URL": T_BAD_ED2K_URL'' (I guess you've got the picture)

If you want to automatize this stuff, execute the following commands:
''cd intl''
''for l in *.lng; do''
''cp $l $l.bak''
''cat $l.bak | sed -e "/T_TN3270_PROG*/aT_ED2K_PROG\, \"ed2k program\"\," \''
''-e "/T_TN3270,\ */aT_ED2K\, \"ed2k\"\," \''
''-e "/T_BAD_TN3270_URL*/aT_BAD_ED2K_URL\, \"Bad ed2k url\"\," > $l''
''done''

Anyway, run afterwards before recompiling links-hacked:
''./synclang''
''cd ..''

Now you can compile with
''./configure'' (add your favourite options here) ''&&''
''make &&''
''make install''

Because links somewhat malforms the urls, we need a small bash script handler:
''cat > /usr/bin/ed2k4links.sh << "EOF"''

''#!/bin/bash''

''ed2k $(echo "ed2k://$1" | sed s/_/\|/g)''
''EOF''
''chmod a+x /usr/bin/ed2k4links.sh''

Do not forget to setup links (Options->Network Options->Mail and Telnet Programs) to call our ''ed2k4links.sh'' for [[ed2k link]]s:
''ed2k4links.sh %''

Attention: The Percent Mark is important! Now links should work with [[ed2k link]]s.

== Remotely handling links ==

You can also handle links remotely, which means that you click over an [[ed2k link]] in a browser somewhere in the world and it gets into your home's [[aMule]] queue.

How?

Easy enough: using [[aMuleCMD]] (thanks '''djtm''' for this tip). Instead of using the [[ed2k command]], use the following as the command to use:

''/'''path'''/'''to'''/amulecmd -rh $server -pw $pw -c "Add %u"''

Obviously, you'll have to replace ''$server'' and ''$pw'' with your server's [[IP]] (or [http://www.webopedia.com/TERM/D/DNS.html DNS]) and your [[External Connections]] password.

Please note that the above tip is only available since [[aMule]] 2.0.0rc8.

'''NOTE:''' In [http://www.konqueror.org Konqueror], if after clicking ''OK'' on the security warning the link is still not being sent to [[aMule]], just right-click on the [[ed2k link]] and tell [http://www.konqueror.org Konqueror] to open it in a new window/tab.

'''NOTE:''' In [http://www.mozilla.org Firefox], it is not possible to start a command with parameters. An easy solution is a shell script with the command described above. You only have to replace %u with $1. This shell script must be executable (chmod +x ed2k.sh) and defined as external ed2k app in Firefox.

'''NOTE:''' If you prefer simple tools, try this shell script (for [http://www.kernel.org Linux]) - can be used with the above mentioned tip:

#!/bin/bash
beep -f 100 -l 40 -r2
(sleep 1; echo dllink $1; sleep 2; echo q;) | nc '''''IP''''' '''''PORT'''''
beep -l 15 -r3

''nc'' is [http://netcat.sourceforge.net Netcat], but you can use telnet too (that's a bit simpler in [http://www.cygwin.com Cygwin]), ''beep'' is a simple program for beeping. ''IP'' and ''PORT'' should be replaced with the [[IP address]] and [[port]] of your remote server. That's it.

AMule problems

2005-08-28T17:28:44Z

83.42.86.182:

<center>
<h4>[[aMule_Project_FAQ:About|aMule]] common problems</h4>

<h2>by ''[[User:Jacobo221|Jacobo221]]''</h2>

'''English''' | [[AMule_problems-es|Español]] | [[AMule_problems-nl|Nederlands]] | [[AMule_problems-hu|Magyar]]
</center>

== I get an "aMule already running: exiting" message on the terminal when starting aMule. Will I be able to start it anyways? ==
The message is very clear: [[aMule]] is already running. But this doesn't refer to the entire system, rather that '''you''' (your user account) is already running [[aMule]].

It might seem that there is no instance of [[aMule]] running if it crashed on you. However, what sometimes happens is that some processes aren't completly closed keeping them in a state known as ''zombie'' or ''defunct''. To find out if this is your problem, run ''ps u | grep amule'' and if it shows any output (except the grep output itself), then there's some other aMule process running with your account. To kill it, either close it normally (if you can) or kill it with ''kill -9 <aMule-PID>'' or ''killall -9 amule'' or logoff and log in again (which, in most cases, will kill all [[aMule]] processes, unless you executed [[aMule]] with ''nohup'' or something similar).

If non of the above suits you, then you can run another instance of [[aMule]] as another user (if you can log in with another account, of course). Read [[FAQ_aMule#Can_I_run_two_aMule_instances_at_the_same_time?|Can I run two aMule instances at the same time?]].

== aMule starts but is never shown but works fine. What's going on? ==
This commonly happens when you set the type of systray integration, in Preferences -> General -> Misc Options, to ''Minimize to trayicon'' which starts [[aMule]] minimized. 
To be able to recover aMule's GUI, edit ''~/.aMule/amule.conf'' and search for ''StartupMinimized=1'' and once you find it, change that line to ''StartupMinimized=0''. The following script will do that for you: 
''sed s/StartupMinimized=1/StartupMinimized=0/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf'' 
When you next start [[aMule]] set the correct systray integration in Preferences so that you can enable "Start minimized" without having [[aMule]] hidden. 
If, for some reason, the above didn't work, try changing the Systray integration manually to the default by unchecking the "Enable tray icon'' option. To do so, set the ''DesktopMode='' value in ''~/.aMule/amule.conf'' to ''4''. The following script will do that for you: 
''sed s/DesktopMode=[0-9]/DesktopMode=4/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf'' 
'''NOTE:''' On [[aMule]] versions previous to 2.0.0rc4, you should set it to ''1'' instead of ''4'' since the Preferences storage changed a little.

== aMule starts but is never connecting/behaving very weird/crashing almost every few seconds/etc...? ==
aMule versions up to 2.0.0-rc3 shouldn't be linked against wxWidgets 2.5.x neither GTK2 although some Linux distributions tend to do so. Please make sure your aMule isn't the case. If unsure, paste you backtrace at [http://www.amule.org/amule/board.php?boardid=33 aMule's Backtraces forum] or join aMule's IRC channel #amule at irc.freenode.net

== Where are my downloaded files? ==
By default, aMule stores completed files in ''~/.aMule/Incoming'' but, since ''~/.aMule'' directory is a hidden directory, your file manager might not show it. Make sure you have enabled your file manager to show hidden files. 
By default, files being downloaded are placed in ''~/.aMule/Temp'', so again, this is a hidden directory and the file managed must be configured to show hidden files.

== Why is aMule taking so much CPU resources at start-up? ==
This happens because aMule is hashing new files found on the Shared Directories. If aMule is always taking a lot of CPU at startup and no new files have been added or modified in any way in the Shared Directories, then something is wrong.

In aMule versions earlier than 2.0.0-rc3 this used to happen when having the Temp, Incoming or any Shared Directory in a FAT32 partition. Since aMule 2.0.0-rc3 this is not happening any more.

Also, in aMule versions earlier than 2.0.0-rc4 filesystems with UTF-8 encoding (known to happen with SuSE 9.1) could present problems when some file or directory in the Shared Directories path contanied a special character. If this is your problem, there's a walkaround (thanks '''nachbarnebenan'''): after aMule has hashed all shared files (that is, when it stops taking a lot of your CPU's resources), close aMule and enconde ~/.aMule/known.met into UTF-8 encoding (you can do this with the application ''[http://www.gnu.org/directory/recode.html recode]'' by running the following command: ''recode u8 ~/.aMule/known.met''). This should be done whenever a files is added or modified in any Shared Directory. So, best option is to upgrade to latest aMule version.

If non of the above helps you, then something went really wrong on ''known.met'' file, probably some external program or user broke it. Best option is to delete it, start aMule and let aMule rehash all files again.

== So now aMule starts, but why is it displaying this message: "No valid servers to connect in serverlist found"? ==
That's because you enabled the option "Auto connect to servers the static list only". So, disable it or add some server to the static list. 
To disable that option, go to Preferences -> Servers -> "Auto connect to servers the static list only" 
To add a server to the static list, go to the Servers window and right-click on the server you want to add to the static list. Then select "Add to static" and do this exact process wit all the servers you want to add to the static list.

== aMule connects to server, but it is always given Low-ID. Why? and, can I do something about it? ==
This can bue due to three reasons:
<ul><li>Some necessary port is not opened in your firewall. Read [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|this]] to get to know what to do and check [http://www.amule.org/testport.php here] if the ports are open.</li>
<li>The server is very busy or maybe badly configured, so it's giving you a [[Low-ID]]. There's nothing that can be done in this case other than reconnect or connect to some other server.</li>
<li>Some ISP forbid the use of p2p applications, such as aMule, by not allowing traffic through popular p2p ports. In these cases, configure aMule to use some other port. It would be even better if it was some popular port used for some other issue. It's been known that on some ISPs it worked with port TCP 25600.</li></ul>

== [[aMule]] was interrupted while completing a file and it is now never completing it (allthough it's 100% downloaded). How can I complete it? ==
This one is easy: Close [[aMule]]. Now go into the Temp directory (by default, ''~/.aMule/Temp'') and run the following command:

''touch ./*''

Finally, run [[aMule]] and let it complete the files.

== I just lost a download. Is there anyway I can recover it? ==
This is strange to happen, but it might, although in most cases it is the result of some non-aMule-related stuff going weird (or user's fault). 
Two things may have happened. Either *.part.met files were deleted, or *.part files were deleted. 
If *.part files have dissapeared, the only solution is to reastart the downloads from the beggining (if *.part.met files are still there, aMule will restart the downloads on next start). However this should '''never''' happen unless the user directly deleted them. 
If *.part.met files have dissapeared but *.part files are still in the Temp directory, then search if *.part.met.bak are also in the Temp directory. If they are, then just rename ''*.part.met.bak'' files to ''*.part.met'' just by running: 
''for file in *.part.met.bak; do mv -f "$file" "${file%.bak}; done'' 
Still, it could happen that, although you have the *.part files, neither *.part.met nor *.part.met.bak files exist any longer. In this case, you would have two ways ways to work out of this: 
Either, use [http://www.bigwillystyle42.com/index.php?dest=mfr MetFileRegenerator] (Java needed) to reconstruct the *.part.met files. 
Or, search again on aMule for the files you were downloading and rename their part number in the *.part.met files to the ones it used to have. For example, if you ware down loading ''aMule_1.2.6.tar.gz'' and that was being downloaded in Temp directory as ''008.part'', then that file used to have it's corresponding ''008.part.met'' file and, probably, it's ''008.part.met.bak'' file. But this two latter files have misteriously dissapeared. Then search again on aMule for ''aMule_1.2.6.tar.gz'' and start downloading it. Close aMule and you'll have this new download as, for example, ''011.part'' file in the Temp directory. Of course, this download will have it's ''011.part.met'' file. Well, rename ''011.part.met'' to ''008.part.met'' and then delete ''011.part'' (and ''011.part.met.bak'' if it existed). Now start aMule and you will have recovered the download from the point it was before the *.part.met files disapeared.

== Why does aMule suddendly become unresponsive to the mouse although it's not hanged? ==
It sometimes happens that you left a dialog window somewhere hidden in the desktop. aMule is waiting for that window to be closed, so it becomes unresponsive untill you click OK, Cancel, or whatever you have to click. 
So, make sure there's no aMule dialog left around in '''any workspace'''.

== Why are some files in my shared folders not shown in the Shared Folders window? ==
This could happen if you added this files after aMule has been started. Press the "Reload" button on Shared Folders window and it should find the new files and hash them (this may take some CPU time).

However, on some releases it has happened that after restarting aMule, some files dissapear from the Shared Folders window alllthough they are in the shared folders. In such cases, the only way to have them back is to delete ''~/.aMule/known.met'' but, of course, on next aMule start, all shared files will have to be rehashed, and that'll take some time most probably.

== I always get a message about addresses.met when I start aMule. What's wrong? ==
This happens when you enable the option Preferences -> Servers -> "Auto-update serverlist at startup" and you have no serverlists' urls in ''addresses.dat''. You can either add some to ''addresses.dat'' by adding them at Preferences -> Servers -> List or just disable Preferences -> Servers -> "Auto-update serverlist at startup" if you don't really need it. 

== I sometimes get a message on the log about credits being lost. Should I be worried? ==
No, you don't need to be worried. Credits for a client are deleted after 150 days (more or less 5 months) without "seeing" that client. Also, bad clients might lose their credits too. So those messages are just for debug information, you souldn't worry about them.

== What should I do if I lose my ''cryptkey.dat'' file? ==
Losing this files means you lose all of your credits. Sorry. Since you'll need to start building credits up again, you'll need to delete ''~/.aMule/preferences.dat'' or you'll not be able to collect credits on [[client|clients]] who have previously identified you (prior to losing cryptkey.dat).

== Why is Upload/Download limit always back to 0 after every restart? ==
This happened on aMule versions previous to 2.0.0-rc4 when you trying to set a Upload or Download limit value higher than the Upload or Download Capacity value. However, since version 2.0.0-rc4 this is fixed (read [[FAQ_aMule#What_is_the_real_point_on_setting_up_Line_Capacities_in_Preferences?_Shouldn't_aMule_only_care_for_the_Bandwidth_Limits?|What is the real point on setting up Line Capacities
in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] to understand why) and shouldn't happen anymore.

== Why is aMule ignoring the bandwith I set per slot? ==
The bandwidth set to each slot can be set in Preferences, but it will be ignored if the bandwidth set per slot doesn't allow at least three connections at the same time. 
So, the maximum speed allowed per slot is '''BandwidthLimit/3'''. 
Please do '''NOT''' confuse '''Bandwidth limit''' with '''Bandwith Capacity'''. Read [[FAQ_aMule#What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?|What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] since the meaning of the Bandwidth Capacity setting is not intuitive. 
Also, if [[aMule]] detects that, after having set all the slots for uploading, still some bandwidth is left before getting to the Bandwidth Limit, it will allow another slot and divide all the slot bandwidths to so use the same amount of bandwidth. 

Example: 
Bandwidth Limit: 7 KBps
Slot allocation: 2 KBps
When [[aMule]] sets the slots to some clients to upload to them, after giving out three slots, it will notice that tehre are no more 2KBps left, since the limit is 7 KBps, but there is still 1 KBps left in the bandwicth before reaching the Bandwidth Limit. So, It will allow another slot to upload to a client and, isntead of giving that last slot a 1 KBps bandwidth connection (and leave the rest with a 2 KBps bandwidth connetcion), it will give all four slots a 1.8 KBps bandwidth connection.

== Why can't I set aMule's download limit to more than X? ==
To keep the ED2K network alive, all ED2K clients have an upload/download limits ratio hardcoded which, depending on the upload limit set, is:

From 0KBps to 3KBps: 
DownloadLimit can't be more than UploadLimit*3 
From 4KBps to 9KBps: 
DownloadLimit can't be more than UploadLimit*4 
UploadLimit values over 9KBps: 
There's no DownloadLimit limitation.

Be carefull when setting 0KBps as Upload Limit . It might not mean what you think it is. Read [[AMule_problems#I_set_Upload_Limit_to_0KBps,_but_aMule_is_still_transfering._What_did_I_do_wrong?|I set Upload Limit to 0KBps, but aMule is still transfering. What did I do wrong?]] to make sure you understand it's meaning.

== I set Upload Limit to 0KBps, but aMule is still transfering. What did I do wrong? ==
Setting Upload limit to 0KBps will not stop transfers, instead, ''0'' value means '''unlimited''', so, it's right the opossite of you're trying to do. There's no way to stop aMule from uploading files, and that's the same on all ED2K clients (eMule, eDonkey, etc). Allowing people not to upload would bring the ED2K network to it's end. 
Even if you don't share any directory, the Temp directory will '''always''' be shared, so that files that you are downloading are shared with other clients.

== Why am I getting "Too many connections" messages on the terminal? ==
This happens when you set a very high value at Preferences -> Connections -> "Connection limits" -> "Max connections". If this value is as almost as big as the the amount of connections your system allows you to have, then aMule will fail to establish connections and display those messages (have in mind that other applications may also have some connections established). 
On Windows 9x/ME platforms there is a limit of 100 TCP connections so, although you might set aMule to establish more than 100 connections, it will be unable to do so. You can change Windows's TCP connections limit by editting the Windows Register ('''Start -> Run -> regedit.exe''') and setting (you'll most surely have to add the value since in most cases it doesn't exist): 
''HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections'' (which is a String type and it's value must be a 32-bit number).

== My progress bars have lost most of their 3D effect and look more ugly now. Can I turn its look back? ==
In most aMule versions setting the progress bar style to the most right on Preferences -> "GUI tweaks" is the way to have the progress bar have the best 3D effect. But in versions 2.0.0-rc4 to 2.0.0-rc6 the best 3D effect is given when the style bar is set to the middle. Setting it to the most right would give the progress bar a flat look while setting it to the most left will give it a dark look.

== All my downloads suddenly paused and I can't resume them. What's going on? ==

Check if there's any free space in the filesystem where the Temp directory is placed. If there is any at all, check if there's more free space than the minimum free space set at Preferences -> Files -> "Min disk space".

The minimum free space required for [[aMule]] is 9.28MB, since that's what [[aMule]] needs to be able to download a [[FAQ_ed2k#What_is_a_chunk?|part]] of a file.

== Why can't I preview a file? ==
First of all you must know that [[aMule]] only allows to preview video files.

To be able to preview a file [[aMule]] requieres two things:
*The file must have a known video extension in it's filename
*You must have downloaded the first 256KBs of the file

Anyway, sometimes it happens that the file is previewable though [[aMule]] doesn't allow you. In that case, go to the Temp directory and preview them manually, if you can and wish.

== Why isn't [[aMule]]'s Preview working at all with MPlayer? ==
Since aMule 2.0.0-rc4 Preview command isn't being run in the same terminal as aMule. As a result, your Preview program may fail to start. This is the case of MPlayer. If you need a terminal to run your Preview player, use some command like ''xterm -e <preview-app>'' i.e.: 
''xterm -T "aMule preview" -iconic -e mplayer -idx''

== After exitting MPlayer on Preview, my aMule keeps locked? ==
Preview used to lock aMule on purpose until aMule reached version 2.0.0-rc4. As a result of this, people using MPlayer suffered from a bug on MPlayer which remains the main process in background when closing the main MPlayer window. The way to walk around this MPlayer bug on aMule versions previous to 2.0.0-rc4 is to exit MPlayer by pressing the '''Q''' key. Any way, it'd be better if you could possibly upgrade aMule to the latest versions.

== Why is ''Transfered'' a smaller number than ''Completed''? ==
It's a common mistake to think it should be bigger or, at least, equal. 
Please read [[FAQ_aMule#What_is_the_difference_between_Transfered_and_Completed_in_the_Tranfers_window?|What is the difference between Transfered and Completed in the Tranfers window?]] to know more about this.

== aMule always slows down my computer when it completes a download. Is this a normal behaviour? ==
Yes it is. When aMule completes a download it checks it has not been corrupted. Allthough this is already checked while downloading (by checking the chunk's hash values), once the file is completely downloaded aMule hashes all the chunks to check that the chunks which were previously downloaded weren't somehow corrupted by the user or an external application while the rest of the file was being downloaded.

== Is there any way to recursively select a whole directory and its contents? ==
Yes, there is. And it's simple:
*On [[aMule]] 2.0.0-rc4 or later, right-click on the icon of the directory you want to recusively select.
*On [[aMule]] 1.x and up to 2.0.0-rc3 (included), while clicking on the directory, hold the CTRL key. 
And that's it.

== I downloaded a file and it got corrupted somehow by my hard disk or some external application once completed. Can I avoid redownloading the whole of it? ==
If you still have the [[ed2k_link|ed2k:// link]], start the download again and when a whole chunk (9.28MB) has been downloaded (any chunk), close [[aMule]], rename the corrupted file to the filename the current download has (something like ''002.part''), touch the corrupted file (i.e.: ''touch ~/.aMule/Temp/002.part*'') and restart [[aMule]]. 
[[aMule]] will detect the completed chunks and the corrupted ones, and will only download the chunks which got corrupted.

== What should I be aware of when using NFS mounts with [[aMule]]? ==

When using NFS mounts with [[aMule]], make sure you unmount those NFS mounts (the ones from the computer being shut down) from the computer running [[aMule]] because, otherwise, [[aMule]] will simply hang until those mounts are back up again. How to notice this? If you leave [[aMule]] running at night, and on the next day you go to the stats and see straight lines for [[Download]]/[[Upload]]/[[Connect]]ions stats (non-zero) and after mounting those NFS mounts, those straight lines drop to zero resuming normal behaviour, that is a sign. Plus, after unmouting the NFS mounts from any computer being shut down, '''reload''' [[aMule]]'s shared files.

''I noticed all this from my frustrating experience of countless days with no downloads at nigh ;) ... --[[User:PedroAlgarvio|PedroAlgarvio]] 00:25, 15 Jun 2005 (CEST)''

AMule problems-es

2005-08-28T17:26:40Z

83.42.86.182:

<center>
<h4>Problemas más comunes en [[aMule_Project_FAQ:About|aMule]]</h4>

<h2>por ''[[User:Jacobo221|Jacobo221]]'' (Traducido por ''[[User:Kno|KNO]]'')</h2>

[[AMule_problems|English]] | '''Español''' | [[AMule_problems-nl|Nederlands]] | [[AMule_problems-hu|Magyar]]
</center>

== Me da un mensaje "aMule already running: exiting" en un terminal cuando arranco aMule. ¿Podré arrancarlo de todas formas? ==
Este mensaje es muy claro: aMule ya esta arrancado. Pero no se refiere al sistema entero, si no que '''tú''' (tu cuenta de usuario) ya está ejecutando aMule. 
Puedes pensar de todas formas que no hay ningún aMule ejecutandose, ya que se colgó. Pero sucede que a veces, algunos procesos no se cierran del todo, quedandose en un estado conocido como ''zombie'' o ''defunc''. Para saber si éste es tu problema ejecuta ''ps u | gre amule'' y si te enseña algo, entonces hay algún otro proceso de aMule ejecutandose con tu cuenta. Para matarlo, puedes cerrarlo normalmente (si puedes) o matarlo con ''kill -9 <aMule_PID>'' o ''killall -9 amule'' o cerrar sesión y entrar de nuevo en el sistema (que en muchos casos mata los procesos de aMule, exepcto si lo has ejecutado con ''nohup'' o algo parecido). 
Si nada de ésto te sirve, puedes ejecutar otro aMules como otro usuario (si puedes entrar en el sistema con otra cuenta, por supuesto). Lee [[FAQ-es#¿Puedo_ejecutar_dos_instancias_de_aMule_al_mismo_tiempo?|¿Puedo ejecutar dos instancias de aMule al mismo tiempo?]].

== aMule arranca pero no se muestra, de todas formas está funcionando bien. ¿Qué está pasando? ==
Esto puede pasar si configuras incorrectamente el tipo de SysTray en Preferencias -> General -> "Integración en Icono del Sistema" y configuras que aMule se minimize en el tray y que arranque minimizado. Asi que te tomaste algo de tiempo en hacerlo, ¿no? 
Para recuperar el GUI de aMule, edita ''~/eMule'', busca ''StartupMinimized=1'' y cambialo por ''StartupMinimized=0''. El siguiente script lo puede hacer por tí (en linux) 
''sed s/StartupMinimized=0/StartupMinimized=1/ ~/.eMule > ~/.eMule.temp && mv -f ~/.eMule.temp ~/.eMule'' 
La próxima vez que arranques amule, configura correctamente la integración con el icono del sistema en las Preferencias para que puedas "Arrancar Minimizado" sin tener aMule oculto. 
Si por alguna razón lo de arriba no funciona, intenta cambiando manualmente la interación con el icono del sistema al valor por defecto "Sin integación en icono del sistema". Para ahcer eso pone el valor ''1'' a ''DesktopMode='' en ''~/.eMule''. El siguiente script lo puede hacer por tí: 
''sed s/DesktopMode=[0-9]/DesktopMode=1/ ~/.eMule > ~/.eMule.temp && mv -f ~/.eMule.temp ~/.eMule'' 

== aMule arranca pero nunca se conecta y se congela o cuelga cada pocos segundos etc... ==
Las versiones de aMule hasta la 2.0.0-rc3 no deben ser linkadas con las librerias wxWidgets 2.5.x nii con GTK2 aunque algunas versiones de Linux lo hacen. Por favor asegurate que no se hace con aMule. Si no estás seguro, pega tu backtrace en [http://www.amule.org/amule/board.php?boardid=33 el foro de Backtraces de aMule] o entra en el cananl de irc de aMule: #amule en irc.freenode.org

== ¿Donde están mis ficheros descargados? ==
Por defecto, aMule guarda los ficheros completados en ''~/.aMule/Incoming'' pero como este directorio es un directorio oculto, puede que tu navegador de ficheros puede no mostrarlo. Asegurate de que el navegador de ficheros muestra los ficheros ocultos. 
Por defecto, los ficheros que estan siendo descargados se colocan en ''~/.aMule/Temp'', asi que de nuevo, este es un directorio oculto y el navegador de ficheros tiene que ser configurado para que muestre los ficheros ocultos.

== ¿Por qué aMule se come tanta CPU al arrancar? ==
Esto ocurre porque aMule esta realizando el hash de los nuevos ficheros encontrados en los directorios compartidos. 
Si aMule siempre se come mucha CPU al arrancar y no hay ficheros nuevos o modificados en tus directorios compartidos es que algo va mal. 
En versiones anteriores a la 2.0.0-rc3 esto solía pasar cuando se tenia el Temp, el Incoming o algún Directorio compartido en una partición FAT32. Desde aMule 2.0.0-rc3 esto no pasa. 
También, en versiones anteriores a la 2.0.0-rc4 en sistemas de ficheros con codificación UTF-8 (se sabe que pasa con SuSE 9.1) puede haber problemas cuando algun fichero o directorio en los Directorios Compartidos contienen caractéres especiales. Si este es tu problema hay un manera de solucionarlos (gracias '''nachbarnebenan'''): después de que aMule haya realizado el hash de todos los ficheros compartidos (esto es, cuando haya parado de consumir casi toda tu CPU), cierra aMule y codifica ~/.aMule/known.met con codificación UTF-8 (puedes hacer ésto con la aplicación ''[http://www.gnu.org/directory/recode.html recode]'' ejecutando el siguiento comando: ''recode u8 ~/.aMule/known.met''). Esto lo debes hacer cada vez que añadas o modifiques algún fichero en algún Directorio Compartido. Así que la mejor opción es actualizar a la última versión de aMule. 
Si nada de lo anterior te sirve, entonces algo está yendo rematadamente mal en el fichero ''known.met'', probablemente algún programa o usuario externo lo rompe. La mejor opción es borrarlo y reiniciar aMule dejandole que haga el rehash de nuevo.

== Bueeeno, ahora aMule arranca, pero ¿Porque me saca este mensaje: "No hay servidores válidos en la lista de servidores" cuando si que los hay? ==
Esto es por que has activado la opción "Autoconectar sólo a servidores fijos". Así que desactívala o añade algún servidor a lista de servidores fijos. 
Para desactivar esta opción, ve a Preferencias -> Servidor -> "Autoconectar sólo a servidores fijos".
Para añadir un servidor a la lista de fijos, ve a la ventana de Servidores y pincha con el botón derecho en el servidor que quieres añadir a la lista de servidores fijos. Entonces selecciona "Añadir a la lista de servidors fijos" y haz lo mismo para todos los servidores que quieras añadir a la lista de servidores fijos.

== aMule se conecta a los servidores, pero siempre obtiene LowID. ¿Por que? Y, ¿Puedo hacer algo al respecto? ==
Esto puede pasar por tres razones:
<ul><li>Te falta abrir alguno de los puertos en tu router/firewall. Lee [[FAQ_eD2k-Kademlia-es#%C2%BFQu%C3%A9_es_ID_baja_e_ID_alta?|esto]] para saber como lo puedes hacer.</li>
<li>El servidor esta ocupado o está mal configurado, y por eso obtienes LowID. Lo único que puedes hacer es reconectarte o conectarte a otro servidor.</li>
<li>Algunos ISP limitan las aplicaciones del tipo P2P, como aMule, no permitiendo el tráfico a través de sus puertos más corrientes. En este caso configura aMule para que use cualquier otro puerto.</li></ul>
Para conocer si se tiene abiertos o no los puertos, se puede visitar la [http://www.amule.org/testport.php página de tests de puertos].

== [[aMule]] se interrumpió cuando completaba un archivo y ahora nunca lo completa (aunque está descargado al 100%). ¿Como puedo completarlo? ==
Este es fácil: Cierra [[aMule]]. Ahora ve al directorio Temp (por defecto, ''~/.aMule/Temp'') y ejecuta el siguiente comando:

''touch ./*''

Finalmente, arranca [[aMule]] y dejalo completar el archivo.

== Perdí una descarga. ¿Hay alguna manera de recuperarla? ==
Es extraño que esto suceda, pero es posible, aunque en la mayoría de los casos es porque algo no relacionado con aMule ha fallado (o por culpa del usuario). 
Han podido pasar dos cosas. O bien los ficheros *.part.met o los *.part han sido borrados. 
Si han desaparecido los *.part, la única solución es comenzar la descarga desde el principio (si aún existen los *.part.met aMule comenzará las descargas la próxima vez que lo arranques). Sin embargo esto '''nunca''' debería haber pasado si el usuario no los hubiera borrado. 
Si los *.part.met han desaparecido pero los *.part continuan en el directorio temporal, comprueba si los *.part.met.bak existen en el directorio. Si existen, solo renombra los ''*.part.met.bak'' a ''*.part.met'' ejecutando: 
''for file in *.part.met.bak; do mv -f "$file" "${file%.bak}; done'' 
También puede pasar que aunque tengas los ficheros *.part, ni los ficheros *.part.met ni los *.part.met.bak existan. En este caso, tendrías dos opciones: 
Usa [http://www.bigwillystyle42.com/document.php?dest=mfr MetFileRegenerator] (requiere Java) para reconstruir los ficheros *.part.met. 
O, vuelve a buscar en aMule los ficheros que estabas descargando y renombra sus ficheros *.part.met files a los que estabas usando. Por ejemplo, si estabas descargando ''aMule_1.2.6.tar.gz'' en el directorio temporal como ''008.part'', este fichero debería tener su correspondiente fichero ''008.part.met'' y, probablemente, su fichero ''008.part.met.bak''. Pero estos dos ficheros han desaparecido misteriosamente. Vuelve a buscar en aMule ''aMule_1.2.6.tar.gz'' y comienza a descargarlo. Cierra aMule y tendrás esta nueva descarga como, por ejemplo, ''011.part'' en el directorio temporal. Obviamente esta descarga tendrá su fichero ''011.part.met''. Renombra ''011.part.met'' a ''008.part.met'' y borra el fichero ''011.part'' (y ''011.part.met.bak'' si es que existe). Arranca aMule y habrás recuperado la descarga desde donde se encontraba antes de que los ficheros *.part.met hubieran desaparecido.

== ¿Por qué aMule de repente no responde al ratón apesar de que no esta colgado? ==
A veces pasa que dejas una ventana abierte y escondida en algún sitio del escritorio. [[aMule]] espera a que esa ventana se cierre, asi que no responde hasta que pinches en OK, Candel o donde tengas que pinchar. 
Así que asegurate de que no hay ninguna ventana de [[aMule]] en '''ningún Escritorio'''.

== ¿Por qué algunos archivos en mi carpeta de compartidos no se muestran en la ventana de ''Archivos Compartidos''? ==
Esto puede pasar si añades estos archivos despues de que [[aMule]] se ha iniciado. Pulsa en el botón 'Recargar' (unas flechas verdes) de la ventana de ''Archivos Compartidos'' y se buscarán los nuevos ficheros y se calculará su hash (esto consumirá bastante tiempo de CPU).

Aún así, en algunas versiones pasa que despues de reiniciar [[aMule]], algunos ficheros desaparecen de la ventana de ''Archivos Compartidos'', apesar de que estan en el directorios compartidos. En estos casos la única manera de tenerlos de nuevo es borrar el fichero ''~/.aMule/known.met'' pero, por supuesto, cuando arranques [[aMule]] la siguiente vez, todos los archivos compartidos serán rehaseados y llevará bastante tiempo.

== Siempre tengo un mensaje sobre addresses.met cuando inicio aMule. ¿Qué está mal? ==
Esto pasa cuando activas la opción Preferencias -> Servidor -> "Actualizar automaticamente la lista de servidores al iniciar" y no tienes direcciones de listas de servidores en el fichero ''addresses.dat''. Puedes añadir alguna a ''addresses.dat'' en Preferencias -> Servidor -> Lista o simplemente deshabilitar Preferencias -> Servidor -> "Actualizar automaticamente la lista de servidores al iniciar" si no lo necesitas.

== A veces tengo un mensaje en el log sobre perdida de créditos. ¿Debería preocuparme? ==
No, no deberias preocuparte. Los creditos para un cliente se borran despues de 150 dias (mas o menos 5 meses) sin "ver" a ese cliente. También se borran los créditos de los clientes "malos" (leechers). Estos mensajes son únicamente información de depurado, así que no te preocupes por ellos.

== ¿Qué debo hacer si pierdo mi archivo ''cryptkey.dat''? ==
Al perder este archivo automáticamente pierdes los créditos, se siente :(
Si quieres comenzar a recuperar créditos de nuevo desde este momento, borra también ''~/.aMule/preferences.dat''. Si no lo haces, no obtendrás créditos en los [[client-es|clientes]] que te hayan identificado alguna vez (antes de perder el fichero ''cryptkey.dat'').

== ¿Por qué mis Límites de Subida/Descarga vuelven siempre a 0 despues de cada reinicio? ==
Esto pasaba en versiones de aMule anteriores a la 2.0.0-4c4 cuando intentabas poner un valor de Límite de Subida o Descarga mayor que los valores de Capacidad de Subida y Descarga.
En cualquier caso, está arreglado desde la versión 2.0.0-rc4 (lee [[FAQ_aMule-es#¿Cual es el verdadero significado de Capacidad en Preferencias? ¿No se debería preocupar aMule únicamente de los Límites?|¿Cual es el verdadero significado de Capacidad en Preferencias? ¿No se debería preocupar aMule únicamente de los Límites?]] para entender por qué) y no debería pasar más.

== ¿Por qué está amule ignorando el ancho de banda que configuro por slot? ==
El ancho de banda por cada slot se configura en las Preferencias, pero será ignorado si el ancho de banda por slog do permite al menos tres conexiones al mismo tiempo. 
Así, que la máxima velocidad por slot es '''LímiteSubida/3'''. 
Por favor, '''NO''' confundas '''Límite Subida''' con '''Capacidad de Subida'''.
Lee [[FAQ_aMule-es#¿Cual es el verdadero significado de Capacidad en Preferencias? ¿No se debería preocupar aMule únicamente de los Límites?|¿Cual es la utilidad de el valor Capacidad en las Preferencias?]] ya que el significado de Capacidad de Subida no es intuitivo.

== ¿Por que no puedo configurar el límite de descarga a un valor mayor que X? ==
Para que la red ED2K siga funcionando, todos los clientes ED2K tienen programados unos límites que, dependiendo en la limitación de la subida, son:

De 1KBps a 3KBps: 
LimiteDescarga no puede ser mayor que LimiteSubida*3 
De 4KBps a 9KBps: 
LimiteDescarga no puede ser mayor que LimiteSubida*4 
Valores para la subida mayores que 9KBps: 
No hay límites en la velocidad de descarga.

Ten cuidado configurando el límite de descarga a 0KBps. Puede no significar lo que tu crees. Lee [[AMule_problems-es#He_configurado_el_límite_de_subida_a_0KBps,_pero_aMule_sigue_transferiendo._¿Que_he_hecho_mal?|He configurado el límite de subida a 0KBps, pero aMule sigue transferiendo. ¿Que he hecho mal?]] para entender su significado.

== He configurado el límite de subida a 0KBps, pero aMule sigue transferiendo. ¿Que he hecho mal? ==
Configurar el límite de subida a 0KBps no detiene la transferencia, sino que, ''0KBps'' significa '''ilimitado''', vamos, justo lo contrario a lo que tu quieres hacer. No hay manera de evitar que aMule suba ficheros, y esto es igual para todos los clientes ED2K (eMule, eDonkey, etc). Permitir que la gente no suba nada llevaría a la red ED2K a su final. 
Incluso si tú no compartes ningún directorio, el directorio Temp '''siempre''' se comparte, por lo tanto los ficheros que tú te estas bajando se comparten con otros clientes.

== ¿Por qué estoy teniendo un mensaje de "Too many connections" (Demasiadas conexiones) en el terminal? ==
Esto pasa cuando configuras un valor muy alto en Preferencias -> Conexión -> Límites -> "Conexiónes Máximas". Si este valor es mayor que el valor de conexiones que permite tu sistema, aMule fallará al establecer conexiones y mostrará estos mensajes (ten en cuenta que otras aplicaciones pueden tener conexiones abiertas). 
En Windows 9x/Me hay un límite de 100 conexiones TCP, así que debes configurar aMule para que no establezca mas de 100 conexiones TCP, ya que no podrá estableceras. Puedes cambiar el límite de conexiones de Windows editando el Registro ('''Inicio -> Ejecutar -> regedit.exe''') y configurando (seguramente tengas que añadir el valor, ya que normalmente no existe): 
''HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections'' 
(que es un de tipo String y su valor debe ser un número de 32-bits).

== Mi barra de progreso casi todo su efecto 3D y se ve muy fea. ¿Puedo ponerla como antes? ==
En casi todas las versiones de aMule colocando la barra deslazadora de Preferencias -> "GUI tweaks" -> "Estilo de la Barra de Progreso" a la derecha, la barra de progreso tendrá su apariencia 3D, pero en las versions entre la 2.0.0-rc4 y la 2.0.0-rc6 deberas colocarla en medio para que tenga el mismo efecto. En estas versiones, poniendola a la derecha, la barra de progreso se verá plana y poniendola en la izquierda se verá oscura.

== De repente todas mis descargas se han parado y no puedo reiniciarlas. ¿Qué está pasando? ==
Comprueba si hay espacio libre en el sistema de ficheros donde está el directorio Temporal. Si sí que lo hay, comprueba que hay más que lo que está configurado en Preferencias -> Archivos -> "Mínimo espacio en Disco".
El espacio mínimo que necesita [[aMule]] es 9.28MB, ya que es lo que [[aMule]] necesita para descargar una [[FAQ_ed2k-es#¿Qué es un chunk?|parte]] de un fichero.

== ¿Por qué no puedo previsualizar un archivo? ==
Ante todo debes saber que aMule solo permite previsualizar archivos de video.

Para poder previsualizar un archivo aMule requiere dos cosas:
*El archivo debe tener una extensión de video conocida (en el nombre de archivo)
*Debe haber bajado los primeros 256KB del archivo

De todas maneras, puede ocurrir que el archivo se pueda previsualizar, pero que aMule no lo permita. En este caso, ve al directorio Temp y previsualiza manualmente, si puedes y lo deseas.

== ¿Por qué no está funcionando la Previsualización con MPlayer? ==
Desde aMule 2.0.0-rc4 el comando Previsualizar no se ejecuta en el mismo terminal que aMule. Como resultado, tu programa de Previsualización falla al arrancar. Este es el caso de MPlayer. Si necesitas un terminal para ejecutar tu reproductor, usa un comando como ''xterm -e <previsualizador>'' por ejemplo: 
''xterm -T "Previsualizador de aMsn" --iconic -e mplayer -idx''

== Despues de salir del MPlayer en una Previsualización, mi amule se queda bloqueado ==
Este bloqueo se usaba en aMule durante la Previsualización hasta la versión 2.0.0-rc4. Como resultado al usar MPlayer y debido a un bug en MPlayer que mantenia el proceso principal en background cuando se cerraba la ventana principal de MPlayer, se bloqueaba aMule. Para evitar este bug del MPlayer se puede salir del MPlayer con la tecla '''Q'''. En cualquier caso, lo mejor es actualizar a la última versión de aMule.

== ¿Por qué lo ''Transferido'' es menor que lo ''Completado''? ==
Es un error común pensar que debería ser mayor, o al menos, igual. 
Por favor lee [[FAQ_aMule-es#¿Cual es la diferencia entre Transferido y Completado en la ventana de Tráfico?|¿Cuál es la diferencia entre Transferido y Complatado en la ventana de Tráfico?]] para saber más sobre ésto.

== aMule siempre hace que mi ordenador vaya lento cuando completa una descarga. ¿Es esto un normal? ==
Si. Cuando aMule completa una descarga comprueba que no hay errores.
A pesar de que ésto se comprueba mientras se está descargando (comprobando los hash de cada chunk), una vez que el fichero se ha completado aMule realiza el hash de todos los chunks para comprobar que los chunks que se han descargado no han sido alterados de alguna manera por el usuario o por una apliación externa mientras se descargaba el resto del archivo.

== ¿Es posible seleccionar un directorio completo y su contenido de forma recursiva? ==
Si. Y es fácil: Mientras haces pinchas en el directorio, pulsa la tecla CTRL. 
Y ya está

== He descargado un archivo y se ha estropeado de alguna manera, por mi disco duro o por alguna apliación externa, despues de terminarlo. ¿Podría evitar tener que descargarme todo el archivo de nuevo? ==
Si aun tienes el [[ed2k_link|enlace ed2k://]], comienza a descargarlo de nuevo y cuando tengas un chunk completo (9.28MB) cierra [[aMule]], renombra el archivo corrupto al nombre temporal de la actual descarga (algo como ''002.part''), haz touch sobre el archivo corrupto (por ejemplo: ''touch ~/.aMule/Temp/002.part*'') y reinicia [[aMule]]. 
[[aMule]] detectará los chunks completos y los estropeados, y solo descargará los chunks que estén estropeados.

AMule problems

2005-08-28T17:22:50Z

83.42.86.182:

<center>
<h4>[[aMule_Project_FAQ:About|aMule]] common problems</h4>

<h2>by ''[[User:Jacobo221|Jacobo221]]''</h2>

'''English''' | [[AMule_problems-es|Español]] | [[AMule_problems-nl|Nederlands]] | [[AMule_problems-hu|Magyar]]
</center>

== I get an "aMule already running: exiting" message on the terminal when starting aMule. Will I be able to start it anyways? ==
The message is very clear: [[aMule]] is already running. But this doesn't refer to the entire system, rather that '''you''' (your user account) is already running [[aMule]].

It might seem that there is no instance of [[aMule]] running if it crashed on you. However, what sometimes happens is that some processes aren't completly closed keeping them in a state known as ''zombie'' or ''defunct''. To find out if this is your problem, run ''ps u | grep amule'' and if it shows any output (except the grep output itself), then there's some other aMule process running with your account. To kill it, either close it normally (if you can) or kill it with ''kill -9 <aMule-PID>'' or ''killall -9 amule'' or logoff and log in again (which, in most cases, will kill all [[aMule]] processes, unless you executed [[aMule]] with ''nohup'' or something similar).

If non of the above suits you, then you can run another instance of [[aMule]] as another user (if you can log in with another account, of course). Read [[FAQ_aMule#Can_I_run_two_aMule_instances_at_the_same_time?|Can I run two aMule instances at the same time?]].

== aMule starts but is never shown but works fine. What's going on? ==
This commonly happens when you set the type of systray integration, in Preferences -> General -> Misc Options, to ''Minimize to trayicon'' which starts [[aMule]] minimized. 
To be able to recover aMule's GUI, edit ''~/.aMule/amule.conf'' and search for ''StartupMinimized=1'' and once you find it, change that line to ''StartupMinimized=0''. The following script will do that for you: 
''sed s/StartupMinimized=1/StartupMinimized=0/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf'' 
When you next start [[aMule]] set the correct systray integration in Preferences so that you can enable "Start minimized" without having [[aMule]] hidden. 
If, for some reason, the above didn't work, try changing the Systray integration manually to the default by unchecking the "Enable tray icon'' option. To do so, set the ''DesktopMode='' value in ''~/.aMule/amule.conf'' to ''4''. The following script will do that for you: 
''sed s/DesktopMode=[0-9]/DesktopMode=4/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf'' 
'''NOTE:''' On [[aMule]] versions previous to 2.0.0rc4, you should set it to ''1'' instead of ''4'' since the Preferences storage changed a little.

== aMule starts but is never connecting/behaving very weird/crashing almost every few seconds/etc...? ==
aMule versions up to 2.0.0-rc3 shouldn't be linked against wxWidgets 2.5.x neither GTK2 although some Linux distributions tend to do so. Please make sure your aMule isn't the case. If unsure, paste you backtrace at [http://www.amule.org/amule/board.php?boardid=33 aMule's Backtraces forum] or join aMule's IRC channel #amule at irc.freenode.net

== Where are my downloaded files? ==
By default, aMule stores completed files in ''~/.aMule/Incoming'' but, since ''~/.aMule'' directory is a hidden directory, your file manager might not show it. Make sure you have enabled your file manager to show hidden files. 
By default, files being downloaded are placed in ''~/.aMule/Temp'', so again, this is a hidden directory and the file managed must be configured to show hidden files.

== Why is aMule taking so much CPU resources at start-up? ==
This happens because aMule is hashing new files found on the Shared Directories. If aMule is always taking a lot of CPU at startup and no new files have been added or modified in any way in the Shared Directories, then something is wrong.

In aMule versions earlier than 2.0.0-rc3 this used to happen when having the Temp, Incoming or any Shared Directory in a FAT32 partition. Since aMule 2.0.0-rc3 this is not happening any more.

Also, in aMule versions earlier than 2.0.0-rc4 filesystems with UTF-8 encoding (known to happen with SuSE 9.1) could present problems when some file or directory in the Shared Directories path contanied a special character. If this is your problem, there's a walkaround (thanks '''nachbarnebenan'''): after aMule has hashed all shared files (that is, when it stops taking a lot of your CPU's resources), close aMule and enconde ~/.aMule/known.met into UTF-8 encoding (you can do this with the application ''[http://www.gnu.org/directory/recode.html recode]'' by running the following command: ''recode u8 ~/.aMule/known.met''). This should be done whenever a files is added or modified in any Shared Directory. So, best option is to upgrade to latest aMule version.

If non of the above helps you, then something went really wrong on ''known.met'' file, probably some external program or user broke it. Best option is to delete it, start aMule and let aMule rehash all files again.

== So now aMule starts, but why is it displaying this message: "No valid servers to connect in serverlist found"? ==
That's because you enabled the option "Auto connect to servers the static list only". So, disable it or add some server to the static list. 
To disable that option, go to Preferences -> Servers -> "Auto connect to servers the static list only" 
To add a server to the static list, go to the Servers window and right-click on the server you want to add to the static list. Then select "Add to static" and do this exact process wit all the servers you want to add to the static list.

== aMule connects to server, but it is always given Low-ID. Why? and, can I do something about it? ==
This can bue due to three reasons:
<ul><li>Some necessary port is not opened in your firewall. Read [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|this]] to get to know what to do and check [http://www.amule.org/testport.php here] if the ports are open.</li>
<li>The server is very busy or maybe badly configured, so it's giving you a [[Low-ID]]. There's nothing that can be done in this case other than reconnect or connect to some other server.</li>
<li>Some ISP forbid the use of p2p applications, such as aMule, by not allowing traffic through popular p2p ports. In these cases, configure aMule to use some other port. It would be even better if it was some popular port used for some other issue. It's been known that on some ISPs it worked with port TCP 25600.</li></ul>

== [[aMule]] was interrupted while completing a file and it is now never completing it (allthough it's 100% downloaded). How can I complete it? ==
This one is easy: Close [[aMule]]. Now go into the Temp directory (by default, ''~/.aMule/Temp'') and run the following command:

''touch ./*''

Finally, run [[aMule]] and let it complete the files.

== I just lost a download. Is there anyway I can recover it? ==
This is strange to happen, but it might, although in most cases it is the result of some non-aMule-related stuff going weird (or user's fault). 
Two things may have happened. Either *.part.met files were deleted, or *.part files were deleted. 
If *.part files have dissapeared, the only solution is to reastart the downloads from the beggining (if *.part.met files are still there, aMule will restart the downloads on next start). However this should '''never''' happen unless the user directly deleted them. 
If *.part.met files have dissapeared but *.part files are still in the Temp directory, then search if *.part.met.bak are also in the Temp directory. If they are, then just rename ''*.part.met.bak'' files to ''*.part.met'' just by running: 
''for file in *.part.met.bak; do mv -f "$file" "${file%.bak}; done'' 
Still, it could happen that, although you have the *.part files, neither *.part.met nor *.part.met.bak files exist any longer. In this case, you would have two ways ways to work out of this: 
Either, use [http://www.bigwillystyle42.com/index.php?dest=mfr MetFileRegenerator] (Java needed) to reconstruct the *.part.met files. 
Or, search again on aMule for the files you were downloading and rename their part number in the *.part.met files to the ones it used to have. For example, if you ware down loading ''aMule_1.2.6.tar.gz'' and that was being downloaded in Temp directory as ''008.part'', then that file used to have it's corresponding ''008.part.met'' file and, probably, it's ''008.part.met.bak'' file. But this two latter files have misteriously dissapeared. Then search again on aMule for ''aMule_1.2.6.tar.gz'' and start downloading it. Close aMule and you'll have this new download as, for example, ''011.part'' file in the Temp directory. Of course, this download will have it's ''011.part.met'' file. Well, rename ''011.part.met'' to ''008.part.met'' and then delete ''011.part'' (and ''011.part.met.bak'' if it existed). Now start aMule and you will have recovered the download from the point it was before the *.part.met files disapeared.

== Why does aMule suddendly become unresponsive to the mouse although it's not hanged? ==
It sometimes happens that you left a dialog window somewhere hidden in the desktop. aMule is waiting for that window to be closed, so it becomes unresponsive untill you click OK, Cancel, or whatever you have to click. 
So, make sure there's no aMule dialog left around in '''any workspace'''.

== Why are some files in my shared folders not shown in the Shared Folders window? ==
This could happen if you added this files after aMule has been started. Press the "Reload" button on Shared Folders window and it should find the new files and hash them (this may take some CPU time).

However, on some releases it has happened that after restarting aMule, some files dissapear from the Shared Folders window alllthough they are in the shared folders. In such cases, the only way to have them back is to delete ''~/.aMule/known.met'' but, of course, on next aMule start, all shared files will have to be rehashed, and that'll take some time most probably.

== I always get a message about addresses.met when I start aMule. What's wrong? ==
This happens when you enable the option Preferences -> Servers -> "Auto-update serverlist at startup" and you have no serverlists' urls in ''addresses.dat''. You can either add some to ''addresses.dat'' by adding them at Preferences -> Servers -> List or just disable Preferences -> Servers -> "Auto-update serverlist at startup" if you don't really need it. 

== I sometimes get a message on the log about credits being lost. Should I be worried? ==
No, you don't need to be worried. Credits for a client are deleted after 150 days (more or less 5 months) without "seeing" that client. Also, bad clients might lose their credits too. So those messages are just for debug information, you souldn't worry about them.

== What should I do if I lose my ''cryptkey.dat'' file? ==
Losing this files means you lose all of your credits. Sorry. Since you'll need to start building credits up again, you'll need to delete ''~/.aMule/preferences.dat'' or you'll not be able to collect credits on [[client|clients]] who have previously identified you (prior to losing cryptkey.dat).

== Why is Upload/Download limit always back to 0 after every restart? ==
This happened on aMule versions previous to 2.0.0-rc4 when you trying to set a Upload or Download limit value higher than the Upload or Download Capacity value. However, since version 2.0.0-rc4 this is fixed (read [[FAQ_aMule#What_is_the_real_point_on_setting_up_Line_Capacities_in_Preferences?_Shouldn't_aMule_only_care_for_the_Bandwidth_Limits?|What is the real point on setting up Line Capacities
in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] to understand why) and shouldn't happen anymore.

== Why is aMule ignoring the bandwith I set per slot? ==
The bandwidth set to each slot can be set in Preferences, but it will be ignored if the bandwidth set per slot doesn't allow at least three connections at the same time. 
So, the maximum speed allowed per slot is '''BandwidthLimit/3'''. 
Please do '''NOT''' confuse '''Bandwidth limit''' with '''Bandwith Capacity'''. Read [[FAQ_aMule#What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?|What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] since the meaning of the Bandwidth Capacity setting is not intuitive. 
Also, if [[aMule]] detects that, after having set all the slots for uploading, still some bandwidth is left before getting to the Bandwidth Limit, it will allow another slot and divide all the slot bandwidths to so use the same amount of bandwidth. 

Example: 
Bandwidth Limit: 7 KBps
Slot allocation: 2 KBps
When [[aMule]] sets the slots to some clients to upload to them, after giving out three slots, it will notice that tehre are no more 2KBps left, since the limit is 7 KBps, but there is still 1 KBps left in the bandwicth before reaching the Bandwidth Limit. So, It will allow another slot to upload to a client and, isntead of giving that last slot a 1 KBps bandwidth connection (and leave the rest with a 2 KBps bandwidth connetcion), it will give all four slots a 1.8 KBps bandwidth connection.

== Why can't I set aMule's download limit to more than X? ==
To keep the ED2K network alive, all ED2K clients have an upload/download limits ratio hardcoded which, depending on the upload limit set, is:

From 0KBps to 3KBps: 
DownloadLimit can't be more than UploadLimit*3 
From 4KBps to 9KBps: 
DownloadLimit can't be more than UploadLimit*4 
UploadLimit values over 9KBps: 
There's no DownloadLimit limitation.

Be carefull when setting 0KBps as Upload Limit . It might not mean what you think it is. Read [[AMule_problems#I_set_Upload_Limit_to_0KBps,_but_aMule_is_still_transfering._What_did_I_do_wrong?|I set Upload Limit to 0KBps, but aMule is still transfering. What did I do wrong?]] to make sure you understand it's meaning.

== I set Upload Limit to 0KBps, but aMule is still transfering. What did I do wrong? ==
Setting Upload limit to 0KBps will not stop transfers, instead, ''0'' value means '''unlimited''', so, it's right the opossite of you're trying to do. There's no way to stop aMule from uploading files, and that's the same on all ED2K clients (eMule, eDonkey, etc). Allowing people not to upload would bring the ED2K network to it's end. 
Even if you don't share any directory, the Temp directory will '''always''' be shared, so that files that you are downloading are shared with other clients.

== Why am I getting "Too many connections" messages on the terminal? ==
This happens when you set a very high value at Preferences -> Connections -> "Connection limits" -> "Max connections". If this value is as almost as big as the the amount of connections your system allows you to have, then aMule will fail to establish connections and display those messages (have in mind that other applications may also have some connections established). 
On Windows 9x/ME platforms there is a limit of 100 TCP connections so, although you might set aMule to establish more than 100 connections, it will be unable to do so. You can change Windows's TCP connections limit by editting the Windows Register ('''Start -> Run -> regedit.exe''') and setting (you'll most surely have to add the value since in most cases it doesn't exist): 
''HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections'' (which is a String type and it's value must be a 32-bit number).

== My progress bars have lost most of their 3D effect and look more ugly now. Can I turn its look back? ==
In most aMule versions setting the progress bar style to the most right on Preferences -> "GUI tweaks" is the way to have the progress bar have the best 3D effect. But in versions 2.0.0-rc4 to 2.0.0-rc6 the best 3D effect is given when the style bar is set to the middle. Setting it to the most right would give the progress bar a flat look while setting it to the most left will give it a dark look.

== All my downloads suddenly paused and I can't resume them. What's going on? ==

Check if there's any free space in the filesystem where the Temp directory is placed. If there is any at all, check if there's more free space than the minimum free space set at Preferences -> Files -> "Min disk space".

The minimum free space required for [[aMule]] is 9.28MB, since that's what [[aMule]] needs to be able to download a [[FAQ_ed2k#What_is_a_chunk?|part]] of a file.

== Why can't I preview a file? ==
First of all you must know that [[aMule]] only allows to preview video files.

To be able to preview a file [[aMule]] requieres two this:
*The file must have a known video extension in it's filename
*You must have downloaded the first 256KBs of the file

Anyway, sometimes it happens that the file is previewable though [[aMule]] doesn't allow you. In that case, go to the Temp directory and preview them manually, if you can and wish.

== Why isn't [[aMule]]'s Preview working at all with MPlayer? ==
Since aMule 2.0.0-rc4 Preview command isn't being run in the same terminal as aMule. As a result, your Preview program may fail to start. This is the case of MPlayer. If you need a terminal to run your Preview player, use some command like ''xterm -e <preview-app>'' i.e.: 
''xterm -T "aMule preview" -iconic -e mplayer -idx''

== After exitting MPlayer on Preview, my aMule keeps locked? ==
Preview used to lock aMule on purpose until aMule reached version 2.0.0-rc4. As a result of this, people using MPlayer suffered from a bug on MPlayer which remains the main process in background when closing the main MPlayer window. The way to walk around this MPlayer bug on aMule versions previous to 2.0.0-rc4 is to exit MPlayer by pressing the '''Q''' key. Any way, it'd be better if you could possibly upgrade aMule to the latest versions.

== Why is ''Transfered'' a smaller number than ''Completed''? ==
It's a common mistake to think it should be bigger or, at least, equal. 
Please read [[FAQ_aMule#What_is_the_difference_between_Transfered_and_Completed_in_the_Tranfers_window?|What is the difference between Transfered and Completed in the Tranfers window?]] to know more about this.

== aMule always slows down my computer when it completes a download. Is this a normal behaviour? ==
Yes it is. When aMule completes a download it checks it has not been corrupted. Allthough this is already checked while downloading (by checking the chunk's hash values), once the file is completely downloaded aMule hashes all the chunks to check that the chunks which were previously downloaded weren't somehow corrupted by the user or an external application while the rest of the file was being downloaded.

== Is there any way to recursively select a whole directory and its contents? ==
Yes, there is. And it's simple:
*On [[aMule]] 2.0.0-rc4 or later, right-click on the icon of the directory you want to recusively select.
*On [[aMule]] 1.x and up to 2.0.0-rc3 (included), while clicking on the directory, hold the CTRL key. 
And that's it.

== I downloaded a file and it got corrupted somehow by my hard disk or some external application once completed. Can I avoid redownloading the whole of it? ==
If you still have the [[ed2k_link|ed2k:// link]], start the download again and when a whole chunk (9.28MB) has been downloaded (any chunk), close [[aMule]], rename the corrupted file to the filename the current download has (something like ''002.part''), touch the corrupted file (i.e.: ''touch ~/.aMule/Temp/002.part*'') and restart [[aMule]]. 
[[aMule]] will detect the completed chunks and the corrupted ones, and will only download the chunks which got corrupted.

== What should I be aware of when using NFS mounts with [[aMule]]? ==

When using NFS mounts with [[aMule]], make sure you unmount those NFS mounts (the ones from the computer being shut down) from the computer running [[aMule]] because, otherwise, [[aMule]] will simply hang until those mounts are back up again. How to notice this? If you leave [[aMule]] running at night, and on the next day you go to the stats and see straight lines for [[Download]]/[[Upload]]/[[Connect]]ions stats (non-zero) and after mounting those NFS mounts, those straight lines drop to zero resuming normal behaviour, that is a sign. Plus, after unmouting the NFS mounts from any computer being shut down, '''reload''' [[aMule]]'s shared files.

''I noticed all this from my frustrating experience of countless days with no downloads at nigh ;) ... --[[User:PedroAlgarvio|PedroAlgarvio]] 00:25, 15 Jun 2005 (CEST)''

Server.met file

2005-08-28T17:00:44Z

83.42.86.182:

== File ==

'''Name:''' ''server.met''

'''Location:''' ''~/.aMule/''

== Description ==

Binary file containing the list of [[server]]s known to [[aMule]].

Because its in binary format, it must be changed within [[aMule]], or with other appropriate tools.

The format description below is for development information purposes.

== Format ==

=== File Format ===

This file's fields are written in [[little endian]] order.

'''Note:''' All digit fields are unsigned unless stated.

*Met Header (1 Byte): With value ''Ox0E'' or ''OxE0'', and is used in [[aMule]] to check for valid ''server.met'' files
*Server Count (4 Bytes): Lists the number of [[server]]s that follow
*Block of servers: Each [[server]] is constituted by the following fields:
**[[Server]] [[IP]] (4 Bytes): Simply that. The [[server]]'s [[IP]].
**[[Server]] [[Port]] (2 Bytes): Simply that. The [[port]] through which [[aMule]] will connect to the [[server]].
**Tag Count (4 Bytes): Lists the number of [[server]] tags that follows.
**Block of Tags: Each [[server]] can have a list of associated tags with the format bellow.

=== Tags Format ===

==== General tags format ====

There are two tag identifiers: A name (string) and an ID (1 Byte)

Which one is used depends on the tag value type given or on the size of the tag name. If tag name length is ''1'', an ID is used.

*Tag value type (1 Byte)
*Tag name length (2 Bytes)
*Tag name (size given above)
*Tag value length (2 Bytes) (Only when the value is a string)
*Tag value (if the value is a string, it's size is given in the above field. If it is not a string, the size depends on the type of value it is)

==== Tag value types ====

{|
|+ Tag types
| '''Tag type (''Code'')''' || '''Explanation'''
|-
| String (''0x02'') (*) || Defines a string tag.
|-
| Unsigned 32 bits number (''0x03'') || Defines a numeric tag.
|}

'''(*):''' Systems with [http://www.unicode.org Unicode] enabled have the same tag string defined twice, the first in [http://www.unicode.org Unicode], and the second in plain [http://www.asciitable.com ASCII], which will be ignored by [http://www.unicode.org Unicode] enabled [[client]]s, and used by non-[http://www.unicode.org Unicode] ones.

==== Tag IDs ====

{|
|+ Tag IDs
| ''ID ('''code''')'' || ''Tag value type'' || ''Description''
|-
| ServerName (''0x01'') || String || Name of the [[server]]
|-
| Description (''0x0B'') || String || Short description about the server
|-
| Ping (''0x0C'') || Unsigned 32 bits number || Time (in ms) it takes to comunicate with the server
|-
| Fail (''0x0D'') || Unsigned 32 bits number || How many times [[connect]]ing to the server failed
|-
| Preference (''0x0E'') || Unsigned 32 bits number || Priority given to this server among the others (Normal=''0'', High=''1'', Low=''2'')
|-
| DNS (''0x85'') || String || [http://en.wikipedia.org/wiki/DNS DNS] of the server
|-
| Max users (''0x87'') || Unsigned 32 bits number || Maximum number of users the server allows to simoultaneously connect to it
|-
| Soft files (''0x88'') || Unsigned 32 bits number || [[Soft files]] number
|-
| Hard files (''0x89'') || Unsigned 32 bits number || [[Hard files]] number
|-
| Last ping (''0x90'') || Unsigned 32 bits number || Last time the server was [[ping]]ed
|-
| Version (''0x91'') || String / Unsigned 32 bits number || Version and name of the software the server is running to support the [[FAQ_ed2k|ed2k]] [[network]]
|-
| [http://www.ietf.org/rfc/rfc768.txt UDP] flags (''0x92'') || Unsigned 32 bits number || Informs of the actions the server accepts through [http://www.ietf.org/rfc/rfc768.txt UDP] connections. This flags are:
*''0x01'': Get sources
*''0x02'': Get files
*''0x08'': New tags
*''0x10'': Unicode
*''0x20'': Get extended sources info
|-
| Auxiliary [[port]]s list (''0x93'') || String || Some servers have additional ports open for those [[user]]s who cannot connect to the standard one (usually because they have a firewall which tries to stop [[P2P]] connections). This servers tell in this field which additional ports they have open. Each additional port is separated from the others by a coma ('','').
|-
| [[LowID]] [[client]]s (''0x94'') || Unsigned 32 bits number || Number of users connected with a LowID
|}

==== Tag Names ====

{| border=0
|+ There are at the moment two tag names recognized by [[aMule]]:
| width="100px" | ''Tag Name'' || ''Tag Value''
|-
| "files" || Unsigned 32 bits number || Shows the number of [[file]]s registered in the [[server]]
|-
|"users" || Unsigned 32 bits number || Shows the number of [[user]]s registered in the [[server]]
|}

== Example ==

The following is an example file:

''E00200000050EFC86CB80B0C000000020100010A004269472042616E4720390201000B0E0077''
''77772E42694742616E472E746F0305007573657273EF1A010003050066696C657331DC8C0003''
''01000C9C00000003010090332B114303010087E0930400030100888813000003010089102700''
''0002010091040031372E3603010092FB0000000301009474580000428722C64E200C00000002''
''0100011E003E3E3E2A2A2A5757572E534558455345584F5345582E434F4D2A2A2A2020''

Here goes the explanation of the file:

*''E0'' <- Validation initial value
*''02000000'' <- ''2'' servers will be listed (remember its [[little endian]])
*Server #1:
**''50EFC86C'' <- [[IP]]: ''108.200.239.80.'' (remember its [[little endian]])
**''B80B'' <- [[Port]]: ''3000'' (remember its [[little endian]])
**''0C000000'' <- ''12'' tags (remember its [[little endian]])
**Tag #1
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''01'' <- Tag name: ''1'' (Server name)
***''0A00'' <- Tag value length: ''10'' (remember its [[little endian]])
***''4269472042616E472039'' <- Tag value: ''BiG BanG 9'' (server name)
**Tag #2
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''0B'' <- Tag name: ''0B'' (Description)
***''0E00'' <- Tag value length: ''14'' (remember its [[little endian]])
***''7777772E42694742616E472E746F'' <- Tag value: ''www.BiGBanG.to'' (server description)
**Tag #3
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0500'' <- Tag name length: ''5'' (remember its [[little endian]])
***''7573657273'' <- Tag name: ''users'' (this is a string, not a code)
***''EF1A0100'' <- Tag value: ''72431'' (remember its [[little endian]])
**Tag #4
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0500'' <- Tag name length: ''5'' (remember its [[little endian]])
***''66696C6573'' <- Tag name: ''files'' (this is a string, not a code)
***''31DC8C00'' <- Tag value: ''9231409'' (remember its [[little endian]])
**Tag #5
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''0C'' <- Tag name: ''0C'' (Ping)
***''9C000000'' <- Tag value: ''156'' (ping time in ms)
**Tag #6
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''90'' <- Tag name: ''90'' (Last ping)
***''332B1143'' <- Tag value: ''5:10:43 28/08/2005'' (last time the server was pinged)
**Tag #7
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''87'' <- Tag name: ''87'' (Max users)
***''E0930400'' <- Tag value: ''300000'' (max users)
**Tag #8
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''88'' <- Tag name: ''88'' (Soft files)
***''88130000'' <- Tag value: ''5000'' (soft files)
**Tag #9
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''89'' <- Tag name: ''89'' (Hard files)
***''10270000'' <- Tag value: ''10000'' (hard files)
**Tag #10
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''91'' <- Tag name: ''91'' (Version)
***''0400'' <- Tag value length: ''4'' (remember its [[little endian]])
***''31372E36'' <- Tag value: ''17.6'' (version)
**Tag #11
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''92'' <- Tag name: ''92'' ([http://www.ietf.org/rfc/rfc768.txt UDP] flags)
***''FB000000'' <- Tag value (in binnary, only the least valuable byte): ''11111001'' ([http://www.ietf.org/rfc/rfc768.txt UDP] flags: get sources, new tags, unicode, extended sources)
**Tag #11
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''94'' <- Tag name: ''94'' (LowID users)
***''74580000'' <- Tag value: ''22644'' (LowID users)
*Server #2
**''428722C6'' <- [[IP]]: ''198.34.135.66'' (remember its [[little endian]])
**''4E20'' <- [[Port]]: ''8270'' (remember its [[little endian]])
**''01000000'' <- ''1'' tag (remember its [[little endian]])
**Tag #1
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''01'' <- Tag name: ''1'' (Server name)
***''1E00'' <- Tag value length: ''30'' (remember its [[little endian]])
***''3E3E3E2A2A2A5757572E534558455345584F5345582E434F4D2A2A2A2020'' <- Tag value: ''***WWW.SEXESEXOSEX.COM*** '' (server name)

== More ==

For more information on tags used in [[eMule]] [[AMule_files|files]] and protocol, check the [http://hydranode.com/docs/ed2k/ed2k-tag.php ed2k tag documentation] at the [http://hydranode.com Hydranode project].

AMule files-hu

2005-08-28T16:59:24Z

83.42.86.182:

<center>[[AMule_files|English]] | [[AMule_files-nl|Nederlands]] | [[AMule_files-de|Deutsch]] | '''Magyar'''</center>

A legtöbb [[aMule-hu|aMule]] konfigfile és adat megegyezeik, vagy kompatibilis az [[eMule-hu|eMule]]éval.

Ne felejtsd el, lehet, hogy nincs meg mindegyik a rendszereden, van, ami csak akkor jön létre, mikor szükség van rá.

Itt egy rövid összefoglaló:
*'''~/.eMule:''' Az [[aMule-hu|aMule]] régi konfigfileja ([[aMule-hu|aMule]] 2.0.0, vagy korábbi verzió).
*'''[[addresses.dat_file-hu|~/.aMule/addresses.dat]]:''' Szerverlisták címeit tartalmazza, ahol új szervereket keres a program indításkor (ha be van állítba a Beállításoknál).
*'''[[amule.conf_file-hu|~/.aMule/amule.conf]]:''' Az [[aMule-hu|aMule]] fő konfigfileja. A legtöbb beállítás itt tárolódik.
*'''[[amulesig.dat_file-hu|~/.aMule/amulesig.dat]]:''' Ez az [[aMule_Project_FAQ:About-hu|aMule]] [[signature-hu|OnLine Aláírás]] fileja, ami megegyezik az [[eMule-hu|eMule]] [[signature-hu|aláírás]] állományával (lásd [[onlinesig.dat_file-hu|''onlinesig.dat'']], lejjebb), de több információt tartalmaz.
*'''~/.aMule/aMule.tmpl:''' Ez volt az [[amuleweb-hu|aMule WebServer]] ideiglenes fileja az [[aMule-hu|aMule]] 2.0.0-es verziójáig.
*'''~/.aMule/aMule-online-sign.png:''' Ez az állomány csak akkor létezik, ha a [[CAS-hu]] már fut egy ideje, az ''-o'' kapcsolóval, és a ''~/.aMule/casrc'' rendesen be lett állítva. Ez egy képfile, ami az [[aMule_Project_FAQ:About-hu|aMule]] státuszáról tárol információkat.
*'''[[casrc_file-hu|~/.aMule/casrc]]:''' Ez az állomány csak akkor létezik, ha a [[CAS-hu]] már fut egy ideje, az ''-o'' kapcsolóval. A [[CAS-hu]] képfileról tartalmaz információkat.
*'''[[clients.met_file-hu|~/.aMule/clients.met]]:''' Az ismert kliensek publikus hashet tartalmazza, valamint a kreditek számát, amivel tartozol nekik.
*'''~/.aMule/clients.met.BAK:''' A [[clients.met_file-hu|clients.met]] backupja.
*'''[[cryptkey.dat_file-hu|~/.aMule/cryptkey.dat]]:''' Ez tartalmazza a 384 bit hosszú, privát [http://www.hup.hu/wiki/index.php/RSA RSA] kulcsát a [[client-hu|kliens]]nek.
*'''[[emfriends.met file-hu|~/.aMule/emfriends.met]]:''' A "Barátok" lista beállításait tartalmazza.
*'''[[ED2KLinks_file-hu|~/.aMule/ED2KLinks]]:''' Ez a file egy külső felület, fileok letöltéséhez.
*'''[[ipfilter.dat file-hu|~/.aMule/ipfilter.dat]]:''' Ez tartalmazza az [[IP-hu|IP]]ket és hozzáférési engedélyeket, amiket az [[IPFilter-hu|IPFilter]] használ.
*'''[[known.met file-hu|~/.aMule/known.met]]:''' Ez tartalmazza a megosztott fileok hashet, és némi infót róluk (méret, elérési út, statisztika, stb.)
*'''[[known2.met file-hu|~/.aMule/known2.met]]:''' A megosztott fileok ellenőrzött [[AICH-hu|AICH]] hasheit tartalmazza.
*'''[[last_version_check_file-hu|~/.aMule/last_version_check]]:''' Ideiglenes file, a legutóbbi hivatalos [[aMule-hu|aMule]] verziószámát tárolja.
*'''[[lastversion_file-hu|~/.aMule/lastversion]]:''' Ez tudatja az [[aMule_Project_FAQ:About-hu|aMule]]lal, hogy verziót váltottál-e, vagy ez az első alkalom, hogy futtatod a programot.
*'''~/.aMule/logfile:''' Az utolsó futás logja.
*'''~/.aMule/muleconn:''' Ez egy socket az [[aMule_Project_FAQ:About-hu|aMule]] kommunikációihoz.
*'''[[nodes.dat file-hu|~/.aMule/nodes.dat]]:''' A Kademlia kapcsolatok jellemzőit tárolja.
*'''[[onlinesig.dat_file-hu|~/.aMule/onlinesig.dat]]:''' Ez egy [[eMule-hu|eMule]] kompatibilis [[signature-hu|OnLineSignature]] file. Más programok használhatják információszerzésre az [[aMule_Project_FAQ:About-hu|aMule]] statisztikáiról. Lásd még [[amulesig.dat_file-hu|''amulesig.dat'']], feljebb.
*'''[[preferences.dat_file-hu|~/.aMule/preferences.dat]]:''' A nyilvános kulcsot tartalmazza (másnéven user hash).
*'''[[remote.conf_file-hu|~/.aMule/remote.conf]]:''' Konfig file a [[External Connections-hu|Külső Kapcsolatok]]hoz.
*'''[[server.met file-hu|~/.aMule/server.met]]:''' Az ismert szerverek listája, a beállításaikkal együtt (prioritás, név, [[IP-hu|IP]], port, ilyesmi).
*'''~/.aMule/server.met.new:''' Ideiglenes file, amíg a program írja a [[server.met file-hu|server.met file]]t. Amint készen van, átnevezi [[server.met file-hu|server.met]]re.
*'''~/.aMule/server_auto.met:''' Ide töltődnek a [[server.met file-hu|server.met file]]ok, mielőtt az [[aMule-hu|aMule]] feldolgozza és hozzáadja a saját [[server.met file-hu|server.met file]]jához.
*'''~/.aMule/server_met.old:''' A [[server.met file-hu|server.met file]] backupja.
*'''[[shareddir.dat_file-hu|~/.aMule/shareddir.dat]]:''' A megoszott könyvtárak elérési útját tárolja.
*'''[[staticservers.dat_file-hu|~/.aMule/staticservers.dat]]:''' A [[static server-hu|kézzel beállított szerver]]ek listáját tárolja.

A többi file az ''~/.aMule/'' könyvtárban minden bizonnyal a fentiek backupja.

Valamint, az Ideiglenes könyvtárban (ami az ''~/.aMule/Temp'', de bármi másra átállítható a Beállításoknál), az [[aMule_Project_FAQ:About-hu|aMule]] minden letöltéshez létrehozza a következő állományokat:

*'''*.part:''' Ez a állomány tartalmazza a letöltött részeit a fileoknak (nem a chunkokat, hiszen a nem befejezett chunkok is itt tárolódnak). Mivel az [[aMule_Project_FAQ:About-hu|aMule]] egyszerre több klienstől is tud tölteni, ennek a filenak a mérete megegyezik a letöltésre váró file teljes méretével. A befejezetlenek részek nullákkal vannak feltöltve.
*'''*.part.met:''' Ez a file tartalmazza a letöltésre váró állományok információit, mint pl. ellenőrzött chunkok, a hátralévő chunkok hash-értékeit, stb.
*'''*.part.met.bak:''' Ez a ''*.part.met'' file backupja. Ez mindig létrejön, mivel a ''*.part.met'' file nélkül, a letöltéseknek nincs értelme az aMule számára. Ha bármelyik ''*.part.met'' file eltűnik, nevezd át a ''*.part.met.bak'' filet ''*.part.met''re.
*'''*.part.met.backup:''' Ez az ideiglenes ''*.part.met'' file, arra az időre, amíg az [[aMule-hu|aMule]] befejezi az írást. Ez után rögtön átnevezi ''*.part.met''re.
*'''*.part.met.seeds:''' Ez a file csak akkor létezik, ha beállítottad az "5 forrás mentése a ritka fájloknál (<20 forrás)" opciót. Ebben az állományban a források IPje tárolódik.

A könyvtárak, amiket az aMule alapbeállítások mellett használ:

*'''~/.aMule/Incoming/:''' Itt tárolja a program a befejezett letöltéseket (kivéve [http://macosx.apple.com MacOS X] alatt).
*'''~/.aMule/Temp/:''' Ide a befejezetlen letöltések kerülnek (ideiglenes fileok).
*'''~/.aMule/webserver/:''' Az [[aMuleWeb-hu|aMuleWeb]] szkinjei kerülnek ide.
*'''~/Documents/aMule Downloads:''' Itt tárolja az aMule a befejezett letöltéseket [http://macosx.apple.com MacOS X] alatt ([[aMule-hu|aMule]] 2.0.0 óta).

AMule-de

2005-08-28T16:43:11Z

83.42.86.182:

<center>[[AMule_Project_FAQ:About|English]] | [[aMule-hu|Magyar]] | [[aMule-es|Español]] | '''Deutsch'''</center>

== [http://www.amule.org aMule]: [http://www.amule.org all-platform Mule] ==

[[aMule]] steht für ''all-platform [[Mule]]''.

[http://www.amule.org aMule] ist ein [[eMule]]-ähnlicher [[client]] für die [[FAQ_eD2k-Kademlia|eD2k und Kademlia Netzwerke]] und unterstützt mehrere Betriebsumgebungen.

Die momentan (offiziell) unterstützten Platformen umfassen:
*[http://www.kernel.org Linux]
*[http://www.bsd.org *BSD]:
**[http://www.freebsd.org FreeBSD]
**[http://www.openbsd.org OpenBSD]
**[http://www.netbsd.org NetBSD]
*[http://www.sun.com/solaris Solaris]
*[http://www.apple.com/macosx MacOS X]
*[http://www.microsoft.com/windows Windows]
*[http://www.microsoft.com/xbox XBox]
*Für andere *nix-Systeme existieren inoffizielle Versionen

[http://www.amule.org aMule] ist vollständig [http://www.gnu.org/philosophy/free-sw.html frei], der Sourcecode wird genauso wie [[eMule]] unter der [[AMule_Project_FAQ:Copyrights|GPL]] veröffentlicht, und beinhaltet keine Adware oder Spyware wie sie sich oft in proprietären [[P2P]]-Anwendungen finden.

[http://www.amule.org aMule] basiert auf [[wxWidgets]] (früher [[wxWidgets|wxWindows]]), wodurch es verschiedene Platformen unterstützen kann.

Alle [http://www.amule.org aMule] [[dependencies|Abhängigkeiten]] finden sich [[dependencies|hier]].

== Geschichte ==

[http://www.amule.org aMule] wurde im September 2003 von [[xMule]] (früher als [[lMule]] bekannt) abgeleitet, hat inzwischen aber immer weniger mit seinem Ursprung gemeinsam.

== Funktionsumfang ==

=== *Mule Features ===

[http://www.amule.org aMule] besitzt die meisten Fähigkeiten von [[eMule]], unter anderem:

* Unterstützung für [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] und [[FAQ_eD2k-Kademlia#What_is_Kademlia?|Kademlia]].
* [http://www.amule.org aMule] gibt es momentan in 28 Sprachen.
* Unterstützung für [[FAQ_eD2k-Kademlia#What_is_a_source?|Source]] Exchange (Quellenaustausch) um Quellen für [[file|Dateien]] effizienter zu finden.
* Große Wartelisten und das [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|Credit System]] stellen sicher, das jeder die Datei erhälstraint, die er will und belohnt diejenigen, die Uploadkapazität für andere Benutzer bereitstellen.
* Unterstützung für komprimierte Datenübertragung und Serverkommunikation mittels [http://www.gzip.org/zlib zlib], was zu schnelleren Datenübertragungen bei komprimierbaren Dateien und weniger Last auf dem [[Server|Server]] führt.
* Unterstützung für [[Secure_User_Identification|Sichere Identifizierung]], um sicherzustellen das der [[User|Benutzer]] [[Hash]] nicht gestohlen werden kann um eine andere Identität vorzutäuschen.
* Unterstützung für [[IPFilter|IP-Filter]] um bekannte schlechte [[IP]]s daran zu hindern, eine Verbindung herzustellen.
* Sowohl die altbekannte Fortschrittsanzeige für Transfers, die Anzeige der abgeschlossenen Prozent oder auch beide gleichzeitig sind vefügbar.
* [http://www.amule.org aMule] unterstützt systrays (Systemicons) sowohl für [http://www.gnome.org Gnome], [http://www.kde.org KDE] und kompatible Fenstermanager. Natürlich auch für [http://www.microsoft.com/windows Windows].
* Unterstützung für [[Signature|Online-Signaturen]], damit man sich seines [http://www.amule.org aMule] rühmen kann.
* Schutz vor [[aggressive client|agressiven Clients]].
* Verwendung von [[MD4 hash]]es um [[FAQ_eD2k-Kademlia#What_is_a_source?|Quellen]] zu finden und gleichzeitig sicherzustellen, dass die Datei dem Original entspricht.
* [[ICH|Intelligent Corruption Handler (ICH)]] und [[AICH]] sorgen für eine schnelle Korrektur an fehlerhaft übertragenen Teilen.
* Automatische [[priority|Prioritäten]] und Quellenmanagement erlauben, viele Downloads zu starten, ohne sie beobachten zu müssen.
* Die Vorschaufunktion ermöglicht es, Videos und Archive zu betrachten, bevor sie [[complete|komplett]] heruntergeladen sind. Für Videovorschauen werden [http://www.mplayerhq.hu MPlayer] oder [http://xine.sourceforge.net Xine] empfohlen, aber [http://www.videolan.org Video Lan Client] sollte ebenfalls funktionieren.
* Unterstützung für [[category|Kategorien]] um die Downloads zu organisieren.
* Um die gesuchten Dateien zu finden, bietet[http://www.amule.org aMule] eine Reihe von [[search|Such]]möglichkeiten:
** [[Server]]-gestützte Suche (Lokal und Global)
** [[FAQ_eD2k-Kademlia#What_is_Kademlia?|Kademlia]]-Suche
** Integration im bevorzugten Browser für einfache Downloads mit einem Klick (with [[ed2k link|ed2k:// Links]]).
* Nachrichten und [[Friend|Friends]]-System. Man kann Nachrichten an andere clients senden und sie als Freunde hinzufügen.
* [http://www.amule.org aMule] unterstützt Aktualisierung der Serverliste von einer URL während das Programm läuft, beim Start oder während es zu anderen Clients [[connect|verbindet]].
* [[PowerShare]] Funktion: Bessere Verwaltung der [[share|bereitgestellten]] Dateien (bekannt als ''Release'').

=== [http://www.amule.org aMule] spezielle Features ===

* [[Multiplatform]].
* [[Proxy]] Unterstützung.
* Verbesserter Schutz gegen agressive Clients.
* Complete [[External Connections]] protocol from scratch.
* [[aMuled|aMule Daemon]] allows you to run a bare [http://www.amule.org aMule] client with no graphical interface and very low CPU and memory usage. Ideal for servers, people who usually control [http://www.amule.org aMule] remotely and those who just usually don't keep taking a look at how far downloads are going.
* [[aMuleGUI|aMule Remote GUI]] to control your [http://www.amule.org aMule] remotely as if you where in front of it.
* [[aMuleWeb]] for browser interface and [[aMuleWeb|amulwebDLG]] is a graphical interface to aMuleWeb. They also work both locally and from remote clients. You can control your [[aMule]] from anywhere in the world as long as you have an internet connection and a browser, no matter what hardware or operating system you use! ;)
* The [[aMuleCMD|amulecmd]] command line interface and [[aMuleCMD|amulecmdDLG]] as a graphical command line interface both allow to remotely control [http://www.amule.org aMule] too. All of them work both locally and from remote clients. You can control your [http://www.amule.org aMule] remotely from anywhere as if you were in a shell!
* [[FAQ_aMule#What_is_slot_allocation?|Slot allocation]] allows you to specify to how many clients you wish to upload to at once. For example, if you have 20KB/s for your maximum upload, you can set [[FAQ_eD2k-Kademlia#What_is_a_slot?|slot]] allocation to 10KB/s which means that you will upload to two users with 10KB/s each.
*Other utilities such as [[CAS]], [[wxCAS]], [[aLinkCreator|aLC]], [[XAS]], [[AMPS]], etc.
* Fast [[ed2k link|eD2k links]] handler at the bottom of every page (can be disabled on Preferences).
* Save 5 sources on rare files (20 or less sources).
* Filter search results.
* Default file permissions for completed downloads.
* Multiple filesystems support.
* Version updates checks.

=== Planned features ===

* Boolean search (''AND'', ''OR'', ''NOT'').
* Skins support.
* Disk allocation for incomplete files.
* [http://www.php.org PHP] (specific implementation) support in [[aMuleWeb]]
* and and and ...

TODO

2005-08-28T09:02:52Z

83.42.86.182:

== Before we start ==

Check this [[AMule_Project_FAQ:FAQ|wiki's FAQ]] if you haven't already taken a look at it.

== Most urgent stuff ==
#Document about skins ( http://forum.amule.org/thread.php?threadid=6938 )
#Document about [[hotkeys]]
#Guide to [[migrate from eMule to aMule]] (done by ''[[User:Matrixhasu|morph]]'')
#Go on for Kademlia specific articles
#Document missing [[aMule_files|files]] and Kademlia files (and explain defaults in [[amule.conf_file|config file]])
#Write good "aMule usage" documents
#(Re)work on the utilities FAQs and articles
#Network packets and protocol design (and EC)

== Someday stuff ==
*Change HTML tags for wiki tags when possible
*Only first word's appearance is linked (damn team decitions...)
*Split large articles into samller articles straight to topic
*Rework the [[Main Page]] and the whole wiki structure

== Always TODOs ==
*Translate [[Main Page|this wiki]]'s articles
*Check everything is ok

IRC rules

2005-08-28T09:01:41Z

83.42.86.182:

== Introduction ==

While you stay at our [[IRC]] channels, you '''must''' follow some rules.

Most of them are basic ethic rules which, for some reason, some people fail to understand. Others are not so intuitive. There for, everybody '''must''' read this article '''before''' entering our IRC channel.

Just keep reading.

== What you must do ==

*You must read topic (''/topic #<channel>'') '''before''' saying anything.
*You must read this article from the beginning to the end '''before entering''' the channel. Did I say "read"? I meant "'''understand'''"!
*You must go to #macMule if you want to talk/ask about [[aMule]] on [http://macosx.apple.com MacOS X].
*You must go to #aMule if you want to talk/ask about [[aMule]] on any platform but on [http://macosx.apple.com MacOS X].
*You must speak english in our channels. They are english speaking channels.
*You must look for an answer in [http://forum.amule.org aMule's Forums] and in [[Main Page|this wiki]] before asking anything.
*You must read twice and, before talking, make sure you understand what other people write.
*You must read twice what you write before sending your message.
*You must stay in the channel for at least 30 minutes if you ask something. We hate people who just want their questoins to be answered right after they ask, in 0-time.
*If you want to talk specifically to someone, open a query (''/query <nick>''). Do not flood the channel with your private conversation unless you believe the conversation may make the knowledge of the rest of the people in the channel richer.

== What you must not do ==

*You must not violate any of your contry's laws nor any of the [http://europa.eu.int European Community] laws nor any of the [http://www.firstgov.gov USA] laws nor any of the international laws while staying at any of our channels. Sounds funny? Well, it's not.
*You must not talk about anything that doesn't regard '''directly''' (in the most strict way) to [[aMule]] as an application. Exceptionally, you may ask questions about the [[FAQ_ed2k|ed2k]] and [[Kademlia]] protocols, but an answer is not guaranteed.
*You must not talk, directly or indirectly, about any copyrighted non-free (in the ''beer way'') material.
*You must not talk about any website which breaks any of our channels rules.
*You must not provide any URL which's contents break any of our channels rules.
*You must not provide '''any''' [[ed2k link]].
*You must not do any kind of publicity about anything unless some channel operator allows you to do so.
*Do not flood. Not even a little. More than tree lines in a row will be enough to be considered flooding.
*Don't ask to ask. Just ask!
*You must not ask anything if you haven't at least tried a little to find out the answer on your own. Did I seay "try a little"? I mean "try as hard as you can".
*You must not ask repeatedly for a question. Wait at least an hour before asking again, even if you get answer. Asking the same question using different words won't make the trick either.
*You must not use any ''away message''.
*You must not use any bots in the channels unless some channel operator allows you to do so.
*Do not split whatever you want to say into several different short lines. This is not Instant Messaging. This is IRC. Get used to it.
*You must not use abreviated words or non-standard language.
*You must not type with capital letters nor user more than two exclamation marks in a single line (scream).
*You must not insult, flame, blame, begin a war, fight, etc.
*You may not enter and leave the channel as if you were hiding from someone. Decide whether you want to enter or leave the channel and then do so. Not the other way round.

== What you can do ==

You can do anything you wish as long as it is not forbidden in any rule in this article. Anyway, we'd like to make emphasys in some things which you can do in our channels which are sometimes forbidden in many other channels around:

*You can talk to the [[aMule Team]]. They are the official channels, so the Team is hearing. Just wait some time till they read. And make no doubt they will read you.
*You can stay idle as long as you wish.
*You can answer questions to other people even if they weren't asking you, as long as you know what you are talking about and as long as what you answer is what you really believe to be true/right.

== Suggestions ==

*Try to always ask&answer in an objective way.
*If you ask a question, wait for a few hours for an answer. Most of the time people are idle (not in front of the computer), so it may take long till someone reads your question. Just don't leave that fast.
*If you get an answer don't become sceptic about what you are told. Otherwise just don't ask.
*Use the latest stable [[aMule]] release.
*Distro specific questions, even if regarding [[aMule]], should go the distro's channel or forums. Most surely we won't know the answer.
*Now here is '''The BIG Suggestion (c)''': Think, then act.

== What if a rule is not clear? ==

This rules are made by the channels operators.

The only people who know exactly what they mean are them. You must try to understand what operators think the rules means. And in case of doubt, just stay silent.

Channel operators may charge on you if they consider you have broken some rule in the interpretation they, as channel operators, make of the rule. And the interpretation may vary depending on the mood, the phase of the moon, the colour of the clouds or the price of gas and pizza.

== Consequences ==

Anyone who doesn't follow one or more of the above rules will be kicked from the channel.

Anyone repeatedly breaking this rules will have to face a ban. There is no rule for ban periods: it depends on our mood in which we are :->

If someone severely breaks some rule, even if it isn't repeatedly, it could also be punished with a ban.

IRC rules

2005-08-28T08:52:36Z

83.42.86.182:

== Introduction ==

While you stay at our [[IRC]] channels, you '''must''' follow some rules.

Most of them are basic ethic rules which, for some reason, some people fail to understand. Others are not so intuitive. There for, everybody '''must''' read this article '''before''' entering our IRC channel.

Just keep reading.

== What you must do ==

*You must read topic (''/topic #<channel>'') '''before''' saying anything.
*You must read this article from the beginning to the end '''before entering''' the channel. Did I say "read"? I meant "'''understand'''"!
*You must read twice and make sure you understand what other people right before talking.
*You must read twice what you write before sending your message.
*You must speak english in our channels. They are english speaking channels.
*If you want to talk specifically to someone, open a query (''/query <nick>''). Do not flood the channel with your private conversation unless you believe the conversation may make the knowledge of the rest of the people in the channel richer.
*You must look for an answer in [http://forum.amule.org aMule's Forums] and in [[Main Page|this wiki]] before asking anything.
*You must go to #macMule if you want to talk/ask about [[aMule]] on [http://macosx.apple.com MacOS X].
*You must go to #aMule if you want to talk/ask about [[aMule]] on any platform but on [http://macosx.apple.com MacOS X].

== What you can do ==

*You can answer questions to other people even if they weren't asking you, as long as you know what you are talking about and as long as what you answer is what you really believe to be true/right.
*You can talk to the [[aMule Team]]. They are the official channels, so the Team is hearing. Just wait some time till they read. And make no doubt they will read you.
*You can stay idle as long as you wish.

== What you must not do ==

*You must not talk about any website which breaks any of our channels rules.
*You must not provide any URL which's contents break any of our channels rules.
*You must not violate any of your contry's laws nor any of the [http://europa.eu.int European Community] laws nor any of the [http://www.firstgov.gov USA] laws nor any of the international laws while staying at any of our channels. Sounds funny? Well, it's not.
*You must not provide '''any''' [[ed2k link]].
*You must not do any kind of publicity about anything unless some channel operator allows you to do so.
*You must not type with capital letters nor user more than two exclamation marks in a single line (scream).
*You must not use any bots in the channels unless some channel operator allows you to do so.
*You must stay in the channel for at least 30 minutes if you ask something. We hate people who just want their questoins to be answered right after they ask, in 0-time.
*You must not ask anything if you haven't at least tried a little to find out the answer on your own. DId I seay "try a little"? I mean "try as hard as you can".
*You must not use abreviated words or non-standard language.
*You must not use any ''away message''.
*You must not ask repeatedly for a question. Wait at least an hour before asking again, even if you get answer. Asking the same question using different words won't make the trick either.
*Do not flood. Not even a little. More than tree lines in a row will be enough to be considered flooding.
*Don't ask to ask. Just ask!
*You must not insult, flame, blame, begin a war, fight, etc.
*You must not talk, directly or indirectly, about any copyrighted non-free (in the ''beer way'') material.
*You may not talk about anything that doesn't regard '''directly''' (in the most strict way) to [[aMule]] as an application. Exceptionally, you may ask questions about the [[FAQ_ed2k|ed2k]] and [[Kademlia]] protocols, but an answer is not guaranteed.
*You may not enter and leave the channel as if you were hiding from someone. Decide whether you want to enter or leave the channel and then do so. Not the other way round.
*Do not split whatever you want to say into several different short lines. This is not Instant Messaging. This is IRC. Get used to it.

== Suggestions ==

*Try to always ask&answer in an objective way.
*If you ask a question, wait for a few hours for an answer. Most of the time people are idle (not in front of the computer), so it may take long till someone reads your question. Just don't leave that fast.
*If you get an answer don't become sceptic about what you are told. Otherwise just don't ask.
*Use the latest stable [[aMule]] release.
*Distro specific questions, even if regarding [[aMule]], should go the distro's channel or forums. Most surely we won't know the answer.
*Now here is '''The BIG Suggestion (c)''': Think, then act.

== What if a rule is not clear? ==

This rules are made by the channels operators.

The only people who know exactly what they mean are them. You must try to understand what you think the rule means. And in case of doubt, just stay silent.

Channels operators may charge on you if they consider you have broken some rule in the interpretation he/she, as a channel operator, makes of the rule. And the interpretation may vary depending on the mood, the phase of the moon, the colour of the clouds or the price gas and pizza.

== Consequences ==

Anyone who doesn't follow one or more of the above rules will be kicked from the channel.

Anyone repeatedly breaking this rules will have to face a ban. There is no rule for ban periods: it depends on our mood in which we are :->

If someone severely breaks some rule, even if it isn't repeatedly, it could also be punished with a ban.

AMule Team

2005-08-28T08:51:22Z

83.42.86.182:

#REDIRECT [[AMule_devs]]

AMule team

2005-08-28T08:51:05Z

83.42.86.182:

#REDIRECT [[AMule_devs]]

IRC

2005-08-28T07:54:04Z

83.42.86.182:

The [[aMule]] [[AMule_devs|team]] and supporters can be found on '''''[irc://irc.freenode.net irc.freenode.net]''''' in the [irc://irc.freenode.net/amule #amule] channel.

While being in out channel you must follow our [[IRC rules]]!

Feel free to pay us a visit =)

Server.met file

2005-08-28T07:23:07Z

83.42.86.182:

== File ==

'''Name:''' ''server.met''

'''Location:''' ''~/.aMule/''

== Description ==

Binary file containing the list of [[server]]s known to [[aMule]].

Because its in binary format, it must be changed within [[aMule]], or with other appropriate tools.

The format description below is for development information purposes.

== Format ==

=== File Format ===

This file's fields are written in [[little endian]] order.

'''Note:''' All digit fields are unsigned unless stated.

*Met Header (1 Byte): With value ''Ox0E'' or ''OxE0'', and is used in [[aMule]] to check for valid ''server.met'' files
*Server Count (4 Bytes): Lists the number of [[server]]s that follow
*Block of servers: Each [[server]] is constituted by the following fields:
**[[Server]] [[IP]] (4 Bytes): Simply that. The [[server]]'s [[IP]].
**[[Server]] [[Port]] (2 Bytes): Simply that. The [[port]] through which [[aMule]] will connect to the [[server]].
**Tag Count (4 Bytes): Lists the number of [[server]] tags that follows.
**Block of Tags: Each [[server]] can have a list of associated tags with the format bellow.

=== Tags Format ===

==== General tags format ====

There are two tag identifiers: A name (string) and an ID (1 Byte)

Which one is used depends on the tag value type given or on the size of the tag name. If tag name length is ''1'', an ID is used.

*Tag value type (1 Byte)
*Tag name length (2 Bytes)
*Tag name (size given above)
*Tag value length (2 Bytes) (Only when the value is a string)
*Tag value (if the value is a string, it's size is given in the above field. If it is not a string, the size depends on the type of value it is)

==== Tag value types ====

{|
|+ Tag types
| '''Tag type (''Code'')''' || '''Explanation'''
|-
| String (''0x02'') (*) || Defines a string tag.
|-
| Unsigned 32 bits number (''0x03'') || Defines a numeric tag.
|}

'''(*):''' Systems with [http://www.unicode.org Unicode] enabled have the same tag string defined twice, the first in [http://www.unicode.org Unicode], and the second in plain [http://www.asciitable.com ASCII], which will be ignored by [http://www.unicode.org Unicode] enabled [[client]]s, and used by non-[http://www.unicode.org Unicode] ones.

==== Tag IDs ====

{|
|+ Tag IDs
| ''ID ('''code''')'' || ''Tag value type'' || ''Description''
|-
| ServerName (''0x01'') || String || Name of the [[server]]
|-
| Description (''0x0B'') || String || Short description about the server
|-
| Ping (''0x0C'') || Unsigned 32 bits number || Time (in ms) it takes to comunicate with the server
|-
| Fail (''0x0D'') || Unsigned 32 bits number || How many times [[connect]]ing to the server failed
|-
| Preference (''0x0E'') || Unsigned 32 bits number || Priority given to this server among the others (Normal=''0'', High=''1'', Low=''2'')
|-
| DNS (''0x85'') || String || [http://en.wikipedia.org/wiki/DNS DNS] of the server
|-
| Max users (''0x87'') || Unsigned 32 bits number || Maximum number of users the server allows to simoultaneously connect to it
|-
| Soft files (''0x88'') || Unsigned 32 bits number || [[Soft files]] number
|-
| Hard files (''0x89'') || Unsigned 32 bits number || [[Hard files]] number
|-
| Last ping (''0x90'') || Unsigned 32 bits number || Last time the server was [[ping]]ed
|-
| Version (''0x91'') || String / Unsigned 32 bits number || Version and name of the software the server is running to support the [[FAQ_ed2k|ed2k]] [[network]]
|-
| [http://www.ietf.org/rfc/rfc768.txt UDP] flags (''0x92'') || Unsigned 32 bits number || Informs of the actions the server accepts through [http://www.ietf.org/rfc/rfc768.txt UDP] connections. This flags are:
*''0x01'': Get sources
*''0x02'': Get files
*''0x08'': New tags
*''0x10'': Unicode
*''0x20'': Get extended sources info
|-
| Auxiliary [[port]]s list (''0x93'') || String || Some servers have additional ports open for those [[user]]s who cannot connect to the standard one (usually because they have a firewall which tries to stop [[P2P]] connections). This servers tell in this field which additional ports they have open. Each additional port is separated from the others by a coma ('','').
|-
| [[LowID]] [[client]]s (''0x94'') || Unsigned 32 bits number || Number of users connected with a LowID
|}

==== Tag Names ====

{| border=0
|+ There are at the moment two tag names recognized by [[aMule]]:
| width="100px" | ''Tag Name'' || ''Tag Value''
|-
| "files" || Unsigned 32 bits number || Shows the number of [[file]]s registered in the [[server]]
|-
|"users" || Unsigned 32 bits number || Shows the number of [[user]]s registered in the [[server]]
|}

== Example ==

The following is an example file:

''E03800000050EFC86CB80B0C000000020100010A004269472042616E4720390201000B0E0077''
''77772E42694742616E472E746F0305007573657273EF1A010003050066696C657331DC8C0003''
''01000C9C00000003010090332B114303010087E0930400030100888813000003010089102700''
''0002010091040031372E3603010092FB0000000301009474580000428722C64E200C00000002''
''0100011E003E3E3E2A2A2A5757572E534558455345584F5345582E434F4D2A2A2A2020''

Here goes the explanation of the file:

*''E0'' <- Validation initial value
*''02000000'' <- ''2'' servers will be listed (remember its [[little endian]])
*Server #1:
**''50EFC86C'' <- [[IP]]: ''108.200.239.80.'' (remember its [[little endian]])
**''B80B'' <- [[Port]]: ''3000'' (remember its [[little endian]])
**''0C000000'' <- ''12'' tags (remember its [[little endian]])
**Tag #1
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''01'' <- Tag name: ''1'' (Server name)
***''0A00'' <- Tag value length: ''10'' (remember its [[little endian]])
***''4269472042616E472039'' <- Tag value: ''BiG BanG 9'' (server name)
**Tag #2
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''0B'' <- Tag name: ''0B'' (Description)
***''0E00'' <- Tag value length: ''14'' (remember its [[little endian]])
***''7777772E42694742616E472E746F'' <- Tag value: ''www.BiGBanG.to'' (server description)
**Tag #3
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0500'' <- Tag name length: ''5'' (remember its [[little endian]])
***''7573657273'' <- Tag name: ''users'' (this is a string, not a code)
***''EF1A0100'' <- Tag value: ''72431'' (remember its [[little endian]])
**Tag #4
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0500'' <- Tag name length: ''5'' (remember its [[little endian]])
***''66696C6573'' <- Tag name: ''files'' (this is a string, not a code)
***''31DC8C00'' <- Tag value: ''9231409'' (remember its [[little endian]])
**Tag #5
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''0C'' <- Tag name: ''0C'' (Ping)
***''9C000000'' <- Tag value: ''156'' (ping time in ms)
**Tag #6
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''90'' <- Tag name: ''90'' (Last ping)
***''332B1143'' <- Tag value: ''5:10:43 28/08/2005'' (last time the server was pinged)
**Tag #7
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''87'' <- Tag name: ''87'' (Max users)
***''E0930400'' <- Tag value: ''300000'' (max users)
**Tag #8
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''88'' <- Tag name: ''88'' (Soft files)
***''88130000'' <- Tag value: ''5000'' (soft files)
**Tag #9
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''89'' <- Tag name: ''89'' (Hard files)
***''10270000'' <- Tag value: ''10000'' (hard files)
**Tag #10
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''91'' <- Tag name: ''91'' (Version)
***''0400'' <- Tag value length: ''4'' (remember its [[little endian]])
***''31372E36'' <- Tag value: ''17.6'' (version)
**Tag #11
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''92'' <- Tag name: ''92'' ([http://www.ietf.org/rfc/rfc768.txt UDP] flags)
***''FB000000'' <- Tag value (in binnary, only the least valuable byte): ''11111001'' ([http://www.ietf.org/rfc/rfc768.txt UDP] flags: get sources, new tags, unicode, extended sources)
**Tag #11
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''94'' <- Tag name: ''94'' (LowID users)
***''74580000'' <- Tag value: ''22644'' (LowID users)
*Server #2
**''428722C6'' <- [[IP]]: ''198.34.135.66'' (remember its [[little endian]])
**''4E20'' <- [[Port]]: ''8270'' (remember its [[little endian]])
**''01000000'' <- ''1'' tag (remember its [[little endian]])
**Tag #1
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''01'' <- Tag name: ''1'' (Server name)
***''1E00'' <- Tag value length: ''30'' (remember its [[little endian]])
***''3E3E3E2A2A2A5757572E534558455345584F5345582E434F4D2A2A2A2020'' <- Tag value: ''***WWW.SEXESEXOSEX.COM*** '' (server name)

== More ==

For more information on tags used in [[eMule]] [[AMule_files|files]] and protocol, check the [http://hydranode.com/docs/ed2k/ed2k-tag.php ed2k tag documentation] at the [http://hydranode.com Hydranode project].

Server.met file

2005-08-28T07:20:12Z

83.42.86.182:

== File ==

'''Name:''' ''server.met''

'''Location:''' ''~/.aMule/''

== Description ==

Binary file containing the list of [[server]]s known to [[aMule]].

Because its in binary format, it must be changed within [[aMule]], or with other appropriate tools.

The format description below is for development information purposes.

== Format ==

=== File Format ===

This file's fields are written in [[little endian]] order.

'''Note:''' All digit fields are unsigned unless stated.

*Met Header (1 Byte): With value ''Ox0E'' or ''OxE0'', and is used in [[aMule]] to check for valid ''server.met'' files
*Server Count (4 Bytes): Lists the number of [[server]]s that follow
*Block of servers: Each [[server]] is constituted by the following fields:
**[[Server]] [[IP]] (4 Bytes): Simply that. The [[server]]'s [[IP]].
**[[Server]] [[Port]] (2 Bytes): Simply that. The [[port]] through which [[aMule]] will connect to the [[server]].
**Tag Count (4 Bytes): Lists the number of [[server]] tags that follows.
**Block of Tags: Each [[server]] can have a list of associated tags with the format bellow.

=== Tags Format ===

==== General tags format ====

There are two tag identifiers: A name (string) and an ID (1 Byte)

Which one is used depends on the tag value type given or on the size of the tag name. If tag name length is ''1'', an ID is used.

*Tag value type (1 Byte)
*Tag name length (2 Bytes)
*Tag name (size given above)
*Tag value length (2 Bytes) (Only when the value is a string)
*Tag value (size wither depends on [[#Tag_value_types|tag type]] or is given above if the value is a string)

==== Tag value types ====

{|
|+ Tag types
| '''Tag type (''Code'')''' || '''Explanation'''
|-
| String (''0x02'') (*) || Defines a string tag.
|-
| Unsigned 32 bits number (''0x03'') || Defines a numeric tag.
|}

'''(*):''' Systems with [http://www.unicode.org Unicode] enabled have the same tag string defined twice, the first in [http://www.unicode.org Unicode], and the second in plain [http://www.asciitable.com ASCII], which will be ignored by [http://www.unicode.org Unicode] enabled [[client]]s, and used by non-[http://www.unicode.org Unicode] ones.

==== Tag IDs ====

{|
|+ Tag IDs
| ''ID ('''code''')'' || ''Tag value type'' || ''Description''
|-
| ServerName (''0x01'') || String || Name of the [[server]]
|-
| Description (''0x0B'') || String || Short description about the server
|-
| Ping (''0x0C'') || Unsigned 32 bits number || Time (in ms) it takes to comunicate with the server
|-
| Fail (''0x0D'') || Unsigned 32 bits number || How many times [[connect]]ing to the server failed
|-
| Preference (''0x0E'') || Unsigned 32 bits number || Priority given to this server among the others (Normal=''0'', High=''1'', Low=''2'')
|-
| DNS (''0x85'') || String || [http://en.wikipedia.org/wiki/DNS DNS] of the server
|-
| Max users (''0x87'') || Unsigned 32 bits number || Maximum number of users the server allows to simoultaneously connect to it
|-
| Soft files (''0x88'') || Unsigned 32 bits number || [[Soft files]] number
|-
| Hard files (''0x89'') || Unsigned 32 bits number || [[Hard files]] number
|-
| Last ping (''0x90'') || Unsigned 32 bits number || Last time the server was [[ping]]ed
|-
| Version (''0x91'') || String / Unsigned 32 bits number || Version and name of the software the server is running to support the [[FAQ_ed2k|ed2k]] [[network]]
|-
| [http://www.ietf.org/rfc/rfc768.txt UDP] flags (''0x92'') || Unsigned 32 bits number || Informs of the actions the server accepts through [http://www.ietf.org/rfc/rfc768.txt UDP] connections. This flags are:
*''0x01'': Get sources
*''0x02'': Get files
*''0x08'': New tags
*''0x10'': Unicode
*''0x20'': Get extended sources info
|-
| Auxiliary [[port]]s list (''0x93'') || String || Some servers have additional ports open for those [[user]]s who cannot connect to the standard one (usually because they have a firewall which tries to stop [[P2P]] connections). This servers tell in this field which additional ports they have open. Each additional port is separated from the others by a coma ('','').
|-
| [[LowID]] [[client]]s (''0x94'') || Unsigned 32 bits number || Number of users connected with a LowID
|}

==== Tag Names ====

{| border=0
|+ There are at the moment two tag names recognized by [[aMule]]:
| width="100px" | ''Tag Name'' || ''Tag Value''
|-
| "files" || Unsigned 32 bits number || Shows the number of [[file]]s registered in the [[server]]
|-
|"users" || Unsigned 32 bits number || Shows the number of [[user]]s registered in the [[server]]
|}

== Example ==

The following is an example file:

''E03800000050EFC86CB80B0C000000020100010A004269472042616E4720390201000B0E0077''
''77772E42694742616E472E746F0305007573657273EF1A010003050066696C657331DC8C0003''
''01000C9C00000003010090332B114303010087E0930400030100888813000003010089102700''
''0002010091040031372E3603010092FB0000000301009474580000428722C64E200C00000002''
''0100011E003E3E3E2A2A2A5757572E534558455345584F5345582E434F4D2A2A2A2020''

Here goes the explanation of the file:

*''E0'' <- Validation initial value
*''02000000'' <- ''2'' servers will be listed (remember its [[little endian]])
*Server #1:
**''50EFC86C'' <- [[IP]]: ''108.200.239.80.'' (remember its [[little endian]])
**''B80B'' <- [[Port]]: ''3000'' (remember its [[little endian]])
**''0C000000'' <- ''12'' tags (remember its [[little endian]])
**Tag #1
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''01'' <- Tag name: ''1'' (Server name)
***''0A00'' <- Tag value length: ''10'' (remember its [[little endian]])
***''4269472042616E472039'' <- Tag value: ''BiG BanG 9'' (server name)
**Tag #2
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''0B'' <- Tag name: ''0B'' (Description)
***''0E00'' <- Tag value length: ''14'' (remember its [[little endian]])
***''7777772E42694742616E472E746F'' <- Tag value: ''www.BiGBanG.to'' (server description)
**Tag #3
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0500'' <- Tag name length: ''5'' (remember its [[little endian]])
***''7573657273'' <- Tag name: ''users'' (this is a string, not a code)
***''EF1A0100'' <- Tag value: ''72431'' (remember its [[little endian]])
**Tag #4
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0500'' <- Tag name length: ''5'' (remember its [[little endian]])
***''66696C6573'' <- Tag name: ''files'' (this is a string, not a code)
***''31DC8C00'' <- Tag value: ''9231409'' (remember its [[little endian]])
**Tag #5
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''0C'' <- Tag name: ''0C'' (Ping)
***''9C000000'' <- Tag value: ''156'' (ping time in ms)
**Tag #6
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''90'' <- Tag name: ''90'' (Last ping)
***''332B1143'' <- Tag value: ''5:10:43 28/08/2005'' (last time the server was pinged)
**Tag #7
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''87'' <- Tag name: ''87'' (Max users)
***''E0930400'' <- Tag value: ''300000'' (max users)
**Tag #8
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''88'' <- Tag name: ''88'' (Soft files)
***''88130000'' <- Tag value: ''5000'' (soft files)
**Tag #9
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''89'' <- Tag name: ''89'' (Hard files)
***''10270000'' <- Tag value: ''10000'' (hard files)
**Tag #10
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''91'' <- Tag name: ''91'' (Version)
***''0400'' <- Tag value length: ''4'' (remember its [[little endian]])
***''31372E36'' <- Tag value: ''17.6'' (version)
**Tag #11
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''92'' <- Tag name: ''92'' ([http://www.ietf.org/rfc/rfc768.txt UDP] flags)
***''FB000000'' <- Tag value (in binnary, only the least valuable byte): ''11111001'' ([http://www.ietf.org/rfc/rfc768.txt UDP] flags: get sources, new tags, unicode, extended sources)
**Tag #11
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''94'' <- Tag name: ''94'' (LowID users)
***''74580000'' <- Tag value: ''22644'' (LowID users)
*Server #2
**''428722C6'' <- [[IP]]: ''198.34.135.66'' (remember its [[little endian]])
**''4E20'' <- [[Port]]: ''8270'' (remember its [[little endian]])
**''01000000'' <- ''1'' tag (remember its [[little endian]])
**Tag #1
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''01'' <- Tag name: ''1'' (Server name)
***''1E00'' <- Tag value length: ''30'' (remember its [[little endian]])
***''3E3E3E2A2A2A5757572E534558455345584F5345582E434F4D2A2A2A2020'' <- Tag value: ''***WWW.SEXESEXOSEX.COM*** '' (server name)

== More ==

For more information on tags used in [[eMule]] [[AMule_files|files]] and protocol, check the [http://hydranode.com/docs/ed2k/ed2k-tag.php ed2k tag documentation] at the [http://hydranode.com Hydranode project].

TODO

2005-08-28T07:19:20Z

83.42.86.182:

== Before we start ==

Check this [[AMule_Project_FAQ:FAQ|wiki's FAQ]] if you haven't already taken a look at it.

== Most urgent stuff ==
#Set IRC rules in a wiki article
#Document about skins ( http://forum.amule.org/thread.php?threadid=6938 )
#Document about [[hotkeys]]
#Guide to [[migrate from eMule to aMule]] (done by ''[[User:Matrixhasu|morph]]'')
#Go on for Kademlia specific articles
#Document missing [[aMule_files|files]] and Kademlia files (and explain defaults in [[amule.conf_file|config file]])
#Write good "aMule usage" documents
#(Re)work on the utilities FAQs and articles
#Network packets and protocol design (and EC)

== Someday stuff ==
*Change HTML tags for wiki tags when possible
*Only first word's appearance is linked (damn team decitions...)
*Split large articles into samller articles straight to topic
*Rework the [[Main Page]] and the whole wiki structure

== Always TODOs ==
*Translate [[Main Page|this wiki]]'s articles
*Check everything is ok

Server.met file

2005-08-28T07:19:07Z

83.42.86.182:

== File ==

'''Name:''' ''server.met''

'''Location:''' ''~/.aMule/''

== Description ==

Binary file containing the list of [[server]]s known to [[aMule]].

Because its in binary format, it must be changed within [[aMule]], or with other appropriate tools.

The format description below is for development information purposes.

== Format ==

=== File Format ===

This file's fields are written in [[little endian]] order.

'''Note:''' All digit fields are unsigned unless stated.

*Met Header (1 Byte): With value ''Ox0E'' or ''OxE0'', and is used in [[aMule]] to check for valid ''server.met'' files
*Server Count (4 Bytes): Lists the number of [[server]]s that follow
*Block of servers: Each [[server]] is constituted by the following fields:
**[[Server]] [[IP]] (4 Bytes): Simply that. The [[server]]'s [[IP]].
**[[Server]] [[Port]] (2 Bytes): Simply that. The [[port]] through which [[aMule]] will connect to the [[server]].
**Tag Count (4 Bytes): Lists the number of [[server]] tags that follows.
**Block of Tags: Each [[server]] can have a list of associated tags with the format bellow.

=== Tags Format ===

==== General tags format ====

There are two tag identifiers: A name (string) and an ID (1 Byte)

Which one is used depends on the tag value type given or on the size of the tag name. If tag name length is ''1'', an ID is used.

*Tag value type (1 Byte)
*Tag name length (2 Bytes)
*Tag name (size given above)
*Tag value length (2 Bytes) (Only when the value is a string)
*Tag value (size wither depends on [[#Tag_value_types|tag type]] or is given above if the value is a string)

==== Tag value types ====

{|
|+ Tag types
| '''Tag type (''Code'')''' || '''Explanation'''
|-
| String (''0x02'') (*) || Defines a string tag.
|-
| Unsigned 32 bits number (''0x03'') || Defines a numeric tag.
|}

'''(*):''' Systems with [http://www.unicode.org Unicode] enabled have the same tag string defined twice, the first in [http://www.unicode.org Unicode], and the second in plain [http://www.asciitable.com ASCII], which will be ignored by [http://www.unicode.org Unicode] enabled [[client]]s, and used by non-[http://www.unicode.org Unicode] ones.

==== Tag IDs ====

{|
|+ Tag IDs
| ''ID ('''code''')'' || ''Tag value type'' || ''Description''
|-
| ServerName (''0x01'') || String || Name of the [[server]]
|-
| Description (''0x0B'') || String || Short description about the server
|-
| Ping (''0x0C'') || Unsigned 32 bits number || Time (in ms) it takes to comunicate with the server
|-
| Fail (''0x0D'') || Unsigned 32 bits number || How many times [[connect]]ing to the server failed
|-
| Preference (''0x0E'') || Unsigned 32 bits number || Priority given to this server among the others (Normal=''0'', High=''1'', Low=''2'')
|-
| DNS (''0x85'') || String || [http://en.wikipedia.org/wiki/DNS DNS] of the server
|-
| Max users (''0x87'') || Unsigned 32 bits number || Maximum number of users the server allows to simoultaneously connect to it
|-
| Soft files (''0x88'') || Unsigned 32 bits number || [[Soft files]] number
|-
| Hard files (''0x89'') || Unsigned 32 bits number || [[Hard files]] number
|-
| Last ping (''0x90'') || Unsigned 32 bits number || Last time the server was [[ping]]ed
|-
| Version (''0x91'') || String / Unsigned 32 bits number || Version and name of the software the server is running to support the [[FAQ_ed2k|ed2k]] [[network]]
|-
| [http://www.ietf.org/rfc/rfc768.txt UDP] flags (''0x92'') || Unsigned 32 bits number || Informs of the actions the server accepts through [http://www.ietf.org/rfc/rfc768.txt UDP] connections. This flags are:
*''0x01'': Get sources
*''0x02'': Get files
*''0x08'': New tags
*''0x10'': Unicode
*''0x20'': Get extended sources info
|-
| Auxiliary [[port]]s list (''0x93'') || String || Some servers have additional ports open for those [[user]]s who cannot connect to the standard one (usually because they have a firewall which tries to stop [[P2P]] connections). This servers tell in this field which additional ports they have open. Each additional port is separated from the others by a coma ('','').
|-
| [[LowID]] [[client]]s (''0x94'') || Unsigned 32 bits number || Number of users connected with a LowID
|}

==== Tag Names ====

{| border=0
|+ There are at the moment two tag names recognized by [[aMule]]:
| width="100px" | ''Tag Name'' || ''Tag Value''
|-
| "files" || Unsigned 32 bits number || Shows the number of [[file]]s registered in the [[server]]
|-
|"users" || Unsigned 32 bits number || Shows the number of [[user]]s registered in the [[server]]
|}

== Example ==

The following is an example file:

''E03800000050EFC86CB80B0C000000020100010A004269472042616E4720390201000B0E0077''
''77772E42694742616E472E746F0305007573657273EF1A010003050066696C657331DC8C0003''
''01000C9C00000003010090332B114303010087E0930400030100888813000003010089102700''
''0002010091040031372E3603010092FB0000000301009474580000428722C64E200C00000002''
''0100011E003E3E3E2A2A2A5757572E534558455345584F5345582E434F4D2A2A2A2020''

Here goes the explanation of the file:

*''E0'' <- Validation initial value
*''02000000'' <- ''2'' servers will be listed (remember its [[little endian]])
*Server #1:
**''50EFC86C'' <- [[IP]]: ''108.200.239.80.'' (remember its [[little endian]])
**''B80B'' <- [[Port]]: ''3000'' (remember its [[little endian]])
**''0C000000'' <- ''12'' tags (remember its [[little endian]])
**Tag #1
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''01'' <- Tag name: ''1'' (Server name)
***''0A00'' <- Tag value length: ''10'' (remember its [[little endian]])
***''4269472042616E472039'' <- Tag value: ''BiG BanG 9'' (server name)
**Tag #2
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''0B'' <- Tag name: ''0B'' (Description)
***''0E00'' <- Tag value length: ''14'' (remember its [[little endian]])
***''7777772E42694742616E472E746F'' <- Tag value: ''www.BiGBanG.to'' (server description)
**Tag #3
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0500'' <- Tag name length: ''5'' (remember its [[little endian]])
***''7573657273'' <- Tag name: ''users'' (this is a string, not a code)
***''EF1A0100'' <- Tag value: ''72431'' (remember its [[little endian]])
**Tag #4
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0500'' <- Tag name length: ''5'' (remember its [[little endian]])
***''66696C6573'' <- Tag name: ''files'' (this is a string, not a code)
***''31DC8C00'' <- Tag value: ''9231409'' (remember its [[little endian]])
**Tag #5
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''0C'' <- Tag name: ''0C'' (Ping)
***''9C000000'' <- Tag value: ''156'' (ping time in ms)
**Tag #6
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''90'' <- Tag name: ''90'' (Last ping)
***''332B1143'' <- Tag value: ''5:10:43 28/08/2005'' (last time the server was pinged)
**Tag #7
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''87'' <- Tag name: ''87'' (Max users)
***''E0930400'' <- Tag value: ''300000'' (max users)
**Tag #8
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''88'' <- Tag name: ''88'' (Soft files)
***''88130000'' <- Tag value: ''5000'' (soft files)
**Tag #9
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''89'' <- Tag name: ''89'' (Hard files)
***''10270000'' <- Tag value: ''10000'' (hard files)
**Tag #10
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''91'' <- Tag name: ''91'' (Version)
***''0400'' <- Tag value length: ''4'' (remember its [[little endian]])
***''31372E36'' <- Tag value: ''17.6'' (version)
**Tag #11
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''92'' <- Tag name: ''92'' ([http://www.ietf.org/rfc/rfc768.txt UDP] flags)
***''FB000000'' <- Tag value (in binnary, only the least valuable byte): ''11111001'' ([http://www.ietf.org/rfc/rfc768.txt UDP] flags: get sources, new tags, unicode, extended sources)
**Tag #11
***''03'' <- Tag type ''3'' (Unsigned 32 bits number)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''94'' <- Tag name: ''94'' (LowID users)
***''74580000'' <- Tag value: ''22644'' (LowID users)
*Server #2
**''428722C6'' <- [[IP]]: ''198.34.135.66'' (remember its [[little endian]])
**''4E20'' <- [[Port]]: ''8270'' (remember its [[little endian]])
**''01000000'' <- ''1'' tag (remember its [[little endian]])
**Tag #1
***''02'' <- Tag type ''2'' (String)
***''0100'' <- Tag name length: ''1'' (remember its [[little endian]])
***''01'' <- Tag name: ''1'' (Server name)
***''1E00'' <- Tag value length: ''30'' (remember its [[little endian]])
***''3E3E3E2A2A2A5757572E534558455345584F5345582E434F4D2A2A2A2020'' <- Tag value: ''***WWW.SEXESEXOSEX.COM*** '' (server name)

== More ==

For more information on tags used in [[eMule]] [[AMule_files|files]] and protocol, check the [http://hydranode.com/docs/ed2k/ed2k-tag.php ed2k tag documentation] at the [http://hydranode.com Hidranode project].

Soft files

2005-08-28T05:36:35Z

83.42.86.182:

Softfiles is the minimun amount of files you must share on the [[server]] (the softfiles amount is specific on each [[server]]).

If you share less amount of files than the softfiles limit, the [[server]] will give you a penalty (what will the penalty be? Depends on the [[server]]).

You might also want to know what the [[hard files]] limit is.

Migrate from eMule to aMule

2005-08-28T05:25:05Z

83.42.86.182:

Here you'll find some tips about the migration of configuration & [[download]] [[file]]s from [[eMule]] to [[aMule]].

== Brief story ==

[[eDonkey2000]] was born some years ago and its great protocol, [[FAQ_ed2k|ed2k]] takes itself into the Olympo of file [[share|sharing]] programs.

Some coders, unsatisfied by that [[client]], started developing a new one, called [[eMule]]. Its source code was open, so anyone (able...) can read it and modify it, and so was. Many client versions came up with patches and new code. Fastly, the [[eDonkey2000]] guys starts arguing against [[eMule]], blaming that the [[P2P]] [[network]] goes constantly slower due to 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 [http://www.kernel.org Linux] community started developing a [http://www.kernel.org 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 rumping up: try to port the changes from [[eMule]] to a [http://www.kernel.org Linux] client: [[aMule]] was born. This fastly became the de facto standard enkey client for [http://www.kernel.org Linux].

[[eDonkey2000]] is now almost dead, and wants even to be payed for a professional version of its client...

== Migration ==

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 temporary file format is compatible, but if we are talking about configurations files, then things change.

Follow my notes below about the migration from [[eMule]] to [[aMule]] of all my downloads.

== Configuration Files ==

There are two important parts in [[eMule]]: the configuration files and temp/shared files. Let's start with configuration files.

In [[eMule]], these files are store under ''config'' directory. In [[aMule]], instead, the configuration files are store under ''~/.aMule'' directory. So the easy step is to copy the files from the [[eMule]]'s configuration directory to [[aMule]]'s. Good, so let's look further...

=== Configuration Files Automatically Imported ===

Many files are read and correctly imported into [[aMule]]; aong them there are:

*''[[clients.met_file|clients.met]]'', stores the other clients [[FAQ_ed2k#What_is_all_this_talk_about_credits,_ratings_and_scoring_about?|credits]]. 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]].
*''[[known.met_file|known.met]]'', it's where details about the downloaded files are stored, the ones printed in green when [[search]]ed again.
*''[[known2.met_file|known2.met]]'', it's where [[AICH]] hashes of shared files are stored.
*''[[server.met_file|server.met]]'' and [[staticservers.dat_file|staticservers.dat]], it contains the saved [[eMule]] [[server]]s.
*''[[ipfilter.dat_file|ipfilter.dat]]'' and ''ipfilter_static.dat'', which contain the [[IP]] denied to [[connect]]/share files with you.
*''[[emfriends.met_file|emfriends.met]]'', it contains the [[friend]]s list.
*''[[addresses.dat file|addresses.dat]]'' contains a list of URLs from where [[aMule]] will download server.met files to merge with it's current server.met file.
*''[[cryptkey.dat_file|cryptkey.dat]]'' and ''preferences.dat'', they uniquely identify you for other clients, so you can keep credits to their side.
*''[[key_index.dat file|key_index.dat]]'', ''[[load_index.dat file|load_index.dat]]'', ''[[nodes.dat file|nodes.dat]]'', ''[[preferencesKad.dat file|preferencesKad.dat]]'' and ''[[src_index.dat file|src_index.dat]]'' are [[Kademlia]] files.
*''[[shareddir.dat file|shareddir.dat]]'' contains the [[hash]]es of the [[share]]d [[file]]s, but it is only compatible with [[eMule]] when using [[aMule]] '''for [http://www.microsoft.com/windows Windows]'''.

These were the good news. The bad ones still have to come...

=== Configuration Files NOT Automatically Imported ===

Here starts the "war bulletin":

*Configuration file: [[eMule]] uses ''preferences.ini'' but [[aMule]] uses ''[[amule.conf_file|amule.conf]]''.
*[[Category|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 [http://www.microsoft.com/windows 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.

Further you'll find how I've imported the missing configurations.

== Importing Missing Configurations ==

We have just said that some configurations are not automatically loaded into [[aMule]] from [[eMule]]; try to find out what we can do to import those data into [[aMule]].

=== Importing Categories ===

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:

[General]
Count=...
[Cat\#1]
Title=...
Incoming=...
Comment=...
Color=...
Priority=...
[Cat\#2]
Title=...
Incoming=...
Comment=
Color=...
Priority=...
...

'''Note:''' I don't know if importing the categories before importing the temp files, they will be classified as in [[eMule]]; I've imported temp files before the categories, but I don't think they will be placed in the tabs as they were in [[eMule]] (if someone can confirm this...).

=== Importing Statistics ===

[[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...

=== Other configurations ===

Configurations not yet imported are the program strictly ones. They are, for example, about the [http://www.ietf.org/rfc/rfc793.txt TCP] and [http://www.faqs.org/rfcs/rfc768.html 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 a real brave guy, you can try to import directly some keys from ''preferences.ini'' to ''amule.conf'', but then do not argue if it doesn't work...

== Temporary & Sharing Files ==

Temporary files are compatible between [[eMule]] and [[aMule]], so you only have to set the ''Temp'' dir inside [[aMule]] (and let it [[hash|rehash]] all files) to have them newly available to download.

For sharing files we have very few things to do: since they are already downloaded, the only thing to do is say to [[aMule]] where they are and wait for rehashing.

== In the end... ==

Those are the steps I've followed to migrate from [[eMule]] to [[aMule]]. Some things may be wrong, and others maybe could be done better, so if any corrections/ideas/additions come to your mind, take the time to update this article!

Nodes.dat file

2005-08-28T05:13:27Z

83.42.86.182:

== File ==

'''Name:''' ''nodes.dat''

'''Location:''' ''~/.aMule/''

== Description ==

This file stores details about other known [[Kademlia]] [[client]]s (also known as [[node]]s).

It is usually used to achieve a successfull [[bootstrap]] faster.

== Format ==

As you can see, all the fields are stored without any separator character. This is done like this because all the fields have a specific size:
*''Number of contacts'': Number of contacts that will be listed (4 bytes)

After specifying the number of contacts that will be listed, the file lists them. Each contact takes 25 bytes, splitted into the following fields:
*''ClientID'': The contact's [[ClientID]] (16 bytes)
*''IP'': The contact's [[IP]] (4 bytes)
*''UDP Port'': The [http://www.ietf.org/rfc/rfc768.txt UDP] [[port]] to [[connect]] to when trying to reach the contact (2 bytes)
*''TCP Port'': The [http://www.ietf.org/rfc/rfc793.txt TCP] [[port]] to [[connect]] to when trying to reach the contact (2 bytes)
*''Type'': This indicates the [[type]] of the contact, which is how much you can be confident on that contact (a scale from ''0'' to ''4'', being ''0'' the best and ''4'' the worst). (1 byte)

Once this data is put together, it is stored in little-endian.

== Example ==

The following is a hex dump of an hypothetic ''preferences.dat'' file:

''0200000012257425DBA4EDDBD097150757404486E55E04DE40123612021F64632587A31EC2FC8566C4A9BAB184E6E9B7D44012361202''

In the above example, the following data can be seen:

*Number of contacts: ''2'' (In hex: ''02000000'', remember it's in [[little endian]])
*Contact #1:
**ClientID: ''12257425DBA4EDDBD097150757404486''
**IP: ''222.4.94.229'' (In hex: ''E55E04DE'', remember it's in [[little endian]])
**[http://www.ietf.org/rfc/rfc768.txt UDP] Port: ''1240'' (In hex: ''4012'', remember it's in [[little endian]])
**[http://www.ietf.org/rfc/rfc793.txt TCP] Port: ''1236'' (In hex: ''3612'', remember it's in [[little endian]])
**Type: ''2'' (In hex: ''02'')
*Contact #2:
**ClientID: ''1F64632587A31EC2FC8566C4A9BAB184''
**IP: ''212.183.233.230'' (In hex: ''E6E9B7D4'', remember it's in [[little endian]])
**[http://www.ietf.org/rfc/rfc768.txt UDP] Port: ''1240'' (In hex: ''4012'', remember it's in [[little endian]])
**[http://www.ietf.org/rfc/rfc793.txt TCP] Port: ''1236'' (In hex: ''3612'', remember it's in [[little endian]])
**Type: ''2'' (In hex: ''02'')

== Extra ==

Since the ''number of contacts'' field is 4 bytes long, the maximum number of [[node]]s you could store in this file is 4294967296 (~4300M), which should be far enough. Anyway, since this number is so big, [[aMule]], [[eMule]] and all clients have hard limitted the amount of contacts that can be stored ([[aMule]]'s hard limit is ''5000'').

Since ''Type 4'' contacts are those which are marked for deletion, there should never be any ''Type 4'' contact in the ''nodes.dat'' file. If there was, it would just be ignored when reading the file.

Type

2005-08-28T05:12:55Z

83.42.86.182:

In the [[Kademlia]] [[network]], the contact type is a way to measure how much you can be confident on that contact.

Initially, contacts are given a ''Type 3'' status when they are known.

Periodically the [[client]] will check if that contact is still alive.

Depending on how long that contact has been alive (on the current session) it will be promoted to more confident types:
*''Type 4'': The contact must be deleted (usually because it is not reachable).
*''Type 3'': This is the type all contacts are given initially, when they are known.
*''Type 2'': This are contacts which have been known for less than an hour but have proven to be still alive.
*''Type 1'': This are contacts which have been known for less than two hours but have proven to be still alive.
*''Type 0'': This are contacts which have been known for two hours or more and have proven to be still alive.

A contact's type is kept between sessions, so that your client knows those contacts which are most time [[connect]]ed to the Kademlia network.

To sum up, types can go from ''0'' to ''4'', being ''0''-contacts the best and ''4''-contacts the worst.

Nodes.dat file

2005-08-28T05:05:57Z

83.42.86.182:

== File ==

'''Name:''' ''nodes.dat''

'''Location:''' ''~/.aMule/''

== Description ==

This file stores details about other known [[Kademlia]] [[client]]s (also known as [[node]]s).

It is usually used to achieve a successfull [[bootstrap]] faster.

== Format ==

As you can see, all the fields are stored without any separator character. This is done like this because all the fields have a specific size:
*''Number of contacts'': Number of contacts that will be listed (4 bytes)

After specifying the number of contacts that will be listed, the file lists them. Each contact takes 25 bytes, splitted into the following fields:
*''ClientID'': The contact's [[ClientID]] (16 bytes)
*''IP'': The contact's [[IP]] (4 bytes)
*''UDP Port'': The [http://www.ietf.org/rfc/rfc768.txt UDP] [[port]] to [[connect]] to when trying to reach the contact (2 bytes)
*''TCP Port'': The [http://www.ietf.org/rfc/rfc793.txt TCP] [[port]] to [[connect]] to when trying to reach the contact (2 bytes)
*''Type'': This indicates the [[type]] of the contact, which is how much you can be confident on that contact (a scale from 0 to 4, being 0 the best and 4 the worst). (1 byte)

Once this data is put together, it is stored in little-endian.

== Example ==

The following is a hex dump of an hypothetic ''preferences.dat'' file:

''0200000012257425DBA4EDDBD097150757404486E55E04DE40123612021F64632587A31EC2FC8566C4A9BAB184E6E9B7D44012361202''

In the above example, the following data can be seen:

*Number of contacts: ''2'' (In hex: ''02000000'', remember it's in [[little endian]])
*Contact #1:
**ClientID: ''12257425DBA4EDDBD097150757404486''
**IP: ''222.4.94.229'' (In hex: ''E55E04DE'', remember it's in [[little endian]])
**[http://www.ietf.org/rfc/rfc768.txt UDP] Port: ''1240'' (In hex: ''4012'', remember it's in [[little endian]])
**[http://www.ietf.org/rfc/rfc793.txt TCP] Port: ''1236'' (In hex: ''3612'', remember it's in [[little endian]])
**Type: ''2'' (In hex: ''02'')
*Contact #2:
**ClientID: ''1F64632587A31EC2FC8566C4A9BAB184''
**IP: ''212.183.233.230'' (In hex: ''E6E9B7D4'', remember it's in [[little endian]])
**[http://www.ietf.org/rfc/rfc768.txt UDP] Port: ''1240'' (In hex: ''4012'', remember it's in [[little endian]])
**[http://www.ietf.org/rfc/rfc793.txt TCP] Port: ''1236'' (In hex: ''3612'', remember it's in [[little endian]])
**Type: ''2'' (In hex: ''02'')

== Extra ==

Since the ''number of contacts'' field is 4 bytes long, the maximum number of [[node]]s you could store in this file is 4294967296 (~4300M), which should be far enough. Anyway, since this number is so big, [[aMule]], [[eMule]] and all clients have hard limitted the amount of contacts that can be stored ([[aMule]]'s hard limit is ''5000'').

Since ''Type 4'' contacts are those which are marked for deletion, there should never be any ''Type 4'' contact in the ''nodes.dat'' file. If there was, it would just be ignored when reading the file.

Nodes.dat file

2005-08-28T04:43:31Z

83.42.86.182:

== File ==

'''Name:''' ''nodes.dat''

'''Location:''' ''~/.aMule/''

== Description ==

This file stores details about other known [[Kademlia]] [[client]]s (also known as [[node]]s).

It is usually used to achieve a successfull [[bootstrap]] faster.

== Format ==

As you can see, all the fields are stored without any separator character. This is done like this because all the fields have a specific size:
*''Number of contacts'': Number of contacts that will be listed (4 bytes)

After specifying the number of contacts that will be listed, the file lists them. Each contact takes 25 bytes, splitted into the following fields:
*''ClientID'': The contact's [[ClientID]] (16 bytes)
*''IP'': The contact's [[IP]] (4 bytes)
*''UDP Port'': The [http://www.ietf.org/rfc/rfc768.txt UDP] [[port]] to [[connect]] to when trying to reach the contact (2 bytes)
*''TCP Port'': The [http://www.ietf.org/rfc/rfc793.txt TCP] [[port]] to [[connect]] to when trying to reach the contact (2 bytes)
*''Type'': (1 byte)

Once this data is put together, it is stored in little-endian.

== Example ==

The following is a hex dump of an hypothetic ''preferences.dat'' file:

''0200000012257425DBA4EDDBD097150757404486E55E04DE40123612021F64632587A31EC2FC8566C4A9BAB184E6E9B7D44012361202''

In the above example, the following data can be seen:

*Number of contacts: ''2'' (In hex: ''02000000'', remember it's in [[little endian]])
*Contact #1:
**ClientID: ''12257425DBA4EDDBD097150757404486''
**IP: ''222.4.94.229'' (In hex: ''E55E04DE'', remember it's in [[little endian]])
**[http://www.ietf.org/rfc/rfc768.txt UDP] Port: ''1240'' (In hex: ''4012'', remember it's in [[little endian]])
**[http://www.ietf.org/rfc/rfc793.txt TCP] Port: ''1236'' (In hex: ''3612'', remember it's in [[little endian]])
**Type: ''2'' (In hex: ''02'')
*Contact #2:
**ClientID: ''1F64632587A31EC2FC8566C4A9BAB184''
**IP: ''212.183.233.230'' (In hex: ''E6E9B7D4'', remember it's in [[little endian]])
**[http://www.ietf.org/rfc/rfc768.txt UDP] Port: ''1240'' (In hex: ''4012'', remember it's in [[little endian]])
**[http://www.ietf.org/rfc/rfc793.txt TCP] Port: ''1236'' (In hex: ''3612'', remember it's in [[little endian]])
**Type: ''2'' (In hex: ''02'')

== Extra ==

Since the ''number of contacts'' field is 4 bytes long, the maximum number of [[node]]s you could store in this file is 4294967296 (~4300M), which should be far enough. Anyway, since this number is so big, [[aMule]], [[eMule]] and all clients have hard limitted the amount of contacts that can be stored ([[aMule]]'s hard limit is ''5000'').

TODO

2005-08-28T04:35:33Z

83.42.86.182:

== Before we start ==

Check this [[AMule_Project_FAQ:FAQ|wiki's FAQ]] if you haven't already taken a look at it.

== Most urgent stuff ==
#Example in [[server.met file]]
#Set IRC rules in a wiki article
#Document about skins ( http://forum.amule.org/thread.php?threadid=6938 )
#Document about [[hotkeys]]
#Guide to [[migrate from eMule to aMule]] (done by ''[[User:Matrixhasu|morph]]'')
#Go on for Kademlia specific articles
#Document missing [[aMule_files|files]] and Kademlia files (and explain defaults in [[amule.conf_file|config file]])
#Write good "aMule usage" documents
#(Re)work on the utilities FAQs and articles
#Network packets and protocol design (and EC)

== Someday stuff ==
*Change HTML tags for wiki tags when possible
*Only first word's appearance is linked (damn team decitions...)
*Split large articles into samller articles straight to topic
*Rework the [[Main Page]] and the whole wiki structure

== Always TODOs ==
*Translate [[Main Page|this wiki]]'s articles
*Check everything is ok

Preferences.dat file

2005-08-28T04:17:00Z

83.42.86.182:

== File ==

'''Name:''' ''preferences.dat''

'''Location:''' ''~/.aMule/''

== Description ==

This file stores the userhash and the configuration file version for your client in the [[FAQ_ed2k|ed2k network]].
In old times, this file used to store [[eMule]]'s configuration.

== Data ==

The current configuration file version is 20 (in hex: ''0x14'').

== Format ==

All the fields are stored without any separator character. This is done like this because all the fields have a specific size:
*''Version'': 1 byte
*''Userhash'': 2 bytes
*''Length'': 4 bytes
*''Flags'': 4 bytes
*''Showcmd'': 4 bytes
*''Maxpositionx'': 4 bytes
*''Maxpositiony'': 4 bytes
*''Minpositionx'': 4 bytes
*''Minpositiony'': 4 bytes
*''Normalpositionleft'': 4 bytes
*''Normalpositiontop'': 4 bytes
*''Normalpositionright'': 4 bytes
*''Normalpositionbottom'': 4 bytes

The relevant fields are the following:
*''Version'': Specifies the configuration file version (the format defined in this articles corresponds to version 20).
*''Userhash'': The userhash.
*''Length'': Length in bytes of the file not counting th Version and Userhash fields (should be 38 bytes).

Once this data is put together, it is stored in little-endian.

== Example ==

The following is a hex dump of an hypothetic ''preferences.dat'' file:

''a3143e6f12dd445b12a0c3c6f7ca5b2d00230000000000000000000000000000000000000000000000000000''

In the above example, the following data can be seen:

*Configuration file version: ''20'' (In hex: ''0x14'')
*Userhash: ''A36F3EDD125B44A012C6C3CAF72D5B23''
*Other fields: Set to zero (''0'')

== Extra ==

[[aMule]] ignores the ''main window position'', ''main window size'', ''length'', ''flags'' and ''showcmd'' fields in this file. That's the reason why this fields aren't explained in this article.

All this ignored fields are set to zero by [[aMule]]. Even if they were set to some other value, [[aMule]] will never read those values. Instead, it uses the preferences set in ''~/.eMule''

Migrate from eMule to aMule

2005-08-28T04:13:22Z

83.42.86.182:

Here you'll find some tips about the migration of configuration & [[download]] [[file]]s from [[eMule]] to [[aMule]].

== Brief story ==

[[eDonkey2000]] was born some years ago and its great protocol, [[FAQ_ed2k|ed2k]] takes itself into the Olympo of file [[share|sharing]] programs.

Some coders, unsatisfied by that [[client]], started developing a new one, called [[eMule]]. Its source code was open, so anyone (able...) can read it and modify it, and so was. Many client versions came up with patches and new code. Fastly, the [[eDonkey2000]] guys starts arguing against [[eMule]], blaming that the [[P2P]] [[network]] goes constantly slower due to 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 [http://www.kernel.org Linux] community started developing a [http://www.kernel.org 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 rumping up: try to port the changes from [[eMule]] to a [http://www.kernel.org Linux] client: [[aMule]] was born. This fastly became the de facto standard enkey client for [http://www.kernel.org Linux].

[[eDonkey2000]] is now almost dead, and wants even to be payed for a professional version of its client...

== Migration ==

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 temporary file format is compatible, but if we are talking about configurations files, then things change.

Follow my notes below about the migration from [[eMule]] to [[aMule]] of all my downloads.

== Configuration Files ==

There are two important parts in [[eMule]]: the configuration files and temp/shared files. Let's start with configuration files.

In [[eMule]], these files are store under ''config'' directory. In [[aMule]], instead, the configuration files are store under ''~/.aMule'' directory. So the easy step is to copy the files from the [[eMule]]'s configuration directory to [[aMule]]'s. Good, so let's look further...

=== Configuration Files Automatically Imported ===

Many files are read and correctly imported into [[aMule]]; aong them there are:

*''[[clients.met_file|clients.met]]'', stores the other clients [[FAQ_ed2k#What_is_all_this_talk_about_credits,_ratings_and_scoring_about?|credits]]. 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]].
*''[[known.met_file|known.met]]'', it's where details about the downloaded files are stored, the ones printed in green when [[search]]ed again.
*''[[known2.met_file|known2.met]]'', it's where [[AICH]] hashes of shared files are stored.
*''[[server.met_file|server.met]]'' and [[staticservers.dat_file|staticservers.dat]], it contains the saved [[eMule]] [[server]]s.
*''[[ipfilter.dat_file|ipfilter.dat]]'' and ''ipfilter_static.dat'', which contain the [[IP]] denied to [[connect]]/share files with you.
*''[[emfriends.met_file|emfriends.met]]'', it contains the [[friend]]s list.
*''[[addresses.dat file|addresses.dat]]'' contains a list of URLs from where [[aMule]] will download server.met files to merge with it's current server.met file.
*''[[cryptkey.dat_file|cryptkey.dat]]'' and ''preferences.dat'', they uniquely identify you for other clients, so you can keep credits to their side.
*''[[key_index.dat file|key_index.dat]]'', ''[[load_index.dat file|load_index.dat]]'', ''[[nodes.dat file|nodes.dat]]'', ''[[preferencesKad.dat file|preferencesKad.dat]]'' and ''[[src_index.dat file|src_index.dat]]'' are [[Kademlia]] files.
*''[[shareddir.dat file|shareddir.dat]]'' contains the [[hash]]es of the [[share]]d [[file]]s, but it is only compatible with [[eMule]] when using [[aMule]] '''for [http://www.microsoft.com/windows Windows]'''.

These were the good news. The bad ones still have to come...

=== Configuration Files NOT Automatically Imported ===

Here starts the "war bulletin":

*Configuration file: [[eMule]] uses ''preferences.ini'' but [[aMule]] uses ''[[amule.conf_file|amule.conf]]''.
*[[Category|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 [http://www.microsoft.com/windows 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.

Further you'll find how I've imported the missing configurations.

== Importing Missing Configurations ==

We have just said that some configurations are not automatically loaded into [[aMule]] from [[eMule]]; try to find out what we can do to import those data into [[aMule]].

=== Importing Categories ===

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:

[General]
Count=...
[Cat\#1]
Title=...
Incoming=...
Comment=...
Color=...
Priority=...
[Cat\#2]
Title=...
Incoming=...
Comment=
Color=...
Priority=...
...

'''Note:''' I don't know if importing the categories before importing the temp files, they will be classified as in [[eMule]]; I've imported temp files before the categories, but I don't think they will be placed in the tabs as they were in [[eMule]] (if someone can confirm this...).

=== Importing Statistics ===

[[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 ('''TODO:''' I don't know what they mean, so leave them where they are...).

'''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...

=== Other configurations ===

Configurations not yet imported are the program strictly ones. They are, for example, about the [http://www.ietf.org/rfc/rfc793.txt TCP] and [http://www.faqs.org/rfcs/rfc768.html 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 a real brave guy, you can try to import directly some keys from ''preferences.ini'' to ''amule.conf'', but then do not argue if it doesn't work...

== Temporary & Sharing Files ==

Temporary files are compatible between [[eMule]] and [[aMule]], so you only have to set the ''Temp'' dir inside [[aMule]] (and let it [[hash|rehash]] all files) to have them newly available to download.

For sharing files we have very few things to do: since they are already downloaded, the only thing to do is say to [[aMule]] where they are and wait for rehashing.

== In the end... ==

Those are the steps I've followed to migrate from [[eMule]] to [[aMule]]. Some things may be wrong, and others maybe could be done better, so if any corrections/ideas/additions come to your mind, take the time to update this article!

Migrate from eMule to aMule

2005-08-28T04:12:49Z

83.42.86.182:

Here you'll find some tips about the migration of configuration & [[download]] [[file]]s from [[eMule]] to [[aMule]].

== Brief story ==

[[eDonkey2000]] was born some years ago and its great protocol, [[FAQ_ed2k|ed2k]] takes itself into the Olympo of file [[share|sharing]] programs.

Some coders, unsatisfied by that [[client]], started developing a new one, called [[eMule]]. Its source code was open, so anyone (able...) can read it and modify it, and so was. Many client versions came up with patches and new code. Fastly, the [[eDonkey2000]] guys starts arguing against [[eMule]], blaming that the [[P2P]] [[network]] goes constantly slower due to 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 [http://www.kernel.org Linux] community started developing a [http://www.kernel.org 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 rumping up: try to port the changes from [[eMule]] to a [http://www.kernel.org Linux] client: [[aMule]] was born. This fastly became the de facto standard enkey client for [http://www.kernel.org Linux].

[[eDonkey2000]] is now almost dead, and wants even to be payed for a professional version of its client...

== Migration ==

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 temporary file format is compatible, but if we are talking about configurations files, then things change.

Follow my notes below about the migration from [[eMule]] to [[aMule]] of all my downloads.

== Configuration Files ==

There are two important parts in [[eMule]]: the configuration files and temp/shared files. Let's start with configuration files.

In [[eMule]], these files are store under ''config'' directory. In [[aMule]], instead, the configuration files are store under ''~/.aMule'' directory. So the easy step is to copy the files from the [[eMule]]'s configuration directory to [[aMule]]'s. Good, so let's look further...

=== Configuration Files Automatically Imported ===

Many files are read and correctly imported into [[aMule]]; aong them there are:

*''[[clients.met_file|clients.met]]'', stores the other clients [[FAQ_ed2k#What_is_all_this_talk_about_credits,_ratings_and_scoring_about?|credits]]. 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]].
*''[[known.met_file|known.met]]'', it's where details about the downloaded files are stored, the ones printed in green when [[search]]ed again.
*''[[known2.met_file|known2.met]]'', it's where [[AICH]] hashes of shared files are stored.
*''[[server.met_file|server.met]]'' and [[staticservers.dat_file|staticservers.dat]], it contains the saved [[eMule]] [[server]]s.
*''[[ipfilter.dat_file|ipfilter.dat]]'' and ''ipfilter_static.dat'', which contain the [[IP]] denied to [[connect]]/share files with you.
*''[[emfriends.met_file|emfriends.met]]'', it contains the [[friend]]s list.
*''[[addresses.dat file|addresses.dat]]'' contains a list of URLs from where [[aMule]] will download server.met files to merge with it's current server.met file.
*''[[cryptkey.dat_file|cryptkey.dat]]'' and ''preferences.dat'', they uniquely identify you for other clients, so you can keep credits to their side.
*''[[key_index.dat file|key_index.dat]]'', ''[[load_index.dat file|load_index.dat]]'', ''[[nodes.dat file|nodes.dat]]'', ''[[preferencesKad.dat file|preferencesKad.dat]]'' and ''[[src_index.dat file|src_index.dat]]'' are [[Kademlia]] files.
*''[[shareddir.dat file|shareddir.dat]]'' contains the [[hash]]es of the [[share]]d [[file]]s, but it is only compatible with [[eMule]] when using [[aMule]] '''for [http://www.microsoft.com/Windows]'''.

These were the good news. The bad ones still have to come...

=== Configuration Files NOT Automatically Imported ===

Here starts the "war bulletin":

*Configuration file: [[eMule]] uses ''preferences.ini'' but [[aMule]] uses ''[[amule.conf_file|amule.conf]]''.
*[[Category|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 [http://www.microsoft.com/windows 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.

Further you'll find how I've imported the missing configurations.

== Importing Missing Configurations ==

We have just said that some configurations are not automatically loaded into [[aMule]] from [[eMule]]; try to find out what we can do to import those data into [[aMule]].

=== Importing Categories ===

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:

[General]
Count=...
[Cat\#1]
Title=...
Incoming=...
Comment=...
Color=...
Priority=...
[Cat\#2]
Title=...
Incoming=...
Comment=
Color=...
Priority=...
...

'''Note:''' I don't know if importing the categories before importing the temp files, they will be classified as in [[eMule]]; I've imported temp files before the categories, but I don't think they will be placed in the tabs as they were in [[eMule]] (if someone can confirm this...).

=== Importing Statistics ===

[[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 ('''TODO:''' I don't know what they mean, so leave them where they are...).

'''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...

=== Other configurations ===

Configurations not yet imported are the program strictly ones. They are, for example, about the [http://www.ietf.org/rfc/rfc793.txt TCP] and [http://www.faqs.org/rfcs/rfc768.html 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 a real brave guy, you can try to import directly some keys from ''preferences.ini'' to ''amule.conf'', but then do not argue if it doesn't work...

== Temporary & Sharing Files ==

Temporary files are compatible between [[eMule]] and [[aMule]], so you only have to set the ''Temp'' dir inside [[aMule]] (and let it [[hash|rehash]] all files) to have them newly available to download.

For sharing files we have very few things to do: since they are already downloaded, the only thing to do is say to [[aMule]] where they are and wait for rehashing.

== In the end... ==

Those are the steps I've followed to migrate from [[eMule]] to [[aMule]]. Some things may be wrong, and others maybe could be done better, so if any corrections/ideas/additions come to your mind, take the time to update this article!

FAQ aMule

2005-08-28T03:59:58Z

83.42.86.182:

<center>
<h4>F.A.Q on [[aMule_Project_FAQ:About|aMule]]</h4>

<h2>by ''[[User:Jacobo221|Jacobo221]]''</h2>

'''English''' | [[FAQ_aMule-es|Español]] | [[FAQ_aMule-it|Italiano]] | [[FAQ_aMule-pt_BR|Português]] | [[FAQ_aMule-fr|Français]] | [[FAQ_aMule-de|Deutsche]] | [[FAQ_aMule-nl|Nederlands]]
</center>

== What is [[aMule_Project_FAQ:About|aMule]]? ==

'''''[[aMule]] is a multi-platform client for the [[FAQ_eD2k-Kademlia|ED2K file sharing network]] and based on the windows client [[eMule]].''''' aMule started in August 2003, as a fork of [[xMule]], which is a fork of [[lMule]].

aMule currently supports [http://www.kernel.org Linux], [http://www.freebsd.org FreeBSD], [http://www.openbsd.org OpenBSD], [http://www.microsoft.com Windows], [http://www.apple.com/macosx MacOS X] and [http://www.microsoft.com/xbox X-Box] on both [http://en.wikipedia.org/wiki/64-bit#32_vs_64_bit 32 and 64 bit] computers. It should be noted that the [http://www.microsoft.com Windows] port is still in development and is not quite ready for general use.

[[aMule]] is intended to be as user friendly and feature rich as [[eMule]] and to remain faithful to the look and feel of [[eMule]] so users familiar with either [[aMule_Project_FAQ:About|aMule]] or [[eMule]] will be able switch between the two easily.

Since [[aMule_Project_FAQ:About|aMule]] is based upon the [[eMule]] codebase, new features in [[eMule]] tend to find their way into [[aMule]] soon after their inclusion into [[eMule]] so users of [[aMule_Project_FAQ:About|aMule]] can expect to ride the cutting-edge of [[FAQ_eD2k-Kademlia|ED2k]] clients.

The best part is that it's developed by a great team whom are probably even more user friendly than [[aMule_Project_FAQ:About|aMule]] itself. Join us in #amule on irc.freenode.net or visit the [http://www.amule.org/amule aMule forums] if you have any suggestions, questions, problems, bugs, patches or anything else that you might think of.

If you are interested in joining the development team, please contact us via the [http://www.amule.org/amule aMule forums] or in the IRC channel.

== How do I view a client's credits? ==

You can see any client's credits (the credits you owe the client) by right clicking on the client's nickname and selecting ''Show Details''. There is no specific value shown so you can either view the total amount of data that client has sent you or the ''Credits Modifier'' (which is called DL/UL Modifier). In the same dialog window, if that client is in your upload queue, you'll be able to view the client's rate and score on you.

== What do those colors in the progress bar mean? ==

On the downloading transfers list: 
Red: Chunks in red are chunks with no sources found on current session. 
Blue: Chunks in blue are chunks with at least one source availble. The more solid blue it is, the more sources available have been found. 
Yellow: Chunks in yellow are chunks which are being downloaded at this very moment. 
Black: Chunks in black are chunks which have already been downloaded and verified. 
Green: When a file is in green it means that it's been completely downloaded and successfully verified (so, it'll be in the Incoming folder).

On the expanded transfers list (can be viewed by double-clicking a transfer): 
Black: Chunks which that client has and you don't have. 
White: Chunks which that client doesn't have. 
Green: Chunks which that client has and you have, too. 
Yellow:Chunks which that client is currently uploading to you.

On the uploading transfers list: 
Black: That client has completed and verified that chunk. 
Grey: That client doesn't have that chunk. 
Keep in mind that not all clients support telling other clients what parts they have already completed when uploading, so some clients might have no bar at all.

On the shared files window: 
Red: When there's no source found to have that same chunk (apart from you, of course). 
Blue: The more solid the blue is, the more spread that chunk is. 
On the search windows: 
Black: Files in black are those which only a client has been found to have. 
Blue: Files in blue are those which two or more clients have been found to have. The more solid the blue is, the more clients have been found to have it. 
Red: Files in red are those which are already in the downloading queue. 
Green: Files in green are those which you are already sharing (you completely downloaded it).

== What are all these icons? ==

See section "Icons and what they signify" in the [[Getting_Started#Icons_and_What_They_Signify|Getting Started]] guide.

== What do those numbers in brackets in the sources column of the searches window mean? ==

Those are the clients who are known to have the complete file. Even if the number in brackets is 0, it doesn't mean that no one has the complete file, it juts means that no client has marked the shared file as "completed" (lots of clients don't do so). It's a way to have an idea of how many people have the complete file but not the definitive way.

== What do all those numbers in the sources column in the transfers window mean? ==

The sources format is XX/YY + ZZ (WW) where XX stands for the number of sources available (the number of sources found that you can download from). YY stands for the number of sources found (the total number of sources found) ZZ stands for the number of "Asked for another file" sources WW stands for the number of sources from whom you are currently downloading some chunk of that file.

== What do all those numbers in the priority column in the extended transfers window mean? ==

That's the queue position you have on that client for that specific file. Not all clients provide such information, so in some cases, nothing is displayed.

The number in brackets is the amount of positions you have "moved" through that client's upload queue. '''Negative''' numbers stand for positions you have '''won''' in the queue since you were added while '''positive''' numbers mean positions you've '''lost''' since since you were added. Notice that when that number is negative, it is displayed blue, while when it's positive, it's displayed red.

== Why are there two transfer rates in the uploading transfer list? ==

When you are uploading some file to some client, the uploading transfer list will show the transfer rate (speed in KBps) in which you are uploading to that client. If, at the same time, that client is uploading to you some file (or files), then the transfer rate's format will change to XX/YY where XX stands for the speed at which you are uploading to that client and YY will stand for the speed at which that client is uploading to you. If you search in the downloading transfers list you'll find that client.

This is useful if you are trying to get a rare file, since you can see which file that client is uploading to you and, if it's the rare file, you can set him a friend slot so that you upload to that client faster and gain more credits on that client (and consequently, download faster from the client).

== What is A4AF? ==

A4AF stands for ''Ask For Another File''. It is a way to optimize the resources on a specific download.

When you try to download a file, aMule gets a list of clients who are sharing that file. Some of these clients might also share some other file which you are also trying to download and, so, you might have that client in two separate download queues.

A4AF tries to avoid this situations. Why? Because you can't download two chunks at the same time from the same client. So, by setting A4AF in a specific download, you are telling aMule to search for any client in that file's download queue who is also in some other file's download queue and remove it from that other download queue. This way, you'll get more sources on that file.

You can also set a specific download to apply A4AF in the opposite way, that is, to give sources to the other downloads. This should be done on downloads which are not to be downloaded with too much hurry or which should be downloaded after some other similar file has been downloaded (in a series of files, for example). This also can be seen as a way of establishing preferences in downloads.

When the request swapping is done, the Queue Rank will be maintained.

'''NOTE:''' A source with a QR lower than 50 in the download with the higher priority will never be swapped. This is done this way to ensure it starts downloading from it.

== What is the difference between Transfered and Completed in the Transfers window? ==

Transfered shows the amount of data you have received concerning that file. This data is downloaded in a compressed format. Once the data gets to your machine, aMule processes it and decompresses it. The total useful data that can be taken from that received data (that is, the parts of that data which are actually real parts of the file you are trying to download and not headers or such stuff) is the amount that can be viewed in the Completed column.

== What is the difference between pausing and stopping a transfer? ==

When a transfer is paused, all connections related to the paused transfer are broken with the other clients so that no data is transfered, but sources aren't dropped, so that when the transfer is resumed, [[aMule_Project_FAQ:About|aMule]] will try to connect to those sources it was transferring from.

Instead, when a transfer is stopped, all sources are dropped so, when it's resumed, [[aMule_Project_FAQ:About|aMule]] will start searching for clients who are sharing that file.

== What are all those files [[aMule_Project_FAQ:About|aMule]] creates the first time it is run? ==

Most them are the same as [[eMule|eMule]]'s.

Detailed information about each and a list of all of [[aMule]]'s files can be found [[aMule files|here]].

== Can I use [[eMule|eMule]]'s files and settings and vice-versa? ==

Most of them yes. The only ones you can't share between [[aMule_Project_FAQ:About|aMule]] and [[eMule]] are the program configuration (that is, preferences.ini in [[eMule]] and ''~/.eMule'' in [[aMule_Project_FAQ:About|aMule]]). All the [[FAQ_eD2k-Kademlia|ED2K network]] related files can be successfully shared between the two applications with no more effort than copying the files in ''~/.aMule'' to the [[eMule]]'s directory and vice-versa. But have in mind that some files in ''~/.aMule'' are [[aMule_Project_FAQ:About|aMule]] specific, such as ''amulesig.dat'' or ''aMule.tmpl'', so it's better to only move those files that are in both the [[aMule_Project_FAQ:About|aMule]] and the [[eMule]] directory.

Moving half downloaded files is easy: just move them from your [[eMule]] temp directory (by default ''C:\Program files\eMule\Temp'') into ''~/.aMule/Temp'' or whatever your temp directory is in your [[aMule]] configuration.

== What is all that stuff in amulesig.dat and onlinesig.dat? ==

I guess you already read what [[amulesig.dat_file|''amulesig.dat'']] and [[onlinesig.dat_file|''onlinesig.dat'']] are for [[FAQ_aMule#What_are_all_those_files_aMule_creates_the_first_time_it_is_run?|above]].

So, this files contain the current [[signature]] (the current [[aMule]] status, if enabled, of course).

Detailed information about each of thee files can be found in the [[amulesig.dat_file|''amulesig.dat'' article]] and the [[onlinesig.dat_file|''onlinesig.dat'' article]].

== I just installed [[aMule_Project_FAQ:About|aMule]] for the first time. How do I set it up? ==

Setting up aMule properly is just a matter of tastes and depends on many factors. If you just wish a quick startup configuration, then continue reading.

Open [[aMule_Project_FAQ:About|aMule]] and click on the Preferences button. Set a nickname and the language in which you wish to have [[aMule_Project_FAQ:About|aMule]]. Then switch to the Connection tab and input your Line Capacities. Then input the Bandwidth Limits according to the maximum amount of bandwidth you want [[aMule_Project_FAQ:About|aMule]] to use. Then switch to the Directories tab and set a directory for both the temporary files (where files will be stored until they are completely downloaded) and the completed files. Finally, select the directories which you want to share. It is not recommended to share too much files. Read below "What are the best settings I can set to have a nice download rate". To select recursively all directories inside a certain directory read [[aMule_problems#Is there any way to recursively select a whole directory and its contents?|Is there any way to recursively select a whole directory and its contents?]].

== Will [[aMule_Project_FAQ:About|aMule]] handle my [[xMule]] and [[lMule]] files? What should I do? ==

[[aMule_Project_FAQ:About|aMule]] automatically handles both [[lMule]] and [[xMule]]'s configuration files, but in different ways:

[[lMule]] has been discontinued for several years now, so [[aMule_Project_FAQ:About|aMule]] understands that you are replacing [[lMule]] with [[aMule_Project_FAQ:About|aMule]], so it renames ~/.lMule folder to ~/.aMule. If you used ~/.lMule/Temp and ~/.lMule/Incoming as your temporary and downloading directories respectively, you should change the paths in Preferences to ~/.aMule/Temp and ~/.aMule/Incoming respectively.

If a ~/.xMule directory is found, it will be kept unchanged and [[aMule]] will just copy the configuration files found in it. That means that the files you were downloading will remain in the ~/.xMule directory if they were downloading there, but since [[aMule_Project_FAQ:About|aMule]] has handled [[xMule]]'s configuration files, it will use still use it. You can either live with that, or move directories ~/.xMule/Temp and ~/.xMule/Incoming into ~/.aMule and change directories in Preferences.

== How do I start my [[aMule_Project_FAQ:About|aMule]] experience? ==

Just click on the Connect button. You should have some servers listed on the Servers window, though. If you have no servers listed, then click on the little button below the Connect button in the Servers window before clicking the Connect button. After some time, [[aMule_Project_FAQ:About|aMule]] will be connected to some server (you'll know because in the lower right corner the "Not connected" message will disappear). When connected, switch to the Search window and search for the file you want and once you find the file you want, double-click on it.

For general [[aMule_Project_FAQ:About|aMule]] usage, join [[aMule_Project_FAQ:About|aMule]] #amule in irc.freenode.net or ask in forums at [http://www.amule.org/amule http://www.amule.org/amule]

== What are the best settings I can set to have a nice download rate? ==

If you understood "Is there any limit on the [[FAQ_eD2k-Kademlia|ED2K]] network?" then you might have seen that, if your provider allows you, the best is to have the upload limit set to a minimum of 10 KBps. Also, if you understood "What is all that credits, rate and score stuff about?", you might also understand that the more you upload, the more you download, so take the upload limit up as much as you can. A good tip (thanks to kaouete) when you are trying to download some rare or "never completing" file, is, whenever you see someone uploading to you some chunk of that file, give that client a friend slot so that, if it tries to download something from you, it gets preference and you gain credits on that client.

== Is there a way to open a text file and load all the ed2k links from the file? ==

Yes, there is. Just place all the ed2k links you want to download in a text file, each ed2k link in a separate line. Name that file ''ED2KLinks'' then place it in ''~/.aMule'' and aMule will automatically detect it, add all those ed2k links to download and remove the file.

You might want to read [[ED2KLinks_file|this]] to know more about this file.

== Can I manage [[aMule_Project_FAQ:About|aMule]] remotely through telnet in the same way I do with [[eDonkey2000|eDonkey]]? ==

Yes you can, but not exactly in the same way as you do with [[eDonkey2000|eDonkey]]. Just start a normal telnet (or ssh) session with the host computer (the one running [[aMule_Project_FAQ:About|aMule]]) and, once in, use amulecmd to take control over [[aMule_Project_FAQ:About|aMule]]. To start new downloads just use the [[ed2k_command|ed2k command]]. Remember [[aMuleCMD]] must be configured.

Another aMule utility that might be of your interest is [[CAS]] (which's command is <code>cas</code>) which will show basic [[aMule_Project_FAQ:About|aMule]] statistics.

Also, [[amuleweb|aMule WebServer]] might be what you are looking for if you can and don't mind using a web browser on the client computer. Have in mind that aMule WebBrowser must also be configured.

== Is there any way to start [[aMule_Project_FAQ:About|aMule]] with no graphical interface? ==

Yes. Since aMule 2.0.0-rc6, you can use aMule Daemon, which can be executed on the command line by typing ''amuled''. To control it, use either aMuleWeb, aMuleCMD or any other such application for remotely controlling aMule.

Anyway, up to aMule 2.0.0-rc6, [[aMule_Project_FAQ:About|aMule]] was a monolithic application. This means that core and GUI were whole inseparable block.

So, for those using an old aMule version or who refuse to use aMuled (aMule Daemon), there are still two walkarounds to run [[aMule_Project_FAQ:About|aMule]] on command line but they're not direct ways:
*Through ''[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]''
*Through ''[http://www.realvnc.com VNC]''

'''Through ''[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]:''' 
You should run <code>[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]</code> and then run aMule in it. Afterwards you can take control over [[aMule_Project_FAQ:About|aMule]] using [[aMuleCMD]] and [[ed2k_command|ed2k]] in the same way as you would if you were accessing [[aMule_Project_FAQ:About|aMule]] remotely over telnet (see above).

Short example: 
Run [http://xfree.org/4.4.0/Xvfb.1.html Xvfb]: 
<code>Xvfb :1 -screen 0 640x480x16 &</code> 
Set display to use for amule: 
<code>export DISPLAY=:1</code> 
Then run [[aMule_Project_FAQ:About|aMule]]: 
<code>amule &</code> 
Note: After running <code>export DISPLAY=:1</code>, all graphical applications launched from that shell will be opened in [http://xfree.org/4.4.0/Xvfb.1.html Xvfb]'s display. To avoid this, you can run [[aMule_Project_FAQ:About|aMule]] with the following command, so that only [[aMule_Project_FAQ:About|aMule]] runs there: 
<code>DISPLAY=:1 amule &</code> 
'''INFO:''' See the [[Screen]] page to know more about the [[Screen]] command

'''Through ''[http://www.realvnc.com VNC]:''' 
It's also possible to use ''vncserver'' instead of [http://xfree.org/4.4.0/Xvfb.1.html Xvfb] to achieve something similar. Just install ''vncserver'' and execute ''vncserver :0 -geometry 1024x768'' followed by ''export DISPLAY=:0''. This will create a hidden [http://xfree.org X] server, accessible only remotely using a [http://www.realvnc.com VNC] client. Once the [http://xfree.org X] server is running, you will need a window manager to manage [[aMule]] window (well, it's not really needed, but it's useful if you want to be able to close [[aMule]] without simply killing it), I recommend [http://fluxbox.sourceforge.net FluxBox] due to its low CPU and memory requirements. Just start it with ''fluxbox &'' and then run [[aMule]] with ''amule &''. Now you can connect to the [http://www.realvnc.com VNC] server and see the [[aMule]] window.

Keep in mind that if [[aMule]] shows any dialog that requires user input (like the one showed the first time [[aMule]] is executed), it will get stuck there until someone connects to the [http://www.realvnc.com VNC] server and clicks ok in the dialog. Usually, this should only need to be done once (and this connection may be used to update the serverlist and set the preferences), from then on [[aMule]] will start without user interaction, showing only some informational messages at startup.

If you need help on this issue, search [[aMule_Project_FAQ:About|aMule]]'s [http://www.amule.org/amule forums] or join #amule [[IRC]] channel at irc.freenode.net and ask.

== Can I run two [[aMule_Project_FAQ:About|aMule]] instances at the same time? ==

Yes you can, although it is not recommended. [[aMule_Project_FAQ:About|aMule]] will only check if the concurrent user is running some [[aMule_Project_FAQ:About|aMule]] instance, so you can run as many [[aMule_Project_FAQ:About|aMule]] instances as user accounts you have access to. To do this, just run <code>xhost +</code> and then <code>su</code> as another user and run aMule from that shell.

Be aware, since [[aMule_Project_FAQ:About|aMule]] can't check if a user is running [[aMule_Project_FAQ:About|aMule]] on another X display. So, if your account is already running some [[aMule_Project_FAQ:About|aMule]] instance in some other X display, do not run another [[aMule_Project_FAQ:About|aMule]] instance on another X display or you might end up with lost configuration settings and corrupt chunks.

== How can I get those nice [[aMule_Project_FAQ:About|aMule]] statistics some people post on the IRC channels? ==

You can either copy and paste [[CAS]]'s (C [[aMule_Project_FAQ:About|aMule]] Statistics) output (to execute [[CAS]], run <code>cas</code>) or, if you use xChat as your IRC client and have the Perl module installed, you could use [[XAS]] (xChat [[aMule_Project_FAQ:About|aMule]] Statistics).

== What is slot allocation? ==

Each upload is a slot, so, if you are uploading to five clients at the same time, you have five upload slots established. So, the amount of slot allocation is the bandwidth which each slot will be given.

As an example, if your upload limit is 20KBps, you can set slot allocation to 2KBps which means 10 clients will be able to download from you at the same time, each of them at a maximum transfer rate of 2KBps.

See section "Why is aMule ignoring the bandwidth I set per slot?" in [[AMule_problems|aMule common problem's FAQ]].

== What is a friend slot? ==

A friend slot is just a slot which is assigned to a client in the friends list. Only one friend can have a slot at the same time. Whenever that friend (who has the friend slot enabled) tries to download a file from you, it will be given highest priority in the uploads queue, since it has that slot always assigned. While that friend isn't downloading, that assigned slot will be given to the client with the highest priority in the upload queue, as expected.

== What is the real point on setting up Line Capacities in Preferences? Shouldn't [[aMule_Project_FAQ:About|aMule]] only care for the Bandwidth Limits? ==

aMule really only cares for the Bandwidth Limits. Line Capacities are only set for the Statics display. Let's see: Imagine you have a 100KBps connection, imagine you want to set the Limit at 40KBps because you have a web server which needs a minimum of 60KBps to serve all the petitions. Now imagine you download rare indonesian free songs. You most surely never download at more than 3KBps ever. So, you could set Line Capacities at 5KBps so that the graph at Statics has some meaning, since if you set it up as a 100KBps connection, the graph will show an horizontal line with no meaning at all.

== aMule is crashing quite often here. Can I set it to restart every time it crashes? ==

No, you can't. But you can have scripts to do so. Some of these scripts even work if aMule '''hangs''' but doesn't '''crash'''. 
The following scripts might suit your needs: 
[http://www.amule.org/amule/thread.php?threadid=1232 http://www.amule.org/amule/thread.php?threadid=1232] 
[http://www.amule.org/amule/thread.php?threadid=542 http://www.amule.org/amule/thread.php?threadid=542] 
[http://deepthought.ena.si/mulerunner http://deepthought.ena.si/mulerunner]

== Can I have aMule get data from the standard input to pass it to GDB or Valgrind? ==

Yes, you can. Up to aMule 2.0.0-rc3 this wasn't allowed, but as of version 2.0.0-rc4 you can with the parameter ''-i'' or ''--enable-stdin''.

Anyway, people with aMule versions previous to 2.0.0-rc4 can use [http://www.amule.org/amule/thread.php?threadid=2474 phoenix's aMule stdin patch].

== How can I switch to aMule from eMule without losing my credits? ==

If you already read [[FAQ_aMule#What_are_all_those_files_aMule_creates_the_first_time_it_is_run?|about the meaning of aMule's files]], you might already know what you have to do: 
Get ''cryptkey.dat'', ''clients.met'', ''preferences.dat'', ''preferencesKad.dat'', ''key_index.dat'', ''load_index.dat'' and ''src_index.dat'' files from eMule's config directory (usually, under Windows, something like ''C:\Program files\eMule\config'') and copy them into ''~/.aMule''. Now start aMule so it reads those files. You're done!

You might still want to take a look at the [[migrate from eMule to aMule]] article, though.

== What's the story behind the [[rabbit]]? ==

Ah, yeah, this all began... ehm... well... I mean... follow the white [[rabbit]] ;-)

== Which one is the recomended distro / Operating System for running [[aMule]]? ==

The absolutely recomended distro is [[YSWPS]]. It's still not a mature distro, but it's worth the effort to look for it.

PreferencesKad.dat file

2005-08-28T03:53:43Z

83.42.86.182:

== File ==

'''Name:''' ''preferencesKad.dat''

'''Location:''' ''~/.aMule/''

== Description ==

This file stores the [[IP]] and [[Kademlia]] [[ClientID]].

== Format ==

The file format is as follows:

*''IP'': Stores the [client]]'s IP (4 bytes)
*''Deprecated field'': This field is no more used, so it's filled with 0s (2 bytes)
*''ClientID'': The client's ClientID (16 bytes)
*''End of tags signal'': Old [[eMule]] clients expected more info to be read on this file. To remain compatible with those clients, this field is set to 0 (1 byte)

Once this data is put together, it is stored in little-endian.

== Example ==

The following is a hex dump of an hypothetic ''preferencesKad.dat'' file:

''000000000000C1A3CBE82BBD354A398A7B623E100EBF00''

In the above example, the following data can be seen:

*IP: ''0.0.0.0'', which means it's not yet set (In hex: ''0x00000000'')
*Deprecated field: ''0'' (In hex: ''0x0000'')
*ClientID: ''C1A3CBE82BBD354A398A7B623E100EBF''
*End of tags signal: ''0'' (In hex: ''0x00'')

== Extra ==

[[aMule]] ignores the ''End of tags signal'' when reading this file, so it is optional to use it. Anyway, [[aMule]] does write it to keep compatibility with old [[eMule]] clients.

Preferences.dat file

2005-08-28T03:50:19Z

83.42.86.182:

== File ==

'''Name:''' ''preferences.dat''

'''Location:''' ''~/.aMule/''

== Description ==

This file stores the userhash and the configuration file version for your client in the [[FAQ_ed2k|ed2k network]].
In old times, this file used to store [[eMule]]'s configuration.

== Data ==

The current configuration file version is 20 (in hex: ''0x14'').

== Format ==

The file format is as follows:

'''VersionUserhashLengthFlagsShowcmdMaxpositionxMaxpositionyMinpositionxMinpositionyNormalpositionleftNormalpositiontopNormalpositionrightNormalpositionbottom'''

As you can see, all the fields are stored without any separator character. This is done like this because all the fields have a specific size:
*''Version'': 1 byte
*''Userhash'': 2 bytes
*''Length'': 4 bytes
*''Flags'': 4 bytes
*''Showcmd'': 4 bytes
*''Maxpositionx'': 4 bytes
*''Maxpositiony'': 4 bytes
*''Minpositionx'': 4 bytes
*''Minpositiony'': 4 bytes
*''Normalpositionleft'': 4 bytes
*''Normalpositiontop'': 4 bytes
*''Normalpositionright'': 4 bytes
*''Normalpositionbottom'': 4 bytes

The relevant fields are the following:
*''Version'': Specifies the configuration file version (the format defined in this articles corresponds to version 20).
*''Userhash'': The userhash.
*''Length'': Length in bytes of the file not counting th Version and Userhash fields (should be 38 bytes).

Once this data is put together, it is stored in little-endian.

== Example ==

The following is a hex dump of an hypothetic ''preferences.dat'' file:

''a3143e6f12dd445b12a0c3c6f7ca5b2d00230000000000000000000000000000000000000000000000000000''

In the above example, the following data can be seen:

*Configuration file version: ''20'' (In hex: ''0x14'')
*Userhash: ''A36F3EDD125B44A012C6C3CAF72D5B23''
*Other fields: Set to zero (''0'')

== Extra ==

[[aMule]] ignores the ''main window position'', ''main window size'', ''length'', ''flags'' and ''showcmd'' fields in this file. That's the reason why this fields aren't explained in this article.

All this ignored fields are set to zero by [[aMule]]. Even if they were set to some other value, [[aMule]] will never read those values. Instead, it uses the preferences set in ''~/.eMule''

Preferences.dat file

2005-08-28T03:30:24Z

83.42.86.182:

== File ==

'''Name:''' ''preferences.dat''

'''Location:''' ''~/.aMule/''

== Description ==

This file stores the userhash and the configuration file version for your client in the [[FAQ_ed2k|ed2k network]].
In old times, this file used to store [[eMule]]'s configuration.

== Data ==

The current configuration file version is 20 (in hex: ''0x14'').

== Format ==

The file format is as follows:

'''VersionUserhashLengthFlagsShowcmdMaxpositionxMaxpositionyMinpositionxMinpositionyNormalpositionleftNormalpositiontopNormalpositionrightNormalpositionbottom'''

As you can see, all the fields are stored without any separator character. This is done like this because all the fields have a specific size:
*''Version'': 1 byte
*''Userhash'': 2 bytes
*''Length'': 4 bytes
*''Flags'': 4 bytes
*''Showcmd'': 4 bytes
*''Maxpositionx'': 4 bytes
*''Maxpositiony'': 4 bytes
*''Minpositionx'': 4 bytes
*''Minpositiony'': 4 bytes
*''Normalpositionleft'': 4 bytes
*''Normalpositiontop'': 4 bytes
*''Normalpositionright'': 4 bytes
*''Normalpositionbottom'': 4 bytes

The relevant fields are the following:
*''Version'': Specifies the configuration file version (the format defined in this articles corresponds to version 20).
*''Userhash'': The userhash.
*''Length'': Length in bytes of the file not counting th Version and Userhash fields (should be 38 bytes).

Once this data is put together, it is stored in little-endian.

== Example ==

The following is a hex dump of an hypothetic ''preferences-dat'' file:

''a3143e6f12dd445b12a0c3c6f7ca5b2d00230000000000000000000000000000000000000000000000000000''

In the above example, the following data can be seen:

*Configuration file version: ''20'' (In hex: ''0x14'')
*Userhash: ''A36F3EDD125B44A012C6C3CAF72D5B23''
*Other fields: Set to zero (''0'')

== Extra ==

[[aMule]] ignores the ''main window position'', ''main window size'', ''length'', ''flags'' and ''showcmd'' fields in this file. That's the reason why this fields aren't explained in this article.

All this ignored fields are set to zero by [[aMule]]. Even if they were set to some other value, [[aMule]] will never read those values. Instead, it uses the preferences set in ''~/.eMule''

FAQ eD2k-Kademlia-es

2005-08-28T01:22:23Z

83.42.86.182:

<center>
<h4>F.A.Q. sobre eD2k-Kademlia</h4>

<h2>(Traducido por ''[[User:Kno|KNO]]'')</h2>

[[FAQ_eD2k-Kademlia|English]] | '''Español''' | [[FAQ_eD2k-Kademlia-it|Italiano]] | [[FAQ_eD2k-Kademlia-de|Deutsche]] | [[FAQ_ed2k-fr|Français]] | [[FAQ_eD2k-Kademlia-nl|Nederlands]]
</center>

== ¿Qué es ED2K? ==
ED2K es un protocolo usado originalmente por el cliente P2P (Peer-to-Peer) [[eDonkey2000], que es de donde proviene. Es un cliente basado en la arquitectura cliente-servidor, con la posibilidad de intercambio de fuentes entre clientes.

La red ED2K está basado en servidores no como las redes P2P como [[Kazaa]], lo cual quiere decir que lo primero que tienes que hacer cuando ejecutas [[aMule]] es conectarte a un servidor (manual o automáticamente).

Una vez conectado correctamente a un servidor, el cliente puede buscar cualquier fichero, tanto localmente (en el servidor al que está conectado) o globalmente (todos los servidores), y los servidores responderán con una lista de todos los ficheros que concuerden con los parámetros de la búsqueda.

Si el usuario comienza una descarga, el cliente empezará a pedir a los servidores fuentes, que los servidores responderán en forma de direcciones IP de clientes que han dicho al servidor que tienen ese fichero.

Lo que se hace en este momento es pedir un sitio en las colas de todas estas fuentes.
Cuando llegas a la primera posición de una de estas colas, el cliente remoto te empieza a dar un chunk lee [[FAQ_ed2k-es#¿Qué_es_todo_esto_de_créditos_tasa_y_puntuación?|¿Qué es todo esto de créditos tasa y puntuación?]], y cuando has descargado ese chunk te vuelves a poner en la cola. De esta manera, diferentes chunks están distribuidos por la red ED2K, así que aunque en un momento dado nadie tenga el fichero completo, se podría completar obteniendo diferentes chunks de gente diferente (es bien sabido que la gente tiende a dejar de compartir un fichero una vez que se lo ha descargado). 
Fijate que un cliente solo da '''un''' chunk a la vez a otro cliente. Aunque un cliente esté en dos colas de subida de diferentes archivos y lleguen al principio de la cola, ese cliente solo dará uno de los archivos a la vez al otro cliente (el otro envio, dependiendo de la aplicación ED2K que use el cliente, probablemente quedará con la máxima prioridad de envio, pero no comenzará hasta que el otro chunk haya sido completamente enviado).

Si ambos usuarios tienen ID alta (ver
[[FAQ_ed2k-es#¿Qué_es_ID_baja_e_ID_alta?|¿Qué es ID baja e ID alta?]]) la transferencia se realizará directamente de cliente a cliente (Peer-to-Peer), pero si uno de los clientes tiene ID baja, la conexión se establecerá a través del servidor, ya que un cliente con ID baja no puede aceptar conexiones entrantes. Como resultado, dos clientes con ID baja '''no pueden''' conectarse el uno al otro.

== ¿Que es Kademlia? ==
Kademlia es la evolución natural de la red ED2K. Kademlia es el futuro. Mira [[FAQ_ed2k-es#¿Hay_limitaciones_en_la_red_ED2K?|¿Hay limitaciones en la red ED2K?]] para mas información de por que'Kademlia es necesario.

Como Kademlia es una red descentralizada, desaparece el cuello de botella que se creaba con la necesidad de servidore (a pesar de que [[Lugdunum]] ha hecho un gran trabajo reduciendo este cuello de botella). Ahora, en vez de conectarte a un servidor, te conectas a un cliente (con una dirección IP y puerto conocidos), que soporte la red [[Kademlia]]. Esto se llama Boot Strapping.

Una vez conectado, dependiendo de la posibilidad de aceptar conexiones entrantes, se te dará el estado de "abierto" o "firewalled", que es parecido a IDAlta e IDBaja en la red ED2K. En este momento se te da una ID.

Cuando se busca, cada cliente actúa como un pequeño servidor y se le da la responsabilidad de ciertas palabras clave o fuentes. Esto añade compejidad a encontrar fuentes, ya que no tienes un servidor centrar al que preguntar, pero a cambio tendrás tu consulta propagada através de la red.

Actualmente, versiónes estable de aMule no soporta Kademlia, pero lo incorporará pronto. Si ud quiere probar Kademlia, ya esta incorporado en [[AMule_CVS-es|aMule-CVS]].

== ¿Es Kademlia lo mismo que Overnet? ==
Corto, claro y conciso: No. Overnet es la evolución natural sin servidores del programa eDonkey, mientras que Kademlia es la evolucion naturar sin servidores de los clientes *Mule. Aún así, es la misma filosofía, pero diferentes reglas. Para saber como funciona Overnet, ve a http://www.edonkey2000.com/documentation/how_on.html pero ten en cuenta que el desarrollo de Overnet es cerrado hasta que llegue a la versión 1.0, mientras que el de Kademlia es completamente abierto desde el principio.

== ¿Qué es un chunk? ==
En el protocolo ED2K, para prevenir la descarga de archivos corruptos, cada archivo se divide en varias partes, que son conocidas como chunks y se obtiene el hash de cada chunk (lee más abajo para saber que es un [[FAQ_ed2k-es#¿Qué_es_un_hash?|¿Qué es un hash?]]). Cada chunk tiene 9.28MB, así que, por ejemplo, un archivo de 15MB se divide en dos chunks (9.28MB + 5.72MB), un archivo de 315KB será un solo chunk y un archivo de 100MB se dividirá en 11 chunks (10x9.28MB + 7.2MB).

== ¿Qué es un hash? ==
Dividiendo cada archivo en chunks (ver [[FAQ_ed2k-es#¿Qué_es_un_chunk?|¿Qué es un chunk?]]) nos evitamos el bajar un archivo entero incorrecto ya que únicamente tendremos que bajar de nuevo el chunk corrupto, pero se necesita un método para identificar chunks corruptos. Esto se hace usando el algoritmo de hash MD4.
Un [[MD4 hash]] es un valor único para cada chunk que es el resultado de una función matematica en cada bit del chunk. Esto significa que modificando un único bit en un chunk el hash resultante será completamente distinto. De este modo se asegura la integridad de cada parte de los archivos a la vez que se descargan.

No solo se obtiene el hash de los chunks, sino que también se obtiene del archivo completo (todos los chunks juntos), así que cada fichero en la red ED2K tiene un identificador único. El hash del archivo no se crea haciendo hash del archivo, sino que se obtiene haciendo el hash de todos los chunks del archivo.

En realidad se necesita tanto el hash del archivo como su tamaño. Esta información está empotrada en las direcciones URL del protocolo ED2k que se ven en multitud de sitios.

Por ejemplo:
ed2k://|file|eMule0.42f-Sources.zip|2407949|CC8C3B104AD58678F69858F1F9B736E9|/

Las partes interesantes son la quinta parte, "2407949", que es el tamaño del fichero en bytes y la última parte, "CC8C3B104AD58678F69858F1F9B736E9", que es el propio hash, expresado en notación hexadecimal, de 32 caracteres de longitud.

El nombre de archivo es irrelevante en el procoso de identificar el archivo.

== ¿Por qué después de buscar, algún archivo aparece como diferente fichero en los resultados, a pesar de que tienen el mismo nombre? ==
Si has entendido [[FAQ_ed2k-es#¿Qué_es_un_hash?|¿Qué es un hash?]] entenderás esto rápidamente. Cuando se inicia una búsqueda, el servidor le dice al cliente ED2K el nombre del archivo encontrado y el hash del archivo completo, para cada archivo que concuerde con la búsqueda. Si dos archivos, a pesar de ser el mismo, tienen alguna diferencia en su contenido, no importa si es mayor o menor, el hash es diferente, así que se considera como un archivo diferente. Esta es la razón por la que dos archivos con nombre diferente aparecen como el mismo archivo: en la red ED2K, el nombre no importa, el hash si.

== ¿Qué es ID baja e ID alta? ==
A cada cliente se le asigna un número de identificación, un ID, que sea único y que lo distinguirá de cualquier otro cliente en el servidor. Si este ID está por debajo de 16777216 (16 millones) entonces tienes una ID baja. Si está por encima, entonces tienes una ID alta. Que te den una ID baja o una ID alta solo depende de si tienes abierto el puerto 4662 (u otro configurado en las Preferencias). Si has entendido [[FAQ_ed2k-es#¿Qué_es_ED2K?|¿Qué es ED2K?]] entenderás las oportunidades que tienen los clientes que tienen ID baja, ya que no pueden conectarse a muchos otros clientes (los que tienen ID baja) y a los que si se puede conectar, lo hace a través del servidor, asi que tendrás tasas bajas de descarga. Esto es por lo que el puerto 4662 TCP (o el que hayas configurado en las preferencias) es tan importante. También, algunos servidores defectuosos rechazan clientes con ID baja ya que los clientes con ID baja tienen que transferir a traes de ellos, así que los grandes servidores se sobrecargaríasn.
Para los clientes con ID alta, su ID es el resultado de una operación matemática con su IP que corresponde a A + 256*B + 256*256*C + 256*256*256*D, donde la IP es A.B.C.D. También hay que pensar que este ID es para identificarse, nada más, aparte de tener un ID por encima o por debajo del número 16777216, no importa si el número es mayor o menor. Esto significa que un cliente con una id como 50000000 no es mejor que un cliente con una ID como 49999999.
Hay una exepción. Algunos servidores mal configurados o muy ocupados dan ID baja a algunos clientes a pesar de que su puererto 4662 TCP está abierto. Esto es una rara excepción, pero puede pasar a veces. 
Para conocer si se tiene abiertos o no los puertos, se puede visitar [http://www.amule.org/testport.php la página de tests de puertos].

== ¿Que puertos tengo que configurar en un firewall o router para ejecuar aMule? ==
No hay que tener abiertos ninguno en concreto para que funcione aMule, pero si para tener una ID alta. Como se ha mencionado arriba, para tener una ID alta, el puerto 4662 TCP (o el que esté configurado en las Preferencias) debe estar escuchando.
A parte de ese puerto, para tener una experiencia óptima con ED2K, deben estar abiertos dos puertos más. El primero el puerto UDP 4672 (que puede ser configurado por otro número en las Preferencias también) y segundo, el puerto secundario UDP que no puede ser configurado en las Preferencias. Este puerto UDP es tu puerto TCP + 3 (por ejemplo: TCP=4662 entonces UDP=4665).

== ¿Qué hace cada puerto? ==
Bien, como la mayoria pueden ser configurado por otro número, ponemos los que son por defecto:

; 4662 TCP: Transferencias cliente a cliente.
; 4672 UDP: Protocolo extendido de eMule, puestos en cola, Ping para Repetición de Archivo
; 4661 TCP: Abierto en servidores. Permite conectarse al servidor.
; 4665 UDP: Abierto en servidores. Permite pedir fuentes. Es siempre el mismo que el puerto de conectarse + 3.
; 4711 TCP: El puerto donde escucha el Sercidor Web.
; 4712 TCP: Puerto para Conexiones Externas. Se usa para comunicar aMule con otras aplicaciones como el Servidor Web o aMuleCMD.

Aunque oficialmente el puerto UDP secundario es el puerto del servidor TCP + 4, algunas (la mayoría?) de las implementaciones lo usan como el puerto TCP del cliente + 3. En cualquier caso, este puerto no se usa mucho (aMule no lo usa y eMule no lo tiene).

== ¿Hay alguna limitación en la red ED2K? ==
No muchas, pero si, las hay: dos límites naturales y una limitación "forzada". Los dos límites naturales se han mencionado antes. El primero el problema de los usuarios con ID baja (sus transferencias envian datos a través del servidor y dos clientes con ID baja no pueden compartir entre ellos). La segunda, aunque ED2K es un protocolo p2p, necesita de servidores para establecer las conexiones p2p. Este último esta solucionado en el protocolo Kademlia.
En cuanto a la limitación "forzada", es solo un límite para asegurarse que los clientes compartan y que la red ED2K no desaparezca: los clientes que tienen un limite de subida de X KBps, donde X está entre 0 y 3.99 (ambos incluido) pueden descargar a un máximo de X*3 KBps. Los clientes que tienen un límite de subida de Y KBps, donde Y está entre 4 y 9.99 (ambos incluidos) pueden descargar a un máximo de Y*4 KBps. Los clientes con un límite de subida de 10Kbps o más no tienen límite de descarga. Esta restricción se establece en la aplicación cliente y puede ser eliminada hackeando el código, pero probablemente resulte en que seas baneado en los servidores que te conectes.
También, cualquier cliente está forzado para permitir al menos tres slots de subida, así que no es posible permitir mas que limite_subida/3 KBps por slot.

Hay un límite más: El tamaño máximo del fichero es de 4GB.

== ¿Hay alguna limitación en la red Kademlia? ==

Sólo una. Al tener que mantener compatibilidad con la red ed2k en lo que a identificación única de los archivos se refiere, la limitación de que el tamaño máximo de los archivos sea 4GB también existe en la red Kademlia.

== En la ventana de Búsqueda, ¿Que filtros hay pra cada tipo de archivo? ==
Ten en cuenta que los filtros de la ventana de Búsqueda no dependen del tipo de archivo, si no de las extensiones de los nombres de archivo, de la siguiente manera: 

Archivos: .ace .arj .rar .tar.bz2 .tar.gz .zip .Z 
Audio: .aac .ape .au .mp2 .mp3 .mp4 .mpc .ogg .wav .wma 
Imágenes de CD: .bin .ccd .cue .img .iso .nrg .sub 
Imágenes: .bmp .gif .jpeg .jpg .png .tif 
Programas: .com .exe 
Vídeos: .avi .divx .mov .mpeg .mpg .ogg .ram .rm .vivo .vob 
Por ello, una película cuyo nombre sea "Cumpleaños.zip" aparecerá en el filtro Archivos, pero no en el filtro Vídeos.

== ¿Qué es una fuente? ==
Una fuentes es un cliente que está compartién algún chunk de algún archivo que tienes en tu cola de descargas y que aún no has completado. Obviamente, cuantas mas fuentes puedas conseguir de un determinado archivo, mas posibilidades tendrás de descargar el archivo y más rápidamente lo descargaras. Ten encuenta que hay diferencias entre "fuentes" y "fuentes disponibles" si tienes ID baja, ya que fuentes serán clientes que comparten un chunk o archivo que aún no has completado mientras que "fuentes disponibles" serán los clientes que comparten un chunk o archivo que aún no has completado y desde los que tu puedes descargar (esto es, una fuente para quien tiene ID alta)

== ¿Qué es todo esto de créditos, tasa y puntuación? ==
Estos tres conceptos tienen que ver con cómo la red ED2k establece las preferencias en las colas de subida. 
La puntuación es el valor más importante: el cliente con la puntuación más alta será el siguiente al que se le asignará un slot. El valor de la puntuación es: puntuación = tasa x tiempo_esperando_en_segundos / 100
pero para entenderlo tenemos que saber que es la tasa. 
La tasa se puede entender como una preferencia objetiva, esto es, la preferencia que se da sin tener en cuenta cuánto tiempo ha estado esperando. Cuando un cliente se añade a la cola de subida, se le da una tasa de 100, este valor se va modificando de acuerdo con lo siguiente: 
La cantidad de créditos, la tasa se multiplica de 1x a 10x.
Dependiendo de la prioridad del fichero puede multiplicarse de 0.2x a 1.8x (Lanzamiento 1.8x, Alta 0,9x Normal 0.7x, Baja 0,6x, Muy baja 0.2x). 
Los usuario de clientes viejos que crean mucho tráfico en la red serán penalizados multiplicando su tasa por 0.5x. 
Los usuarios baneados no tendrán tasa (esto es, su tasa se multiplicara por 0). 
Estos valores multiplicadores son conocidos como "modificadores". Los clientes con una valor modificador mayor que 1 serán cargados con amarillo en el icono. 
Así que solo nos falta de saber qué son los créditos. Los créditos son un premio por subir archivos a un cliente. Los créditos se intercambian entre dos clientes y no son globales, así que tu no puedes ver tus propios créditos pero puedes saber cuantos créditos tienen los otros usuarios contigo (esto es, los créditos que debes a esos clientes). Como los créditos son manejados por el cliente que sube, puedes estar subiendo a un cliente que no soporte los créditos, asi que no ganarás créditos con él, pero ese cliente ganará créditos contigo si obtienes algo de él, ya que tú si tienes soporte de créditos. Estos créditos se guardan en el fichero clients.met. 
El modificador usado para la tasa es el menor de entre: 
(upload_total x 2)/download_total o sqrt(upload_total+2) donde upload_total y download_total están medidos en MiBs. 
Si el resultado es menor que 1, entonces se pone a 1 y si es mayor de 10, se pone a 10. Además, si el upload_total es menor que 1MB, el modificador se pone a 1 y si el download_total es 1, el modificador se pone a 10. 

== ¿Qué es un slot? ==
Cuando estás subiendo archivos, tu ancho de banda (que puede variar dependiendo de los limites de subida o de el límite natura de tu tipo de conexión) se dividirá en slots. Así, cada slot tendrá una cantidad de KBps que será asignada a cada cliente que intente descargar algo de tí.

FAQ eD2k-Kademlia

2005-08-28T01:19:05Z

83.42.86.182:

<center>
<h4>F.A.Q. on eD2k-Kademlia</h4>

'''English''' | [[FAQ_eD2k-Kademlia-es|Español]] | [[FAQ_eD2k-Kademlia-it|Italiano]] | [[FAQ_eD2k-Kademlia-de|Deutsche]] | [[FAQ_ed2k-fr|Français]] | [[FAQ_eD2k-Kademlia-nl|Nederlands]]
</center>

== What is ED2K? ==

ED2K is a protocol originally used by the P2P (Peer-to-Peer) client [[eDonkey2000]], which is where the name comes from. It is a server-client based protocol, with the ability to exchange sources between clients.

The ED2K network is server based like many other P2P networks such as [[Kazaa]] (Kazaa is server based, but hides the server connection from the user), which means that the first thing you do when you run [[aMule]] is to connect to a server (either manually or automatically).

Once successfully connected to a server, the client can search, either locally (the connected server) or globally (all servers), for any file and the servers asked will provide the client with a list of all the files which match search parameters.

If the user starts a download, the client will then ask the server for sources, which the server will return in the form of IP addresses for the clients that have told the server that they have the specific file.

Then the remote client will begin to upload a whole chunk to your client as soon as you are the [[FAQ_eD2k-Kademlia#What_is_all_this_talk_about_credits,_ratings_and_scoring_about?|first in the queue]], and when the chunk has been completly sent, you will be taken back to its upload queue. This way different chunks get spread around the ED2K network, so that, although no-one may have at a same given moment the complete file, it may be completed by downloading the different chunks from different people (it is well known that users tend to stop sharing a file once it has been completed).

Note that clients upload only '''one''' chunk at a time to another client. Even if a client is in the upload queue of two different files of a same user and gets to the top of both, that user will only upload one of the files to that client (the other upload, depending on the ED2K application the client uses, will probably remain as a maximum priority upload, but will not begin until the other chunk has been successfully uploaded).

If both users have HighID (see [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|What is LowID and HighID?]]) the transfer will be done directly from client to client (Peer-to-Peer), but if one of the clients have LowID, the connection will be established through the server, since LowID cannot accept incoming connections. As a result, two LowID clients '''cannot''' connect to each other.

== What is Kademlia? ==

Kademlia is a natural evolution of the ED2K network. Kademlia is the future. See [[FAQ_eD2k-Kademlia#Are_there_any_limitations_on_the_ED2K_network?|Are there any limitations on the ED2K network?]] for more information on why Kademlia is necessary.

Since Kademlia is a decentralized network, it removes the bottleneck that was previously caused by the need for servers (though [[Lugdunum]] has done great work in reducing this bottleneck). Now, instead of connecting to a server, you just connect to a client (with a known IP-address and port), which supports the network [[Kademlia]]. This is called the Boot Strapping.

Once connected, depending on your ability to accept incoming connections, you are given either "open" or "firewalled" status, which is similar to the HighID and LowID of the ED2K network. Then you are given an ID.

When searching, each client acts as a small server and is given responsibility for certain keywords or sources. This adds to the complexity of finding sources, as you no longer have a central server to ask, but instead will have to propagate the query through the network.

Currently, Kademlia isn't supported by aMule stable releases, but it will be soon. If you would like to test Kademlia, it is now supported with [[AMule_CVS|aMule-CVS]].

== Is Kademlia the same as Overnet? ==

Short and clear: No. Overnet is the natural serverless evolution of the eDonkey software, while Kademlia is the natural serverless evolution of *Mule clients. Both are based on the original [[Kademlia]] algorithm but have been applied in different ways and there for are incompatible. So, it's the same philosophy, but different rules. To learn about how Overnet works, refer to http://www.edonkey2000.com/documentation/how_on.html but, keep in mind, Overnet's development is closed until it reaches version 1.0, while Kademlia's development is completly open from the very beginning.

== What is a chunk? ==

In the ED2K protocol, to avoid sharing corrupt files, each file is divided into various parts, which are known as chunks, and then each chunk is hashed (read below to know what a [[FAQ_eD2k-Kademlia#What_is_a_hash?|hash]] is). Each chunk is 9.28MB in size, so a 15MB file will be divided into two chunks (9.28MB + 5.72MB), a 315KB file will be a single chunk and a 100MB file will be divided into 11 chunks (10x9.28MB + 7.2MB).

== What is a hash? ==

Dividing each file into chunks (see [[FAQ_eD2k-Kademlia#What_is_a_chunk?|What is a chunk?]]) will avoid the problem of downloading a whole corrupted file since only the corrupted chunk will have to be downloaded again, but a method to identify corrupted chunks is needed. This is done by using MD4 hashes.

A [[MD4 hash]] is a unique value each chunk is given and is the result of a mathematical operation on every single bit on the chunk. This means that modifying a single bit in a chunk would result in a completely different hash. That means that the [[client]] needs to verify the integrity of each part of a file as it is downloaded.

Not only are the chunks hashed but also, in order to get a file-hash, all chunks's hashes are concatenated one after the other in their file order (that is: chunk1's_hash+chunk2's_hash+chunk3's_hash+...) and the resulting string is hashed. This way, each file on the ED2K network has a unique identifier. The file hash isn't taken from hashing the whole file, but from hashing the value of the the chunk's hashes.

In reality, you need both the hash of a file and its size. These pieces of information is embedded in the ED2k URLs found in many places.

Take this for example: 
ed2k://|file|eMule0.42f-Sources.zip|2407949|CC8C3B104AD58678F69858F1F9B736E9|/

The interesting parts are the fifth part, "2407949", which is the size of the file in bytes and the last part, "CC8C3B104AD58678F69858F1F9B736E9", which is the hash itself, stored as hex-decimals, 32 letters long.

The filename itself is irrelevant in the process of identifying the file.

== Why after searching, some files which are the same appear as a different file in the results, although they even have the same name? ==

If you understood "What is a hash" you will understand this quickly. When a search is started, the server tells the ED2K client the filename of the found file and the hash of the complete file for each file which matches the search. If two files, although being the same, have some difference in their content, no matter if it's big or small, the hash is different, so they are considered as a different file. That's also the reason why two file with different file name appear as the same file: on the ED2K network, the filename isn't important, the hash is.

== What is LowID and HighID? ==

Each client is assigned an ID (Identification) number which is unique and will distinguish the client from all other clients on the server. If this ID is below 16777216 (16 million) then you have a LowID and anything over is a HighID. Whether your client receives a high or low ID will depend on your client and whether or not the Client TCP port is open. Client TCP Port is an customisable option located in Preferences -> Connection. The default port is 4662 which is fine. If you understand [[FAQ_ed2k#What_is_ED2K?|what ED2K is]], odds are you'll understand the chances that clients with LowIDs may be unable to connect to other clients with LowIDs which reduces transfer rates significantly. This is the reason why having port 4662 TCP (or the one set in Preferences) is so important. Some of the larger servers refuse clients with LowIDs and disallow connections since LowID clients have data transfered through the server, rather than directly from the other client, which in turn adds more overhead for the server.

For clients with a HighID, their ID is the result of a mathematical operation with their IP which corresponds to A + 256*B + 256*256*C + 256*256*256*D, where the IP is A.B.C.D. Keep in mind that this ID has identification purposes as well. Apart from having an ID over or under 16777216, it does not matter if the ID is bigger or smaller. This means a client with an ID of 50000000 isn't any better than a client with an ID of 49999999. The only exception is at times servers are either incorrectly configured or are very busy and issue LowIDs to clients even though port 4662 TCP is open. These are rare exceptions but it can happen sometimes.

If you're unsure about having proper port settings, you can test your ports [http://www.amule.org/testport.php here].

== Which ports do I have to configure in a firewall or router to run aMule? ==

One has to distinguish between incoming and outgoing connections. Normally, all ports of a router are open for sending data (outgoing connection).

So, in this normal case, You only have to configure the ports for ''incoming'' connections:

aMule works even with no specific ports opened, but you won't get a HighID in this case. As mentioned above, to be given a HighID, port 4662 TCP (or the one set in the Preferences) must be listening (i.e. opened in your firewall and forwarded in your router).

Apart from that port, to have an optimal ED2K experience, one more port should be enabled for listening as well: UDP port 4672 (which can also be changed to any other number in the Preferences).

== What does each port do? ==

Well, since most ports can be configured to be set to any other number, the defaults will be listed. The traffic direction is from client perspective (You).

; 4661 TCP (outgoing): Port, on which a server listens for connection (defined by server).
; 4665 UDP (outgoing): used for global server searches and global source queries. This is always Server TCP port (in this case 4661) + 4.
; 4662 TCP (outgoing and incoming): Client to client transfers.
; 4672 UDP (outgoing and incoming): Extended eMule protocol, Queue Rating, File Reask Ping
; 4711 TCP: WebServer listening port.
; 4712 TCP: External Connection port. Used to communicate aMule with other applications such as aMule WebServer or aMuleCMD.

== Are there any limitations on the ED2K network? ==

Not much, but yes, there are: two natural limits and a "forced" limitation. The two natural limits have already been mentioned before. First, the issues on LowID users (their transfers involve data through the server and two LowID clients can't share between them). The second, although ED2K is a p2p protocol, it needs servers to establish the p2p connection. This latter one is solved in the Kademlia protocol.

About the "forced" limitation, it's only a limit to make sure that clients share so that the ED2K network will not disappear: clients which have an upload limit of X KBps, where X is between 0 and 3.99 (both included) can download at a maximum of X*3 KBps. Clients which have an upload limit of Y KBps, where Y is Between 4 and 9.99 (both included) can download at a maximum of Y*4 KBps. Clients with an upload limit of 10KBps or more have no downloading limitations. This restriction is set in the client application so it could be by-passed by hacking the code, but that would probably result in being banned from the servers you connect to.

Also, any client is forced to allow at least three upload slots, so it's not possible to allow more than upload_limit/3 KBps per slot.

There is one last limit: Network file limit is 4GB.

Additionally, this is not an eD2k limitation but a server limitation, servers will only send 300 results for your searches, so don't expect any more results.

== Are there any limitations on the Kademlia network? ==

Just one. As it is a network derived from the ed2k network and, there for, has to maintain compatibility when it comes to identify files uniquely, the 4GB maximum file size limit exisits in the Kademlia network too.

== In search window, what filter stands for which filetype? ==

Keep in mind that the filters in the search window don't depend on the file type, but on the extensions of the filenames, in the following way:

Archive: .ace .arj .rar .tar.bz2 .tar.gz .zip .Z 
Audio: .aac .ape .au .mp2 .mp3 .mp4 .mpc .ogg .wav .wma 
CDImage: .bin .ccd .cue .img .iso .nrg .sub 
Picture: .bmp .gif .jpeg .jpg .png .tif 
Program: .com .exe 
Video: .avi .divx .mov .mpeg .mpg .ogg .ram .rm .vivo .vob

So, a movie file that has the name "Birthday.zip" will appear in the Archive filter, but not in the Video filter.

== What is a source? ==

A source is a client which is sharing some chunk in some file you have in your downloading queue which you still have not completed. Obviously, the more sources you can get for a given file, the more possibilities you have to download the file and the quicker you'll download it. Keep in mind that there's a difference between "sources" and "available sources" if you're on LowID, since "sources"s stands for clients sharing a chunk or file you still haven't completed, while "available sources" stands for clients sharing a chunk or file you still haven't completed and from who you can download (that is, a source who is on HighID).

== What is all this talk about credits, ratings and scoring about? ==

All three concepts have to do with the way in which the ED2K network establishes the uploading queues preferences.

The score is the most important value: the client with the higher score will be the next client which you'll provide a slot to. The way in the score value is set is this: score = rate x time_waiting_in_seconds / 100
So, to understand this, we must known what rate is.

Rate is can be understood as an objective preference. This is, the preference which a client is given without caring how much time it's been waiting. When a client is added to the uploading queue, it gets a rate of 100. This value is modified following according to this:

According to the amount of credits, the rate will be multiplied by 1x to 10x.
Depending on the file priority, it will be multiplied by 0.2x to 1.8x (Release 1.8x, High 0.9x, Normal 0.7x, Low 0.6x, Very Low: 0.2x). 
Users on specific old clients which load too much the network traffic will get penalized by multiplying their rate by 0.5x. 
Banned clients will instantly get no rate (that is, their rate will by multiplied by 0). 
This multiplying values are known as "modifiers". Clients with a modifier value strictly bigger than 1 will be marked as yellow in the icon. 
So we only have credits left to known. Credits are a prize you get for uploading files to a specific user. Credits are exchanged between two specific clients, they are not global, so your own credits can't be viewed, although you can know the credits any other user has on you (that is, the credits you owe that client). Since credits are managed by the uploading client, you might be uploading to some client with no credits support, so you will gain no credits on him, although that client will actually get credits on you if it uploads to you, since you do have credits support. This credits are stored in clients.met file. 
The credits modifier used by rate is the lower between these two: (upload_total x 2)/download_total or sqrt(upload_total+2) where both upload_total and download_total are measured in MBs. 
If the result is lower than 1, then it is set to 1 and if it is bigger than 10, it is set to 10. In addition, if the uploaded total is less than 1MB, the modifier is set to 1 and if the downloaded total is equal to 0, then the modifier is set to 10.

== What is a slot? ==

When uploading files, your upload bandwidth (which may vary depending on the upload limit or the natural connection-type upload limit) will be divided into slots. So, each slot is an amount of KBps which will be assigned to each client who tries to download from you.

FAQ eD2k-Kademlia

2005-08-28T01:10:41Z

83.42.86.182:

<center>
<h4>F.A.Q. on eD2k-Kademlia</h4>

'''English''' | [[FAQ_eD2k-Kademlia-es|Español]] | [[FAQ_eD2k-Kademlia-it|Italiano]] | [[FAQ_eD2k-Kademlia-de|Deutsche]] | [[FAQ_ed2k-fr|Français]] | [[FAQ_eD2k-Kademlia-nl|Nederlands]]
</center>

== What is ED2K? ==

ED2K is a protocol originally used by the P2P (Peer-to-Peer) client [[eDonkey2000]], which is where the name comes from. It is a server-client based protocol, with the ability to exchange sources between clients.

The ED2K network is server based like many other P2P networks such as [[Kazaa]] (Kazaa is server based, but hides the server connection from the user), which means that the first thing you do when you run [[aMule]] is to connect to a server (either manually or automatically).

Once successfully connected to a server, the client can search, either locally (the connected server) or globally (all servers), for any file and the servers asked will provide the client with a list of all the files which match search parameters.

If the user starts a download, the client will then ask the server for sources, which the server will return in the form of IP addresses for the clients that have told the server that they have the specific file.

Then the remote client will begin to upload a whole chunk to your client as soon as you are the [[FAQ_eD2k-Kademlia#What_is_all_this_talk_about_credits,_ratings_and_scoring_about?|first in the queue]], and when the chunk has been completly sent, you will be taken back to its upload queue. This way different chunks get spread around the ED2K network, so that, although no-one may have at a same given moment the complete file, it may be completed by downloading the different chunks from different people (it is well known that users tend to stop sharing a file once it has been completed).

Note that clients upload only '''one''' chunk at a time to another client. Even if a client is in the upload queue of two different files of a same user and gets to the top of both, that user will only upload one of the files to that client (the other upload, depending on the ED2K application the client uses, will probably remain as a maximum priority upload, but will not begin until the other chunk has been successfully uploaded).

If both users have HighID (see [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|What is LowID and HighID?]]) the transfer will be done directly from client to client (Peer-to-Peer), but if one of the clients have LowID, the connection will be established through the server, since LowID cannot accept incoming connections. As a result, two LowID clients '''cannot''' connect to each other.

== What is Kademlia? ==

Kademlia is a natural evolution of the ED2K network. Kademlia is the future. See [[FAQ_eD2k-Kademlia#Are_there_any_limitations_on_the_ED2K_network?|Are there any limitations on the ED2K network?]] for more information on why Kademlia is necessary.

Since Kademlia is a decentralized network, it removes the bottleneck that was previously caused by the need for servers (though [[Lugdunum]] has done great work in reducing this bottleneck). Now, instead of connecting to a server, you just connect to a client (with a known IP-address and port), which supports the network [[Kademlia]]. This is called the Boot Strapping.

Once connected, depending on your ability to accept incoming connections, you are given either "open" or "firewalled" status, which is similar to the HighID and LowID of the ED2K network. Then you are given an ID.

When searching, each client acts as a small server and is given responsibility for certain keywords or sources. This adds to the complexity of finding sources, as you no longer have a central server to ask, but instead will have to propagate the query through the network.

Currently, Kademlia isn't supported by aMule stable releases, but it will be soon. If you would like to test Kademlia, it is now supported with [[AMule_CVS|aMule-CVS]].

TODO: Does Kademlia remove the 4 GB file size limit ?

== Is Kademlia the same as Overnet? ==

Short and clear: No. Overnet is the natural serverless evolution of the eDonkey software, while Kademlia is the natural serverless evolution of *Mule clients. Both are based on the original [[Kademlia]] algorithm but have been applied in different ways and there for are incompatible. So, it's the same philosophy, but different rules. To learn about how Overnet works, refer to http://www.edonkey2000.com/documentation/how_on.html but, keep in mind, Overnet's development is closed until it reaches version 1.0, while Kademlia's development is completly open from the very beginning.

== What is a chunk? ==

In the ED2K protocol, to avoid sharing corrupt files, each file is divided into various parts, which are known as chunks, and then each chunk is hashed (read below to know what a [[FAQ_eD2k-Kademlia#What_is_a_hash?|hash]] is). Each chunk is 9.28MB in size, so a 15MB file will be divided into two chunks (9.28MB + 5.72MB), a 315KB file will be a single chunk and a 100MB file will be divided into 11 chunks (10x9.28MB + 7.2MB).

== What is a hash? ==

Dividing each file into chunks (see [[FAQ_eD2k-Kademlia#What_is_a_chunk?|What is a chunk?]]) will avoid the problem of downloading a whole corrupted file since only the corrupted chunk will have to be downloaded again, but a method to identify corrupted chunks is needed. This is done by using MD4 hashes.

A [[MD4 hash]] is a unique value each chunk is given and is the result of a mathematical operation on every single bit on the chunk. This means that modifying a single bit in a chunk would result in a completely different hash. That means that the [[client]] needs to verify the integrity of each part of a file as it is downloaded.

Not only are the chunks hashed but also, in order to get a file-hash, all chunks's hashes are concatenated one after the other in their file order (that is: chunk1's_hash+chunk2's_hash+chunk3's_hash+...) and the resulting string is hashed. This way, each file on the ED2K network has a unique identifier. The file hash isn't taken from hashing the whole file, but from hashing the value of the the chunk's hashes.

In reality, you need both the hash of a file and its size. These pieces of information is embedded in the ED2k URLs found in many places.

Take this for example: 
ed2k://|file|eMule0.42f-Sources.zip|2407949|CC8C3B104AD58678F69858F1F9B736E9|/

The interesting parts are the fifth part, "2407949", which is the size of the file in bytes and the last part, "CC8C3B104AD58678F69858F1F9B736E9", which is the hash itself, stored as hex-decimals, 32 letters long.

The filename itself is irrelevant in the process of identifying the file.

== Why after searching, some files which are the same appear as a different file in the results, although they even have the same name? ==

If you understood "What is a hash" you will understand this quickly. When a search is started, the server tells the ED2K client the filename of the found file and the hash of the complete file for each file which matches the search. If two files, although being the same, have some difference in their content, no matter if it's big or small, the hash is different, so they are considered as a different file. That's also the reason why two file with different file name appear as the same file: on the ED2K network, the filename isn't important, the hash is.

== What is LowID and HighID? ==

Each client is assigned an ID (Identification) number which is unique and will distinguish the client from all other clients on the server. If this ID is below 16777216 (16 million) then you have a LowID and anything over is a HighID. Whether your client receives a high or low ID will depend on your client and whether or not the Client TCP port is open. Client TCP Port is an customisable option located in Preferences -> Connection. The default port is 4662 which is fine. If you understand [[FAQ_ed2k#What_is_ED2K?|what ED2K is]], odds are you'll understand the chances that clients with LowIDs may be unable to connect to other clients with LowIDs which reduces transfer rates significantly. This is the reason why having port 4662 TCP (or the one set in Preferences) is so important. Some of the larger servers refuse clients with LowIDs and disallow connections since LowID clients have data transfered through the server, rather than directly from the other client, which in turn adds more overhead for the server.

For clients with a HighID, their ID is the result of a mathematical operation with their IP which corresponds to A + 256*B + 256*256*C + 256*256*256*D, where the IP is A.B.C.D. Keep in mind that this ID has identification purposes as well. Apart from having an ID over or under 16777216, it does not matter if the ID is bigger or smaller. This means a client with an ID of 50000000 isn't any better than a client with an ID of 49999999. The only exception is at times servers are either incorrectly configured or are very busy and issue LowIDs to clients even though port 4662 TCP is open. These are rare exceptions but it can happen sometimes.

If you're unsure about having proper port settings, you can test your ports [http://www.amule.org/testport.php here].

== Which ports do I have to configure in a firewall or router to run aMule? ==

One has to distinguish between incoming and outgoing connections. Normally, all ports of a router are open for sending data (outgoing connection).

So, in this normal case, You only have to configure the ports for ''incoming'' connections:

aMule works even with no specific ports opened, but you won't get a HighID in this case. As mentioned above, to be given a HighID, port 4662 TCP (or the one set in the Preferences) must be listening (i.e. opened in your firewall and forwarded in your router).

Apart from that port, to have an optimal ED2K experience, one more port should be enabled for listening as well: UDP port 4672 (which can also be changed to any other number in the Preferences).

== What does each port do? ==

Well, since most ports can be configured to be set to any other number, the defaults will be listed. The traffic direction is from client perspective (You).

; 4661 TCP (outgoing): Port, on which a server listens for connection (defined by server).
; 4665 UDP (outgoing): used for global server searches and global source queries. This is always Server TCP port (in this case 4661) + 4.
; 4662 TCP (outgoing and incoming): Client to client transfers.
; 4672 UDP (outgoing and incoming): Extended eMule protocol, Queue Rating, File Reask Ping
; 4711 TCP: WebServer listening port.
; 4712 TCP: External Connection port. Used to communicate aMule with other applications such as aMule WebServer or aMuleCMD.

== Are there any limitations on the ED2K network? ==

Not much, but yes, there are: two natural limits and a "forced" limitation. The two natural limits have already been mentioned before. First, the issues on LowID users (their transfers involve data through the server and two LowID clients can't share between them). The second, although ED2K is a p2p protocol, it needs servers to establish the p2p connection. This latter one is solved in the Kademlia protocol.

About the "forced" limitation, it's only a limit to make sure that clients share so that the ED2K network will not disappear: clients which have an upload limit of X KBps, where X is between 0 and 3.99 (both included) can download at a maximum of X*3 KBps. Clients which have an upload limit of Y KBps, where Y is Between 4 and 9.99 (both included) can download at a maximum of Y*4 KBps. Clients with an upload limit of 10KBps or more have no downloading limitations. This restriction is set in the client application so it could be by-passed by hacking the code, but that would probably result in being banned from the servers you connect to.

Also, any client is forced to allow at least three upload slots, so it's not possible to allow more than upload_limit/3 KBps per slot.

There is one last limit: Network file limit is 4GB.

Additionally, this is not an eD2k limitation but a server limitation, servers will only send 300 results for your searches, so don't expect any more results.

== In search window, what filter stands for which filetype? ==

Keep in mind that the filters in the search window don't depend on the file type, but on the extensions of the filenames, in the following way:

Archive: .ace .arj .rar .tar.bz2 .tar.gz .zip .Z 
Audio: .aac .ape .au .mp2 .mp3 .mp4 .mpc .ogg .wav .wma 
CDImage: .bin .ccd .cue .img .iso .nrg .sub 
Picture: .bmp .gif .jpeg .jpg .png .tif 
Program: .com .exe 
Video: .avi .divx .mov .mpeg .mpg .ogg .ram .rm .vivo .vob

So, a movie file that has the name "Birthday.zip" will appear in the Archive filter, but not in the Video filter.

== What is a source? ==

A source is a client which is sharing some chunk in some file you have in your downloading queue which you still have not completed. Obviously, the more sources you can get for a given file, the more possibilities you have to download the file and the quicker you'll download it. Keep in mind that there's a difference between "sources" and "available sources" if you're on LowID, since "sources"s stands for clients sharing a chunk or file you still haven't completed, while "available sources" stands for clients sharing a chunk or file you still haven't completed and from who you can download (that is, a source who is on HighID).

== What is all this talk about credits, ratings and scoring about? ==

All three concepts have to do with the way in which the ED2K network establishes the uploading queues preferences.

The score is the most important value: the client with the higher score will be the next client which you'll provide a slot to. The way in the score value is set is this: score = rate x time_waiting_in_seconds / 100
So, to understand this, we must known what rate is.

Rate is can be understood as an objective preference. This is, the preference which a client is given without caring how much time it's been waiting. When a client is added to the uploading queue, it gets a rate of 100. This value is modified following according to this:

According to the amount of credits, the rate will be multiplied by 1x to 10x.
Depending on the file priority, it will be multiplied by 0.2x to 1.8x (Release 1.8x, High 0.9x, Normal 0.7x, Low 0.6x, Very Low: 0.2x). 
Users on specific old clients which load too much the network traffic will get penalized by multiplying their rate by 0.5x. 
Banned clients will instantly get no rate (that is, their rate will by multiplied by 0). 
This multiplying values are known as "modifiers". Clients with a modifier value strictly bigger than 1 will be marked as yellow in the icon. 
So we only have credits left to known. Credits are a prize you get for uploading files to a specific user. Credits are exchanged between two specific clients, they are not global, so your own credits can't be viewed, although you can know the credits any other user has on you (that is, the credits you owe that client). Since credits are managed by the uploading client, you might be uploading to some client with no credits support, so you will gain no credits on him, although that client will actually get credits on you if it uploads to you, since you do have credits support. This credits are stored in clients.met file. 
The credits modifier used by rate is the lower between these two: (upload_total x 2)/download_total or sqrt(upload_total+2) where both upload_total and download_total are measured in MBs. 
If the result is lower than 1, then it is set to 1 and if it is bigger than 10, it is set to 10. In addition, if the uploaded total is less than 1MB, the modifier is set to 1 and if the downloaded total is equal to 0, then the modifier is set to 10.

== What is a slot? ==

When uploading files, your upload bandwidth (which may vary depending on the upload limit or the natural connection-type upload limit) will be divided into slots. So, each slot is an amount of KBps which will be assigned to each client who tries to download from you.

Kademlia

2005-08-28T01:02:32Z

83.42.86.182:

[[FAQ_eD2k-Kademlia#What_is_Kademlia?|Kademlia]] is a [[Server|server]]less [[network]] for the *[[Mule]] [[client]]s.

It is based on the Kademlia algorithm by [http://www.scs.cs.nyu.edu/~petar Petar Maymounkov] and [http://www.scs.cs.nyu.edu/~dm David Mazières] ([http://www.nyu.edu New York University], 2002).

For information about it you can either read the [[FAQ_eD2k-Kademlia#What_is_Kademlia?|ED2K-Kademlia FAQ]] or see [http://emule-project.net/home/perl/help.cgi?l=1&rm=show_topic&topic_id=232 eMule's support page].

FAQ eD2k-Kademlia

2005-08-28T00:57:22Z

83.42.86.182:

<center>
<h4>F.A.Q. on eD2k-Kademlia</h4>

'''English''' | [[FAQ_eD2k-Kademlia-es|Español]] | [[FAQ_eD2k-Kademlia-it|Italiano]] | [[FAQ_eD2k-Kademlia-de|Deutsche]] | [[FAQ_ed2k-fr|Français]] | [[FAQ_eD2k-Kademlia-nl|Nederlands]]
</center>

== What is ED2K? ==

ED2K is a protocol originally used by the P2P (Peer-to-Peer) client [[eDonkey2000]], which is where the name comes from. It is a server-client based protocol, with the ability to exchange sources between clients.

The ED2K network is server based like many other P2P networks such as [[Kazaa]] (Kazaa is server based, but hides the server connection from the user), which means that the first thing you do when you run [[aMule]] is to connect to a server (either manually or automatically).

Once successfully connected to a server, the client can search, either locally (the connected server) or globally (all servers), for any file and the servers asked will provide the client with a list of all the files which match search parameters.

If the user starts a download, the client will then ask the server for sources, which the server will return in the form of IP addresses for the clients that have told the server that they have the specific file.

Then the remote client will begin to upload a whole chunk to your client as soon as you are the [[FAQ_eD2k-Kademlia#What_is_all_this_talk_about_credits,_ratings_and_scoring_about?|first in the queue]], and when the chunk has been completly sent, you will be taken back to its upload queue. This way different chunks get spread around the ED2K network, so that, although no-one may have at a same given moment the complete file, it may be completed by downloading the different chunks from different people (it is well known that users tend to stop sharing a file once it has been completed).

Note that clients upload only '''one''' chunk at a time to another client. Even if a client is in the upload queue of two different files of a same user and gets to the top of both, that user will only upload one of the files to that client (the other upload, depending on the ED2K application the client uses, will probably remain as a maximum priority upload, but will not begin until the other chunk has been successfully uploaded).

If both users have HighID (see [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|What is LowID and HighID?]]) the transfer will be done directly from client to client (Peer-to-Peer), but if one of the clients have LowID, the connection will be established through the server, since LowID cannot accept incoming connections. As a result, two LowID clients '''cannot''' connect to each other.

== What is Kademlia? ==

Kademlia is a natural evolution of the ED2K network. Kademlia is the future. See [[FAQ_eD2k-Kademlia#Are_there_any_limitations_on_the_ED2K_network?|Are there any limitations on the ED2K network?]] for more information on why Kademlia is necessary.

Since Kademlia is a decentralized network, it removes the bottleneck that was previously caused by the need for servers (though [[Lugdunum]] has done great work in reducing this bottleneck). Now, instead of connecting to a server, you just connect to a client (with a known IP-address and port), which supports the network [[Kademlia]]. This is called the Boot Strapping.

Once connected, depending on your ability to accept incoming connections, you are given either "open" or "firewalled" status, which is similar to the HighID and LowID of the ED2K network. Then you are given an ID.

At the moment, "firewalled" users aren’t supported by the Kademlia network, and therefore won’t be given an ID and will be unable to connect. Firewalled support will be added later.

When searching, each client acts as a small server and is given responsibility for certain keywords or sources. This adds to the complexity of finding sources, as you no longer have a central server to ask, but instead will have to propagate the query through the network.

Currently, Kademlia isn't supported by aMule stable releases, but it will be soon. If you would like to test Kademlia, it is now supported with [[AMule_CVS|aMule-CVS]].

TODO: Does Kademlia remove the 4 GB file size limit ?

== Is Kademlia the same as Overnet? ==

Short and clear: No. Overnet is the natural serverless evolution of the eDonkey software, while Kademlia is the natural serverless evolution of *Mule clients. Both are based on the original [[Kademlia]] algorithm but have been applied in different ways and there for are incompatible. So, it's the same philosophy, but different rules. To learn about how Overnet works, refer to http://www.edonkey2000.com/documentation/how_on.html but, keep in mind, Overnet's development is closed until it reaches version 1.0, while Kademlia's development is completly open from the very beginning.

== What is a chunk? ==

In the ED2K protocol, to avoid sharing corrupt files, each file is divided into various parts, which are known as chunks, and then each chunk is hashed (read below to know what a [[FAQ_eD2k-Kademlia#What_is_a_hash?|hash]] is). Each chunk is 9.28MB in size, so a 15MB file will be divided into two chunks (9.28MB + 5.72MB), a 315KB file will be a single chunk and a 100MB file will be divided into 11 chunks (10x9.28MB + 7.2MB).

== What is a hash? ==

Dividing each file into chunks (see [[FAQ_eD2k-Kademlia#What_is_a_chunk?|What is a chunk?]]) will avoid the problem of downloading a whole corrupted file since only the corrupted chunk will have to be downloaded again, but a method to identify corrupted chunks is needed. This is done by using MD4 hashes.

A [[MD4 hash]] is a unique value each chunk is given and is the result of a mathematical operation on every single bit on the chunk. This means that modifying a single bit in a chunk would result in a completely different hash. That means that the [[client]] needs to verify the integrity of each part of a file as it is downloaded.

Not only are the chunks hashed but also, in order to get a file-hash, all chunks's hashes are concatenated one after the other in their file order (that is: chunk1's_hash+chunk2's_hash+chunk3's_hash+...) and the resulting string is hashed. This way, each file on the ED2K network has a unique identifier. The file hash isn't taken from hashing the whole file, but from hashing the value of the the chunk's hashes.

In reality, you need both the hash of a file and its size. These pieces of information is embedded in the ED2k URLs found in many places.

Take this for example: 
ed2k://|file|eMule0.42f-Sources.zip|2407949|CC8C3B104AD58678F69858F1F9B736E9|/

The interesting parts are the fifth part, "2407949", which is the size of the file in bytes and the last part, "CC8C3B104AD58678F69858F1F9B736E9", which is the hash itself, stored as hex-decimals, 32 letters long.

The filename itself is irrelevant in the process of identifying the file.

== Why after searching, some files which are the same appear as a different file in the results, although they even have the same name? ==

If you understood "What is a hash" you will understand this quickly. When a search is started, the server tells the ED2K client the filename of the found file and the hash of the complete file for each file which matches the search. If two files, although being the same, have some difference in their content, no matter if it's big or small, the hash is different, so they are considered as a different file. That's also the reason why two file with different file name appear as the same file: on the ED2K network, the filename isn't important, the hash is.

== What is LowID and HighID? ==

Each client is assigned an ID (Identification) number which is unique and will distinguish the client from all other clients on the server. If this ID is below 16777216 (16 million) then you have a LowID and anything over is a HighID. Whether your client receives a high or low ID will depend on your client and whether or not the Client TCP port is open. Client TCP Port is an customisable option located in Preferences -> Connection. The default port is 4662 which is fine. If you understand [[FAQ_ed2k#What_is_ED2K?|what ED2K is]], odds are you'll understand the chances that clients with LowIDs may be unable to connect to other clients with LowIDs which reduces transfer rates significantly. This is the reason why having port 4662 TCP (or the one set in Preferences) is so important. Some of the larger servers refuse clients with LowIDs and disallow connections since LowID clients have data transfered through the server, rather than directly from the other client, which in turn adds more overhead for the server.

For clients with a HighID, their ID is the result of a mathematical operation with their IP which corresponds to A + 256*B + 256*256*C + 256*256*256*D, where the IP is A.B.C.D. Keep in mind that this ID has identification purposes as well. Apart from having an ID over or under 16777216, it does not matter if the ID is bigger or smaller. This means a client with an ID of 50000000 isn't any better than a client with an ID of 49999999. The only exception is at times servers are either incorrectly configured or are very busy and issue LowIDs to clients even though port 4662 TCP is open. These are rare exceptions but it can happen sometimes.

If you're unsure about having proper port settings, you can test your ports [http://www.amule.org/testport.php here].

== Which ports do I have to configure in a firewall or router to run aMule? ==

One has to distinguish between incoming and outgoing connections. Normally, all ports of a router are open for sending data (outgoing connection).

So, in this normal case, You only have to configure the ports for ''incoming'' connections:

aMule works even with no specific ports opened, but you won't get a HighID in this case. As mentioned above, to be given a HighID, port 4662 TCP (or the one set in the Preferences) must be listening (i.e. opened in your firewall and forwarded in your router).

Apart from that port, to have an optimal ED2K experience, one more port should be enabled for listening as well: UDP port 4672 (which can also be changed to any other number in the Preferences).

== What does each port do? ==

Well, since most ports can be configured to be set to any other number, the defaults will be listed. The traffic direction is from client perspective (You).

; 4661 TCP (outgoing): Port, on which a server listens for connection (defined by server).
; 4665 UDP (outgoing): used for global server searches and global source queries. This is always Server TCP port (in this case 4661) + 4.
; 4662 TCP (outgoing and incoming): Client to client transfers.
; 4672 UDP (outgoing and incoming): Extended eMule protocol, Queue Rating, File Reask Ping
; 4711 TCP: WebServer listening port.
; 4712 TCP: External Connection port. Used to communicate aMule with other applications such as aMule WebServer or aMuleCMD.

== Are there any limitations on the ED2K network? ==

Not much, but yes, there are: two natural limits and a "forced" limitation. The two natural limits have already been mentioned before. First, the issues on LowID users (their transfers involve data through the server and two LowID clients can't share between them). The second, although ED2K is a p2p protocol, it needs servers to establish the p2p connection. This latter one is solved in the Kademlia protocol.

About the "forced" limitation, it's only a limit to make sure that clients share so that the ED2K network will not disappear: clients which have an upload limit of X KBps, where X is between 0 and 3.99 (both included) can download at a maximum of X*3 KBps. Clients which have an upload limit of Y KBps, where Y is Between 4 and 9.99 (both included) can download at a maximum of Y*4 KBps. Clients with an upload limit of 10KBps or more have no downloading limitations. This restriction is set in the client application so it could be by-passed by hacking the code, but that would probably result in being banned from the servers you connect to.

Also, any client is forced to allow at least three upload slots, so it's not possible to allow more than upload_limit/3 KBps per slot.

There is one last limit: Network file limit is 4GB.

Additionally, this is not an eD2k limitation but a server limitation, servers will only send 300 results for your searches, so don't expect any more results.

== In search window, what filter stands for which filetype? ==

Keep in mind that the filters in the search window don't depend on the file type, but on the extensions of the filenames, in the following way:

Archive: .ace .arj .rar .tar.bz2 .tar.gz .zip .Z 
Audio: .aac .ape .au .mp2 .mp3 .mp4 .mpc .ogg .wav .wma 
CDImage: .bin .ccd .cue .img .iso .nrg .sub 
Picture: .bmp .gif .jpeg .jpg .png .tif 
Program: .com .exe 
Video: .avi .divx .mov .mpeg .mpg .ogg .ram .rm .vivo .vob

So, a movie file that has the name "Birthday.zip" will appear in the Archive filter, but not in the Video filter.

== What is a source? ==

A source is a client which is sharing some chunk in some file you have in your downloading queue which you still have not completed. Obviously, the more sources you can get for a given file, the more possibilities you have to download the file and the quicker you'll download it. Keep in mind that there's a difference between "sources" and "available sources" if you're on LowID, since "sources"s stands for clients sharing a chunk or file you still haven't completed, while "available sources" stands for clients sharing a chunk or file you still haven't completed and from who you can download (that is, a source who is on HighID).

== What is all this talk about credits, ratings and scoring about? ==

All three concepts have to do with the way in which the ED2K network establishes the uploading queues preferences.

The score is the most important value: the client with the higher score will be the next client which you'll provide a slot to. The way in the score value is set is this: score = rate x time_waiting_in_seconds / 100
So, to understand this, we must known what rate is.

Rate is can be understood as an objective preference. This is, the preference which a client is given without caring how much time it's been waiting. When a client is added to the uploading queue, it gets a rate of 100. This value is modified following according to this:

According to the amount of credits, the rate will be multiplied by 1x to 10x.
Depending on the file priority, it will be multiplied by 0.2x to 1.8x (Release 1.8x, High 0.9x, Normal 0.7x, Low 0.6x, Very Low: 0.2x). 
Users on specific old clients which load too much the network traffic will get penalized by multiplying their rate by 0.5x. 
Banned clients will instantly get no rate (that is, their rate will by multiplied by 0). 
This multiplying values are known as "modifiers". Clients with a modifier value strictly bigger than 1 will be marked as yellow in the icon. 
So we only have credits left to known. Credits are a prize you get for uploading files to a specific user. Credits are exchanged between two specific clients, they are not global, so your own credits can't be viewed, although you can know the credits any other user has on you (that is, the credits you owe that client). Since credits are managed by the uploading client, you might be uploading to some client with no credits support, so you will gain no credits on him, although that client will actually get credits on you if it uploads to you, since you do have credits support. This credits are stored in clients.met file. 
The credits modifier used by rate is the lower between these two: (upload_total x 2)/download_total or sqrt(upload_total+2) where both upload_total and download_total are measured in MBs. 
If the result is lower than 1, then it is set to 1 and if it is bigger than 10, it is set to 10. In addition, if the uploaded total is less than 1MB, the modifier is set to 1 and if the downloaded total is equal to 0, then the modifier is set to 10.

== What is a slot? ==

When uploading files, your upload bandwidth (which may vary depending on the upload limit or the natural connection-type upload limit) will be divided into slots. So, each slot is an amount of KBps which will be assigned to each client who tries to download from you.

AMule files

2005-08-28T00:43:31Z

83.42.86.182:

<center>'''English''' | [[AMule_files-nl|Nederlands]] | [[AMule_files-de|Deutsch]] | [[AMule_files-hu|Magyar]]</center>

Most [[aMule]]'s config files and data are the same as or is compatible with [[eMule|eMule]]'s.

Have in mind that you might not have all of them on your hard disk, since they are generated when needed.

Here is a list and the usage of each of them:
*'''~/.eMule:''' [[aMule]]'s old personal configuration file (version prior to [[aMule]] 2.0.0).
*'''[[addresses.dat_file|~/.aMule/addresses.dat]]:''' Contains a list of serverlist URLs to check (if enabled in Preferences) for new servers on startup.
*'''[[amule.conf_file|~/.aMule/amule.conf]]:''' [[aMule]]'s personal configuration file (where most preferences are stored).
*'''[[amulesig.dat_file|~/.aMule/amulesig.dat]]:''' This is [[aMule_Project_FAQ:About|aMule]]'s [[signature|OnLineSignature]] file, which is the same as [[eMule|eMule]]'s [[signature|signature]] (see [[onlinesig.dat_file|''onlinesig.dat'']] below) but with extended information.
*'''~/.aMule/aMule.tmpl:''' This was the template file which [[amuleweb|aMule WebServer]] used in version prior to [[aMule]] 2.0.0.
*'''~/.aMule/aMule-online-sign.png:''' This file will only exist if [[CAS]] has been run sometime with the ''-o'' switch and ''~/.aMule/casrc'' was successfully configured. It is an image containing details on [[aMule_Project_FAQ:About|aMule]]'s status.*'''~/.aMule/aMule-online-sign.html:''' This file will only exist if [[CAS]] has been asked sometime to generate an [http://www.w3.org/MarkUp HTML] stats page. This [http://www.w3.org/MarkUp HTML] page contains details on [[aMule_Project_FAQ:About|aMule]]'s status.
*'''[[casrc_file|~/.aMule/casrc]]:''' This file will only exist if [[CAS]] has been run sometime with the ''-o'' switch. It contains the settings for the [[CAS]] image creation.
*'''[[clients.met_file|~/.aMule/clients.met]]:''' Contains the public hashes of other known clients along with the credits it owes each of them.
*'''~/.aMule/clients.met.BAK:''' Backup of [[clients.met file]].
*'''[[cryptkey.dat_file|~/.aMule/cryptkey.dat]]:''' It contains the unique 384 bit private [http://www.rsasecurity.com/rsalabs/node.asp?id=2125 RSA] key of your [[client]].
*'''[[emfriends.met file|~/.aMule/emfriends.met]]:''' Contains your friends list configuration.
*'''[[ED2KLinks_file|~/.aMule/ED2KLinks]]:''' This file acts as an external interface to add downloads to [[aMule]].
*'''[[ipfilter.dat file|~/.aMule/ipfilter.dat]]:''' This file contains the [[IP]] ranges and access levels restrictions which will be passed to [[IPFilter]].
*'''~/.aMule/ipfilter.download:''' This is where [[ipfilter.dat file]]s are temporary downloaded, before being renamed to ''ipfilter.dat'' (if the download succeeds).
*'''~/.aMule/ipfilter_static.dat:''' This file contains the [[IP]] ranges and access levels restrictions which will be passed to [[IPFilter]]. The difference between this file and [[ipfilter.dat file]] is that this one contains static [[IP]] ranges which will override those in ''ipfilter.dat'' in case of collision, and that this file will never be modified by [[aMule]], while ''ipfilter.dat'' may be auto-updated.
*'''[[key_index.dat file|~/.aMule/key_index.dat]]:'''
*'''[[known.met file|~/.aMule/known.met]]:''' This file stores the hashes and some details of your shared files like size, path, statics, etc.
*'''[[known2.met file|~/.aMule/known2.met]]:''' This file stores the verified [[AICH]] hashes of your shared files.
*'''[[last_version_check_file|~/.aMule/last_version_check]]:''' Temporary file containing the version of the latest official [[aMule]] release available.
*'''[[lastversion_file|~/.aMule/lastversion]]:''' This is only for [[aMule_Project_FAQ:About|aMule]] to know if you changed your version or if it's the first time you run it.
*'''[[load_index.dat file|~/.aMule/load_index.dat]]:''' Contains keyIDs of other [[Kademlia]] clientsand the date when they where last seen.
*'''~/.aMule/logfile:''' This file contains the log of the last [[aMule_Project_FAQ:About|aMule]] execution.
*'''~/.aMule/muleconn:''' This file is a socket for [[aMule_Project_FAQ:About|aMule]] communications.
*'''[[nodes.dat file|~/.aMule/nodes.dat]]:''' Contains a list of Kademlia contacts and details on how to contact each of them.
*'''[[onlinesig.dat_file|~/.aMule/onlinesig.dat]]:''' This is an [[eMule|eMule]] compatible [[signature|OnLineSignature]] file. It's used by other applications to know basic information on [[aMule_Project_FAQ:About|aMule]]'s stat. See also [[amulesig.dat_file|''amulesig.dat'']] above.
*'''[[preferences.dat_file|~/.aMule/preferences.dat]]:''' Contains the public key of your client on the [[FAQ_ed2k|ed2k]] network, also known as user hash.
*'''[[preferencesKad.dat_file|~/.aMule/preferencesKad.dat]]:''' Contains the [[IP]] and client ID of your client on the [[Kademlia]] network, that is, your identification keys.
*'''[[remote.conf_file|~/.aMule/remote.conf]]:''' Configuration file for [[External Connections]].
*'''[[server.met file|~/.aMule/server.met]]:''' This is a list of all known servers and your preferences about them (priority, name, [[IP]], port and such).
*'''~/.aMule/server.met.download:''' This is where [[server.met file]]s are temporary downloaded, before being renamed to ''server.met'' (if the download succeeds).
*'''~/.aMule/server.met.new:''' Temporal file while it is being written into disk. As soon as [[aMule]] is finished writting it, it is renamed to [[server.met file|server.met]].
*'''~/.aMule/server_auto.met:''' Here is where [[server.met file]]s are downloaded before merging them with [[aMule]]'s [[server.met file]].
*'''~/.aMule/server_met.old:''' Backup of [[server.met file]].
*'''[[shareddir.dat_file|~/.aMule/shareddir.dat]]:''' Stores the paths to all shared directories.
*'''[[src_index.dat file|~/.aMule/src_index.dat]]:'''
*'''[[staticservers.dat_file|~/.aMule/staticservers.dat]]:''' Stores a list of [[static server]]s.
*'''~/aMule-online-sign.{png|jpg|bmp}:''' Default location where [[wxCAS]] stores the stat image.
*'''~/my_ed2k_link.txt:''' Default location where [[aLinkCreator]] stores computed [[ed2k link]]s.
*'''/usr/share/fonts/corefonts/times.ttf:''' Default location where [[CAS]] will look for a font to generate the stats image.
*'''/usr/share/pixmaps/stat.png:''' Default location where [[CAS]] will look for a template image to generate the stats image.
*'''/usr/share/pixmaps/tmp.html:''' Default location where [[CAS]] will look for a template [http://www.w3c.com/MarkUp HTML] page to generate the stats [http://www.w3c.com/MarkUp HTML] page.

Other files in ''~/.aMule/'' are most surely backups of some of the above files.
Also, on the Temp directory (which is ''~/.aMule/Temp'' by default but can be set to any other on Preferences), [[aMule_Project_FAQ:About|aMule]] will create, for each download in queue, the following files:

*'''[[part file|*.part]]:''' This file contains the downloaded parts (not chunks, since not completed chunks are also stored here) of the download. As [[aMule_Project_FAQ:About|aMule]] is able to download from more than one user at the same time, this file has the size of the complete file. The missing parts are filled with zeros.
*'''[[part.met file|*.part.met]]:''' This file contains information on the downloaded parts of the download, the verified chunks, the hash values of the remaining chunks, etc.
*'''*.part.met.bak:''' This are backups of the ''[[part.met file|*.part.met]]'' files. Every now and then aMule creates this backups since without the ''*.part.met'' file, a download has no meaning for aMule. If any ''*.part.met'' file "disappeared, you should rename the ''*.part.met.bak'' to ''*.part.met''.
*'''*.part.met.backup:''' This are temporal ''[[part.met file|*.part.met]]'' while the data is being stored. As soon as [[aMule]] finishes writting the file, it is renamed to ''*.part.met''.
*'''[[part.met.seeds file|*.part.met.seeds]]:''' This file only exists if you have enabled to store the [[IP]]s of sources of rare files in the preferences, so that [[aMule_Project_FAQ:About|aMule]] can try to connect to these sources again after a restart.

The directories in ''~/.aMule/'' have the following use:

*'''~/.aMule/Incoming/:''' By default, the directory where [[aMule_Project_FAQ:About|aMule]] stores the completed downloads (except on [http://macosx.apple.com MacOS X]).
*'''~/.aMule/Temp/:''' By default, the directory where [[aMule_Project_FAQ:About|aMule]] stores the non-completed downloads (temporary files).
*'''~/.aMule/webserver/:''' This directory contains the skins for [[aMuleWeb]].
*'''~/aMule Downloads:''' By default, the directory where [[aMule_Project_FAQ:About|aMule]] stores the completed downloads on [http://www.microsoft.com/windows Windows].
*'''~/Documents/aMule Downloads:''' By default, the directory where [[aMule_Project_FAQ:About|aMule]] stores the completed downloads on [http://macosx.apple.com MacOS X] (since [[aMule]] 2.0.0).