AMule Project FAQ - User contributions [en]

HowTo compile on Mac

2007-08-24T21:33:39Z

Lionel77: Xcode clarification

How to get and install [[aMule]] on [http://www.apple.com/macosx/ Apple Mac OS X].

# You can simply download the finished application ('binary release') or
# You compile it from a [[aMule CVS|CVS source snapshot]].

''The preceding version of this page covering [[aMule]] 2.0.0rc8 and earlier is archived [[HowTo_compile_on_Mac_v200rc8|here]].''

== Binary releases ==

If you don't want to bother with installing and compiling all those tools and sources, then get one of the pre-compiled [[aMule]] applications. The official release is considered 'stable', but every now and then applications are built from the current source to allow more people to test new features or the like.

# Latest official binary release: [http://www.amule.org/files/files.php?cat=30 aMule-2.1.3-Mac]
# Periodically compiled binary from cvs: [http://forum.amule.org/index.php?topic=5051.0 amule forum]

Now, to install the downloaded binary, just drag the aMule application to a folder of your choice (e.g., ''/Applications'').

To start aMule, double-click the application icon.

'''Note:''' You might want to take a look at the [[Mac specific usage]] article.

== Compiling from source ==

Compiling from source allows most current bug reports, because you can compile and test the [[aMule CVS|CVS snapshot]] of the very day.

To compile [[aMule]] from source you need some development tools, the [[wxWidgets]] library and the [http://dl.amule.org aMule source].

=== Get the sources and development tools ===

==== [http://developer.apple.com/tools/xcode Xcode] ====

[http://developer.apple.com/tools/xcode Xcode] is [http://www.apple.com Apple]'s development environment. We need it for the [http://gcc.gnu.org GCC] compiler.

You will need at least version 2.1 of Xcode, a more recent version is preferable though. [http://developer.apple.com/tools/xcode Xcode] is included on the OS X 10.4 DVD, but early versions of 10.4 were shipped with Xcode 2.0, so you will need to check that the version on your DVD is at least 2.1.

Alternatively, you can download the most recent version of Xcode from Apple, but you will need to sign up for a free-of-charge developer account first.

# Get Xcode from http://developer.apple.com/tools/download
# "Member Site"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"

==== [http://www.macports.org MacPorts] (formerly known as DarwinPorts) ====

[http://www.macports.org MacPorts] is an open source installer for lots of open source tools ported to [http://macos.apple.com Mac OS X]. aMule needs a few of these tools to compile properly. Alternatively, you can also use [http://fink.sourceforge.net Fink] to install these tools or you can install them manually.

# Download the most recent version of [http://www.macports.org MacPorts]
# Read [http://trac.macosforge.org/projects/macports/wiki MacPorts' documentation] to learn how to install applications through [http://www.macports.org MacPorts].

The tools that you will need to install are:
# automake
# flex
# gettext (only required if you want to use a language other than English in aMule)
# libpng

==== [[wxWidgets|wxMac]] ====

[[wxWidgets|wxMac]] is the port of the [[wxWidgets]] library for [http://macos.apple.com Mac OS X]. This library is used to make [[aMule]] 'multi-platform'.

# Get the source from: http://www.wxwidgets.org/downloads/ (Source Archives: wxMac)
# Extract the archive (just double-click it)

Or get the current [[wx-cvs|CVS snapshot]]. Warning: the [[wxMac]] [[wx-cvs|CVS]] is frequently in a bad condition (e.g., currently you need to switch the vswprintf implementation that wx uses, see [http://forum.amule.org/index.php?topic=9915.msg58058#msg58058 here] for more details).

bash: cd ~/Desktop
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login
Note: password is 'anoncvs'
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac

==== [http://www.amule.org aMule itself] ====

# Get latest daily [[aMule CVS|CVS source snapshot]]: [http://www.hirnriss.net/?area=cvs aMule CVS]
# Extract the archive (just double-click it)

=== Compile the sources ===

Put the ''amule'' folder and the ''wxMac'' folder in the same place, e.g. on the desktop (if using another location, ensure that there are no spaces in the path as this can lead to file not found errors with [[wxMac]]).

==== Compile [[wxMac]] ====

This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source.

The following assumes that you have placed the above packages on your Desktop. 
''cd'' into the ''wxMac'' folder, ''configure'' and ''make'':

bash: cd ~/Desktop/wxMac-2.8.4/build
bash: ../configure --disable-shared --enable-unicode --enable-debug --enable-debug_gdb
bash: make

'''Note:''' The second command above makes sure that wxMac is compiled with debug information. This information allows you to submit a helpful stacktrace if [[aMule]] crashes or a sample if it hangs to the [[aMule devs|aMule developers]]. If you do not want to compile a debug version then you can use "--disable-debug --disable-debug_gdb" instead.

'''Note:''' If you want to compile a [http://en.wikipedia.org/wiki/Universal_binary Universal Binary] of aMule (i.e., a version of aMule that runs on both PowerPC based and Intel based Macs) then you can add the "--enable-universal_binary" parameter at the end of the second command. If you don't include this parameter wxMac and aMule will be compiled for your native architechture only.

'''Note:''' The above make command may take up to 45 minutes, depending on the speed of your CPU(s) and the parameters you chose.

==== Compile [[aMule]] ====

Now ''cd'' into the ''amule'' folder, ''configure'' and ''make'':

'''Note:''' You can copy and paste the 4 lines for ''./configure'' in one go.

bash: cd ~/Desktop/amule-cvs
bash: ./configure --disable-systray --disable-gtk --enable-embedded_crypto \
--with-wx-config=../wxMac-2.8.4/build/wx-config \
--enable-cas --enable-webserver --enable-amulecmd \
--enable-debug --disable-optimize

bash: make
bash: ./src/utils/scripts/mac_packager

'''Note:''' If you don't want to compile aMule with debug information (see above) you can use "--disable-debug --enable-optimize" in the configure statement.

'''Note:''' In order to compile aMule as a Universal Binary (see above) you will need to add the following parameters to the configure statement:
--disable-dependency-tracking \
CFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk" \
CXXFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk"

==== Running [[aMule]] ====
Once the mac_packager script has finished, you can move the aMule application from the amule-cvs folder to anywhere on your hard drive.

'''Important:''' Because aMule CVS versions contain experimental code they need to be started via the Terminal to prevent users from accidentally running a potentially unstable application:
# Drag the aMule application onto a Terminal window. Terminal will insert the path to the application onto the command line. It will also add a space after the path.
# Now delete the space at the end of the path and paste "/Contents/MacOS/amule --even-if-lfroen-surreptitiously-removes-it-this-will-stay". Then hit return to start aMule.

If starting aMule this way annoys you, you can simply comment out the check for the above switch in amule.cpp before you compile aMule. If you do this, however, we strongly urge you to not pass along the resulting binary to anybody else.

HowTo compile on Mac

2007-08-24T21:16:45Z

Lionel77: Removed XCode 2.0 warning

How to get and install [[aMule]] on [http://www.apple.com/macosx/ Apple Mac OS X].

# You can simply download the finished application ('binary release') or
# You compile it from a [[aMule CVS|CVS source snapshot]].

''The preceding version of this page covering [[aMule]] 2.0.0rc8 and earlier is archived [[HowTo_compile_on_Mac_v200rc8|here]].''

== Binary releases ==

If you don't want to bother with installing and compiling all those tools and sources, then get one of the pre-compiled [[aMule]] applications. The official release is considered 'stable', but every now and then applications are built from the current source to allow more people to test new features or the like.

# Latest official binary release: [http://www.amule.org/files/files.php?cat=30 aMule-2.1.3-Mac]
# Periodically compiled binary from cvs: [http://forum.amule.org/index.php?topic=5051.0 amule forum]

Now, to install the downloaded binary, just drag the aMule application to a folder of your choice (e.g., ''/Applications'').

To start aMule, double-click the application icon.

'''Note:''' You might want to take a look at the [[Mac specific usage]] article.

== Compiling from source ==

Compiling from source allows most current bug reports, because you can compile and test the [[aMule CVS|CVS snapshot]] of the very day.

To compile [[aMule]] from source you need some development tools, the [[wxWidgets]] library and the [http://dl.amule.org aMule source].

=== Get the sources and development tools ===

==== [http://developer.apple.com/tools/xcode Xcode] ====

[http://developer.apple.com/tools/xcode Xcode] is [http://www.apple.com Apple]'s development environment. We need it for the [http://gcc.gnu.org GCC] compiler.

You may have [http://developer.apple.com/tools/xcode Xcode] on CD/DVD (it is on the [http://www.apple.com/macosx/ OS X] 10.4 DVD), but we strongly recommend that you download a more recent version from [http://www.apple.com Apple]. You will need to sign up for a free-of-charge developer account first, though.

# Get XCode from http://developer.apple.com/tools/download
# "Member Site"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"

==== [http://www.macports.org MacPorts] (formerly known as DarwinPorts) ====

[http://www.macports.org MacPorts] is an open source installer for lots of open source tools ported to [http://macos.apple.com Mac OS X]. aMule needs a few of these tools to compile properly. Alternatively, you can also use [http://fink.sourceforge.net Fink] to install these tools or you can install them manually.

# Download the most recent version of [http://www.macports.org MacPorts]
# Read [http://trac.macosforge.org/projects/macports/wiki MacPorts' documentation] to learn how to install applications through [http://www.macports.org MacPorts].

The tools that you will need to install are:
# automake
# flex
# gettext (only required if you want to use a language other than English in aMule)
# libpng

==== [[wxWidgets|wxMac]] ====

[[wxWidgets|wxMac]] is the port of the [[wxWidgets]] library for [http://macos.apple.com Mac OS X]. This library is used to make [[aMule]] 'multi-platform'.

# Get the source from: http://www.wxwidgets.org/downloads/ (Source Archives: wxMac)
# Extract the archive (just double-click it)

Or get the current [[wx-cvs|CVS snapshot]]. Warning: the [[wxMac]] [[wx-cvs|CVS]] is frequently in a bad condition (e.g., currently you need to switch the vswprintf implementation that wx uses, see [http://forum.amule.org/index.php?topic=9915.msg58058#msg58058 here] for more details).

bash: cd ~/Desktop
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login
Note: password is 'anoncvs'
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac

==== [http://www.amule.org aMule itself] ====

# Get latest daily [[aMule CVS|CVS source snapshot]]: [http://www.hirnriss.net/?area=cvs aMule CVS]
# Extract the archive (just double-click it)

=== Compile the sources ===

Put the ''amule'' folder and the ''wxMac'' folder in the same place, e.g. on the desktop (if using another location, ensure that there are no spaces in the path as this can lead to file not found errors with [[wxMac]]).

==== Compile [[wxMac]] ====

This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source.

The following assumes that you have placed the above packages on your Desktop. 
''cd'' into the ''wxMac'' folder, ''configure'' and ''make'':

bash: cd ~/Desktop/wxMac-2.8.4/build
bash: ../configure --disable-shared --enable-unicode --enable-debug --enable-debug_gdb
bash: make

'''Note:''' The second command above makes sure that wxMac is compiled with debug information. This information allows you to submit a helpful stacktrace if [[aMule]] crashes or a sample if it hangs to the [[aMule devs|aMule developers]]. If you do not want to compile a debug version then you can use "--disable-debug --disable-debug_gdb" instead.

'''Note:''' If you want to compile a [http://en.wikipedia.org/wiki/Universal_binary Universal Binary] of aMule (i.e., a version of aMule that runs on both PowerPC based and Intel based Macs) then you can add the "--enable-universal_binary" parameter at the end of the second command. If you don't include this parameter wxMac and aMule will be compiled for your native architechture only.

'''Note:''' The above make command may take up to 45 minutes, depending on the speed of your CPU(s) and the parameters you chose.

==== Compile [[aMule]] ====

Now ''cd'' into the ''amule'' folder, ''configure'' and ''make'':

'''Note:''' You can copy and paste the 4 lines for ''./configure'' in one go.

bash: cd ~/Desktop/amule-cvs
bash: ./configure --disable-systray --disable-gtk --enable-embedded_crypto \
--with-wx-config=../wxMac-2.8.4/build/wx-config \
--enable-cas --enable-webserver --enable-amulecmd \
--enable-debug --disable-optimize

bash: make
bash: ./src/utils/scripts/mac_packager

'''Note:''' If you don't want to compile aMule with debug information (see above) you can use "--disable-debug --enable-optimize" in the configure statement.

'''Note:''' In order to compile aMule as a Universal Binary (see above) you will need to add the following parameters to the configure statement:
--disable-dependency-tracking \
CFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk" \
CXXFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk"

==== Running [[aMule]] ====
Once the mac_packager script has finished, you can move the aMule application from the amule-cvs folder to anywhere on your hard drive.

'''Important:''' Because aMule CVS versions contain experimental code they need to be started via the Terminal to prevent users from accidentally running a potentially unstable application:
# Drag the aMule application onto a Terminal window. Terminal will insert the path to the application onto the command line. It will also add a space after the path.
# Now delete the space at the end of the path and paste "/Contents/MacOS/amule --even-if-lfroen-surreptitiously-removes-it-this-will-stay". Then hit return to start aMule.

If starting aMule this way annoys you, you can simply comment out the check for the above switch in amule.cpp before you compile aMule. If you do this, however, we strongly urge you to not pass along the resulting binary to anybody else.

HowTo compile on Mac

2007-08-24T21:16:01Z

Lionel77: Download XCode

How to get and install [[aMule]] on [http://www.apple.com/macosx/ Apple Mac OS X].

# You can simply download the finished application ('binary release') or
# You compile it from a [[aMule CVS|CVS source snapshot]].

''The preceding version of this page covering [[aMule]] 2.0.0rc8 and earlier is archived [[HowTo_compile_on_Mac_v200rc8|here]].''

== Binary releases ==

If you don't want to bother with installing and compiling all those tools and sources, then get one of the pre-compiled [[aMule]] applications. The official release is considered 'stable', but every now and then applications are built from the current source to allow more people to test new features or the like.

# Latest official binary release: [http://www.amule.org/files/files.php?cat=30 aMule-2.1.3-Mac]
# Periodically compiled binary from cvs: [http://forum.amule.org/index.php?topic=5051.0 amule forum]

Now, to install the downloaded binary, just drag the aMule application to a folder of your choice (e.g., ''/Applications'').

To start aMule, double-click the application icon.

'''Note:''' You might want to take a look at the [[Mac specific usage]] article.

== Compiling from source ==

Compiling from source allows most current bug reports, because you can compile and test the [[aMule CVS|CVS snapshot]] of the very day.

To compile [[aMule]] from source you need some development tools, the [[wxWidgets]] library and the [http://dl.amule.org aMule source].

=== Get the sources and development tools ===

==== [http://developer.apple.com/tools/xcode Xcode] ====

[http://developer.apple.com/tools/xcode Xcode] is [http://www.apple.com Apple]'s development environment. We need it for the [http://gcc.gnu.org GCC] compiler.

You may have [http://developer.apple.com/tools/xcode Xcode] on CD/DVD (it is on the [http://www.apple.com/macosx/ OS X] 10.4 DVD), but we strongly recommend that you download a more recent version from [http://www.apple.com Apple]. You will need to sign up for a free-of-charge developer account first, though.

# Get XCode from http://developer.apple.com/tools/download
# "Member Site"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"

==== [http://www.macports.org MacPorts] (formerly known as DarwinPorts) ====

[http://www.macports.org MacPorts] is an open source installer for lots of open source tools ported to [http://macos.apple.com Mac OS X]. aMule needs a few of these tools to compile properly. Alternatively, you can also use [http://fink.sourceforge.net Fink] to install these tools or you can install them manually.

# Download the most recent version of [http://www.macports.org MacPorts]
# Read [http://trac.macosforge.org/projects/macports/wiki MacPorts' documentation] to learn how to install applications through [http://www.macports.org MacPorts].

The tools that you will need to install are:
# automake
# flex
# gettext (only required if you want to use a language other than English in aMule)
# libpng

==== [[wxWidgets|wxMac]] ====

[[wxWidgets|wxMac]] is the port of the [[wxWidgets]] library for [http://macos.apple.com Mac OS X]. This library is used to make [[aMule]] 'multi-platform'.

# Get the source from: http://www.wxwidgets.org/downloads/ (Source Archives: wxMac)
# Extract the archive (just double-click it)

Or get the current [[wx-cvs|CVS snapshot]]. Warning: the [[wxMac]] [[wx-cvs|CVS]] is frequently in a bad condition (e.g., currently you need to switch the vswprintf implementation that wx uses, see [http://forum.amule.org/index.php?topic=9915.msg58058#msg58058 here] for more details).

bash: cd ~/Desktop
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login
Note: password is 'anoncvs'
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac

==== [http://www.amule.org aMule itself] ====

# Get latest daily [[aMule CVS|CVS source snapshot]]: [http://www.hirnriss.net/?area=cvs aMule CVS]
# Extract the archive (just double-click it)

=== Compile the sources ===

Put the ''amule'' folder and the ''wxMac'' folder in the same place, e.g. on the desktop (if using another location, ensure that there are no spaces in the path as this can lead to file not found errors with [[wxMac]]).

'''Important:''' If you use [http://developer.apple.com/tools/xcode Xcode] 2.0 then the [http://gcc.gnu.org gcc] 4.0 that comes with it is somewhat broken and can't compile aMule. There are two solutions: upgrade to [http://developer.apple.com/tools/xcode Xcode] 2.1 by [[#Xcode|downloading]] it from [http://www.apple.com Apple] for free, or switch your system to use [http://gcc.gnu.org gcc] 3.3. If your prefer to switch to [http://gcc.gnu.org gcc] 3.3, first check the version of your current default [http://gcc.gnu.org gcc] with ''gcc --version'' and then switch to version 3.3 if required:

bash: gcc --version
bash: sudo gcc_select 3.3

==== Compile [[wxMac]] ====

This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source.

The following assumes that you have placed the above packages on your Desktop. 
''cd'' into the ''wxMac'' folder, ''configure'' and ''make'':

bash: cd ~/Desktop/wxMac-2.8.4/build
bash: ../configure --disable-shared --enable-unicode --enable-debug --enable-debug_gdb
bash: make

'''Note:''' The second command above makes sure that wxMac is compiled with debug information. This information allows you to submit a helpful stacktrace if [[aMule]] crashes or a sample if it hangs to the [[aMule devs|aMule developers]]. If you do not want to compile a debug version then you can use "--disable-debug --disable-debug_gdb" instead.

'''Note:''' If you want to compile a [http://en.wikipedia.org/wiki/Universal_binary Universal Binary] of aMule (i.e., a version of aMule that runs on both PowerPC based and Intel based Macs) then you can add the "--enable-universal_binary" parameter at the end of the second command. If you don't include this parameter wxMac and aMule will be compiled for your native architechture only.

'''Note:''' The above make command may take up to 45 minutes, depending on the speed of your CPU(s) and the parameters you chose.

==== Compile [[aMule]] ====

Now ''cd'' into the ''amule'' folder, ''configure'' and ''make'':

'''Note:''' You can copy and paste the 4 lines for ''./configure'' in one go.

bash: cd ~/Desktop/amule-cvs
bash: ./configure --disable-systray --disable-gtk --enable-embedded_crypto \
--with-wx-config=../wxMac-2.8.4/build/wx-config \
--enable-cas --enable-webserver --enable-amulecmd \
--enable-debug --disable-optimize

bash: make
bash: ./src/utils/scripts/mac_packager

'''Note:''' If you don't want to compile aMule with debug information (see above) you can use "--disable-debug --enable-optimize" in the configure statement.

'''Note:''' In order to compile aMule as a Universal Binary (see above) you will need to add the following parameters to the configure statement:
--disable-dependency-tracking \
CFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk" \
CXXFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk"

==== Running [[aMule]] ====
Once the mac_packager script has finished, you can move the aMule application from the amule-cvs folder to anywhere on your hard drive.

'''Important:''' Because aMule CVS versions contain experimental code they need to be started via the Terminal to prevent users from accidentally running a potentially unstable application:
# Drag the aMule application onto a Terminal window. Terminal will insert the path to the application onto the command line. It will also add a space after the path.
# Now delete the space at the end of the path and paste "/Contents/MacOS/amule --even-if-lfroen-surreptitiously-removes-it-this-will-stay". Then hit return to start aMule.

If starting aMule this way annoys you, you can simply comment out the check for the above switch in amule.cpp before you compile aMule. If you do this, however, we strongly urge you to not pass along the resulting binary to anybody else.

HowTo compile on Mac

2007-08-24T21:07:43Z

Lionel77: gettext info added

How to get and install [[aMule]] on [http://www.apple.com/macosx/ Apple Mac OS X].

# You can simply download the finished application ('binary release') or
# You compile it from a [[aMule CVS|CVS source snapshot]].

''The preceding version of this page covering [[aMule]] 2.0.0rc8 and earlier is archived [[HowTo_compile_on_Mac_v200rc8|here]].''

== Binary releases ==

If you don't want to bother with installing and compiling all those tools and sources, then get one of the pre-compiled [[aMule]] applications. The official release is considered 'stable', but every now and then applications are built from the current source to allow more people to test new features or the like.

# Latest official binary release: [http://www.amule.org/files/files.php?cat=30 aMule-2.1.3-Mac]
# Periodically compiled binary from cvs: [http://forum.amule.org/index.php?topic=5051.0 amule forum]

Now, to install the downloaded binary, just drag the aMule application to a folder of your choice (e.g., ''/Applications'').

To start aMule, double-click the application icon.

'''Note:''' You might want to take a look at the [[Mac specific usage]] article.

== Compiling from source ==

Compiling from source allows most current bug reports, because you can compile and test the [[aMule CVS|CVS snapshot]] of the very day.

To compile [[aMule]] from source you need some development tools, the [[wxWidgets]] library and the [http://dl.amule.org aMule source].

=== Get the sources and development tools ===

==== [http://developer.apple.com/tools/xcode Xcode] ====

[http://developer.apple.com/tools/xcode Xcode] is [http://www.apple.com Apple]'s development environment. We need it for the [http://gcc.gnu.org GCC] compiler. You may have [http://developer.apple.com/tools/xcode Xcode] on CD/DVD, e.g. it is on the [http://www.apple.com/macosx/ OS X] 10.4 DVD.

Otherwise, you can download it from [http://www.apple.com Apple], but you must sign up for a free-of-charge developer account first.

# Get XCode from http://developer.apple.com/tools/download
# "Member Site"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"

==== [http://www.macports.org MacPorts] (formerly known as DarwinPorts) ====

[http://www.macports.org MacPorts] is an open source installer for lots of open source tools ported to [http://macos.apple.com Mac OS X]. aMule needs a few of these tools to compile properly. Alternatively, you can also use [http://fink.sourceforge.net Fink] to install these tools or you can install them manually.

# Download the most recent version of [http://www.macports.org MacPorts]
# Read [http://trac.macosforge.org/projects/macports/wiki MacPorts' documentation] to learn how to install applications through [http://www.macports.org MacPorts].

The tools that you will need to install are:
# automake
# flex
# gettext (only required if you want to use a language other than English in aMule)
# libpng

==== [[wxWidgets|wxMac]] ====

[[wxWidgets|wxMac]] is the port of the [[wxWidgets]] library for [http://macos.apple.com Mac OS X]. This library is used to make [[aMule]] 'multi-platform'.

# Get the source from: http://www.wxwidgets.org/downloads/ (Source Archives: wxMac)
# Extract the archive (just double-click it)

Or get the current [[wx-cvs|CVS snapshot]]. Warning: the [[wxMac]] [[wx-cvs|CVS]] is frequently in a bad condition (e.g., currently you need to switch the vswprintf implementation that wx uses, see [http://forum.amule.org/index.php?topic=9915.msg58058#msg58058 here] for more details).

bash: cd ~/Desktop
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login
Note: password is 'anoncvs'
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac

==== [http://www.amule.org aMule itself] ====

# Get latest daily [[aMule CVS|CVS source snapshot]]: [http://www.hirnriss.net/?area=cvs aMule CVS]
# Extract the archive (just double-click it)

=== Compile the sources ===

Put the ''amule'' folder and the ''wxMac'' folder in the same place, e.g. on the desktop (if using another location, ensure that there are no spaces in the path as this can lead to file not found errors with [[wxMac]]).

'''Important:''' If you use [http://developer.apple.com/tools/xcode Xcode] 2.0 then the [http://gcc.gnu.org gcc] 4.0 that comes with it is somewhat broken and can't compile aMule. There are two solutions: upgrade to [http://developer.apple.com/tools/xcode Xcode] 2.1 by [[#Xcode|downloading]] it from [http://www.apple.com Apple] for free, or switch your system to use [http://gcc.gnu.org gcc] 3.3. If your prefer to switch to [http://gcc.gnu.org gcc] 3.3, first check the version of your current default [http://gcc.gnu.org gcc] with ''gcc --version'' and then switch to version 3.3 if required:

bash: gcc --version
bash: sudo gcc_select 3.3

==== Compile [[wxMac]] ====

This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source.

The following assumes that you have placed the above packages on your Desktop. 
''cd'' into the ''wxMac'' folder, ''configure'' and ''make'':

bash: cd ~/Desktop/wxMac-2.8.4/build
bash: ../configure --disable-shared --enable-unicode --enable-debug --enable-debug_gdb
bash: make

'''Note:''' The second command above makes sure that wxMac is compiled with debug information. This information allows you to submit a helpful stacktrace if [[aMule]] crashes or a sample if it hangs to the [[aMule devs|aMule developers]]. If you do not want to compile a debug version then you can use "--disable-debug --disable-debug_gdb" instead.

'''Note:''' If you want to compile a [http://en.wikipedia.org/wiki/Universal_binary Universal Binary] of aMule (i.e., a version of aMule that runs on both PowerPC based and Intel based Macs) then you can add the "--enable-universal_binary" parameter at the end of the second command. If you don't include this parameter wxMac and aMule will be compiled for your native architechture only.

'''Note:''' The above make command may take up to 45 minutes, depending on the speed of your CPU(s) and the parameters you chose.

==== Compile [[aMule]] ====

Now ''cd'' into the ''amule'' folder, ''configure'' and ''make'':

'''Note:''' You can copy and paste the 4 lines for ''./configure'' in one go.

bash: cd ~/Desktop/amule-cvs
bash: ./configure --disable-systray --disable-gtk --enable-embedded_crypto \
--with-wx-config=../wxMac-2.8.4/build/wx-config \
--enable-cas --enable-webserver --enable-amulecmd \
--enable-debug --disable-optimize

bash: make
bash: ./src/utils/scripts/mac_packager

'''Note:''' If you don't want to compile aMule with debug information (see above) you can use "--disable-debug --enable-optimize" in the configure statement.

'''Note:''' In order to compile aMule as a Universal Binary (see above) you will need to add the following parameters to the configure statement:
--disable-dependency-tracking \
CFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk" \
CXXFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk"

==== Running [[aMule]] ====
Once the mac_packager script has finished, you can move the aMule application from the amule-cvs folder to anywhere on your hard drive.

'''Important:''' Because aMule CVS versions contain experimental code they need to be started via the Terminal to prevent users from accidentally running a potentially unstable application:
# Drag the aMule application onto a Terminal window. Terminal will insert the path to the application onto the command line. It will also add a space after the path.
# Now delete the space at the end of the path and paste "/Contents/MacOS/amule --even-if-lfroen-surreptitiously-removes-it-this-will-stay". Then hit return to start aMule.

If starting aMule this way annoys you, you can simply comment out the check for the above switch in amule.cpp before you compile aMule. If you do this, however, we strongly urge you to not pass along the resulting binary to anybody else.

HowTo compile on Mac

2007-08-24T06:58:05Z

Lionel77: Major rewrite -- MacPorts instead of Fink, newly required packages, Universal Binary, etc.

How to get and install [[aMule]] on [http://www.apple.com/macosx/ Apple Mac OS X].

# You can simply download the finished application ('binary release') or
# You compile it from a [[aMule CVS|CVS source snapshot]].

''The preceding version of this page covering [[aMule]] 2.0.0rc8 and earlier is archived [[HowTo_compile_on_Mac_v200rc8|here]].''

== Binary releases ==

If you don't want to bother with installing and compiling all those tools and sources, then get one of the pre-compiled [[aMule]] applications. The official release is considered 'stable', but every now and then applications are built from the current source to allow more people to test new features or the like.

# Latest official binary release: [http://www.amule.org/files/files.php?cat=30 aMule-2.1.3-Mac]
# Periodically compiled binary from cvs: [http://forum.amule.org/index.php?topic=5051.0 amule forum]

Now, to install the downloaded binary, just drag the aMule application to a folder of your choice (e.g., ''/Applications'').

To start aMule, double-click the application icon.

'''Note:''' You might want to take a look at the [[Mac specific usage]] article.

== Compiling from source ==

Compiling from source allows most current bug reports, because you can compile and test the [[aMule CVS|CVS snapshot]] of the very day.

To compile [[aMule]] from source you need some development tools, the [[wxWidgets]] library and the [http://dl.amule.org aMule source].

=== Get the sources and development tools ===

==== [http://developer.apple.com/tools/xcode Xcode] ====

[http://developer.apple.com/tools/xcode Xcode] is [http://www.apple.com Apple]'s development environment. We need it for the [http://gcc.gnu.org GCC] compiler. You may have [http://developer.apple.com/tools/xcode Xcode] on CD/DVD, e.g. it is on the [http://www.apple.com/macosx/ OS X] 10.4 DVD.

Otherwise, you can download it from [http://www.apple.com Apple], but you must sign up for a free-of-charge developer account first.

# Get XCode from http://developer.apple.com/tools/download
# "Member Site"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"

==== [http://www.macports.org MacPorts] (formerly known as DarwinPorts) ====

[http://www.macports.org MacPorts] is an open source installer for lots of open source tools ported to [http://macos.apple.com Mac OS X]. aMule needs a few of these tools to compile properly. Alternatively, you can also use [http://fink.sourceforge.net Fink] to install these tools or you can install them manually.

# Download the most recent version of [http://www.macports.org MacPorts]
# Read [http://trac.macosforge.org/projects/macports/wiki MacPorts' documentation] to learn how to install applications through [http://www.macports.org MacPorts].

The tools that you will need to install are:
# automake
# flex
# gettext
# libpng

==== [[wxWidgets|wxMac]] ====

[[wxWidgets|wxMac]] is the port of the [[wxWidgets]] library for [http://macos.apple.com Mac OS X]. This library is used to make [[aMule]] 'multi-platform'.

# Get the source from: http://www.wxwidgets.org/downloads/ (Source Archives: wxMac)
# Extract the archive (just double-click it)

Or get the current [[wx-cvs|CVS snapshot]]. Warning: the [[wxMac]] [[wx-cvs|CVS]] is frequently in a bad condition (e.g., currently you need to switch the vswprintf implementation that wx uses, see [http://forum.amule.org/index.php?topic=9915.msg58058#msg58058 here] for more details).

bash: cd ~/Desktop
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login
Note: password is 'anoncvs'
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac

==== [http://www.amule.org aMule itself] ====

# Get latest daily [[aMule CVS|CVS source snapshot]]: [http://www.hirnriss.net/?area=cvs aMule CVS]
# Extract the archive (just double-click it)

=== Compile the sources ===

Put the ''amule'' folder and the ''wxMac'' folder in the same place, e.g. on the desktop (if using another location, ensure that there are no spaces in the path as this can lead to file not found errors with [[wxMac]]).

'''Important:''' If you use [http://developer.apple.com/tools/xcode Xcode] 2.0 then the [http://gcc.gnu.org gcc] 4.0 that comes with it is somewhat broken and can't compile aMule. There are two solutions: upgrade to [http://developer.apple.com/tools/xcode Xcode] 2.1 by [[#Xcode|downloading]] it from [http://www.apple.com Apple] for free, or switch your system to use [http://gcc.gnu.org gcc] 3.3. If your prefer to switch to [http://gcc.gnu.org gcc] 3.3, first check the version of your current default [http://gcc.gnu.org gcc] with ''gcc --version'' and then switch to version 3.3 if required:

bash: gcc --version
bash: sudo gcc_select 3.3

==== Compile [[wxMac]] ====

This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source.

The following assumes that you have placed the above packages on your Desktop. 
''cd'' into the ''wxMac'' folder, ''configure'' and ''make'':

bash: cd ~/Desktop/wxMac-2.8.4/build
bash: ../configure --disable-shared --enable-unicode --enable-debug --enable-debug_gdb
bash: make

'''Note:''' The second command above makes sure that wxMac is compiled with debug information. This information allows you to submit a helpful stacktrace if [[aMule]] crashes or a sample if it hangs to the [[aMule devs|aMule developers]]. If you do not want to compile a debug version then you can use "--disable-debug --disable-debug_gdb" instead.

'''Note:''' If you want to compile a [http://en.wikipedia.org/wiki/Universal_binary Universal Binary] of aMule (i.e., a version of aMule that runs on both PowerPC based and Intel based Macs) then you can add the "--enable-universal_binary" parameter at the end of the second command. If you don't include this parameter wxMac and aMule will be compiled for your native architechture only.

'''Note:''' The above make command may take up to 45 minutes, depending on the speed of your CPU(s) and the parameters you chose.

==== Compile [[aMule]] ====

Now ''cd'' into the ''amule'' folder, ''configure'' and ''make'':

'''Note:''' You can copy and paste the 4 lines for ''./configure'' in one go.

bash: cd ~/Desktop/amule-cvs
bash: ./configure --disable-systray --disable-gtk --enable-embedded_crypto \
--with-wx-config=../wxMac-2.8.4/build/wx-config \
--enable-cas --enable-webserver --enable-amulecmd \
--enable-debug --disable-optimize

bash: make
bash: ./src/utils/scripts/mac_packager

'''Note:''' If you don't want to compile aMule with debug information (see above) you can use "--disable-debug --enable-optimize" in the configure statement.

'''Note:''' In order to compile aMule as a Universal Binary (see above) you will need to add the following parameters to the configure statement:
--disable-dependency-tracking \
CFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk" \
CXXFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk"

==== Running [[aMule]] ====
Once the mac_packager script has finished, you can move the aMule application from the amule-cvs folder to anywhere on your hard drive.

'''Important:''' Because aMule CVS versions contain experimental code they need to be started via the Terminal to prevent users from accidentally running a potentially unstable application:
# Drag the aMule application onto a Terminal window. Terminal will insert the path to the application onto the command line. It will also add a space after the path.
# Now delete the space at the end of the path and paste "/Contents/MacOS/amule --even-if-lfroen-surreptitiously-removes-it-this-will-stay". Then hit return to start aMule.

If starting aMule this way annoys you, you can simply comment out the check for the above switch in amule.cpp before you compile aMule. If you do this, however, we strongly urge you to not pass along the resulting binary to anybody else.

Talk:HowTo compile on Mac

2007-08-17T03:05:32Z

Lionel77:

I need to install newer versions of flex and automake to compile amule successfully on my machine. Maybe we should just add those as dependencies that should be installed through Fink. -- lionel77

HowTo compile on Mac

2007-08-16T05:29:22Z

Lionel77: /* wxMac */ Updated link to wxMac sources and forum link to vswprintf issues

How to get and install [[aMule]] on [http://www.apple.com/macosx/ Apple Mac OS X].

# You can simply download the finished application ('binary release') or
# You compile it from a [[aMule CVS|CVS source snapshot]].

''The preceding version of this page covering [[aMule]] 2.0.0rc8 and earlier is archived [[HowTo_compile_on_Mac_v200rc8|here]].''

== Binary releases ==

If you don't want to bother with installing and compiling all those tools and sources, then get one of the pre-compiled [[aMule]] applications. The official release is considered 'stable', but every now and then applications are built from the current source to allow more people to test new features or the like.

# Latest official binary release: [http://www.amule.org/files/files.php?cat=30 aMule-2.1.3-Mac]
# Periodically compiled binary from cvs: [http://forum.amule.org/index.php?topic=5051.0 amule forum]

Now, to install the downloaded binary, just drag the aMule application to a folder of your choice (e.g., ''/Applications'').

To start aMule, double-click the application icon.

'''Note:''' You might want to take a look at the [[Mac specific usage]] article.

== Compiling from source ==

Compiling from source allows most current bug reports, because you can compile and test the [[aMule CVS|CVS snapshot]] of the very day.

To compile [[aMule]] from source you need some development tools, the [[wxWidgets]] library and the [http://dl.amule.org aMule source].

=== Get the sources and development tools ===

==== [http://developer.apple.com/tools/xcode Xcode] ====

[http://developer.apple.com/tools/xcode Xcode] is [http://www.apple.com Apple]'s development environment. We need it for the [http://gcc.gnu.org GCC] compiler. You may have [http://developer.apple.com/tools/xcode Xcode] on CD/DVD, e.g. it is on the [http://www.apple.com/macosx/ OS X] 10.4 DVD.

Otherwise, you can download it from [http://www.apple.com Apple], but you must sign up for a free-of-charge developer account first.

# Get XCode from http://developer.apple.com/tools/download
# "Member Site"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"

==== [http://fink.sourceforge.net Fink] ====

'''Optional:''' [http://fink.sourceforge.net Fink] and [http://www.gnu.org/software/gettext gettext] are not strictly required to compile [[aMule]], but without them [[aMule]] will only appear in english.

[http://fink.sourceforge.net Fink] is an open source installer for lots of open source tools ported to [http://macos.apple.com Mac OSX]. We need it to install the open source tool [http://www.gnu.org/software/gettext gettext].

# Get [http://fink.sourceforge.net Fink] from http://fink.sourceforge.net/download
# Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink].

==== [http://www.gnu.org/software/gettext gettext] ====

'''Optional:''' [http://www.gnu.org/software/gettext gettext] and [http://fink.sourceforge.net Fink] are not strictly required to compile [[aMule]], but without them [[aMule]] will only appear in english.

[http://www.gnu.org/software/gettext gettext] is an open source library for text internationalization. This library is used to make [[aMule]] multi-lingual.
# Get and install the [http://www.gnu.org/software/gettext gettext] library with [http://fink.sourceforge.net Fink]. The package name is [http://www.gnu.org/software/gettext gettext].

==== [[wxWidgets|wxMac]] ====

[[wxWidgets|wxMac]] is the port of the [[wxWidgets]] library for [http://macos.apple.com Mac OSX]. This library is used to make [[aMule]] 'multi-platform'.

# Get the source from: http://www.wxwidgets.org/downloads/ (Source Archives: wxMac)
# Extract the archive (just double-click it)

Or get the current [[wx-cvs|CVS snapshot]]. Warning: the [[wxMac]] [[wx-cvs|CVS]] is frequently in a bad condition (e.g., currently you need to switch the vswprintf implementation that wx uses, see [http://forum.amule.org/index.php?topic=9915.msg58058#msg58058 here] for more details).

bash: cd ~/Desktop
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login
Note: password is 'anoncvs'
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac

==== [http://www.amule.org aMule itself] ====

# Get latest daily [[aMule CVS|CVS source snapshot]]: [http://www.hirnriss.net/?area=cvs aMule CVS]
# Extract the archive (just double-click it)

=== Compile the sources ===

Put the ''amule'' folder and the ''wxMac'' folder in the same place, e.g. on the desktop (if using another location, ensure that there are no spaces in the path as this can lead to file not found errors with [[wxMac]]).

'''Important:''' If you use [http://developer.apple.com/tools/xcode Xcode] 2.0 then the [http://gcc.gnu.org gcc] 4.0 that comes with it is somewhat broken and can't compile aMule. There are two solutions: upgrade to [http://developer.apple.com/tools/xcode Xcode] 2.1 by [[#Xcode|downloading]] it from [http://www.apple.com Apple] for free, or switch your system to use [http://gcc.gnu.org gcc] 3.3. If your prefer to switch to [http://gcc.gnu.org gcc] 3.3, first check the version of your current default [http://gcc.gnu.org gcc] with ''gcc --version'' and then switch to version 3.3 if required:

bash: gcc --version
bash: sudo gcc_select 3.3

==== Compile [[wxMac]] ====

This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source.

The following assumes that you have placed the above packages on your Desktop. 
''cd'' into the ''wxMac'' folder, ''configure'' and ''make'':

bash: cd ~/Desktop/wxMac-2.8.3/build
bash: ../configure --disable-shared --enable-unicode
bash: make

'''NOTE:''' This took approx. 30 minutes on a G4 at 1 GHz.

==== Compile [[aMule]] ====

Now ''cd'' into the ''amule'' folder, ''configure'' and ''make'':

'''NOTE:''' You can copy'n'paste the 3 lines for ''./configure'' in one go.

bash: cd ~/Desktop/aMule
bash: ./configure --disable-systray --disable-gtk \
--with-wx-config=../wxMac-2.8.3/build/wx-config \
--disable-debug --enable-optimize '''''OPTIONAL'''''

bash: make
bash: strip src/amule '''''OPTIONAL'''''
bash: mv src/amule aMule.app/Contents/MacOS/

The two lines marked as '''''OPTIONAL''''' are optional, that is, the last two options to ''./configure'' and the ''strip'' command. They result in a dramatically reduced file size (approx. 3 MB instead of 50 MB) but disable all possibilities to submit a helpful stacktrace if [[aMule]] crashes or a sample if it hangs to the [[aMule devs|aMule developers]].

=== Problems and solutions ===

*If [http://fink.sourceforge.net Fink] reports something like: ''After unpacking 11.2GB will be freed'', don't be afraid. [http://fink.sourceforge.net Fink] has evolved into a different way of managing packet's size and some old ("old": at least some months old) packages' sizes aren't handled correctly on the output. If this is your case, devide the number by 1024. So, what the above example really means is: ''After unpacking 11.2MB will be freed''.

*If you get an error like this: ''You cannot open the application "amule" because it may be damaged or incomplete'', right click on ''amule'', then click on ''Show Packages Contents'', go to "Contents">"MacOS"> and double click on ''amule''. Next time you start from ''aMule.app'' it will run fine. If you still get the same error, move ''aMule.app'' to the desktop and run it from there.

HowTo compile on Mac

2006-11-28T01:35:19Z

Lionel77: =Compile aMule= Updated folder name

How to get and install [[aMule]] on [http://www.apple.com/macosx/ Apple Mac OS X].

# You can simply download the finished application ('binary release') or
# You compile it from a [[aMule CVS|CVS source snapshot]].

''The preceding version of this page covering [[aMule]] 2.0.0rc8 and earlier is archived [[HowTo_compile_on_Mac_v200rc8|here]].''

== Binary releases ==

If you don't want to bother with installing and compiling all those tools and sources, then get one of the pre-compiled [[aMule]] applications. The official release is considered 'stable', but every now and then applications are built from the current source to allow more people to test new features or the like.

# Latest official binary release: [http://www.amule.org/files/files.php?cat=30 aMule-2.1.3-Mac]
# Periodically compiled binary from cvs: [http://forum.amule.org/thread.php?threadid=5051 amule forum]

Now, to install the downloaded binary, just drag the aMule application to a folder of your choice (e.g., ''/Applications'').

To start aMule, double-click the application icon.

'''Note:''' You might want to take a look at the [[Mac specific usage]] article.

== Compiling from source ==

Compiling from source allows most current bug reports, because you can compile and test the [[aMule CVS|CVS snapshot]] of the very day.

To compile [[aMule]] from source you need some development tools, the [[wxWidgets]] library and the [http://dl.amule.org aMule source].

=== Get the sources and development tools ===

==== [http://developer.apple.com/tools/xcode Xcode] ====

[http://developer.apple.com/tools/xcode Xcode] is [http://www.apple.com Apple]'s development environment. We need it for the [http://gcc.gnu.org GCC] compiler. You may have [http://developer.apple.com/tools/xcode Xcode] on CD/DVD, e.g. it is on the [http://www.apple.com/macosx/ OS X] 10.4 DVD.

Otherwise, you can download it from [http://www.apple.com Apple], but you must sign up for a free-of-charge developer account first.

# Get XCode from http://developer.apple.com/tools/download
# "Member Site"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"

==== [http://fink.sourceforge.net Fink] ====

'''Optional:''' [http://fink.sourceforge.net Fink] and [http://www.gnu.org/software/gettext gettext] are not strictly required to compile [[aMule]], but without them [[aMule]] will only appear in english.

[http://fink.sourceforge.net Fink] is an open source installer for lots of open source tools ported to [http://macos.apple.com Mac OSX]. We need it to install the open source tool [http://www.gnu.org/software/gettext gettext].

# Get [http://fink.sourceforge.net Fink] from http://fink.sourceforge.net/download
# Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink].

==== [http://www.gnu.org/software/gettext gettext] ====

'''Optional:''' [http://www.gnu.org/software/gettext gettext] and [http://fink.sourceforge.net Fink] are not strictly required to compile [[aMule]], but without them [[aMule]] will only appear in english.

[http://www.gnu.org/software/gettext gettext] is an open source library for text internationalization. This library is used to make [[aMule]] multi-lingual.
# Get and install the [http://www.gnu.org/software/gettext gettext] library with [http://fink.sourceforge.net Fink]. The package name is [http://www.gnu.org/software/gettext gettext].

==== [[wxWidgets|wxMac]] ====

[[wxWidgets|wxMac]] is the port of the [[wxWidgets]] library for [http://macos.apple.com Mac OSX]. This library is used to make [[aMule]] 'multi-platform'.

# Get the source from: http://prdownloads.sourceforge.net/wxwindows/wxMac-2.6.3.tar.gz
# Extract the archive (just double-click it)

Or get the current [[wx-cvs|CVS snapshot]]. Warning: the [[wxMac]] [[wx-cvs|CVS]] is frequently in a bad condition (e.g., currently you need to switch the vswprintf implementation that wx uses, see [http://forum.amule.org/thread.php?postid=58058#post58058 here] for more details).

bash: cd ~/Desktop
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login
Note: password is 'anoncvs'
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac

==== [http://www.amule.org aMule itself] ====

# Get latest daily [[aMule CVS|CVS source snapshot]]: [http://www.amule.org/files/download.php?file=5 aMule CVS]
# Extract the archive (just double-click it)

=== Compile the sources ===

Put the ''amule'' folder and the ''wxMac'' folder in the same place, e.g. on the desktop (if using another location, ensure that there are no spaces in the path as this can lead to file not found errors with [[wxMac]]).

'''Important:''' If you use [http://developer.apple.com/tools/xcode Xcode] 2.0 then the [http://gcc.gnu.org gcc] 4.0 that comes with it is somewhat broken and can't compile aMule. There are two solutions: upgrade to [http://developer.apple.com/tools/xcode Xcode] 2.1 by [[#Xcode|downloading]] it from [http://www.apple.com Apple] for free, or switch your system to use [http://gcc.gnu.org gcc] 3.3. If your prefer to switch to [http://gcc.gnu.org gcc] 3.3, first check the version of your current default [http://gcc.gnu.org gcc] with ''gcc --version'' and then switch to version 3.3 if required:

bash: gcc --version
bash: sudo gcc_select 3.3

==== Compile [[wxMac]] ====

This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source.

The following assumes that you have placed the above packages on your Desktop. 
''cd'' into the ''wxMac'' folder, ''configure'' and ''make'':

bash: cd ~/Desktop/wxMac-2.6.3/build
bash: ../configure --disable-shared --enable-unicode
bash: make

'''NOTE:''' This took approx. 30 minutes on a G4 at 1 GHz.

==== Compile [[aMule]] ====

Now ''cd'' into the ''amule'' folder, ''configure'' and ''make'':

'''NOTE:''' You can copy'n'paste the 3 lines for ''./configure'' in one go.

bash: cd ~/Desktop/aMule
bash: ./configure --disable-systray --disable-gtk \
--with-wx-config=../wxMac-2.6.3/build/wx-config \
--disable-debug --enable-optimize '''''OPTIONAL'''''

bash: make
bash: strip src/amule '''''OPTIONAL'''''
bash: mv src/amule aMule.app/Contents/MacOS/

The two lines marked as '''''OPTIONAL''''' are optional, that is, the last two options to ''./configure'' and the ''strip'' command. They result in a dramatically reduced file size (approx. 3 MB instead of 50 MB) but disable all possibilities to submit a helpful stacktrace if [[aMule]] crashes or a sample if it hangs to the [[aMule devs|aMule developers]].

=== Problems and solutions ===

*If [http://fink.sourceforge.net Fink] reports something like: ''After unpacking 11.2GB will be freed'', don't be afraid. [http://fink.sourceforge.net Fink] has evolved into a different way of managing packet's size and some old ("old": at least some months old) packages' sizes aren't handled correctly on the output. If this is your case, devide the number by 1024. So, what the above example really means is: ''After unpacking 11.2MB will be freed''.

*If you get an error like this: ''You cannot open the application "amule" because it may be damaged or incomplete'', right click on ''amule'', then click on ''Show Packages Contents'', go to "Contents">"MacOS"> and double click on ''amule''. Next time you start from ''aMule.app'' it will run fine. If you still get the same error, move ''aMule.app'' to the desktop and run it from there.

HowTo compile on Mac

2006-11-28T01:23:32Z

Lionel77: =Compile wxMac= Fixed folder name

How to get and install [[aMule]] on [http://www.apple.com/macosx/ Apple Mac OS X].

# You can simply download the finished application ('binary release') or
# You compile it from a [[aMule CVS|CVS source snapshot]].

''The preceding version of this page covering [[aMule]] 2.0.0rc8 and earlier is archived [[HowTo_compile_on_Mac_v200rc8|here]].''

== Binary releases ==

If you don't want to bother with installing and compiling all those tools and sources, then get one of the pre-compiled [[aMule]] applications. The official release is considered 'stable', but every now and then applications are built from the current source to allow more people to test new features or the like.

# Latest official binary release: [http://www.amule.org/files/files.php?cat=30 aMule-2.1.3-Mac]
# Periodically compiled binary from cvs: [http://forum.amule.org/thread.php?threadid=5051 amule forum]

Now, to install the downloaded binary, just drag the aMule application to a folder of your choice (e.g., ''/Applications'').

To start aMule, double-click the application icon.

'''Note:''' You might want to take a look at the [[Mac specific usage]] article.

== Compiling from source ==

Compiling from source allows most current bug reports, because you can compile and test the [[aMule CVS|CVS snapshot]] of the very day.

To compile [[aMule]] from source you need some development tools, the [[wxWidgets]] library and the [http://dl.amule.org aMule source].

=== Get the sources and development tools ===

==== [http://developer.apple.com/tools/xcode Xcode] ====

[http://developer.apple.com/tools/xcode Xcode] is [http://www.apple.com Apple]'s development environment. We need it for the [http://gcc.gnu.org GCC] compiler. You may have [http://developer.apple.com/tools/xcode Xcode] on CD/DVD, e.g. it is on the [http://www.apple.com/macosx/ OS X] 10.4 DVD.

Otherwise, you can download it from [http://www.apple.com Apple], but you must sign up for a free-of-charge developer account first.

# Get XCode from http://developer.apple.com/tools/download
# "Member Site"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"

==== [http://fink.sourceforge.net Fink] ====

'''Optional:''' [http://fink.sourceforge.net Fink] and [http://www.gnu.org/software/gettext gettext] are not strictly required to compile [[aMule]], but without them [[aMule]] will only appear in english.

[http://fink.sourceforge.net Fink] is an open source installer for lots of open source tools ported to [http://macos.apple.com Mac OSX]. We need it to install the open source tool [http://www.gnu.org/software/gettext gettext].

# Get [http://fink.sourceforge.net Fink] from http://fink.sourceforge.net/download
# Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink].

==== [http://www.gnu.org/software/gettext gettext] ====

'''Optional:''' [http://www.gnu.org/software/gettext gettext] and [http://fink.sourceforge.net Fink] are not strictly required to compile [[aMule]], but without them [[aMule]] will only appear in english.

[http://www.gnu.org/software/gettext gettext] is an open source library for text internationalization. This library is used to make [[aMule]] multi-lingual.
# Get and install the [http://www.gnu.org/software/gettext gettext] library with [http://fink.sourceforge.net Fink]. The package name is [http://www.gnu.org/software/gettext gettext].

==== [[wxWidgets|wxMac]] ====

[[wxWidgets|wxMac]] is the port of the [[wxWidgets]] library for [http://macos.apple.com Mac OSX]. This library is used to make [[aMule]] 'multi-platform'.

# Get the source from: http://prdownloads.sourceforge.net/wxwindows/wxMac-2.6.3.tar.gz
# Extract the archive (just double-click it)

Or get the current [[wx-cvs|CVS snapshot]]. Warning: the [[wxMac]] [[wx-cvs|CVS]] is frequently in a bad condition (e.g., currently you need to switch the vswprintf implementation that wx uses, see [http://forum.amule.org/thread.php?postid=58058#post58058 here] for more details).

bash: cd ~/Desktop
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login
Note: password is 'anoncvs'
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac

==== [http://www.amule.org aMule itself] ====

# Get latest daily [[aMule CVS|CVS source snapshot]]: [http://www.amule.org/files/download.php?file=5 aMule CVS]
# Extract the archive (just double-click it)

=== Compile the sources ===

Put the ''amule'' folder and the ''wxMac'' folder in the same place, e.g. on the desktop (if using another location, ensure that there are no spaces in the path as this can lead to file not found errors with [[wxMac]]).

'''Important:''' If you use [http://developer.apple.com/tools/xcode Xcode] 2.0 then the [http://gcc.gnu.org gcc] 4.0 that comes with it is somewhat broken and can't compile aMule. There are two solutions: upgrade to [http://developer.apple.com/tools/xcode Xcode] 2.1 by [[#Xcode|downloading]] it from [http://www.apple.com Apple] for free, or switch your system to use [http://gcc.gnu.org gcc] 3.3. If your prefer to switch to [http://gcc.gnu.org gcc] 3.3, first check the version of your current default [http://gcc.gnu.org gcc] with ''gcc --version'' and then switch to version 3.3 if required:

bash: gcc --version
bash: sudo gcc_select 3.3

==== Compile [[wxMac]] ====

This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source.

The following assumes that you have placed the above packages on your Desktop. 
''cd'' into the ''wxMac'' folder, ''configure'' and ''make'':

bash: cd ~/Desktop/wxMac-2.6.3/build
bash: ../configure --disable-shared --enable-unicode
bash: make

'''NOTE:''' This took approx. 30 minutes on a G4 at 1 GHz.

==== Compile [[aMule]] ====

Now ''cd'' into the ''amule'' folder, ''configure'' and ''make'':

'''NOTE:''' You can copy'n'paste the 3 lines for ''./configure'' in one go.

bash: cd ~/Desktop/aMule
bash: ./configure --disable-systray --disable-gtk \
--with-wx-config=../wxMac-2.6.1/build/wx-config \
--disable-debug --enable-optimize '''''OPTIONAL'''''

bash: make
bash: strip src/amule '''''OPTIONAL'''''
bash: mv src/amule aMule.app/Contents/MacOS/

The two lines marked as '''''OPTIONAL''''' are optional, that is, the last two options to ''./configure'' and the ''strip'' command. They result in a dramatically reduced file size (approx. 3 MB instead of 50 MB) but disable all possibilities to submit a helpful stacktrace if [[aMule]] crashes or a sample if it hangs to the [[aMule devs|aMule developers]].

=== Problems and solutions ===

*If [http://fink.sourceforge.net Fink] reports something like: ''After unpacking 11.2GB will be freed'', don't be afraid. [http://fink.sourceforge.net Fink] has evolved into a different way of managing packet's size and some old ("old": at least some months old) packages' sizes aren't handled correctly on the output. If this is your case, devide the number by 1024. So, what the above example really means is: ''After unpacking 11.2MB will be freed''.

*If you get an error like this: ''You cannot open the application "amule" because it may be damaged or incomplete'', right click on ''amule'', then click on ''Show Packages Contents'', go to "Contents">"MacOS"> and double click on ''amule''. Next time you start from ''aMule.app'' it will run fine. If you still get the same error, move ''aMule.app'' to the desktop and run it from there.

HowTo compile on Mac

2006-11-28T01:21:45Z

Lionel77: =wxMac= Updated link to wx source | included vswprintf for wx cvs

How to get and install [[aMule]] on [http://www.apple.com/macosx/ Apple Mac OS X].

# You can simply download the finished application ('binary release') or
# You compile it from a [[aMule CVS|CVS source snapshot]].

''The preceding version of this page covering [[aMule]] 2.0.0rc8 and earlier is archived [[HowTo_compile_on_Mac_v200rc8|here]].''

== Binary releases ==

If you don't want to bother with installing and compiling all those tools and sources, then get one of the pre-compiled [[aMule]] applications. The official release is considered 'stable', but every now and then applications are built from the current source to allow more people to test new features or the like.

# Latest official binary release: [http://www.amule.org/files/files.php?cat=30 aMule-2.1.3-Mac]
# Periodically compiled binary from cvs: [http://forum.amule.org/thread.php?threadid=5051 amule forum]

Now, to install the downloaded binary, just drag the aMule application to a folder of your choice (e.g., ''/Applications'').

To start aMule, double-click the application icon.

'''Note:''' You might want to take a look at the [[Mac specific usage]] article.

== Compiling from source ==

Compiling from source allows most current bug reports, because you can compile and test the [[aMule CVS|CVS snapshot]] of the very day.

To compile [[aMule]] from source you need some development tools, the [[wxWidgets]] library and the [http://dl.amule.org aMule source].

=== Get the sources and development tools ===

==== [http://developer.apple.com/tools/xcode Xcode] ====

[http://developer.apple.com/tools/xcode Xcode] is [http://www.apple.com Apple]'s development environment. We need it for the [http://gcc.gnu.org GCC] compiler. You may have [http://developer.apple.com/tools/xcode Xcode] on CD/DVD, e.g. it is on the [http://www.apple.com/macosx/ OS X] 10.4 DVD.

Otherwise, you can download it from [http://www.apple.com Apple], but you must sign up for a free-of-charge developer account first.

# Get XCode from http://developer.apple.com/tools/download
# "Member Site"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"

==== [http://fink.sourceforge.net Fink] ====

'''Optional:''' [http://fink.sourceforge.net Fink] and [http://www.gnu.org/software/gettext gettext] are not strictly required to compile [[aMule]], but without them [[aMule]] will only appear in english.

[http://fink.sourceforge.net Fink] is an open source installer for lots of open source tools ported to [http://macos.apple.com Mac OSX]. We need it to install the open source tool [http://www.gnu.org/software/gettext gettext].

# Get [http://fink.sourceforge.net Fink] from http://fink.sourceforge.net/download
# Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink].

==== [http://www.gnu.org/software/gettext gettext] ====

'''Optional:''' [http://www.gnu.org/software/gettext gettext] and [http://fink.sourceforge.net Fink] are not strictly required to compile [[aMule]], but without them [[aMule]] will only appear in english.

[http://www.gnu.org/software/gettext gettext] is an open source library for text internationalization. This library is used to make [[aMule]] multi-lingual.
# Get and install the [http://www.gnu.org/software/gettext gettext] library with [http://fink.sourceforge.net Fink]. The package name is [http://www.gnu.org/software/gettext gettext].

==== [[wxWidgets|wxMac]] ====

[[wxWidgets|wxMac]] is the port of the [[wxWidgets]] library for [http://macos.apple.com Mac OSX]. This library is used to make [[aMule]] 'multi-platform'.

# Get the source from: http://prdownloads.sourceforge.net/wxwindows/wxMac-2.6.3.tar.gz
# Extract the archive (just double-click it)

Or get the current [[wx-cvs|CVS snapshot]]. Warning: the [[wxMac]] [[wx-cvs|CVS]] is frequently in a bad condition (e.g., currently you need to switch the vswprintf implementation that wx uses, see [http://forum.amule.org/thread.php?postid=58058#post58058 here] for more details).

bash: cd ~/Desktop
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login
Note: password is 'anoncvs'
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac

==== [http://www.amule.org aMule itself] ====

# Get latest daily [[aMule CVS|CVS source snapshot]]: [http://www.amule.org/files/download.php?file=5 aMule CVS]
# Extract the archive (just double-click it)

=== Compile the sources ===

Put the ''amule'' folder and the ''wxMac'' folder in the same place, e.g. on the desktop (if using another location, ensure that there are no spaces in the path as this can lead to file not found errors with [[wxMac]]).

'''Important:''' If you use [http://developer.apple.com/tools/xcode Xcode] 2.0 then the [http://gcc.gnu.org gcc] 4.0 that comes with it is somewhat broken and can't compile aMule. There are two solutions: upgrade to [http://developer.apple.com/tools/xcode Xcode] 2.1 by [[#Xcode|downloading]] it from [http://www.apple.com Apple] for free, or switch your system to use [http://gcc.gnu.org gcc] 3.3. If your prefer to switch to [http://gcc.gnu.org gcc] 3.3, first check the version of your current default [http://gcc.gnu.org gcc] with ''gcc --version'' and then switch to version 3.3 if required:

bash: gcc --version
bash: sudo gcc_select 3.3

==== Compile [[wxMac]] ====

This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source.

The following assumes that you have placed the above packages on your Desktop. 
''cd'' into the ''wxMac'' folder, ''configure'' and ''make'':

bash: cd ~/Desktop/wxMac-2.6.1/build
bash: ../configure --disable-shared --enable-unicode
bash: make

'''NOTE:''' This took approx. 30 minutes on a G4 at 1 GHz.

==== Compile [[aMule]] ====

Now ''cd'' into the ''amule'' folder, ''configure'' and ''make'':

'''NOTE:''' You can copy'n'paste the 3 lines for ''./configure'' in one go.

bash: cd ~/Desktop/aMule
bash: ./configure --disable-systray --disable-gtk \
--with-wx-config=../wxMac-2.6.1/build/wx-config \
--disable-debug --enable-optimize '''''OPTIONAL'''''

bash: make
bash: strip src/amule '''''OPTIONAL'''''
bash: mv src/amule aMule.app/Contents/MacOS/

The two lines marked as '''''OPTIONAL''''' are optional, that is, the last two options to ''./configure'' and the ''strip'' command. They result in a dramatically reduced file size (approx. 3 MB instead of 50 MB) but disable all possibilities to submit a helpful stacktrace if [[aMule]] crashes or a sample if it hangs to the [[aMule devs|aMule developers]].

=== Problems and solutions ===

*If [http://fink.sourceforge.net Fink] reports something like: ''After unpacking 11.2GB will be freed'', don't be afraid. [http://fink.sourceforge.net Fink] has evolved into a different way of managing packet's size and some old ("old": at least some months old) packages' sizes aren't handled correctly on the output. If this is your case, devide the number by 1024. So, what the above example really means is: ''After unpacking 11.2MB will be freed''.

*If you get an error like this: ''You cannot open the application "amule" because it may be damaged or incomplete'', right click on ''amule'', then click on ''Show Packages Contents'', go to "Contents">"MacOS"> and double click on ''amule''. Next time you start from ''aMule.app'' it will run fine. If you still get the same error, move ''aMule.app'' to the desktop and run it from there.

HowTo compile on Mac

2006-11-28T01:07:03Z

Lionel77: =Binary releases= Updated link to stable release

How to get and install [[aMule]] on [http://www.apple.com/macosx/ Apple Mac OS X].

# You can simply download the finished application ('binary release') or
# You compile it from a [[aMule CVS|CVS source snapshot]].

''The preceding version of this page covering [[aMule]] 2.0.0rc8 and earlier is archived [[HowTo_compile_on_Mac_v200rc8|here]].''

== Binary releases ==

If you don't want to bother with installing and compiling all those tools and sources, then get one of the pre-compiled [[aMule]] applications. The official release is considered 'stable', but every now and then applications are built from the current source to allow more people to test new features or the like.

# Latest official binary release: [http://www.amule.org/files/files.php?cat=30 aMule-2.1.3-Mac]
# Periodically compiled binary from cvs: [http://forum.amule.org/thread.php?threadid=5051 amule forum]

Now, to install the downloaded binary, just drag the aMule application to a folder of your choice (e.g., ''/Applications'').

To start aMule, double-click the application icon.

'''Note:''' You might want to take a look at the [[Mac specific usage]] article.

== Compiling from source ==

Compiling from source allows most current bug reports, because you can compile and test the [[aMule CVS|CVS snapshot]] of the very day.

To compile [[aMule]] from source you need some development tools, the [[wxWidgets]] library and the [http://dl.amule.org aMule source].

=== Get the sources and development tools ===

==== [http://developer.apple.com/tools/xcode Xcode] ====

[http://developer.apple.com/tools/xcode Xcode] is [http://www.apple.com Apple]'s development environment. We need it for the [http://gcc.gnu.org GCC] compiler. You may have [http://developer.apple.com/tools/xcode Xcode] on CD/DVD, e.g. it is on the [http://www.apple.com/macosx/ OS X] 10.4 DVD.

Otherwise, you can download it from [http://www.apple.com Apple], but you must sign up for a free-of-charge developer account first.

# Get XCode from http://developer.apple.com/tools/download
# "Member Site"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"

==== [http://fink.sourceforge.net Fink] ====

'''Optional:''' [http://fink.sourceforge.net Fink] and [http://www.gnu.org/software/gettext gettext] are not strictly required to compile [[aMule]], but without them [[aMule]] will only appear in english.

[http://fink.sourceforge.net Fink] is an open source installer for lots of open source tools ported to [http://macos.apple.com Mac OSX]. We need it to install the open source tool [http://www.gnu.org/software/gettext gettext].

# Get [http://fink.sourceforge.net Fink] from http://fink.sourceforge.net/download
# Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink].

==== [http://www.gnu.org/software/gettext gettext] ====

'''Optional:''' [http://www.gnu.org/software/gettext gettext] and [http://fink.sourceforge.net Fink] are not strictly required to compile [[aMule]], but without them [[aMule]] will only appear in english.

[http://www.gnu.org/software/gettext gettext] is an open source library for text internationalization. This library is used to make [[aMule]] multi-lingual.
# Get and install the [http://www.gnu.org/software/gettext gettext] library with [http://fink.sourceforge.net Fink]. The package name is [http://www.gnu.org/software/gettext gettext].

==== [[wxWidgets|wxMac]] ====

[[wxWidgets|wxMac]] is the port of the [[wxWidgets]] library for [http://macos.apple.com Mac OSX]. This library is used to make [[aMule]] 'multi-platform'.

# Get the source from: http://prdownloads.sourceforge.net/wxwindows/wxMac-2.6.1.tar.gz
# Extract the archive (just double-click it)

Or get the current [[wx-cvs|CVS snapshot]]. Warning: the [[wxMac]] [[wx-cvs|CVS]] is frequently in a bad condition.

bash: cd ~/Desktop
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login
Note: password is 'anoncvs'
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac

==== [http://www.amule.org aMule itself] ====

# Get latest daily [[aMule CVS|CVS source snapshot]]: [http://www.amule.org/files/download.php?file=5 aMule CVS]
# Extract the archive (just double-click it)

=== Compile the sources ===

Put the ''amule'' folder and the ''wxMac'' folder in the same place, e.g. on the desktop (if using another location, ensure that there are no spaces in the path as this can lead to file not found errors with [[wxMac]]).

'''Important:''' If you use [http://developer.apple.com/tools/xcode Xcode] 2.0 then the [http://gcc.gnu.org gcc] 4.0 that comes with it is somewhat broken and can't compile aMule. There are two solutions: upgrade to [http://developer.apple.com/tools/xcode Xcode] 2.1 by [[#Xcode|downloading]] it from [http://www.apple.com Apple] for free, or switch your system to use [http://gcc.gnu.org gcc] 3.3. If your prefer to switch to [http://gcc.gnu.org gcc] 3.3, first check the version of your current default [http://gcc.gnu.org gcc] with ''gcc --version'' and then switch to version 3.3 if required:

bash: gcc --version
bash: sudo gcc_select 3.3

==== Compile [[wxMac]] ====

This step is only needed once, even if you later download and compile a newer version of the [[aMule CVS]] source.

The following assumes that you have placed the above packages on your Desktop. 
''cd'' into the ''wxMac'' folder, ''configure'' and ''make'':

bash: cd ~/Desktop/wxMac-2.6.1/build
bash: ../configure --disable-shared --enable-unicode
bash: make

'''NOTE:''' This took approx. 30 minutes on a G4 at 1 GHz.

==== Compile [[aMule]] ====

Now ''cd'' into the ''amule'' folder, ''configure'' and ''make'':

'''NOTE:''' You can copy'n'paste the 3 lines for ''./configure'' in one go.

bash: cd ~/Desktop/aMule
bash: ./configure --disable-systray --disable-gtk \
--with-wx-config=../wxMac-2.6.1/build/wx-config \
--disable-debug --enable-optimize '''''OPTIONAL'''''

bash: make
bash: strip src/amule '''''OPTIONAL'''''
bash: mv src/amule aMule.app/Contents/MacOS/

The two lines marked as '''''OPTIONAL''''' are optional, that is, the last two options to ''./configure'' and the ''strip'' command. They result in a dramatically reduced file size (approx. 3 MB instead of 50 MB) but disable all possibilities to submit a helpful stacktrace if [[aMule]] crashes or a sample if it hangs to the [[aMule devs|aMule developers]].

=== Problems and solutions ===

*If [http://fink.sourceforge.net Fink] reports something like: ''After unpacking 11.2GB will be freed'', don't be afraid. [http://fink.sourceforge.net Fink] has evolved into a different way of managing packet's size and some old ("old": at least some months old) packages' sizes aren't handled correctly on the output. If this is your case, devide the number by 1024. So, what the above example really means is: ''After unpacking 11.2MB will be freed''.

*If you get an error like this: ''You cannot open the application "amule" because it may be damaged or incomplete'', right click on ''amule'', then click on ''Show Packages Contents'', go to "Contents">"MacOS"> and double click on ''amule''. Next time you start from ''aMule.app'' it will run fine. If you still get the same error, move ''aMule.app'' to the desktop and run it from there.

AMule files

2006-09-15T03:44:34Z

Lionel77: added note about amule folder on mac os x

<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 (On Mac OS X the "~/.aMule" folder corresponds to "~/Library/Application Support/aMule"):
*'''~/.eMule:''' [[aMule]]'s old personal configuration file (version prior to [[aMule]] 2.0.0). It was renamed to ''~/.aMule/amule.conf''.
*'''[[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.
*'''[[logfile_file|~/.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. It is no longer used since 2.1.0
*'''[[muleLock_file|~/.aMule/muleLock]]:''' This file contains currently running's user's aMule PID. It prevents uers from running two aMules simoultaneously. It replaces the old ''muleconn'' socket file.
*'''[[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.
*'''[[tmp.html_file|/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:''' The directory where [[aMule_Project_FAQ:About|aMule]] stored the completed downloads on [http://www.microsoft.com/windows Windows] in old versions (previous to [[aMule]] 2.1.0).
*'''~/Documents/aMule Downloads:''' By default, the directory where [[aMule_Project_FAQ:About|aMule]] stores the completed downloads on [[MacOS X]] and [http://www.microsoft.com/windows Windows] (since [[aMule]] 2.0.0).
*'''''<app_dir>''/Incoming:''' In [[MacOS X]] and [http://www.microsoft.com/windows Windows], if [[aMule]] cannot determine the user's ''Documents'' folder, it will store the downloaded files here.

Soon

2005-12-31T15:12:05Z

Lionel77: created

(1) before long, without undue time lapse 
(2) in a prompt manner, speedily 
(3) before the usual time (archaic) 
(4) the time until the next aMule release, i.e. something in between right now and never

Getting Started

2005-10-07T00:23:47Z

Lionel77: Made description of high/low ID icon less ambigous

<center>
'''English''' | [[Getting_Started-fr|Français]] | [[Getting_Started-nl|Nederlands]] | [[Getting_Started-es|Español]] | [[Getting_Started-de|Deutsch]] | [[Getting_Started-hu|Magyar]]
</center>

== What is [[aMule]] ==

[[aMule]] is a [[P2P|p2p]], or peer-to-peer, client for the [[FAQ_eD2k-Kademlia|eD2k]] network, commonly known as [[FAQ_eD2k-Kademlia|eDonkey network]] or eD2k network ([[eDonkey2000]]). This guide does not require you to be familiar with these networks (but it does help), however it does require that you have [[aMule]] installed on your computer.
If you haven't installed [[aMule]] yet, please refer to the proper installation guide for your system. Links to these guides can be found on the [[Main_Page|main page]].

--[[User:Xaignar|Xaignar]] 01:12, 10 Jul 2004 (CEST)

== Running [[aMule]] for the first time ==
First, launch [[aMule]]. This can be done by executing the command ''amule'' in a console window or by whatever method might be provided by your distro and/or windows manager in terms of icons, etc.

Once started, if you are using the [http://www.gnu.org/software/cvs CVS] build, [[aMule]] will display a notification telling you that you are running it for the first time. Read this to learn what you are getting yourself into ;)

=== Configuring [[aMule]] ===
Before you begin file sharing, you will need to properly configure [[aMule]]. This includes connection speeds and limits, directories to be used, proxies, port settings and other settings.
You can access [[aMule]] preferences by clicking on the ''Preferences'' icon at the top of the [[aMule]] window.

==== Connection Speed ====
You should know that the eDonkey clients enforce upload. This means that in order to download, you'll have to share files yourself (don't worry if you don't have anything to share). This is enforced in two ways:
* Your download speed depends on how fast you upload. If your upload speed is set to anything below 10kb/s then your maximum download speed will be 3 or 4 times your uploadspeed (read [[FAQ_eD2k-Kademlia#Are_there_any_limitations_on_the_ED2K_network?|this]] to know more about it), so if you limit your upload speed to 5kb/s, you'll only be able to download with 20kb/s.
* Partially downloaded files are shared as well. You automatically start sharing a file after you've received at least one [[FAQ_eD2k-Kademlia#What_is_a_chunk?|chunk]] (a [[FAQ_eD2k-Kademlia#What_is_a_chunk?|chunk]] is a 9.28Mb piece of a file).

Note: If you ever enter the [http://forum.amule.org aMule forum] or [[IRC|IRC channel]] to complain about this or demand that we change the ratio, I will hunt you down and eat your spleen. -- [[User:Xaignar|Xaignar]]

When you first open the Preferences dialog, the page shown will be "General", which contains some general settings, like the [[nickname]] other people will see when they download from or upload to you.
To proceed, click on the tab named "Connection":

http://www.amule.org/dev-up/Limits.png

The only settings relevant to this guide are the settings under "Bandwidth Limits" marked "Upload" and "Download". You don't need to enter a max download speed, but it is recommended that you set the upload speed to around 80% of your actual speed, since it can cause slower downloads otherwise.

Once you have entered the proper values, you can explore the rest of the settings. To save the changes, simply click the "OK" button.

=== Connecting to a Server ===

You should now be looking at the servers dialog:

http://www.amule.org/dev-up/ServerDlg.png

The empty list normally contains the servers you know about, but since this is the first time you're running [[aMule]], you don't have any. To remedy this situation, simply click in the text-field containing the text ''http://www.srv1000.com/azz/server.met'' and press enter.
A dialog will pop up and close again once the download has completed.

You should now have a full list of servers, if not search google for ''server.met'' and place the file in the folder ''.aMule'' on your home dir. The list should look like this:

http://www.amule.org/dev-up/ServerList.png

Next you need to connect to a [[server]]. Normally it's a good idea to select one with as many users as possible, but for now, lets just click the large "Connect" button near the top-left of the window. This will connect you to a random server. Please wait while [[aMule]] contacts servers and tries to establish an connection. Once this happens, proceed on to the next section.

=== [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|High and Low ID]] ===
Because [[P2P|p2p]] networks work by [[Client|clients]] directly connecting to each other, being behind a firewalls, or routers that do not/cannot pass traffic on specific ports, can really cause problems. If you don't know whenever or not you are behind a firewall, simply look at the globe icon in the bottom-right of the window. If its arrows are green, then you have [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|High ID]] and can proceed, but if they are yellow, then you need to take a look at the page on [[Firewall|Firewalls]] and/or [[AMule_problems#aMule_connects_to_server,_but_it_is_always_given_LowID._Why?_and,_can_I_do_something_about_it?|common problems]], since having a [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|Low ID]] greatly reduces [[P2P|p2p]] experiences.

== Basic Usage ==
This will cover some basic usage of [[aMule]].

=== Searching and Downloading ===
OK, this is what [[P2P|p2p]]'ing is about: Downloading files.
For the sake of this guide, I'll presume that you are really keen on downloading the latest [http://www.knoppix.org Knoppix] CD (who isn't?). To download this, first ensure that you are connected to a server and then click on the "Searches" button.

This will bring up the search dialog:

http://www.amule.org/dev-up/SearchDlg.png

Since we only care about CD images, we click on "Extended Options" and select the option "CD-Images" from the "Type" dropdown menu. Also select the "[[Search#Local_search|Local]] [[Search]]" setting, since we don't really need to search anything other than the currently connected [[server]]. Then we enter ''Knoppix'' in the top "Name" field and hit enter or the "Search" button. You should now have a listful of results:

http://www.amule.org/dev-up/SearchResults.png

Lets sort the list by [[FAQ_eD2k-Kademlia#What_is_a_source?|sources]], by clicking twice on the field marked "Sources", this makes it easier to find popular files. The second one looks interesting, so we double-click on it (or click on it and then on the "Download" button). This will queue the file for download.

Results can be displayed in a number of colors, which signify the following:
* Blue represents the number of sources, the more sources the darker the blue.
* Red represents files that you are currently downloading.
* Green is for files you have downloaded or shared before, in other words files you already have.

=== The Download Queue ===
Click on the "Transfers" button to bring forth a list of files you have queued for download:

http://www.amule.org/dev-up/DownloadQueue.png

If you're lucky, the progress bar will turn a nice dark shade of blue, which means that a lot of people have that file (read [[FAQ_aMule#What_do_those_colors_in_the_progress_bar_mean?|this]] to know more about it). Beware of files that have parts marked in red, since it means that no-one has that part of the file and you most likely wont be able to complete the download.

If you double-click on any of the files, you can see the [[FAQ_eD2k-Kademlia#What_is_a_source?|sources]] you have found for that file.

==== Of Rows and Columns ====
These are the columns of the Download Queue:

; ''Filename'' : The name of the file.
; ''Size'' : The size of the file. The eDonkey2000 network supports files up to 4GB in size (read [[FAQ_eD2k-Kademlia#Are_there_any_limitations_on_the_ED2K_network?|more]] about this).
; ''Transferred'' : Shows the amount downloaded.
; ''Completed'' : This column displays how much of the file you have actually completed. Please note that this can differ from the Transferred column because of corruptions or gains made by the compression *Mule [[Client|clients]] use (read [[FAQ_aMule#What_is_the_difference_between_Transfered_and_Completed_in_the_Transfers_window?|more]] about this difference).
; ''Progress'' : This bar displays the current progress of the file, the colours signifying the following (alternative [[FAQ_aMule#What_do_those_colors_in_the_progress_bar_mean?|resource]]):
* Blue: How many sources provide this part, the darker the colour, the more sources provide it.
* Red: There are no known [[FAQ_eD2k-Kademlia#What_is_a_source?|sources]] that provide this part.
* Black: You have already downloaded this part.
* Yellow: You are currently downloading this part.
: The green bar on top of the larger bar gives an indication of the actual progress.
; ''Sources'' : There are 3 fields in this column, though mostly only 2 are shown (alternative [[FAQ_aMule#What_do_all_those_numbers_in_the_sources_column_in_the_transfers_window_mean?|resource]]):
: <Asked [[FAQ_eD2k-Kademlia#What_is_a_source?|Sources]]>[/<All [[FAQ_eD2k-Kademlia#What_is_a_source?|Sources]]>] [+ <[[FAQ_aMule#What_is_A4AF?|A4AF]] [[FAQ_eD2k-Kademlia#What_is_a_source?|Sources]]> ] [(<Transferring [[FAQ_eD2k-Kademlia#What_is_a_source?|sources]]>)]
: 'Asked [[FAQ_eD2k-Kademlia#What_is_a_source?|Sources]]' are those that have been asked for the file.
: 'All [[FAQ_eD2k-Kademlia#What_is_a_source?|Sources]]' are all [[FAQ_eD2k-Kademlia#What_is_a_source?|sources]] of that file, asked and unasked.
: '[[FAQ_aMule#What_is_A4AF?|A4AF (Asked For Another File)]] [[FAQ_eD2k-Kademlia#What_is_a_source?|Sources]]' are [[FAQ_eD2k-Kademlia#What_is_a_source?|sources]] that provide that file, but have been asked for anther one.
: 'Transferring [[FAQ_eD2k-Kademlia#What_is_a_source?|sources]]' are [[FAQ_eD2k-Kademlia#What_is_a_source?|sources]] which are uploading that file to you at this very moment.
; ''Priority'' : The priority of the file. Files are set to auto-priority by default, which means that [[aMule]] will manage it by itself. Priorities affect how [[aMule]] allocates [[FAQ_eD2k-Kademlia#What_is_a_source?|sources]] that are known to provide multiple files and thus means that high-priority files get more [[FAQ_eD2k-Kademlia#What_is_a_source?|sources]]. Read [[FAQ_aMule#What_do_all_those_numbers_in_the_priority_column_in_the_extended_transfers_window_mean?|more]] about this.
; ''Status'' : The current status of the file. Waiting means that you are waiting for [[FAQ_eD2k-Kademlia#What_is_a_source?|sources]] to start uploading to you.
; ''Time Remaining'' : An guess at how fast the file will be completed. Only shows something when you are currently receiving the file.
; ''Last Seen Complete'' : This shows the last time you've seen the entire file provided by the [[FAQ_eD2k-Kademlia#What_is_a_source?|sources]] you've asked.
; ''Last Reception'' : This shows the last time you were downloading parts of this file.

=== The Upload Queue ===
The upload queue can be found just beneath the download queue, and shows who are downloading files from you (you might want to read [[FAQ_aMule#Why_are_there_two_transfer_rates_in_the_uploading_transfer_list?|this]]). In case you are wondering, no, you cannot stop uploads. If you click on the blue icon next to the "Uploads" label, you can see who are queued for downloading from you, rather than the people who are actually downloading from you right now.

=== Icons and What They Signify ===
These are the icons that can be found on the Transfers page.

* '''Source Status'''
** http://www.amule.org/dev-up/Source_1.png - [[Client]] is sending you either a file or a hashset.
** http://www.amule.org/dev-up/Source_2.png - You are either on this [[Client|clients]] queue or currently asking it for a file.
** http://www.amule.org/dev-up/Source_3.png - You are currently connecting to this [[Client|client]].
** http://www.amule.org/dev-up/Source_4.png - [[Client]] has been asked for another file, has no needed parts or is unable to connect because of a [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|Low ID]].
** http://www.amule.org/dev-up/Source_5.png - Status is unknown.

* '''eDonkey Clients'''
** http://www.amule.org/dev-up/Client_aMule.png - [[aMule]]
** http://www.amule.org/dev-up/Client_eDonkey.png - [[eDonkey2000]]
** http://www.amule.org/dev-up/Client_eMule.png - [[eMule]]
** http://www.amule.org/dev-up/Client_Friend.png - [[Client]] is a [[Friend]]
** http://www.amule.org/dev-up/Client_Lphant.png - [[lphant]]
** http://www.amule.org/dev-up/Client_MLDonkey.png - [[mlDonkey]]
** http://www.amule.org/dev-up/Client_Shareaza.png - [[Shareaza]]
** http://www.amule.org/dev-up/Client_Unknown.png - Unknown [[Client]]
** http://www.amule.org/dev-up/Client_xMule.png - [[xMule]]

* '''Modifiers'''
** http://www.amule.org/dev-up/Client_Mod_eMuleProt.png - [[Client]] supports the extended [[eMule]] protocols. Source-sharing and such.
** http://www.amule.org/dev-up/Client_Mod_GoodCredit.png - [[Client]] has a good [[FAQ_eD2k-Kademlia#What_is_all_this_talk_about_credits,_ratings_and_scoring_about?|credit-rating]].
** http://www.amule.org/dev-up/Client_Mod_NormCredit.png - [[Client]] has a normal [[FAQ_eD2k-Kademlia#What_is_all_this_talk_about_credits,_ratings_and_scoring_about?|credit-rating]].
** http://www.amule.org/dev-up/Client_Mod_SecId_Good.png - [[Client]] has been [[Secure_User_Identification|securely identified]].
** http://www.amule.org/dev-up/Client_Mod_SecId_Bad.png - [[Client]] has been for some reason been identified as a [[bad guy]].

* '''File [[comment]]s'''
** http://www.amule.org/dev-up/File_Comment.png - This file has either been rated or someone has added a [[comment]].
** http://www.amule.org/dev-up/File_Comment_Bad.png - This file has been rated as [[Fake]] by at least one person.

=== Where Are The Files? ===
Once [[aMule]] starts downloading a file, it will create a number of files to keep track of that specific download. These files can be found in the subdir ''.aMule/Temp'' in your homedir (''~/.aMule/Temp''), but should not be touched in most cases.

If you have incompleted downloads from [[eMule]], you can simply place the temp files in the ''~/.aMule/Temp'' directory if you wish for [[aMule]] to continue downloading them.

However, once a file has been completed, it will be moved away from ''~/.aMule/Temp'' and to ''~/.aMule/Incoming'', where all completed files are placed by default. You can change both of these paths in the preferences should you wish to do so.

Also, please note that the ''.aMule'' directory is a hidden directory, so you might have to enable showing of hidden files in your file-mananger, should you use one such.

=== [[Share|Sharing]] [[File]]s ===
First off, note the [[FAQ_ed2k|eDonkey2000 network]] is not meant to [[share]] small [[file]]s such as audio clips, but instead is optimized for distribution of larger [[file]]s. Also note that its your own responsibility to ensure that you do not violate any local laws regarding material shared.

You can share files in two ways in [[aMule]]:

The first method is to place the [[file]]s in the "Incoming" directory (''~/.aMule/Incoming'' on [http://www.unix.org Unix] like systems). After this has been done, you must either restart [[aMule]] or press the "Reload" button on the SharedFiles page.

http://www.amule.org/reload_button.png

The second method is to explicitly add [[shared directory|shared directories]] in which [[aMule]] will look for [[file]]s to [[share]]. This is done by clicking on the "Preferences" button and selecting the "Directories" page.

http://www.amule.org/images/screenshots/prefs7.png

From there, you can browse to the directory you wish to [[share]] via the directory-tree. Double-clicking on the folder icon will [[share]] the given directory and right-clicking on the folder icon will [[share]] the directory recursively.

== Conclusion ==
Hopefully this brief introduction has given you an idea of how [[aMule]] works. If you feel that something is missing from this guide, please let us know or add it yourself.

Getting Started-de

2005-10-07T00:21:38Z

Lionel77: High/Low-ID Icon praezisiert

<center>
[[Getting_Started|English]] | [[Getting_Started-fr|Français]] | [[Getting_Started-nl|Nederlands]] | [[Getting_Started-es|Español]] | '''Deutsch''' | [[Getting_Started-hu|Magyar]]
</center>

== Was ist [[aMule]] ==

[[aMule]] ist ein [[P2P-de|P2P]], oder auch Peer-to-Peer-Client für das [[FAQ_eD2k-Kademlia-de|eD2k]] Netzwerk, besser bekannt als [[FAQ_eD2k-Kademlia-de|eDonkey Netzwerk]] oder eD2k Netzwerk ([[eDonkey2000]]). Diese Anleitung setzt nicht voraus, dass du vertraut bist mit diesen Netzwerken (obwohl es hilft), jedoch muss [[aMule]] auf deinem Rechner bereits installiert sein.
Wenn du [[aMule]] noch nicht installiert hast, lies die entsprechende Anleitung für dein Betriebssystem. Links zu diesen Anleitungen findest du auf der [[Main_Page|Hauptseite]].

--[[User:Xaignar|Xaignar]] 01:12, 10 Jul 2004 (CEST)

== Ausführen von [[aMule]] zum ersten Mal ==
Zuerst starte [[aMule]]. Dies macht man durch Eingabe des Befehls ''amule'' in einem Konsolenfenster oder welche Methode auch immer von deiner Distribution und/oder Windows-Manager zur Verfügung gestellt wird, also im Sinne von Icons, usw.

Einmal gestartet wird, sofern du den [http://www.gnu.org/software/cvs CVS-build] benutzt, [[aMule]] dir eine Nachricht anzeigen, dass du das Programm zum ersten Mal ausführst. Lies die Nachricht, damit du weisst, auf was du dich eingelassen hast ;)

=== [[aMule]] konfigurieren ===
Du musst zuerst [[aMule]] ordentlich konfigurieren, bevor du Daten tauschen kannst. Unter anderem deine Übertragungsrate, welche Verzeichnisse benutzt werden sollen, Proxies, Portnummern und andere Einstellungen.
Du kannst die [[aMule]] Einstellungen erreichen durch einen Klick auf den Knopf ''Preferences'' im oberen Bereich des [[aMule]] Fensters.

==== Verbindungsgeschwindigkeit ====
Du solltest wissen, dass eDonkey-Clients auch <nowiki>"upload"</nowiki> erfordern. Das bedeutet, dass du selbst auch Dateien hochladen musst, wenn du etwas runterladen willst (mach dir keine Gedanken, wenn du (noch) nichts zum anbieten hast). Dies wird auf zweierlei Art umgesetzt:
* Wie schnell du runterladen kannst, hängt davon ab, wie schnell du hochlädst. Wenn du deine <nowiki>"upload"</nowiki> Geschwindigkeit unterhalb der 10kb/s begrenzt, dann wird deine maximale <nowiki>"download"</nowiki> Geschwindigkeit auch nur 3 oder 4 mal höher liegen (lies [[FAQ_eD2k-Kademlia-de#Gibt_es_Grenzen_im_ED2k-Netzwerk?|dies]] um mehr darüber zu erfahren). Wenn du zum Beispiel deinen <nowiki>"upload"</nowiki> auf 5kb/s begrenzt, kannst du auch nur mit 20kb/s runterladen.
* Teilweise runtergeladene Dateien werden auch hochgeladen. Du bietest automatisch eine Datei zum Hochladen an, sobald du auch nur einen (kompletten) [[FAQ_eD2k-Kademlia-de#Was_ist_ein_Block?|Block]] von dieser Datei runtergeladen hast (ein [[FAQ_eD2k-Kademlia-de#Was_ist_ein_Block?|Block]] ist ein 9.28Mb grosses Stück einer Datei).

Anmerkung: Wenn du jemals das [http://forum.amule.org aMule Forum] oder [[IRC|IRC Channel]] betrittst, um dich darüber zu beschweren oder gar forderst, das wir das up/down-Verhältnis ändern, werde ich dich aufspüren und deine Milz verschlingen. -- [[User:Xaignar|Xaignar]]

Wenn du den "Einstellungen"-Dialog öffnest, wird die "General"-Seite angezeigt, welche einige allgemeine Einstellungen beinhaltet, wie den [[nickname]], den andere Leute sehen werden, wenn sie von dir runterladen oder zu dir hochladen.
Um fortzufahren, klicke auf den Reiter namens "Verbindung":

http://www.amule.org/dev-up/Limits.png

Die einzigen relevanten Einstellungen für diese Anleitung sind unter "Bandwidth Limits" markiert als "Upload" and "Download". Du brauchst keine maximale Download-Geschwindigkeit angeben, aber es wird empfohlen, die Upload-Geschwindigkeit auf ca. 80% der verfügbaren Bandbreite einzustellen, da ansonsten der Download sich verzögert und ausgebremst wird.

Nachdem du die Werte eingegeben hast, kannst du den Rest der Einstellungen erkunden. Um die Änderungen zu speichern, einfach auf "OK" klicken.

=== Verbinden zu einem [[Server-de|Server]] ===

Du solltest nun die [[Server-de|Server]] Einstellungen sehen:

http://www.amule.org/dev-up/ServerDlg.png

Das leere Feld enthält normalerweise alle benannten [[Server-de|Server]], aber da [[aMule]] erstmals läuft, sind dem Programm noch keine bekannt. Dies wird behoben, indem man einfach in das Feld mit dem Text ''http://www.srv1000.com/azz/server.met'' klickt und die Enter-Taste drückt.
Das Runterladen der [[Server-de|Server]]-Daten wird durch ein Dialogfeld dargestellt.

Du solltest nun über eine Liste von [[Server-de|Servern]] verfügen, falls nicht, suche bei [http://www.google.com google] nach ''server.met'' und kopiere die Datei in dein ''.aMule'' Verzeichnis. Die Liste sollte ungefähr so aussehen:

http://www.amule.org/dev-up/ServerList.png

Als nächstes musst du eine Verbindung zu einem dieser [[Server-de|Server]] aufbauen. Normalerweise ist es eine gute Idee einen Server mit möglichst vielen Usern auszuwählen, aber im Augenblick reicht ein einfacher Klick auf den "Connect" Knopf oben links im Fenster. Die Verbindung wird dann zu einem zufällig ausgewählten Server aufgebaut. [[aMule]] kontaktiert verschiedene Server und versucht eine Verbindung zu ihnen herzustellen. Sofern du mit irgendeinem Server verbunden bist, geht es mit dem nächsten Abschnitt weiter.

=== [[FAQ_eD2k-Kademlia-de#Was_sind_niedrige_und_hohe_IDs?|Hohe und niedrige ID]] ===
Weil [[P2P-de|P2P]] Netze auf [[Client-de|Clients]] beruhen, die sich direkt miteinander verbinden, kann es zu Problemen kommen, wenn man sich hinter einer Firewall befindet oder hinter einem Router, der auf bestimmten Ports den Verkehr nicht weiterleitet. Wenn du nicht weisst, ob du dich hinter einer Firewall befindest, schau einfach auf das Weltkugel-Icon unten rechts im Fenster. Sind die Pfeile grün, hast du eine [[FAQ_eD2k-Kademlia-de#Was_sind_niedrige_und_hohe_IDs?|hohe ID]] und kannst in der Anleitung fortfahren, sind sie jedoch gelb, solltest du mal einen Blick auf die Seite über [[Firewall|Firewalls]] respektive über [[AMule_problems#aMule_connects_to_server,_but_it_is_always_given_LowID._Why?_and,_can_I_do_something_about_it?|häufige Probleme]] werfen, da eine [[FAQ_eD2k-Kademlia-de#Was_sind_niedrige_und_hohe_IDs?|niedrige ID]] die Möglichkeiten von [[P2P-de|P2P]] stark einschränkt.

== Benutzung ==
Dies wird den allgemeinen Umgang mit [[aMule]] abdecken.

=== Suchen und Runterladen ===
OK, um folgendes geht es beim [[P2P-de|P2P]]: Dateien runterladen.
Aus rechtlichen Gründen und zum Wohle dieser Anleitung gehe ich mal davon aus, dass ihr wirklich scharf darauf seid, die neueste [http://www.knoppix.org Knoppix] CD zu ziehen (wer nicht?). Verbinde dich mit einem Server und klicke auf den "Suchen"-Knopf.

Dies öffnet den Suchen-Dialog:

http://www.amule.org/dev-up/SearchDlg.png

Da du lediglich CD-Images suchst, klickst du auf "Erweiterte Parameter" und wählst die Option "CD-Images" aus der "Datei Typ" Liste. Desweiteren wählst du "[[Search#Local_search|Local]] [[Search]]", da du in diesem Fall nur den augenblicklich verbundenen [[Server-de|Server]] durchsuchen willst. Dann gibst du ''Knoppix'' in das obere "Name" Feld und drückst Enter oder den "Suchen" Knopf. Nun solltest du ein Liste mit Suchergebnissen sehen:

http://www.amule.org/dev-up/SearchResults.png

Um die Liste nach der Anzahl der [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|Quellen]] zu sortieren, klicke zweimal auf das Feld "Sources", dies vereinfacht die Suche nach weit verbreitete Dateien. Der zweite Eintrag sieht vielversprechend aus, also doppelklicken wir darauf (oder mit einem Klick auswählen und dann auf den "Download"-Knopf). Die Datei wird in die Liste zum Runterladen aufgenommen.

Die Ergebnisse erscheinen in verschiedenen Farben und bedeuten:
* Blau entspricht der Anzahl der Quellen, je mehr Quellen desto dunkler das Blau.
* Rot für Dateien, die du gerade runterlädst.
* Grün für Dateien, die du bereits hast (oder hattest).

=== Der Download Queue ===
Klick auf den "Transfer"-Knopf für eine Übersicht der Dateien, die du zum runterladen ausgewählt hast:

http://www.amule.org/dev-up/DownloadQueue.png

Wenn du Glück hast, wird der Fortschrittsbalken eine dunkle blaue Farbe annehmen. Dies bedeutet, dass viele Leute die Datei zur Verfügung stellen (siehe [[FAQ_aMule#What_do_those_colors_in_the_progress_bar_mean?|hier]], um mehr darüber zu erfahren). Vorsicht bei Dateien mit roten Abschnitten - diese warnen vor nicht verfügbaren Teilen der Datei.

Durch einen Doppelklick auf eine der Dateien kannst du dir die [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|Quellen]] anzeigen lassen, die für diese Datei gefunden wurden.

==== Von Zeilen und Spalten ====
Dies sind die Spalten im Download-Fenster :

; ''Filename'' : Der Name der Datei.
; ''Size'' : Die Grösse der Datei. Das eDonkey2000 Netzwerk unterstützt Dateien mit bis zu 4GB Grösse (lies [[FAQ_eD2k-Kademlia-de#Gibt_es_Grenzen_im_ED2k-Netzwerk?|mehr]] darüber).
; ''Transferred'' : Zeigt die Anzahl der bereits transferierten Daten.
; ''Completed'' : Zeigt an, wieviel von der Datei schon fertiggestellt wurde. Please note that this can differ from the Transferred column because of corruptions or gains made by the compression *Mule [[Client-de|clients]] use (read [[FAQ_aMule#What_is_the_difference_between_Transfered_and_Completed_in_the_Transfers_window?|more]] about this difference).
; ''Progress'' : This bar displays the current progress of the file, the colours signifying the following (alternative [[FAQ_aMule#What_do_those_colors_in_the_progress_bar_mean?|resource]]):
* Blau: Die Menge der Quellen für diesen Teil, je dunkler die Farbe, desto mehr Quellen stellen diesen bereit.
* Rot: Es gibt keine bekannten [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|Quellen]], die diesen Teil zur Verfügung stellen.
* Schwarz: Du hast diesen Teil bereits runtergeladen.
* Gelb: Du lädst diesen Teil gerade runter.
: Der grüne Balken oberhalb des grösseren Balkens zeigt den Fortschritt an.
; ''Quellen'' : Diese Spalte enthält drei Felder, von denen aber meistens nur 2 tatsächlich angezeigt werden. (alternative [[FAQ_aMule#What_do_all_those_numbers_in_the_sources_column_in_the_transfers_window_mean?|resource]]):
: <Asked [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|Sources]]>[/<All [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|Sources]]>] [+ <[[FAQ_aMule#What_is_A4AF?|A4AF]] [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|Sources]]> ] [(<Transferring [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|sources]]>)]
: 'Asked [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|Sources]]' are those that have been asked for the file.
: 'All [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|Sources]]' are all [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|sources]] of that file, asked and unasked.
: '[[FAQ_aMule#What_is_A4AF?|A4AF (Asked For Another File)]] [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|Sources]]' are [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|sources]] that provide that file, but have been asked for anther one.
: 'Transferring [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|sources]]' are [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|sources]] which are uploading that file to you at this very moment.
; ''Priority'' : The priority of the file. Files are set to auto-priority by default, which means that [[aMule]] will manage it by itself. Priorities affect how [[aMule]] allocates [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|sources]] that are known to provide multiple files and thus means that high-priority files get more [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|sources]]. Read [[FAQ_aMule#What_do_all_those_numbers_in_the_priority_column_in_the_extended_transfers_window_mean?|more]] about this.
; ''Status'' : The current status of the file. Waiting means that you are waiting for [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|sources]] to start uploading to you.
; ''Time Remaining'' : An guess at how fast the file will be completed. Only shows something when you are currently receiving the file.
; ''Last Seen Complete'' : This shows the last time you've seen the entire file provided by the [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|sources]] you've asked.
; ''Last Reception'' : This shows the last time you were downloading parts of this file.

=== Der Upload Queue ===
Die Anzeige der Uploads findest Du direkt unter der Anzeige der Downloads und hier kannst Du sehen, welche Dateien gerade hochgeladen werden (genaueres gibt es [[FAQ_aMule-de#Warum_werden_in_der_Uploadliste_zwei_Geschwindigkeiten_angegeben?|hier]]). Uploads können nicht beendet oder verhindert werden (falls du das gerade überlegst). Ein Klick auf das blaue Icon neben dem "Uploads" Label fördert die Upload Warteschlange zu Tage.

=== Icons und ihre Bedeutung ===
Dies sind die Icons der "Transfer"-Seite.

* '''Status der Quelle'''
** http://www.amule.org/dev-up/Source_1.png - [[Client-de|Client]] schickt dir entweder eine Datei oder ein hashset.
** http://www.amule.org/dev-up/Source_2.png - Du bist entweder in der Warteschlange dieses [[Client-de|Clients]] oder fragst gerade eine Datei an.
** http://www.amule.org/dev-up/Source_3.png - Du vesuchst gerade dich mit diesem [[Client-de|Client]] zu verbinden.
** http://www.amule.org/dev-up/Source_4.png - [[Client-de|Client]] wurde schon um eine andere Datei gebeten, hat keine benötigten Teile oder kann keine Verbindung herstellen wegen einer [[FAQ_eD2k-Kademlia-de#Was_sind_niedrige_und_hohe_IDs?|niedrigen ID]].
** http://www.amule.org/dev-up/Source_5.png - Status unbekannt.

* '''eDonkey Clients'''
** http://www.amule.org/dev-up/Client_aMule.png - [[aMule]]
** http://www.amule.org/dev-up/Client_eDonkey.png - [[eDonkey2000]]
** http://www.amule.org/dev-up/Client_eMule.png - [[EMule-de|eMule]]
** http://www.amule.org/dev-up/Client_Friend.png - [[Client-de|Client]] ist ein [[Friend|Freund]]
** http://www.amule.org/dev-up/Client_Lphant.png - [[lphant]]
** http://www.amule.org/dev-up/Client_MLDonkey.png - [[mlDonkey]]
** http://www.amule.org/dev-up/Client_Shareaza.png - [[Shareaza]]
** http://www.amule.org/dev-up/Client_Unknown.png - Unbekannter [[Client-de|Client]]
** http://www.amule.org/dev-up/Client_xMule.png - [[xMule]]

* '''Modifikatoren'''
** http://www.amule.org/dev-up/Client_Mod_eMuleProt.png - [[Client-de|Client]] unterstützt das extended [[EMule-de|eMule]] Protokoll. Source-sharing und sowas.
** http://www.amule.org/dev-up/Client_Mod_GoodCredit.png - [[Client-de|Client]] hat einen hohen [[FAQ_eD2k-Kademlia-de#Was_hat_es_mit_diesem_ganzen_Krempel_(Credits,_Bewertungen,_Ratings,_Warteschlangen)_auf_sich?|Modifikator]].
** http://www.amule.org/dev-up/Client_Mod_NormCredit.png - [[Client-de|Client]] hat einen normalen [[FAQ_eD2k-Kademlia-de#Was_hat_es_mit_diesem_ganzen_Krempel_(Credits,_Bewertungen,_Ratings,_Warteschlangen)_auf_sich?|Modifikator]].
** http://www.amule.org/dev-up/Client_Mod_SecId_Good.png - [[Client-de|Client]] wurde [[Secure_User_Identification|securely identified]].
** http://www.amule.org/dev-up/Client_Mod_SecId_Bad.png - [[Client-de|Client]] wurde aus irgendeinem Grund als [[bad guy]] identifiziert.

* '''File [[comment]]s'''
** http://www.amule.org/dev-up/File_Comment.png - Diese Datei wurde Bewertet oder mit einem ([[comment|Kommentar]]) versehen.
** http://www.amule.org/dev-up/File_Comment_Bad.png - Diese Datei wurde von mindestens einer Person als [[Fake]] eingestuft.

=== Wo sind die Dateien? ===
Nach dem Start des Runterladens einer Datei erzeugt [[aMule]] temporäre Dateien im Unterverzeichnis ''.aMule/Temp'' deines Home-Verzeichnisses (''~/.aMule/Temp''). Dieser Pfad braucht in den allermeisten Fällen nicht verändert werden.

Wenn du noch unvollständige Downloads von [[EMule-de|eMule]] hast, kannst du einfach deren temporäre Dateien in das ''~/.aMule/Temp'' Verzeichnis kopieren und den Download der noch fehlenden Teile fortsetzen.

Wenn eine Datei vollständig runtergeladen wurde, wird sie von ''~/.aMule/Temp'' nach ''~/.aMule/Incoming'' verschoben, dort landen sämtliche vollständige Dateien. Du kannst die Verzeichnisse in den Einstellungen auch ändern, wenn du möchtest.

Bedenke bitte, dass das ''.aMule'' Verzeichnis ein verstecktes Verzeichnis ist. Du musst dir also in deinem Dateibrowser "versteckte Dateien anzeigen" lassen, um diese zu sehen.

== Zum Abschluss ==
Hoffentlich hat dir diese kurze Einführung eine Idee davon vermittelt wie [[aMule]] funktioniert. Wenn du das Gefühl hast, dass etwas fehlt, lass es uns bitte wissen oder füge es selbst hinzu.

Shared directory

2005-08-27T09:16:29Z

Lionel77: spelling & sentence structures

When a directory is [[share]]d through [[aMule]], all of its content ([[file]]s in it) is made available to other [[eD2k]]/[[Kademlia]] [[client]]s.

To [[share]] a directory in [[aMule]], go to '''Preferences''' -> '''Directories''' and check the box next to the directory you want to [[share]].

By default, [[share|sharing]] a directory does not result in its subdirectories (the directories inside that directory) being [[share]]d. If you want to [[share]] a directory recursively (that is, the [[file]]s in a directory and all of its subdirectories), '''dobule-click''' the folder icon by the directory name.

'''ATTENTION:''' Be '''very careful''' which directories you [[share]] or you could wind up accidentally making your sensitive data (passwords, address book, private stuff, etc.) available to the rest of the world.

Talk:Priority

2005-08-27T08:56:25Z

Lionel77: more specific infos

I think the verbal descriptions for the different priorities are a little clumsy and a bit confusing (e.g. right now "high" seems to upload more than "very high").
How about making "release" a bit more specific (e.g., "Files with release priority are always uploaded whenever clients asks for them, i.e. as long as these files are requested no other files are uploaded.")
Then we could drop the labels of very high to very low and instead include the specific queue position modifier (e.g., 1.0x) that each is associated with. I think a number of people would find that much more informative.

lio

FAQ eD2k-Kademlia

2005-03-04T05:40:03Z

Lionel77: another note about port forwarding and some re-formulations

<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 first in the queue, read [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|What_is_all_that_credits,_rate_and_score_stuff_about?]] and, when the chunk has been completly sent, you will be taken back to it's 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, but it will be soon.

== 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. 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, have in mind, Overnet's development is closed untill 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 in 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 it is novel 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 concatenate 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 identifying number, an ID, which will be unique and will distinguish him from any other client on the server. If this ID is below 16777216 (16 million) then you have a LowID. If it's over, then you have a HighID. To be given a high or low ID will only depend on having TCP port 4662 (or the one set up in Preferences) opened. If you understood "What is ED2K" you might understand that chances are that clients on LowID may be unable to connect to many other clients (all those on LowID) so will have a lower transfer rate. That's why having port 4662 TCP (or the one set in Preferences) is so important. Also, some big servers refuse clients on LowID to connect to them since LowID clients have data transfered through the server and so, those big servers could be overcharged. 
For HighID clients, 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. Also have in mind that this ID has identification purposes, nothing else, so apart from having and ID over or under the 16777216 number, it does not matter if the ID is bigger or smaller. This means a client with an ID like 50000000 isn't better than a client with an ID like 49999999. 
There's still an exception. Sometimes badly configured or very busy servers give LowID to some clients although the 4662 TCP port is opened. This are rare exceptions, but it might happen sometime. 
Check [http://www.amule.org/testport.php here] if you have your ports opened.

== Which ports do I have to configure in a firewall or router to run aMule? ==
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, two more ports should be enabled as well. First, the UDP port 4672 (which can also be changed to any other number in the Preferences) and secondly, the secondary UDP port which can't be set in the Preferences. This UDP port is your TCP port + 3 (e.g.: TCP=4662 then UDP=4665).

== What does each port do? ==
Well, since most ports can be configured to be set to any other number, the defaults will be listed:

; 4662 TCP: Client to client transfers.
; 4672 UDP: Extended eMule protocol, Queue Rating, File Reask Ping
; 4661 TCP: Opened on server. Allows connection to server.
; 4665 UDP: Opened on server. Allows asking for sources. It is always server TCP port + 4.
; 4711 TCP: WebServer listening port.
; 4712 TCP: External Connection port. Used to communicate aMule with other applications such as aMule WebServer or aMuleCMD.

Although officially the secondary UDP port is server TCP port + 4, some (most?) implementations use it as client TCP + 3. Any way, this port is mostly not used (aMule doesn't use it, eMule doesn't have it).

== 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.

== In search window, what filter stands for which filetype? ==
Have 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 which's filename is "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. Have 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 that credits, rate and score stuff 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 is slow

2005-03-04T05:28:22Z

Lionel77: added note about port forwarding

<center>'''English''' | [[AMule_is_slow-it|Italiano]] | [[AMule_is_slow-nl|Nederlands]]</center>

== [[aMule]] is slow ==

So [[aMule]] is slow? This can be due to:

*[[#Your fault|Your fault]]
*[[#The network's fault|The network's fault]]

== Your fault ==

This is a list of issues which can be the reason for slow download speeds:

*A low value in "Preferences"->"Download limit".
*A low value in "Preferences"->"Upload limit". Upload limits under 4 kbps limit your download speed to 3 times your upload speed. Upload limits under 10 kbps limit your download speed to 4 times your upload speed. Upload limits above or equal to 10 kbps give you unlimited download speed, limited only by the "Download limit" preference value (read [[FAQ_eD2k-Kademlia#Are_there_any_limitations_on_the_ED2K_network?|this link]] to know more about it).
*A too high value in "Preferences"->"Upload limit". Your line may get congested! (depends on your line-speed)
*A too low value in "Preferences"->"Max Connections". There are not enough connections available.
*A too high value in "Preferences"->"Max Connections". Too many connections are congesting your line.
*A too low value in "Core Tweaks"->"Max New Connections". It takes very long to aquire sources.
*A too high value in "Core Tweaks"->"Max New Connections". Your line gets congested, many new connections produce much overhead-bandwidth.
*Having [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|Low ID]].
*Some [http://en.wikipedia.org/wiki/ISP ISP]s block or limit connections to the standard [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] [[FAQ_eD2k-Kademlia#Which_ports_do_I_have_to_configure_in_a_firewall_or_router_to_run_aMule?|ports]]. Try changing the port in "Preferences"->"Connections" to some other values.
*Your firewall may be blocking some ports/protocols used by [[aMule]] and/or you did not forward these ports in your router (again, see [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|Low ID]]).

== The network's fault ==

We're sorry to tell you that sometimes, the low speeds aren't due to a bad [[aMule]] code or a bad configuration, but due to other facts. This is a list:

*The [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] is a slow network. In some other [[P2P]] networks you can easily download faster. The [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] network is one of the fastest [[P2P]] networks existing, but its main goal is availability. While on other popular networks you'll be able to download very fast, you'll quickly find out that in the [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] network there are millions of files you'll be unable to find in any other network.
*[[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|Credits]]. If you are running [[aMule]] for the first time or if you deleted some files in the ''~/.aMule'' directory, you'll have no [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|credits]]. [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|Credits]] grant fast downloads. If you don't know what they are, read [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|this]].
*The file's availability. Rare files, old files, extremly new files... this kind of files have very few [[FAQ_eD2k-Kademlia#What_is_a_source?|source]]s, so it takes quite some time for [[aMule]] to connect to some other [[client]] sharing it.

AMule devs

2005-02-23T07:20:11Z

Lionel77: =Testers=

== The [[aMule]] Project ==
The aMule project is led by a bunch in people who toil away in front of their computers, so that you can enjoy a stable and featureful P2P client.
This page is about us.

== The Team ==
These are the people who work on aMule:

=== Developers ===
* [[User:deltaHF|deltaHF]]: Webmaster, Admin and from-time-to-time-coder ;)
* [[User:falso|falso]]: [[CAS]] coder.
* [[User:GonoszTopi|GonoszTopi]]: [[External Connections]] developer.
* [[User:Hetfield|Hetfield]]: Ex-Admin, pretty-no-free-time coder.
* [[User:Jacobo221|Jacobo221]]: Our man-for-all
* [[User:ken|Ken]]: The big [http://www.apple.com/macosx Mac] guy.
* [[User:Kry|Kry]]: Main developer and Admin
* [[User:lfroen|lfroen]]: Core/GUI dedicated guy.
* [[User:Phoenix|Phoenix]]: Code janitor junior.
* [[User:thepolish|thepolish]]: [[aMule]] [[FAQ_utils|tools]] coder.
* [[User:Unleashed|Unleashed]]: Sometimes around ;)
* [[User:Xaignar|Xaignar]]: Code janitor extraordinaire!

=== Testers ===
* [[User:Citroklar|Citroklar]]: Tester, slave-work-coder (sometimes)
* ender`: Tester
* [[User:lionel77|lionel77]]: Tester and provider of binaries for Mac OS
* nachbarnebenan: Tester, and life-complicator by using large&strange nicks ;-P
* nich: Tester
* skolnick: Solaris tester
* [[User:Stefanero|Stefanero]]: Supporter, Tester, and [[aMuleWeb]] Guru
* thedude0001: Tester

=== Special Gold Guest Members ===
* [[User:Bigbob|Bigbob]]: Also known as ''[[User:Bigbob|Creteil]]''; [[aMule]] project creator.
* [[User:Madcat|Madcat]]: The one and only kitty dev.
* [[User:Tiku|Tiku]]: And God said: Let there be [[lMule]]!

=== Others ===
* [[User:Bootstrap|bootstrap]]: [[IRC]] bot (''bootbox'') and [[aMule CVS]] hoster
* [[User:uberpenguin|uberpenguin]]: uberpenguin is extremely difficult to classify... Let us call him the 'official bystander to *mule'.
* niet: [http://www.dns.net/dnsrd DNS] stuff, [[XAS]], tester.

=== Former Team-members ===
These are people who have worked on [[aMule]] in the past.
Please note that this list doesn't include the people from before [[aMule]] forked off from [[xMule]], nor does it include people from the [[LMule]] days. If you wish to learn more about those, please visit the websites of those projects.

==== Developers ====
* shakraw: [[aMuleWeb]] mantainer.

==== Testers ====

== Helping ==
We can always use another helping hand, and if you are interested, then I'd encourage you to contact us and see if you can help us. Currently, what we need the most is developers and testers, though also translators and others.

=== Becoming a Developer ===
To become a [[aMule]] Developer (tm), you'll need at the very least a working knowledge of C++, since that is the language in which [[aMule]] is written. You'll also need to learn about the GUI toolkit used by [[aMule]]: [[wxWidgets]]. Of course, you will have to follow our [[Coding Style]] rules or we will beat you to death with a brick in a sock.

However, we do not require that you are an expert, only that you are willing to help and willing to learn.

If you are interested, then simply drop by on [[IRC]] and let us know. Currently we use a private [http://www.gnu.org/software/cvs CVS] server, but after you've submitted a patch or two you can easily get r/w access to it. You can also post patches on the [http://www.amule-project.net/amule/board.php?boardid=47 Development] forum, however, virtually all discussions regarding development happens on [[IRC]], so learning about that is a good idea as well.

We can use your skills if you are using one of the platforms where we aim at being usable on: [http://www.unix.org Unix], *[http://www.bsd.org BSD], [http://www.sun.com/solaris Solaris], [http://www.apple.com Macs] and [http://www.microsoft.com/windows Windows].
And if your operating system of choice isn't on that list, then maybe you can help add it.

=== Becoming a Tester ===
We need people who are willing to create complete bug-reports, as the standard is pretty low regarding user reports. This is rather simple, but takes patience. Please contact us on [[IRC]] for more information and read [[Backtraces|this guide on creating useful backtraces]].

=== Becoming a Translator ===
[[aMule]] already includes translations for a number of languages, however, we'll always welcome more, and even if your language of choice has been done already, then perhaps you can help improve it. Please see the [http://forum.amule.org/board.php?boardid=40 Translations forum] for more information on current translations, or contact us on [[IRC]]. Also, take a deep look into the [[Translations|aMule translation howto]].

Of course, you can also work on [[Translating_Wiki|translating this wiki]]'s articles. There's still a lot of work to do!

Talk:Wie alles begann

2005-02-04T06:51:50Z

Lionel77: realized that the page is actually not a bogus page

looks like somebody created a bogus test page. i wasn't able to figure out how to delete this page (probably don't have the privs), so maybe one of you guys can take care of this.

cheers,
lionel

EDIT:
nevermind, i just realized that the german faq actually links to this page, so better not remove it. i'm heading for bed now before i break something else... ;o)

Talk:Wie alles begann

2005-02-04T06:44:42Z

Lionel77:

looks like somebody created a bogus test page. i wasn't able to figure out how to delete this page (probably don't have the privs), so maybe one of you guys can take care of this.

cheers,
lionel

FAQ aMule

2004-11-21T08:52:14Z

Lionel77: removed "os x client not ready" // spelling and some grammar fixes

<center><h4>F.A.Q on [[aMule_Project_FAQ:About|aMule]]</h4> 
<h2>by [[User:Jacobo221|Jacobo221]]</h2> 
[[FAQ_aMule|Version in English]] | [[FAQ_aMule-es|Versión en Español]] | [[FAQ_aMule-it|Versione in Italiano]] | [[FAQ_aMule-fr|Version en Français]]</center>

== What is [[aMule_Project_FAQ:About|aMule]]? ==
'''''[[aMule]] is a multi-platform client for the [[FAQ_eD2k-Kademlia|ED2K file sharing network]] based on the windows client [[eMule]].''''' 
aMule started in August 2003 as a fork of [[xMule]], which is a fork of [[lMule]].

It currently supports Linux, FreeBSD, OpenBSD, Windows, MacOS X and X-Box on both 32 bits and 64 bits computers. It should be noted that the Windows port isn't ready for general usage yet.

[[aMule]] is intended to be as user-friendly and feature-plenty as [[eMule]] and to remain faithful to the look 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 to [[aMule]] soon after their inclusion in [[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 which is even more user-friendly than [[aMule_Project_FAQ:About|aMule]] itself (if possible), so please join #amule on irc.freenode.net or visit the [http://www.amule.org/amule forums], if you have any suggestions, questions, problems, bugs, patches or what else you might think of.

If you are interested in joining the development team, please contact us either through the [http://www.amule.org/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 him) by right clicking on it's name 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). On that same dialog window, if that client is on your upload queue, you'll be able to view it'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 on current session found. 
Blue: Chunks in blue are chunks with at least one available source. 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 been already 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. 
Have in mind that not all clients support telling other clients which 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]] guide.

== What do those numbers in brackets in the search 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). 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 amount of available sources (the amount of sources found you can download from). 
YY stands for the amount of found sources (the total amount of sources found) 
ZZ stands for the number of "Asked for another file" sources 
WW stands for the amount of sources from who 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 in which you are uploading to that client and YY will stand for the speed in 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 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 clients (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 this 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. Here is a list and the meaning of each of them (have in mind that you might not have all of them on your hard disk): 
~/.eMule: aMule's personal configuration (that is, things such as you nickname, your Temp and Incoming directories, your upload and download limits, and such...). 
~/.aMule/addresses.dat: Contains a list of serverlist URLs to check (if enabled in Preferences) for new servers on startup. 
~/.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 below) but with extended information (extended information includes nickname, session and total downloaded and uploaded bytes, [[aMule_Project_FAQ:About|aMule]] version, [[aMule_Project_FAQ:About|aMule]] uptime and number of shared files). 
~/.aMule/aMule.tmpl: This is the template file which [[amuleweb|aMule WebServer]] uses to create the web page. 
~/.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/casrc: This file will only exist if [[CAS|CAS]] has been run sometime with the -o switch. It contains the settings for the [[CAS|CAS]] image creation. 
~/.aMule/clients.met: Contains the public hashes of other known clients along with the credits it owes each of them. 
~/.aMule/cryptkey.dat: It contains the unique 384 bit private RSA key of your client. 
~/.aMule/emfriends.met: Contains your friends list configuration 
~/.aMule/ipfilter.dat: This file contains the IP ranges and access levels restrictions which will be passed to ipfilter. 
~/.aMule/Incoming: By default, the directory where [[aMule_Project_FAQ:About|aMule]] stores the completed downloads. 
~/.aMule/known.met: This file stores the hashes and some details of your shared files like size, path, statics, etc... 
~/.aMule/known2.met: This file stores the verified [[AICH]] hashes of your shared files. 
~/.aMule/lastversion: This is only for [[aMule_Project_FAQ:About|aMule]] to know if it's the first time you're starting [[aMule_Project_FAQ:About|aMule]], if you had [[aMule_Project_FAQ:About|aMule]] installed before and which version you had installed previously. 
~/.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. 
~/.aMule/onlinesig: 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 (if it's online, which server it's connected to, upload and download rate, and clients in queue). 
~/.aMule/preferences.dat: Contains the public key of your client, also known as user hash. 
~/.aMule/server.met: This is a list of all known servers and you're preferences on them (priority, name, ip, port and such). 
~/.aMule/shareddir.dat: Stores the paths to all shared directories. 
~/.aMule/Temp: By default, the directory where [[aMule_Project_FAQ:About|aMule]] stores the not completed downloads (temporary files). 
~/.aMule/webserver: This directory contains the necessary files for aMule WebServer to display a nice Web page. 
Other files on ~/.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 three or four files): 
*.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: 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 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.seeds: This file only exists if you have enabled to store the IPs 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.

== 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 the half downloaded files is easy: just place 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 and onlinesig.dat are for [[FAQ_aMule#What_are_all_those_files_aMule_creates_the_first_time_it_is_run?|above]]. So, this is the meaning of their contents (have in mind that if [[aMule_Project_FAQ:About|aMule]] crashes, the contents of both files will be the last written status): 
onlinesig.dat 
It is composed of two lines separated by a line feed character (with no carriage return character). The first one, when [[aMule_Project_FAQ:About|aMule]] is offline, will contain a 0 (zero) and nothing else, but when [[aMule_Project_FAQ:About|aMule]] is online, it'll contain a 1 (number one) followed by | (the pipe character) then the name of there server it's currently connected to followed by the pipe character, then the IP of the server it's currently connected to followed by the pipe character and finally the port it is connected to on that server. 
The second line contains, in this order, the downloading rate, the uploading rate and the number of users on queue, with a pipe character ('|') between each of them. 
The second line does '''not''' end in a newline character ('\n'). 
When [[aMule_Project_FAQ:About|aMule]] is cleanly closed the second line contains the same structure but filled with zeros, while the first line will only contain a single zero. 
amulesig.dat 
aMule's [[signature|signature]] file is much more powerful than [[eMule]]'s and has as much lines as fields. It's structure is: 
The first line will contain a 0 (zero) if [[aMule_Project_FAQ:About|aMule]] is disconnected or has been cleanly closed, a 2 if it's connecting (only since aMule 2.0.0-rc4), or a 1 (number 1) if it's online. 
The second third and forth line contain the name, IP and port of the server aMule is connected to (in this order) or a zero if it's offline. Since aMule 2.0.0-rc4 it will also contain a 0 when aMule's status is connecting or cleanly closed. 
The fifth line will contain an capital H or a capital L depending if [[aMule_Project_FAQ:About|aMule]] is connected on high or low ID. If [[aMule_Project_FAQ:About|aMule]] is disconnected. Again, since aMule 2.0.0-rc4 it will also contain a 0 when aMule's status is connecting or cleanly closed, this line will contain a zero. 
The sixth and seventh lines contain the speed in which [[aMule_Project_FAQ:About|aMule]] is downloading and uploading respectively. Since aMule 2.0.0-rc4 both lines contain "0.0" when [[aMule_Project_FAQ:About|aMule]] is cleanly closed. 
The eighth and ninth lines contain the number of clients on the upload queue and the amount of shared files respectively. Since aMule 2.0.0-rc4 both lines are set to zero too when aMule is cleanly closed. 
The tenth line contains the nickname of the user. 
The eleventh and twelve lines contain the total amount of bytes downloaded and uploaded respectively. 
The thirteenth line contains the [[aMule_Project_FAQ:About|aMule]] version. 
The fourteenth and fifteenth line contains the amount of bytes downloaded and uploaded in the current session respectively. Since aMule 2.0.0-rc4, both will be 0 if aMule is connecting or was cleanly closed 
The sixteenth (and last) line contains the amount of time [[aMule_Project_FAQ:About|aMule]] has been running. It will be followed by a space and "secs" "mins" or "hours" depending on the value (or the same time abbreviations in your configure language). Since aMule 2.0.0-rc4, if aMule is connecting or was cleanly closed this field will contain 00 followed by the abbreviation "secs" (or that same abbreviation in your configured language). 
The last line must be followed by a new line character ('\n').

== 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 bellow "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 temporal and downloading directories respectively, you should change the paths in Preferences to ~/.aMule/Temp and ~/.aMule/Incoming respectively. 
[[xMule]] is officially dead since May 2004 (official [[xMule]]'s death announcement on [[xMule]] forums by its main developer at, the now non-existent web page, [http://www.xmule.org http://www.xmule.org]), but for historical reasons, [[aMule_Project_FAQ:About|aMule]] will remain the ~/.xMule directory with its name and just copy from it its configuration files. This 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, share well known and popular files (don't share too much (not more than approximately 200 files) or you'll get banned from some servers for giving too much traffic) and try to share small-sized popular files since some [[FAQ_eD2k-Kademlia|ED2K]] clients give extra credits for providing them a whole small-sized files. 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]] statics some people post on the IRC channels? ==
You can either copy and paste [[CAS]]'s (C [[aMule_Project_FAQ:About|aMule]] Statics) 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]] Statics).

== 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 loosing 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'' and ''preferences.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!

== What is all this [[rabbit]] story about? ==
Ah, yeah, this all began... ehm... well... I mean... follow the white [[rabbit]] ;-)

AMule makes everything slow

2004-11-21T08:11:43Z

Lionel77: just typos

== [[aMule]] makes everything slow ==

So when you are running [[aMule]], suddenly every other application using the net runs slow. Then you should read this document carefully.

== How to fix this problem ==

Well, the reason is that you have badly configured [[aMule]]. Check the following:

*"Preferences"->"Connection"->"Bandwidth Limits"->"Upload": If this value is very high, so high that it takes more than 75% of your upload bandwidth, you will get very bad downloading speeds, since most packets on the internet are [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] packets, which require both up and down packets. In other words, to download something, you need to upload some information.
*"Preferences"->"Connection"->"Max Sources per File"->"Hard Limit": This specifies the maximum amount of sources you allow for each file being downloaded. Each source is a connection, so many sources require many connections and so, a bit of bandwidth. Have in mind that if you are downloading ''F'' files (where ''F'' is a number) and you set Hard Limit's value to ''X'' (where ''X'' is a number), you'll be allowing ''X''*''F'' connections.
*"Preferences"->"Connection"->"Connection Limits"->"Max Connections": This specifies the maximum amount of connections you allow [[aMule]] to handle at the same time. Once again, each connection takes a bit of your bandwidth so, adjust it to whatever suits you.

== What are the values that suit my needs ==

This will depend on your connection type ([http://en.wikipedia.org/wiki/Integrated_Services_Digital_Network ISDN], Modem, [http://en.wikipedia.org/wiki/DSL DSL], Cable, T1, etc...), your [http://en.wikipedia.org/wiki/ISP ISP], the bandwidth your other apps need and the amount of files you are downloading (also, in the [http://en.wikipedia.org/wiki/CPU CPU] if it is slow).

As you see, it is very personal and it's impossible to tell what suits your needs and what not. The only way to get it right is to go testing. The procedure is:

*Set it to some value.
**If it's ok: then tweak those values a little to see if you can get some more connections (improving the speed) without loosing effectiveness on the other apps.
**If the other apps suffer from lack of bandwidth: lower the values so that [[aMule]] takes less bandwidth.
*Repeat the above steps until you find the values which suit better your needs.