AMule Project FAQ - User contributions [en]

Changelog 2.0.0-rc8

2004-12-23T18:32:50Z

80.224.220.41: damn, kry... :P

== Version 2.0.0rc8 (The "last rc" version) ==
''2004-12-21''

'''Baz:'''
* Fix for server stats for users/files not being updated correctly.
* Fix for ERROR and WARNING server messages not being shown.
* Fixed server / transfers window splitters not being loaded/saved correctly.
* Fixed categories on search dialog not being refreshed on category name change.

'''deltaHF:'''
* Show comments for shared files

'''Hetfield:'''
* Some fix in new Tray system and desktopMode bypass

'''Jacobo221:'''
* Added option to select the max and min size-type in advanced searches.
* When "Extended Parameters" in Search tab is not selected, defaults are used.
* Now "Auto-update serverlist at startup" checks if there's a serverlist to avoid annoying messages at startup.
* "Clear completed downloads" is now disabled while no completed downloads are listed.
* Context menu for download items only enables relevant information now.
* Context menu little optimization (removed an unuseful loop) and Open File fix.
* Added bitmap button wich pops-up the last status log line (useful when it doesn't fit the window).
* Merged Preview and Open File and enabled Open File.
* New Port column in Servers tab (splitting IP column).
* Moved "Always filter bad IPs" from Server to Security in Preferences.
* Changed "Preference" in servers tab as suggested by Sir and "IP" to "Address" since that's more accurate (could be DNS).
* Optimizations in the RLE code.
* Based on kry's patch, also darken paused files' progress bar.
* Translations updates.
* Fixed: Servers priority now working. (reported by Sir)
* Fixed: Now all unset Server Priorities are set to normal. (reported by plaenky)
* Fixed: Sorting Servers by priority works now.
* Fixed: Setting "A4AF to others" works now.
* Fixed: Server names sorting now differences between names and IPs.
* Fixed: Last byte is now drawn in bar progress.
* Fixed: Stop button now working after second global search and another hidden bug in global searches' progress bar. (reported by ecforum)

'''ken_aMule:'''
* Fixed ipfilter on big endian archs.
* Fixed wxWidget's bugs that were creating serious memleaks on Mac

'''Kry:'''
* When a socket connection error like WOULD_BLOCK happens, aMule retries the connection to avoid just-once errors
* Stopped files are now darker than non-sources ones.
* AICH e-links working now, with masterhash and with hashset
* Proper handling of removing -fomit-frame-pointer flag that worls on all platforms.
* Initial support for wx-compliant systray. Will be ready for 2.0.0 final release.
* aMule no longer crashes on opening a non-existing folder. CDirIterator is safe now.
* Fixed crash on app close - never call a pure virtual function from a destructor.
* Moved the init/close code of aMule to where they belong: destructor/constructor.
* Much more debug info available to debug packets (packet dump and others)
* Major network improvements:
** Improved the socket processing on CPU usage and performance.
** Coded the functions handling the network string/bytes conversion of ips and hostnames and the generic hostname solving thread, non dependant from host's socket implementation. Less CPU and more reliable on both cases.
* Crash fixed on wrong arguments for wxString::Format
* New option on right click on downloading or search files for showing eserver's stats for that filehash. Needs browser correctly configured on preferences.
* Implemented messages filtering, from know clients/bogus clients/by words.
* Fixed hashing files changing display status.
* Fixed crash where transferwnd and clientlistctrl could be accessed before created.
* Listen socket on accepting connection no longer uses a blocking socket (CPU improvement).
* Not linking anymore to gtk libs if not needed.
* "GTK: Not Detected" is now either "Not Detected" or "Not Used" to avoid confusion.
* Fix for crashing on 'OK' button on preferences.
* Fix for preferences window being unreachable if aMule is minimized while showing it.
* Fix for crash on HTTP dialog if StopAnimation() was not called on destructor.
* Fixed crash when shutdown and preferences window open.
* Implemented OS_Info tag. Broke it 400 times, and fixed it 401 times, so working.
* Implemented statistics tree for OS_Info tag.
* Fixed several memory corruption issued caused by icons with wrong size.
* Fixed several memory corruption bugs on amule init/close.
* When aMule crashes, it not longer fails saving:
** Preferences (Saved on 'OK')
** Categories (Saved on changes)
** Total upload / download bytes (saved while running).
* Fixed crash on OP_MULTIPACKETANSWER
* Sent wxInt and wxUInt classes usage down the drain for the standard int / uint
* Implemented "Share hidden files" checkbox.
* Immplemented the CT_EMULECOMPAT_OPTIONS new tag. Right now only OS info support capabilities.
* Implemented new short tags style for server and client interchange of info. Fixes not being able to browse eMule >=0.42x shared files.
* Fixed aMule daemon compilation to use wxBase headers and libraries. This fixes amuled not compiling on wxBase only-boxes, thus making it kinnda pointless.
* Fixed AMD64 and GCC4.0 compilation/run, closes debian bug #285110
* Fixed some performance issues on Log text controls.
* Fixed long browsers requests on WebSocket. Buffer is now enlarged accordingly.
* Fixed timeout on webserver socket being... 10 minutes!!!
* Fixed several 100% cpu errors on WebSocket.
* Fixed our source exchange implementation that was... uh... wrong.
* Fixed stats tree on webserver.
* Misc. work on ECv2 implementation of messages.
* aMule can send now RGB encoded images via ECv2
* Webserber can read ECv2 Image tags via the new CDynPngImage class.
* eMule+ is now recognised under compatible client tag 0x05
* Unicode fixes on webserver.
* Got rid of almost all wxString::GetData()
* Major CPU improvements on WebServer.cpp
* otherfunctions.* is now clean from aMule specific stuff. Can be used anywhere.
* otherfunctions now have a namespace (surprinsigly named 'otherfunctions')
* Changed wxFileStreamInput -> wxFile (less class overhead).
* Several speed fixes on Stats code.
* Fixed possible crash on search thread creation + verbose on error.
* Fixed aMule crashing when local search is not returning and we click stop or start another search.
* Fixed severeral endianess bugs.
* General rewrite of UDP Socket
** Received packets when app is not ready are now discarded.
** Small fix preventing memleaks and some strange asserts
** Fixed a severe memleak if 2 UDP packets are send at the same time, before the first one finishes.
** Fixed the host solving fail not cleaning the data (another severe memleak)
** Fixed sending wrong data to wrong servers and thus not being replied.
** Fixed some server udp packets never reaching destination.
* Unicode fixes (char*/wxString issues)
* General cleaning, bugfixing and documenting.
* Added files:
**StringFunctions.(h/cpp)
**NetworkFunctions.(h/cpp)
:==================::MAC::===================
* Fixed server connection crashes related to accepting a connection from a being destroyed socket. Probably fixes also some random BSD/Linux crashes on conection.
* Got rid of all <wx/wx.h> includes, improved compilation speed greatly.
* Fixed stats color boxes
* Fixed servers saving, not anymore stored wrong internaly.
* Coded Mac packager script for releases with included libcurl and wxWidgets.
* Included Mac aMule.app bundle on sources.
* Fixed sharing /Volumes and other special folders.
* Fixed crash on server.met download

'''permats:'''
* FIXED: Preferences -> Security -> Permissions wasn't being correctly saved for directories.

'''phoenix:'''
* Lots of unicode fixes.
* Added readline and history support to amuleweb/amulecmd text clients.
* Added template loading capability to amuleweb with the new command line parameter -t.
* Changed m4/readline.m4 so that readline libs are only used when needed, i.e., no longer append readline libs to LIBS, use READLINE_LIBS instead.
* Fixed crash in aMule when amuleweb tried to get transfers tab and aMule had never connected to a server before.
* New backtrace output with demangled function names, file names and line numbers, when possible.
* Initial (not functional yet) SOCKS5 proxy support.
* Initial (not functional yet) SOCKS4 proxy support.
* Initial (not functional yet) HTTP proxy support.
* Updated some tests in configure.in.
* Fixed a problem with _() usage. Static string initialization must be done with wxTRANSLATE, and wxGetTranslation() must be explicitly called in code instead of _().
* Fixed a bug in WebServer.cpp:CWebServer::GetStatusBox(): return value was missing end tags.
* Changed back to macro the inline function version of unicode2char() when using UNICODE. Unfortunately, when the fucntion returns, the string object gets out of scope, so we stick to the macro version for now.

'''lfroen:'''
* Moving amuleweb to EC version 2.0
* Fixes on amuleweb socket code
* Added generated png images to amuleweb
* Added RLE encoder for gap and parts status to EC
* Fixes in amule daemon

'''Madcat:'''
* Added support for detecting HydraNode clients.

'''GonoszTopi:'''
* Initial work on EC protocol version 2.0.
* Fixed a crash on broken language files (.po)
* Some GUI cosmetics.
* Lots of i18n fixes.
* As a side effect, fixed the "Any" search in webserver.
* Fixed webserver connection with empty passwords. Smile
* Fixed webserver connection with guest account.
* Added "add <ed2k link>" command to amulecmd.
* Tracked down and killed a number of hidden bugs.
* Added commands to change/monitor bandwidth settings to amulecmd.
* Made wxTRANSLATE actually work.
* Fixed graphs in webserver. Also added the missing back.gif file.
* Fixed buffer overflow problem in ed2k link handler.
* Stats bug fixed.

'''wizeman:'''
* Helped finding the code snippet where WebSocket was failing on request.
* Fixed 'Safe Max connections' code. It's safer to use it now, and it works.
* Fixed bug where amule would start consuming 100% cpu when it received a corrupted EC packet.
* Fixed webserver, it wouldn't close connection when it received a POST request.
* Fixed webserver crash: added mutex to make variable wcThreads thread-safe.
* Fixed webserver <-> amule communication corruption when the webserver received simultaneous requests. The problem was that all webserver threads were using the same socket for sending/receiving EC packets to/from amule without synchronization.

'''Xaignar:'''
* Added the new casting macros to otherfunctions.
* Added a helper-function to CMuleListCtrl for use in the Sorter functions.
* Fixed the priority-column on Server List.
* Added the handling of friends to ECv2 implementation.
* Merged CUploadListCtrl and CQueueListCtrl on CClientListCtrl.
* Added the posibility to see a list of all existing clients.
* Fixed aMule dialog not always being unfrozen upon restoring it from tray.
* Some changes to the overhead calculation functions.
* Slight improvement of the GetScore function CPU usage.
* Replaced "theApp.glob_prefs->" with the new usage "thePrefs::"
* Fixed the MyTimer class behind GetTickCount returning random values on close.
* Fixed two crashes on ClientList.
* Fixed compilation for solaris on several places.
* Make sure that clients cant just crash us by sending a aich-request for an invalid hash.
* Fixed a couple of sub-menues.
* Removed the leech-mod checks, they were getted outdated anyway
* Fixed open sockets count.
* Avoid re-layouting the entire dlg when updating some labels.
* Small fix to CMuleNoteBook.
* Adding a missing event-handler en shared files tab.
* Changed the primary hashing thread to do both MD4 and AICH hashing for non-part files. This cut down hashing of ~2.8gb of data from ~12:40 minutes to ~7 minutes on tests.
* Adding checks against the user sharing the following dirs: Home-dir, .aMule, Temp-dir. Sharing home is allowed but results in a warning.
* Fixed the Upload-parts drawing.
* Fixed sorting by filename on the Uploading list.
* Fixed crash on server list auto-update. Removes the possibility of overrunning a array.
* Optimization of UpdatePartsInfo, which now no longer needs to traverse the parts-info arrays of each source for that file.
* Fixed the redraw problems where some things wouldn't be erased on list controls.
* Code cleaning, documenting and rewrite.

'''Special Thanks To:'''

* Translators:
:Ateo: (US english / en_US)
:biger [HUN]: (Hungarian / hu_HU)
:experience.chris: (German / de_DE)
:GhePeU: (Italian / it_IT)
:Gusar: (Slovenian / sl_SL)
:ilbuio: (Italian / it_IT)
:KamiKazeNH: (Brazilian / pt_BR)
:mad_soft: (Spanish / es_ES)
:nbfnw: (Chinese / zh_CH)
:Ogon: (Polish / pl_PL)
:piarres: (Basque / es_EU)
:pukyxd: (Catalan / es_CA)
:Supersnail (Dutch / nl_NL)
:Typhon: (Slovenian / sl_SL)

* Contributors:
:alehack, alus,
:boutros, fossybaer,
:Frankk, han,
:junaru, sebaX,
:skolnick, sLiCeR\,
:Vollstrecker, volpop,
:{xmb}

* Bug and feature reporters:
:Banerjee, chisky2003,
:Danny, ecforum,
:fctk, Gnucco,
:hades, jaguarwan,
:jolupa, juanii,
:kdka, kno,
:m2kio, MichaelLong,
:Pableron, pi-c,
:plaenky, realcruncher,
:Sir, Sniffer,
:sosonok, |Syrius|,
:xplode_me

* Everyone at:
:<nowiki>#amule</nowiki> irc.freenode.net
:wiki http://wiki.amule.org
:forums http://forum.amule.org
:bugtracker http://bugs.amule.org

* All aMule users!!!

'''Welcome our new aMule team members:'''
lionel77, ken_aMule, nachbarnebenan & one2one

Compilation Installation-fr

2004-12-20T02:08:33Z

80.224.220.41:

<center>
[[Compilation_Installation|English]] | '''Français'''
</center>

== Installation Manuelle ==

Pour installer aMule vous pouvez soit l'installer à partir de zéro, comme décrit dans '''Compiler à partir des sources''' soit utiliser les RPM comme décrit dans la section '''Installer en utilisant les RPM''', ce qui peut grandement accélérer les choses.

'''Remarque:''' Ce HowTo utilise [[wxWidgets]] 2.4.2 et [[libcrypto|Crypto++]] 5.1 en exemple, cependant [[aMule]] peut également être compilé en utilisant [[wxWidgets]] 2.5.x et les versions de [[libcrypto|Crypto++]] plus récentes que la 5.1. A partir de la 2.0.0-rc6, vous n'avez même plus besoin de Crypto++.

== Compiler à partir des sources ==

'''ATTENTION''' Soyez sur de n'avoir '''aucune''' copie de [[wxWidgets]] d'installée. Si vous avez déjà un [[wxWidgets]] d'installé, allez voir [[How to uninstall wxWidgets]] avant de démarrer une nouvelle installation. Si vous avez encore des problèmes après sa, alors [[Check_if_wx_is_installed_twice|check if wx is installed twice]], parce que c'est un problème courant de compilation et de runtime.

'''REMARQUE :''' dans [[wxWidgets]] >= 2.5.1, [[wxBase]] n'est pas distribué comme un tarball séparé. Donc si vous comptez compiler [[wxWidgets|wxGTK]] 2.5.x, sautez la seconde étape (compilation de [[wxBase]]).

==== Etape 1 : [[wxWidgets|wxGTK]] ====

*téléchargez [[wxWidgets|wxGTK]] ->
**[http://download.berlios.be/amule/wxGTK-2.4.2.tar.gz wxGTK-2.4.2.tar.gz]

*compilez [[wxWidgets|wxGTK]] ->
**''tar -zxvf wxGTK-2.4.2.tar.gz''
***''cd wxGTK-2.4.2''
***''./configure --prefix=/usr --disable-gtk2 --with-gtk && make''

*en tant que '''root''' :
**''make install''
**''ldconfig''

==== Etape 2 : [[wxBase]] ====

*téléchargez [[wxBase|wxBase]] ->
**[http://download.berlios.de/amule/wxBase-2.4.2.tar.gz wxBase-2.4.2.tar.gz]

*compilez [[wxBase]] ->
**''tar -zxvf wxBase-2.4.2.tar.gz''
**''cd wxBase-2.4.2''
**''./configure --prefix=/usr && make''
**''ln -sf /usr/bin/wxgtk-2.4-config /usr/bin/wx-config''
**''ln -sf /usr/bin/wxbase-2.4-config /usr/bin/wxbase-config''
**''ldconfig''

==== Etape 3 : [[libcrypto|Crypto++]] ====

'''Remarque :''' Nécessaire seulement pour les versions de 2.0.0-rc1 à 2.0.0-rc5 (inclue).

*téléchargez [[libcrypto]]++ ->
**[http://download.berlios.de/amule/crypto-5.2.1.tar.bz2 crypto-5.2.1.tar.bz2]

*compilez [[libcrypto]]++ ->
**''tar xvjf crypto-5.2.1.tar.bz2''
**''cd crypto-5.2.1''
**''make''
::Si vous rencontrez des problèmes en compilant avec de plus vieilles versions de [http://gcc.gnu.org gcc], cela peut être du à un retour à la ligne de [http://www.freedos.org DOS] perdu dans certains fichiers. Appellez
:::''file * | grep CRLF | while read file rest; do dos2unix ${file%:}; done''
::pour les convertir en retour à la ligne UNIX (syntaxe de [http://www.gnu.org/software/bash/bash.html bash]).

*en tant que '''root''':
:Sur les précédentes versions de [[libcrypto]]++, lancer ''make install'' devrais suffire. Depuis [[libcrypto]]++ 5.2 cela n'est plus possible. Donc faites ceci :
:*''cp libcryptopp.a /usr/lib/''
:*''mkdir /usr/include/cryptopp''
:*''cp *.h /usr/include/cryptopp/''
:*''ldconfig''

==== Etape 4 : [[aMule]] ====

*téléchargez la dernière version de [[aMule]] ->
**[https://developer.berlios.de/project/showfiles.php?group_id=1296 dernier aMule]
*compilez [[aMule]] ->
**''tar -zxvf aMule-X.X.X.tar.gz'' (remplacez X par le bon numéro de version...)
**''cd aMule-X.X.X''
**''./configure --disable-debug --enable-optimise && make''
*en tant que '''root''':
**''make install''
*lancez [[aMule]] comme simple utilisateur à partir de votre console en tapant -> ''amule''

== Installer avec les RPM ==

==== Etape 1 : [[wxWidgets|wxGTK]] ====

*téléchargez [[wxWidgets|wxGTK]] et [[wxWidgets|wxGTK]]-devel ->
**[http://download.berlios.de/amule/wxGTK-2.4.2-1.i386.rpm wxGTK-2.4.2-1.i386.rpm] [http://download.berlios.de/amule/wxGTK-devel-2.4.2-1.i386.rpm wxGTK-devel-2.4.2-1.i386.rpm]

* installez [[wxWidgets|wxGTK]] ->
**en tant que '''root''':
***''rpm -Uvh wxGTK-2.4.2-1.i386.rpm wxGTK-devel-2.4.2-1.i386.rpm''
***''ldconfig''

==== Etape 2 : [[wxBase]] ====
*téléchargez [[wxBase]] ->
**[http://download.berlios.de/amule/wxBase-2.4.2-1.i586.rpm wxBase-2.4.2-1.i586.rpm]

*installez [[wxBase]] ->
**en tant que '''root''':
***''rpm -Uvh wxBase-2.4.2-1.i586.rpm''
***''ln -sf /usr/bin/wxgtk-2.4-config /usr/bin/wx-config''
***''ln -sf /usr/bin/wxbase-2.4-config /usr/bin/wxbase-config''
***''ldconfig''

==== Etape 3 : [[libcrypto|Crypto++]] ====

'''Remarque :''' Nécessaire uniquement pour les versions de 2.0.0-rc1 à 2.0.0-rc5 (inclue).

*téléchargez [[libcrypto]]++ ->
**[http://www.redhat.com RedHat] & [http://www.suse.com SuSE]: [http://download.berlios.de/amule/libcryptopp-5.2.1-1.i586-RH-SuSE.rpm libcryptopp-5.2.1-1.i586-RH-SuSE.rpm] and [http://download.berlios.de/amule/libcryptopp-devel-5.2.1-1.i586-RH-SuSE.rpm libcryptopp-devel-5.2.1-1.i586-RH-SuSE.rpm]
**[http://fedora.redhat.com FC]: [http://download.berlios.de/amule/libcryptopp-5.2.1-1.i586-FC.rpm libcryptopp-5.2.1-1.i586-FC.rpm] et [http://download.berlios.de/amule/libcryptopp-devel-5.2.1-1.i586-FC.rpm libcryptopp-devel-5.2.1-1.i586-FC.rpm]
**[http://www.mandrake.com MDK]: [http://download.berlios.de/amule/libcryptopp5-5.1-2mdk.i586.rpm libcryptopp5-5.1-2mdk.i586.rpm] et [http://download.berlios.de/amule/libcryptopp5-devel-5.1-2mdk.i586.rpm libcryptopp5-devel-5.1-2mdk.i586.rpm]
*en tant que '''root''':
**''rpm -Uvh le-packet-téléchargé-au-dessus.rpm''

==== Etape 4 : [[aMule]] ====

*téléchargez la dernière version de [[aMule]] ->
**[https://developer.berlios.de/project/showfiles.php?group_id=1296 latest aMule]

* installez [[aMule]] ->
**en tant que '''root''':
***''rpm -Uvh aMule-X.X.X-1.iX86-X.rpm'' (Remplacez X par le bon numéro de version)

* lancez [[aMule]] comme simple utilisateur en tapant dans votre console -> ''amule''

FAQ aMule

2004-12-20T02:07:24Z

80.224.220.41:

<center>
<h4>F.A.Q on [[aMule_Project_FAQ:About|aMule]]</h4>

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

'''English''' | [[FAQ_aMule-es|Español]] | [[FAQ_aMule-it|Italiano]] | [[FAQ_aMule-pt_BR|Portuguese]] | [[FAQ_aMule-fr|Français]] | [[FAQ_aMule-de|Deutsche]]
</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.

Detailed information about each and a list of all of [[aMule]]'s files can be found [[aMule files|here]].

== Can I use [[eMule|eMule]]'s files and settings and vice-versa? ==
Most of them yes. The only ones you can't share between [[aMule_Project_FAQ:About|aMule]] and [[eMule]] are the program configuration (that is, preferences.ini in [[eMule]] and ''~/.eMule'' in [[aMule_Project_FAQ:About|aMule]]). All the [[FAQ_eD2k-Kademlia|ED2K network]] related files can be successfully shared between the two applications with no more effort than copying the files in ''~/.aMule'' to the [[eMule]]'s directory and vice-versa. But have in mind that some files in ''~/.aMule'' are [[aMule_Project_FAQ:About|aMule]] specific, such as ''amulesig.dat'' or ''aMule.tmpl'', so it's better to only move those files that are in both the [[aMule_Project_FAQ:About|aMule]] and the [[eMule]] directory.

Moving 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_file|''amulesig.dat'']] and [[onlinesig.dat_file|''onlinesig.dat'']] are for [[FAQ_aMule#What_are_all_those_files_aMule_creates_the_first_time_it_is_run?|above]].

So, this files contain the current [[signature]] (the current [[aMule]] status, if enabled, of course).

Detailed information about each of thee files can be found in the [[amulesig.dat_file|''amulesig.dat'' article]] and the [[onlinesig.dat_file|''onlinesig.dat'' article]].

== I just installed [[aMule_Project_FAQ:About|aMule]] for the first time. How do I set it up? ==
Setting up aMule properly is just a matter of tastes and depends on many factors. If you just wish a quick startup configuration, then continue reading. 
Open [[aMule_Project_FAQ:About|aMule]] and click on the Preferences button. Set a nickname and the language in which you wish to have [[aMule_Project_FAQ:About|aMule]]. Then switch to the Connection tab and input your Line Capacities. Then input the Bandwidth Limits according to the maximum amount of bandwidth you want [[aMule_Project_FAQ:About|aMule]] to use. Then switch to the Directories tab and set a directory for both the temporary files (where files will be stored until they are completely downloaded) and the completed files. Finally, select the directories which you want to share. It is not recommended to share too much files. Read 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]] ;-)

User:J-m

2004-12-20T02:06:08Z

80.224.220.41:

'''[[aMule]] user :)'''

Main [[aMule]] concerns:
*Translated [[aMule]]'s [[Compilation_Installation|compilation/installation from scratch howto]] to [[Compilation_Installation-fr|french]].

Rabbit

2004-12-18T17:28:51Z

80.224.220.41:

Follow the white rabbit ... cause things are amiss in wonderland. =(^.^)=

I assume the authors of the "rabbit" joke have got their inspiration from three sources:
* [http://www.clydelewis.com/dis/follow/follow.htm The movie]
* "Follow the White Rabbit Neo."
* [http://www.sabian.org/alicech1.htm The book]
* [http://lyrics.ivory.org/wrabbit.html The song]

First time the "rabbit" has emerged was in the [http://www.gnu.org/software/cvs CVS] [http://cvs.sourceforge.net/viewcvs.py/amule/amule-cvs/src/ChatSelector.cpp?r1=1.13&r2=1.14 commit by run (libcw)]

''line 326 libcw 1.14 #warning [[User:Bigbob|Creteil]]? I know you are here [[User:Bigbob|Creteil]]... follow the white rabbit.''

Then [[User:Madcat|MadCat]] added a nice [http://www.wps.com/projects/codes ASCII] art:

,-.,-.
\ \\ \
\ \\_\
/ \
__| a a|
/` `'. = y)=
/ `"`}
_| \ }
{ \ ), //
'-', /__\ ( (
jgs (______)\_)_)

after that....
:everything went down the rabbit's hole......... =:)

Rabbit

2004-12-18T17:20:48Z

80.224.220.41:

Follow the white rabbit ... cause things are amiss in wonderland. =(^.^)=

I assume the authors of the "rabbit" joke have got their inspiration from three sources:
* [http://www.clydelewis.com/dis/follow/follow.htm The movie]
* "Follow the White Rabbit Neo."
* [http://www.sabian.org/alicech1.htm The book]
* [http://lyrics.ivory.org/wrabbit.html The song]

First time the "rabbit" has emerged was in the [http://www.gnu.org/software/cvs CVS] [http://cvs.sourceforge.net/viewcvs.py/amule/amule-cvs/src/ChatSelector.cpp?r1=1.13&r2=1.14 commit by run (libcw)]

''line 326 libcw 1.14 #warning [[User:Bigbob|Creteil]]? I know you are here [[User:Bigbob|Creteil]]... follow the white rabbit.''

Then [[User:Madcat|MadCat]] added a nice ASCII art

,-.,-.
\ \\ \
\ \\_\
/ \
__| a a|
/` `'. = y)=
/ `"`}
_| \ }
{ \ ), //
'-', /__\ ( (
jgs (______)\_)_)

after that....
everything went down the rabbit's hole......... =:)

AMule files

2004-12-18T15:36:06Z

80.224.220.41:

Most [[aMule]]'s config files and data are the same as or copatible with [[eMule|eMule]]'s.

Have in mind that you might not have all of them on your hard disk, since they are generated when needed.

Here is a list and the usage of each of them:
*'''~/.eMule:''' aMule's personal configuration file (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.
*'''[[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 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]] has been run sometime with the -o switch. It contains the settings for the [[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 [http://www.rsasecurity.com/rsalabs/node.asp?id=2125 RSA] key of your client.
*'''~/.aMule/emfriends.met:''' Contains your friends list configuration.
*'''[[ED2KLinks_file|~/.aMule/ED2KLinks]]:'''
*'''~/.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.
*'''[[lastversion_file|~/.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.
*'''[[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, also known as user hash.
*'''~/.aMule/server.met:''' This is a list of all known servers and your preferences about them (priority, name, [[IP]], port and such).
*'''[[shareddir.dat_file|~/.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 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:''' 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 [[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.

TODO

2004-12-17T19:39:32Z

80.224.220.41:

*Change HTML tags for wiki tags when possible
* Links in large files like FAQs
*Translate [[Main Page|this wiki]]'s articles
*Split large articles into samller articles straight to topic
*Explain config files entries and their defaults
*Data files format
*Network packets and protocol design

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

Preferences.dat file

2004-12-17T19:37:33Z

80.224.220.41:

== File ==

'''Name:''' ''preferences.dat''

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

== Description ==

This file used to store [[eMule]]'s configuration in it's earlier versions. Nowadays, it only stores the userhash and the configuration file version.

== Data ==

The current configuration file version is 20 (in hex: ''0x14'').

== Format ==

The file format is as follows:

'''VersionUserhashLengthFlagsShowcmdMaxpositionxMaxpositionyMinpositionxMinpositionyNormalpositionleftNormalpositiontopNormalpositionrightNormalpositionbottom'''

As you can see, all the fields are stored without any separator character. This is done like this because all the fields have a specific size:
*''Version'': 1 byte
*''Userhash'': 2 bytes
*''Length'': 4 bytes
*''Flags'': 4 bytes
*''Showcmd'': 4 bytes
*''Maxpositionx'': 4 bytes
*''Maxpositiony'': 4 bytes
*''Minpositionx'': 4 bytes
*''Minpositiony'': 4 bytes
*''Normalpositionleft'': 4 bytes
*''Normalpositiontop'': 4 bytes
*''Normalpositionright'': 4 bytes
*''Normalpositionbottom'': 4 bytes

The relevant fields are the following:
*''Version'': Specifies the configuration file version (the format defined in this articles corresponds to version 20).
*''Userhash'': The userhash.
*''Length'': Length in bytes of the file not counting th Version and Userhash fields (should be 38 bytes).

Once this data is put together, it is stored in little-endian.

== Example ==

The following is a hex dump of an hypothetic ''preferences-dat'' file:

''a3143e6f12dd445b12a0c3c6f7ca5b2d00230000000000000000000000000000000000000000000000000000''

In the above example, the following data can be seen:

*Configuration file version: ''20'' (In hex: ''0x14'')
*Userhash: ''A36F3EDD125B44A012C6C3CAF72D5B23''
*Other fields: Set to zero (''0'')

== Extra ==

[[aMule]] ignores the ''main window position'', ''main window size'', ''length'', ''flags'' and ''showcmd'' fields in this file. That's the reason why this fields aren't explained in this article.

All this ignored fields are set to zero by [[aMule]]. Even if they were set to some other value, [[aMule]] will never read those values. Instead, it uses the preferences set in ''~/.eMule''

Preferences.dat file

2004-12-17T19:34:25Z

80.224.220.41:

== File ==

'''Name:''' ''preferences.dat''

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

== Description ==

This file used to store [[eMule]]'s configuration in it's earlier versions. Nowadays, it only stores the userhash and the configuration file version.

== Data ==

The current configuration file version is 20 (in hex: ''0x14'').

== Format ==

The file format is as follows:

'''VersionUserhashLengthFlagsShowcmdMaxpositionxMaxpositionyMinpositionxMinpositionyNormalpositionleftNormalpositiontopNormalpositionrightNormalpositionbottom'''

As you can see, all the fields are stored without any separator character. This is done like this because all the fields have a specific size:
*''Version'': 1 byte
*''Userhash'': 2 bytes
*''Length'': 4 bytes
*''Flags'': 4 bytes
*''Showcmd'': 4 bytes
*''Maxpositionx'': 4 bytes
*''Maxpositiony'': 4 bytes
*''Minpositionx'': 4 bytes
*''Minpositiony'': 4 bytes
*''Normalpositionleft'': 4 bytes
*''Normalpositiontop'': 4 bytes
*''Normalpositionright'': 4 bytes
*''Normalpositionbottom'': 4 bytes

The relevant fields are the following:
*''Version'': Specifies the configuration file version (the format defined in this articles corresponds to version 20).
*''Userhash'': The userhash.
*''Length'': Length in bytes of the file not counting th Version and Userhash fields (should be 38 bytes).

Once this data is put together, it is stored in little-endian.

== Example ==

The following is a hex dump of an hypothetic ''preferences-dat'' file:

''a3143e6f12dd445b12a0c3c6f7ca5b2d00230000000000000000000000000000000000000000000000000000''

In the above example, the following data can be seen:

*Configuration file version: ''20'' (In hex: ''0x14'')
*Userhash: ''A36F3EDD125B44A012C6C3CAF72D5B23''
*Other fields: ---

== Extra ==

[[aMule]] ignores the main window position, main window size, showcmd, flags and length fields in this file. That's the reason why this fields aren't specified in this article.

FAQ amps

2004-12-15T01:50:36Z

80.224.220.41:

The FAQ for [[AMPS]] is well covered in three [http://forum.amule.org forum] threads and the ''README'' file packaged with the [[AMPS]] distribution (which I will copy verbatim here below):

[http://forum.amule.org/thread.php?threadid=2313 AMPS announcements] - Announcements about AMPS as well as a link to the package download

[http://www.amule.org/amule/thread.php?sid=&postid=13729 AMPS signature images] - Some alternate base images for the [[signature]] image generated by [[AMPS]]. Some of these will probably be included in future [[AMPS]] revisions.

[http://www.amule.org/amule/thread.php?threadid=2085 i18n info] - Information about translations and where to post if you have questions/comments/revisions regarding them.

'''From the [[AMPS]] ''README'' file:'''
<pre>
AMPS - AMule PHP Statistics

Copyright (c) 2004 Matt Britt <uberpenguin@hotpop.com>
Thanks to BigBob for writing the original aStats, which inspired this script

To use AMPS, just copy this entire directory somewhere under your HTTP
server's document root. AMPS requires that your PHP binaries have been
compiled with GD and FreeType support (configure options '--with-gd[=DIR]
--enable-gd-native-ttf'). Since AMPS has to access files outside the document
root of your webserver (specifically the aMule signature file), the safe_mode
option in your '/etc/php.ini' MUST be set to 'off'. If you want AMPS to display
in a different language, append '?lang=xx' to the 'index.php' file where 'xx' is
the two-letter country code (assuming that translation exists) such as en, de,
fr, etc. If you input a country code the script does not recognize, it will
simply default to en. Or you could just use the handy language selection drop-
down list at the bottom of the page!

AMPS looks for the aMule signature file (amulesig.dat) in /tmp. So make sure
amulesig.dat is actually being written to /tmp (the default is ~/.aMule).

If you would like to add a translation in your language, open the file 'en.inc'
in the 'langs/' directory, translate all the strings, and save the translated
file as 'xx.inc' where 'xx' is the two-leter language code (en, fr, etc). That's
it! Also, you probably will want to add the two-letter language code to the
array $completedlangs that is set near the top of 'index.php'. If you produce a
translation, please be sure to send it to me for inclusion in the main
distribution!

Sometime in the near future I will complete the theme support I have stubbed
into the script. If you have a colour scheme that you think looks good, modify
'style.css' and be sure to send me a copy of your new syle so I can include it
in future versions!

Please send any bugs, translations, or verbal abuse to <uberpenguin@hotpop.com>

Questions or comments regarding translations can be directed to the respective
translators listed in the CHANGELOG file.
</pre>

Additionally, ensure ''amulesig.dat'' is readable by your web server's [http://www.php.org PHP] module by modifying the ownership/group or permissions of the file so that the webserver user has read permission.

Using another wxinstall-de

2004-12-13T19:40:53Z

80.224.220.41:

<center>
[[Using another wxinstall|English]] | '''Deutsch'''
</center>

Wenn schon eine Version von [[wxWidgets]] installiert ist, Sie aber aus bestimmten Gründen eine andere (vielleicht neuere) verwenden möchten, ist das auf die folgende Art und Weise zu erreichen:

Zuerst das Verzeichnis erstellen (als Beispiel wird hier ''~/aMule/'' verwendet), in dem [[wxWidgets]] und [[aMule]] installiert werden (sie müssen nicht im gleichen Verzeichnis liegen, aber es vereinfacht die Sache).

Zweitsn müssen [[wxWidgets]] und [[aMule]] entsprechend konfiguriert werden (ausgehend von [[wxWidgets]] 2.4.2 und aktuellem (=>rc7) aMule).

Empfehlenswert ist es, die Artikel über [[Compilation_Installation#Step_1:_wxGTK|Compilieren von wxGTK]] und (wahlweise, nur wenn man ein [[wxWidgets]] vor Version 2.5 installiert) [[Compilation_Installation#Step_2:_wxBase|Compilieren von wxBase]] zu lesen.

Im Quellverzeichnis von [[aMule]]: 
''./configure --prefix=~/aMule/ --enable-debug --disable-optimize --with-wx-config=/home/'''user'''/aMule/bin/wx-config --with-wxbase-config=/home/'''user'''/aMule/bin/wxbase-2.4-config'' 
''make && make install''

'''HINWEIS 1:''' Bei einigen Distributionen muss statt ''--with-wx-config=/home/'''Nutzername'''/aMule/bin/wx-config'' ''--with-wx-config=/home/'''Nutzername'''/aMule/bin/wxgtk-2.4-config'' verwendet werden.

'''HINWEIS 2:''' Es kann passieren, dass [[wxBase]] bei der Installation ''wx-config'' überschreibt. Man kann das überprüfen, indem man ''wx-config --basename'' aufruft, es sollte ''wx_gtk'' anzeigen. Falls nicht, muss man [[wxGTK]] nocheinmal installieren, so dass es seinerseits wieder ''wx-config'' überschreibt und mit [[wxGTK]] verbindet.

Im obigen Beispiel wäre das fertige [[aMule]] Binary in ''~/aMule/bin/'' zu finden.

Die Option ''--with-wxbase-config=...'' sollte nur mit [[wxWidgets]]-Versionen vor 2.5 verwendet werden.

Damit [[aMule]] seine Bibliotheken findet, muss man vor dem Start die Pfade für den Linker anpassen:

''export LD_LIBRARY_PATH=~/aMule/lib:$LD_LIBRARY_PATH'' 
''export LC_ALL=en_EN.UTF-8''

Immer schön daran denken, [[Backtraces]] zu erzeugen, wenn aMule abstürzt und sie dem [[AMule_devs|aMule Entwicklerteam]] zu schicken.

Changelog 2.0.0-rc7

2004-12-09T19:28:53Z

80.224.220.41:

== Version 2.0.0rc7 (The "99,6% Final" version) ==
''2004-10-19''

'''bisley:'''
; : * Added session ratio and total ratio to XAS

'''deltaHF:'''
; : * Got back from hell and changed one icon on the GUI ;)

'''Jacobo221:'''
; : aMule GUI:
; : * Fixed two almost-the-same bugs when clicked download button and no items where selected (as reported by powtrix/willy, thanks)
; : aMuleWeb:
; : * Fixed a bug where up/down limits woudln't be displayed correctly if their string length were different
; : aMuleCMD:
; : * Added 'list' (or 'find') command to search for a file in the downloads queue by name or by number (or just show all)
; : * Added the ability to resume/pause all downloads at the same time through amulecmd (very handy when all downloads have been paused due to lack of space)
; : * Fixed two bugs on amulecmd by which using 'pause' or 'resume' without arguments would pause/resume the oldest download.
; : * Fixed a bug so that help command no longer is send to core
; : * Fixed other commands sending blank data to core
; : * Cleaned unneeded output log messages + added sent command messages to log (for easier security monitoring)
; : * Several command simplifications on amulecmd to make it easier to use (while maintaining backwards compatibility).
; : * Lots of translations lacks

'''KingFish:'''
; : * Fixed broken compilation in SysTray.cpp with gcc 3.3.4.

'''Kry:'''
; : * Fixed: Crashes related to animation deletion on http download dialog
; : * Fixed: 0-size server.met file crashing aMule on startup and on download.
; : * Fixed: GUI blocking on server connection.
; : * Fixed: The last (hopefully) "fixed minsize" bug. FileDetail dialog was growing :)
; : * Misc code cleaning.
; : * Mac:
; : * Enabling wxCocoa compilation
; : * Fixed: Secure Ident was not working on big endian archs.
; : * Fixed: ClientID endianess issues leading to faking low/high id
; : * Fixed: Several fields were not having correct size on preferences.
; : * Fixed: Curl preform_multi was crashing the http download dialog on Mac. This means server.met update and ipfilter update was crashing. Currently the fix disables 'Cancel' button on that dialog, while we wait for curl lib to fix this issue.

'''lfroen:'''
; : * Removed debug printf's in timer.cpp
; : * Fix for deadlock on connection timeout in ServerSocket.cpp
; : * Fixed assert when build with wx-cvs
; : * Added option for disabling SIGSEG handling: useful for debuging in amuled.cpp
; : * EMSocket.h cleanup
; : * Fixed unclosed sockets (CLOSE_WAIT) and few stability problems
; : * Make CEMSocket::OnReceive thread safe. MAX_SIZE reduced, cause even theoretically tcp can buffer up to 64K
; : * amuled fixes

'''mfs:'''
; : * Fixed crashes on friendlist when keeping keys pressed
; : * Fixed one server not being removed when several servers selected
; : * Fixed access problems on deleting the ipfilter while accessing it

'''Phoenix:'''
; : * Fixed '&' char next to Preferences in amuleweb web page, as reported by DreamWalker.
; : * ExternalConn: protected GETCATTITLE command from buffer overflow.
; : * Start removing unused code from ExternalConn.cpp.
; : * Fixed high CPU usage problem in amuleweb, thanks to jaguarwan for the report. Daemonizing amuleweb should be done using the -q switch.

'''ThePolish:'''
; : * Implemented new hits system in wxCas to display and save download rate records.
; : * Changed wxCas layout to try to avoid display bug with wx-cvs
; : * Added translations update (Thanks to all translators)
; : * Removed wxCas documentation to slim source tree (now downloadable from berlios)

'''Seagull:'''
; : * Patch adding "Directory" column to the shared-files dialog.
; : * Patch to add "Swap to this file" option for sources marked as "Asked For Another File" on download queue.

'''Unleashed:'''
; : * Better fix for amuleweb's high CPU usage problem. Now main thread only gets woken up when absolutely needed.

'''Xaignar:'''
; : * Reinsured that the preferences will be saved upon clicking "Ok".
; : * Removed SSE2 specific optimizations from the embedded Crypto++ sources, they would break very easily and crash aMule.
; : * Fixed a bug where we would sometimes attempt to remove a client from the wrong file, resulting in dangling pointers and crashes.
; : * Ensured that the statistics-dialog would be updated when preferences relating to it where changed.
; : * Added sainity checks to category-loading, to avoid adding categories without incomming dir or name.
; : * Initial fix for crashes if aMule tried to share an inaccessible folder.
; : * The redraw problems on restoring from minimized state should be fixed.
; : * Fixed the shared-files list, which would draw columns regardless of whenever or not they were hidden.
; : * Fixed the progress-bars in the shared-files dialog. It should now work properly for both part and completed files.
; : * Fixed a bug in the ipfilter, where non-numeric chars on lines would cause wrong ranges of IPs to be filtered.
; : * Re-added the priority menu for servers, which had gone missing due to a mistake.
; : * Stopped the client-credits class from attempting to load older versions of the lists, which again would lead to mem-corruption.
; : * Fixed hidden columns on download queue, which would still be drawn.
; : * Added sainity checks to loading of clients.met file, since corrupted files would lead to potentially huge ammounts of mem-corruption.
; : * Added "Completed Sources" column to the shared-files dialog.
; : * Fixed a bug in sockets where disconnected sockets wouldn't be removed immediatly, but left to timeout instead.
; : * Fixed an end-less loop on the AICH thread if a file on the queue was removed from the list of shared files.
; : * Fixed an end-less loop when changing file-status by category.
; : * Fixed the auto-priority menu-item on the download list when multiple items where selected. It would un-set auto-priotity instead.
; : * A bit of optimization in CPartFile. More work will follow later.
; : * Properly initialized a number of variables.
; : * Fixed the column-width saving/loading which I managed to break shortly before rc6 was release. Whoops. :p
; : * Ampersands will no longer be doubled when lines are added to the log-view.

'''Special Thanks To:'''

; : * Translators in this release:
; : biger [HUN]: (Hungarian / hu_HU)
; : GhePeU: (Italian / it_IT)
; : mad_soft: (Spanish / es_ES)
; : Ogon: (Polish / pl_PL)
; : piarres: (Basque / es_EU)
; : powtrix/willy: (Brazilian / pt_BR)
; : punkyxd: (Catalan / es_CA)
; : stefanero: (German / de_DE)
; : Supersnail: (Dutch / nl_NL)

; : * Testers and bug reporters:
; : angel, BiByFoK,
; : bill_bool, boutros,
; : elui, Gaenya,
; : jolupa, ken_aMule,
; : mad_soft, Mig21,
; : one2one, powtrix,
; : RedDwarf, skolnick,
; : wi777

; : * Everyone at:
; : #amule irc.freenode.net
; : wiki http://wiki.amule.org
; : forums http://forum.amule.org
; : bugtracker http://bugs.amule.org

; : * All aMule users!!!

Signature

2004-12-09T12:21:11Z

80.224.220.41:

Online Signature is a ''mono-directional'' way [[aMule]] has to communicate with external utilities (such as [[CAS]], [[wxCAS]], [[AMPS]], etc...).

It consists of a file [[aMule]] writes on disc from-time-to-time (by default, every 5 seconds, but this can be changed in "Preferences" -> "Online Singature") to inform about it's current status.

[[aMule]] currently supports two signature files formats:
*[[amulesig.dat_file|aMule singature file (''amulesig.dat'')]]
*[[onlinesig.dat_file|eMule signature file (''onlinesig.dat'')]]

More information about this can be found at [[FAQ_aMule#What_is_all_that_stuff_in_amulesig.dat_and_onlinesig.dat?|aMule's FAQ]].

External Connections

2004-12-09T12:16:24Z

80.224.220.41:

External Connections is the ''bi-directional'' way [[aMule]] has to communicate with external utilities, like the [[aMuleWeb]] and [[aMuleCMD]]. So, when a user is controlling [[aMule]] remotely, it is sending the commands through the External Conections port and [[aMule]] is reading them there (when controlling through a web browser, what is really happening is that [[aMuleWeb]] is getting the actions, interpreting them and sending the commands to the External Connection ports).

If both [[aMule]] and their utilities run on the same machine, there's no need to redirect the External Connections port in a [[Firewall]]ed environment (NAT network with a router, etc...). If you had to connect to the External Connections port from somewhere out of the network, it would be necessary to configure the router/[[Firewall]]/etc properly to accept connections through the External Connection port (this would happen, for example, connecting through [[aMuleCMD]] from somewhere outside the network).

As of [[aMule]] 2.0.0-rc8, External Connections reached [[ECv2|version 2.0]]. This version is a complete rewrite of the protocol and is '''NOT''' backwards compatible, so it is heavily suggested to upgrade to both a server (that is, [[aMule]]) and [[client]] supporting it. Information about [[ECv2|External Connections v2]] can be reached [[ECv2|here]].

'''NOTE:''' There are alternate ways of communicating with [[aMule]] although External Connections is the only ''bi-directional'' way. Other ways of communication with [[aMule]] would be the [[Signature|Online Signature]] (outgoing direction) and [[ED2KLinks file]] (ingoing direction).

Using another wxinstall

2004-12-01T12:44:14Z

80.224.220.41:

If there's already a version of [[wxWidgets]] installed, but you want [[aMule]] to use another (probably newer) one, here are the steps to follow:

First, create the target directory (in this article, as an example, ''~/aMule/'' will be used), where [[wxWidgets]] and [[aMule]] will reside (they don't need to be in the same dir, but it makes life easier). Then configure [[wxWidgets]] and [[aMule]] accordingly (assuming [[wxWidgets]] 2.4.2 and current (=>rc7) aMule).

It is recommended that you read the article about [[Compilation_Installation#Step_1:_wxGTK|how to compile wxGTK]] and (optionally, only if installing a [[wxWidgets]] version prior to 2.5) [[Compilation_Installation#Step_2:_wxBase|how to compile wxBase]]

In [[aMule]] source dir: 
''./configure --prefix=~/aMule/ --enable-debug --disable-optimize --with-wx-config=/home/'''user'''/aMule/bin/wx-config --with-wxbase-config=/home/'''user'''/aMule/bin/wxbase-2.4-config'' 
''make && make install''

'''NOTE:''' On some distros, instead of ''--with-wx-config=/home/'''user'''/aMule/bin/wx-config'' you might need to use ''--with-wx-config=/home/'''user'''/aMule/bin/wxgtk-2.4-config''

'''NOTE 2:''' Sometimes [[wxBase]] will overwrite ''wx-config''. You can know if it has done so by running ''wx-config --basename''. It should show ''wx_gtk''. If it doesn't, please reinstall [[wxGTK]] so it will overwritte ''wx-config'' to link it to the [[wxGTK]] file.

On the above example, [[aMule]] binnary will be installed in ''~/aMule/'' directory.

Also note that ''--with-wxbase-config=...'' should only be used with [[wxWidgets]] versions prior to 2.5.

To start [[aMule]], you need to explicitely specifiy the LD path each time you run it:

''export LD_LIBRARY_PATH=~/aMule/lib:$LD_LIBRARY_PATH'' 
''export LC_ALL=en_EN.UTF-8''

Please remember to create [[Backtraces]] and provide them to the [[AMule_devs|aMule development team]].

Using another wxinstall

2004-11-30T15:38:51Z

80.224.220.41:

If there's already a version of [[wxWidgets]] installed, but you want [[aMule]] to use another (probably newer) one, here are the steps to follow:

First, create the target directory (in this article, as an example, ''~/aMule/'' will be used), where [[wxWidgets]] and [[aMule]] will reside (they don't need to be in the same dir, but it makes life easier). Then configure [[wxWidgets]] and [[aMule]] accordingly (assuming [[wxWidgets]] 2.4.2 and current (=>rc7) aMule).

It is recommended that you read the article about [[Compilation_Installation#Step_1:_wxGTK|how to compile wxGTK]] and (optionally, only if installing a [[wxWidgets]] version prior to 2.5) [[Compilation_Installation#Step_2:_wxBase|how to compile wxBase]]

In [[aMule]] source dir: 
''./configure --prefix=~/aMule/ --enable-debug --disable-optimize --with-wx-config=~/aMule/bin/wx-config --with-wxbase-config=~/aMule/bin/wxbase-2.4-config'' 
''make && make install''

'''NOTE:''' On some distros, instead of ''--with-wx-config=~/aMule/bin/wx-config'' you might need to use ''--with-wx-config=~/aMule/bin/wxgtk-2.4-config''

'''NOTE 2:''' Sometimes [[wxBase]] will overwrite ''wx-config''. You can know if it has done so by running ''wx-config --basename''. It should show ''wx_gtk''. If it doesn't, please reinstall [[wxGTK]] so it will overwritte ''wx-config'' to link it to the [[wxGTK]] file.

On the above example, [[aMule]] binnary will be installed in ''~/aMule/'' directory.

Also note that ''--with-wxbase-config=...'' should only be used with [[wxWidgets]] versions prior to 2.5.

To start [[aMule]], you need to explicitely specifiy the LD path each time you run it:

''export LD_LIBRARY_PATH=~/aMule/lib:$LD_LIBRARY_PATH'' 
''export LC_ALL=en_EN.UTF-8''

Please remember to create [[Backtraces]] and provide them to the [[AMule_devs|aMule development team]].

Using another wxinstall

2004-11-30T15:32:32Z

80.224.220.41:

If there's already a version of [[wxWidgets]] installed, but you want [[aMule]] to use another (probably newer) one, here are the steps to follow:

First, create the target directory, where [[wxWidgets]] and [[aMule]] will reside (they don't need to be in the same dir, but it makes life easier). Then configure [[wxWidgets]] and [[aMule]] accordingly (assuming [[wxWidgets]] 2.4.2 and current (=>rc7) aMule).

in [[wxWidgets|wxGTK]] source dir:
''<pre>
mkdir ~/aMule
./configure --prefix=~/aMule --disable-gtk2 --with-gtk
make && make install
</pre>''

in [[wxWidgets|wxBase]] source dir:
''<pre>
mkdir ~/aMule
./configure --prefix=~/aMule
make && make install
</pre>''

In [[aMule]] source dir:
''<pre>
./configure --prefix=~/aMule/ --enable-debug --disable-optimize --with-wx-config=~/aMule/bin/wx-config --with-wxbase-config=~/aMule/bin/wxbase-2.4-config
make && make install
</pre>''

'''NOTE:''' On some distros, instead of ''--with-wx-config=~/aMule/bin/wx-config'' you might need to use ''--with-wx-config=~/aMule/bin/wxgtk-2.4-config''

'''NOTE 2:''' Sometimes [[wxBase]] will overwrite ''wx-config''. You can know if it has done so by running ''wx-cinfig --basename''. It should show ''wx_gtk''. If it doesn't, please reinstall [[wxGTK]] so it will overwritte ''wx-config'' to link it to the [[wxGTK]] file.

To start [[aMule]], you need to explicitely specifiy the LD path each time you run it:

''export LD_LIBRARY_PATH=~/aMule/lib:$LD_LIBRARY_PATH'' 
''export LC_ALL=en_EN.UTF-8''

Please remember to create [[Backtraces]] and provide them to the [[AMule_devs|aMule development team]].

How to launch VNC with aMule at Linux boot

2004-11-18T00:22:48Z

80.224.220.41:

<h2>''By [[User:Frankk|Frankk]]''</h2>

== General ==

This describes a very simple configuration to launch [http://www.redstonesoftware.com/vnc.html VNC] at [http://www.kernel.org Linux] startup (as a specified user). [[aMule]] will be launched automatically with [http://www.redstonesoftware.com/vnc.html VNC].
This will work in [http://www.slackware.com Slackware] and distro based on the same init method. If someone knows how to modify it to make it work under other distros you are welcome to add it to this page. Thanks.

Add the ''rc.vnc'' script to ''/etc/rc.d''

Modify user according to the user running [[aMule]]. 
The ''rm /tmp/.X11-unix/X$theScreen'' is there in case the server crashes or your mother/wife removes the power plug cleaning the room... ;-)

''<pre>
#!/bin/sh
#
# Startup/Stop script for vncserver.
#

#Here, the choosen user to run amule
theUser=choosenuser
#And here, the choosen screen to run the vncserver
theScreen=1

case "$1" in

'start')
if [ -f /tmp/.X11-unix/X$theScreen ]; then rm /tmp/.X11-unix/X$theScreen; fi
/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen"
;;

'stop')
/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver -kill :$theScreen"
;;

*)
echo "Usage: /etc/init.d/rc.vnc { start | stop }"
;;

esac
</pre>''

Make it executable with:

''<pre>chmod 755 /etc/rc.d/rc.vnc</pre>''

Modify the following files:

In ''/etc/rc.d/rc.local'' add:

''# Start VNC server''
''if [ -x /etc/rc.d/rc.vnc ]; then''
''. /etc/rc.d/rc.vnc start''
''fi''

In ''/etc/rc.d/rc.6'' add:

''# Shut down the VNC server''
''if [ -x /etc/rc.d/rc.vnc ]; then''
''/etc/rc.d/rc.vnc stop''
''fi''

In ''~/.vnc/xstartup'' (in home directory of the user specified above) add (change with your preferred [[aMule]] startup script):

''amule &''

== On [http://www.debian.org Debian] Woody ==

Run (as root):

''apt-get install vncserver xvncviewer''
''apt-get install vncserver flwm''

There is no support for ''~/.vnc/xstartup'' so, instead, use ''$vncStartup'' in ''.vncrc'' to determine a xstartup-script (this replaces your ''~/.xsession'' file).

For more information, read ''man vnc.conf''

For example, in a Woody/Sarge/Sid: 
Login as the user who is going to run [[aMule]] 
''mkdir ~/.vnc/'' 
Create the ''~/.vnc/xstartup'' file, with the next content 

''/usr/bin/flwm &''
''/usr/bin/amule &''
''/usr/bin/amule &''

With sone versions of [http://www.redstonesoftware.com/vnc.html vncserver], it's necessary to launch at least twice the [[aMule]]. The [http://flwm.sourceforge.net flwm] is an optional window manager.

Create the file ''~/.vncrc'' with the next content: 
Login as the user and run ''xvncviewer :1'' to create the password file and debug possible probelms (the logs are under the ''~/.vnc/'' dir

''$vncStartup = "/home/amule/.vnc/xstartup";''
''$geometry ="800x600";''

(replace ''/home/amule'' for the home of the user running [http://www.redstonesoftware.com/vnc.html VNC])

To show the [[aMule]] window, run:
''xvncviewer localhost:1''

If you want to autostart a [http://www.redstonesoftware.com/vnc.html VNC] session on system startup, you can put a line in ''/etc/init.d/bootmisc.sh'' like this:

''su '''username''' -c vncserver''

Replace '''username''' with the name of the user that you want to launch vnc. (Added by '''ghent''')

== [http://www.mandrake.com Mandrake] 10.0 ==

The script from [[User:Frankk|Frankk]] is the one I use, but you can customize the size of the [http://www.redstonesoftware.com/vnc.html VNC] server :
''/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen"''

add

''/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen -geometry 1240x980"''

or whatever value.

Personaly, I use as xstartup script ([http://www.icewm.org iceWM] is really nice and so CPU-cheap) :

''#!/bin/sh''
''starticewm&''
''amule''

To start [http://www.redstonesoftware.com/vnc.html VNC] at startup, I called the previous script ''/etc/init.d/amulevnc'' and chmod to 744 (''chmod 744 /etc/init.d/amulevnc'' as root). 
Instead of modifying ''/etc/rc.d/rc.vnc'', I added links in the corresponding ''/etc/rc$RUNLEVEL.d'' directories. 
It's quite simple to understand how it works: 
Each directory represents a runlevel, and contains links to the scripts from ''/etc/init.d'' which need to be run/stop. 
For instance, the link ''/etc/rc5.d/S55sshd'' to ''/etc/init.d/sshd'' will start ''sshd'' on runlevel 5,
whereas ''/etc/rc6.d/K25sshd'' linked to ''/etc/init.d/sshd'' will stop it in runlevel 6. 
You get it? Links starting with 'KXX' will stop a service, and those starting with 'SXX' will start them. The number will define the order.

So to run [http://www.redstonesoftware.com/vnc.html VNC] on startup, just do (as root :-) )
''re>ln -s /etc/init.d/amulevnc /etc/rc5.d/S99amule''
''ln -s /etc/init.d/amulevnc /etc/rc6.d/K02amule''
and you're all set!

PS: This method should work on systems other than [http://www.mandrake.com Mandrake], give it a test.

Questions & comments: ''air_1 '''at''' libertysurtf.fr''

HowTo compile on Mac

2004-11-17T23:27:12Z

80.224.220.41:

The following steps will lead you to install [[aMule]] in your [http://www.apple.com/macosx MacOS X] box.

This HowTo is written to install [[aMule]] 2.0.0-rc7 but should work for any other version. Please note that you should always download the latest [[aMule]] version available.

'''NOTE:''' This document explains how to download files using [http://curl.haxx.se curl]. However, [http://curl.haxx.se curl] might not be installed on your system: either install it (you can use [http://fink.sourceforge.net Fink] to instal it) or download the files with whatever application you want (maybe your web browser), but place then in the directory that's being used on each part of the guide, otherwise the commands that are shown here will not work.

# Install [http://developer.apple.com/tools/xcode Xcode Tools] from http://developer.apple.com/tools/download
# "Getting ADC ID"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"
# Install (or verify installation if already installed) [http://fink.sourceforge.net Fink], since [http://www.gnu.org/software/gettext gettext] and [[wxMac]] are installed along with [http://fink.sourceforge.net Fink], from http://fink.sourceforge.net/download
# Install [http://www.gnu.org/software/gettext gettext] and [[wxMac]] ([[wxMac]] is only available through [http://fink.sourceforge.net Fink] [http://fink.sourceforge.net/faq/usage-fink.php?phpLang=en#unstable unstable] on [http://www.apple.com/macosx MacOS] 10.3. If you are using [http://fink.sourceforge.net Fink] stable or [http://www.apple.com/macosx MacOS] 10.2 or earlier, either [http://fink.sourceforge.net/faq/usage-fink.php?phpLang=en#unstable upgrade Fink to unstable] and/or [http://www.apple.com/macosx MacOS] to 10.3, or check the [[#Installing wxMac form sources|Installing wxMac form sources section]] of this document and then go on with this section) through [http://fink.sourceforge.net Fink]. Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink] (the [http://www.gnu.org/software/gettext gettext] package is ''gettext'' and the [[wxMac]] package is ''wxmac'' and ''wxmac-shlibs''),
# Read the documentation at http://fink.sourceforge.net/download to learn how to install [[wxMac]].
# Make ''amule'' dir in your home directory: ''mkdir ~/amule''
# Enter the ''amule'' directory you just created: ''cd ~/amule''
# Get [[aMule]]'s latest source code (aMule 2.0.0-rc7 sourcecode: [http://download.berlios.de/amule/aMule-2.0.0rc7.tar.bz2 http://download.berlios.de/amule/aMule-2.0.0rc7.tar.bz2]) and place it in your ''~/amule'' directory: curl -O http://download.berlios.de/amule/aMule-2.0.0rc7.tar.bz2
# Extract it: ''tar -xjf aMule-2.0.0rc7.tar.bz2''
# Enter [[aMule]]'s sources directory: ''cd aMule-2.0.0rc7''
# Prepare the compilation (thanks to '''one_2_one''' and '''Babboia''' for his test&fix): ''./configure --disable-systray --disable-gtk --with-wx-config=/sw/bin/wx-config''
# And compile it: ''make''
# '''Optional:''' You can reduce the size of [[aMule]] from 44MB to 3MB by doing the following (anyway, this will make the [[aMule]] binnary loose debug info, so you'll be unable to report problems to the [[aMule devs|aMule Team]] to make [[aMule]] a better program, which it is not recommended): ''strip src/amule''
# Get back to your ''amule'' directory: ''cd ~/amule''
# Download [http://download.berlios.de/amule/aMule-App-Container.tar.bz2 aMule's app-Container]: ''curl -O http://download.berlios.de/amule/aMule-App-Container.tar.bz2''
# Extract it: ''tar -xjf aMule-App-Container.tar.bz2''
# Copy the ''amule'' binnary to the app-Container directory: ''cp aMule-2.0.0rc7/src/amule amule.app/Contents/MacOS/''
# And move ''amule.app'' directory to your Applications folder: ''mv amule.app /Applications''
# If everything went ok, you can safely remove the downloaded packages:
## Remove [[aMule]]'s sources package: ''rm ~/amule/aMule-2.0.0rc7.tar.bz2''
## Remove the app-Container package: ''rm aMule-App-Container.tar.bz2''
## Optionally remove the extracted [[aMule]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/amule/aMule-2.0.0rc7''
## Optionally, if you if you decided to remove the extracted [[aMule]] sources, remove the ''~/amule'' directory (which should be empty by now): ''rmdir ~/amule''

== Installing [[wxMac]] form sources ==

Only follow this part of the guide if [[wxMac]] is not available through your [http://fink.sourceforge.net Fink] installation or if you really know what you're doing. In any other case, just jump to the next section.

# Create a directory where all the work will be done: ''mkdir ~/wxmac''
# Enter that directory: ''cd ~/wxmac''
# Download [[wxMac]] sources: ''curl -O ftp://biolpc22.york.ac.uk/pub/2.5.3/wxMac-2.5.3.tar.gz''
# Extract the file: ''tar -xzf wxMac-2.5.3.tar.gz''
# Enter the extracted sources' directory: ''cd wxMac-2.5.3''
# Directory ''build'' should already be there. If not, create it with: ''mkdir build''
# Now enter ''build'' directory: ''cd build''
# Prepare the compilation: ''../configure''
# And compile: ''make''
# Now install [[wxMac]] compilation: ''sudo make install''
# Get back to your home directory, you're done: ''cd ~''
# If everything went ok, you can safely remove:
## [[wxMac]]'s sources package: ''rm wxMac-2.5.3.tar.gz''
## Optionally remove the extracted [[wxMac]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/wxmac

'''NOTE:''' Since you're installing [[wxMac]] from sources instead of through [http://fink.sourceforge.net Fink], use ''./configure --disable-systray --disable-gtk --with-wx-config=/usr/local/bin/wx-config'' as your configure command at [[aMule]]'s compilation instead of ''./configure --disable-systray --disable-gtk --with-wx-config=/sw/bin/wx-config''

== 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 the app-Container failed to extract try running this command instead of the app-Container extraction step: ''mkdir -p amule.app/Contents/MacOS''

*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

2004-11-17T17:45:29Z

80.224.220.41:

The following steps will lead you to install [[aMule]] in your [http://www.apple.com/macosx MacOS X] box.

This HowTo is written to install [[aMule]] 2.0.0-rc7 but should work for any other version. Please note that you should always download the latest [[aMule]] version available.

'''NOTE:''' This document explains how to download files using [http://curl.haxx.se curl]. However, [http://curl.haxx.se curl] might not be installed on your system: either install it (you can use [http://fink.sourceforge.net Fink] to instal it) or download the files with whatever application you want (maybe your web browser), but place then in the directory that's being used on each part of the guide, otherwise the commands that are shown here will not work.

# Install [http://developer.apple.com/tools/xcode Xcode Tools] from http://developer.apple.com/tools/download
# "Getting ADC ID"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"
# Install (or verify installation if already installed) [http://fink.sourceforge.net Fink], since [http://www.gnu.org/software/gettext gettext] and [[wxMac]] are installed along with [http://fink.sourceforge.net Fink], from http://fink.sourceforge.net/download
# Install [http://www.gnu.org/software/gettext gettext] and [[wxMac]] ([[wxMac]] is only available through [http://fink.sourceforge.net Fink] [http://fink.sourceforge.net/faq/usage-fink.php?phpLang=en#unstable unstable] on [http://www.apple.com/macosx MacOS] 10.3. If you are using [http://fink.sourceforge.net Fink] stable or [http://www.apple.com/macosx MacOS] 10.2 or earlier, either [http://fink.sourceforge.net/faq/usage-fink.php?phpLang=en#unstable upgrade Fink to unstable] and/or [http://www.apple.com/macosx MacOS] to 10.3, or check the [[#Installing wxMac form sources|Installing wxMac form sources section]] of this document and then go on with this section) through [http://fink.sourceforge.net Fink]. Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink] (the [http://www.gnu.org/software/gettext gettext] package is ''gettext'' and the [[wxMac]] package is ''wxmac'' and ''wxmac-shlibs''),
# Read the documentation at http://fink.sourceforge.net/download to learn how to install [[wxMac]].
# Make ''amule'' dir in your home directory: ''mkdir ~/amule''
# Enter the ''amule'' directory you just created: ''cd ~/amule''
# Get [[aMule]]'s latest source code (aMule 2.0.0-rc7 sourcecode: [http://download.berlios.de/amule/aMule-2.0.0rc7.tar.bz2 http://download.berlios.de/amule/aMule-2.0.0rc7.tar.bz2]) and place it in your ''~/amule'' directory: curl -O http://download.berlios.de/amule/aMule-2.0.0rc7.tar.bz2
# Extract it: ''tar -xjf aMule-2.0.0rc7.tar.bz2''
# Enter [[aMule]]'s sources directory: ''cd aMule-2.0.0rc7''
# Prepare the compilation (thanks to '''one_2_one''' and '''Babboia''' for his test&fix): ''./configure --disable-systray --disable-gtk --with-wx-config=/usr/local/bin/wx-config''
# And compile it: ''make''
# '''Optional:''' You can reduce the size of [[aMule]] from 44MB to 3MB by doing the following (anyway, this will make the [[aMule]] binnary loose debug info, so you'll be unable to report problems to the [[aMule devs|aMule Team]] to make [[aMule]] a better program, which it is not recommended): ''strip src/amule''
# Get back to your ''amule'' directory: ''cd ~/amule''
# Download [http://download.berlios.de/amule/aMule-App-Container.tar.bz2 aMule's app-Container]: ''curl -O http://download.berlios.de/amule/aMule-App-Container.tar.bz2''
# Extract it: ''tar -xjf aMule-App-Container.tar.bz2''
# Copy the ''amule'' binnary to the app-Container directory: ''cp aMule-2.0.0rc7/src/amule amule.app/Contents/MacOS/''
# And move ''amule.app'' directory to your Applications folder: ''mv amule.app /Applications''
# If everything went ok, you can safely remove the downloaded packages:
## Remove [[aMule]]'s sources package: ''rm ~/amule/aMule-2.0.0rc7.tar.bz2''
## Remove the app-Container package: ''rm aMule-App-Container.tar.bz2''
## Optionally remove the extracted [[aMule]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/amule/aMule-2.0.0rc7''
## Optionally, if you if you decided to remove the extracted [[aMule]] sources, remove the ''~/amule'' directory (which should be empty by now): ''rmdir ~/amule''

== Installing [[wxMac]] form sources ==

Only follow this part of the guide if [[wxMac]] is not available through your [http://fink.sourceforge.net Fink] installation or if you really know what you're doing. In any other case, just jump to the next section.

# Create a directory where all the work will be done: ''mkdir ~/wxmac''
# Enter that directory: ''cd ~/wxmac''
# Download [[wxMac]] sources: ''curl -O ftp://biolpc22.york.ac.uk/pub/2.5.3/wxMac-2.5.3.tar.gz''
# Extract the file: ''tar -xzf wxMac-2.5.3.tar.gz''
# Enter the extracted sources' directory: ''cd wxMac-2.5.3''
# Directory ''build'' should already be there. If not, create it with: ''mkdir build''
# Now enter ''build'' directory: ''cd build''
# Prepare the compilation: ''../configure''
# And compile: ''make''
# Now install [[wxMac]] compilation: ''sudo make install''
# Get back to your home directory, you're done: ''cd ~''
# If everything went ok, you can safely remove:
## [[wxMac]]'s sources package: ''rm wxMac-2.5.3.tar.gz''
## Optionally remove the extracted [[wxMac]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/wxmac

== 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 the app-Container failed to extract try running this command instead of the app-Container extraction step: ''mkdir -p amule.app/Contents/MacOS''

*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

2004-11-17T16:27:59Z

80.224.220.41:

The following steps will lead you to install [[aMule]] in your [http://www.apple.com/macosx MacOS X] box.

This HowTo is written to install [[aMule]] 2.0.0-rc7 but should work for any other version. Please note that you should always download the latest [[aMule]] version available.

'''NOTE:''' This document explains how to download files using [http://curl.haxx.se curl]. However, [http://curl.haxx.se curl] might not be installed on your system: either install it (you can use [http://fink.sourceforge.net Fink] to instal it) or download the files with whatever application you want (maybe your web browser), but place then in the directory that's being used on each part of the guide, otherwise the commands that are shown here will not work.

# Install [http://developer.apple.com/tools/xcode Xcode Tools] from http://developer.apple.com/tools/download
# "Getting ADC ID"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"
# Install (or verify installation if already installed) [http://fink.sourceforge.net Fink], since [http://www.gnu.org/software/gettext gettext] and [[wxMac]] are installed along with [http://fink.sourceforge.net Fink], from http://fink.sourceforge.net/download
# Install [http://www.gnu.org/software/gettext gettext] and [[wxMac]] ([[wxMac]] is only available through [http://fink.sourceforge.net Fink] unstable on [http://www.apple.com/macosx MacOS] 10.3. If you are using [http://fink.sourceforge.net Fink] stable or [http://www.apple.com/macosx MacOS] 10.2 or earlier, either upgrade [http://fink.sourceforge.net Fink] to unstable and/or [http://www.apple.com/macosx MacOS] to 10.3, or check the [[#Installing wxMac form sources|Installing wxMac form sources section]] of this document and then go on with this section) through [http://fink.sourceforge.net Fink]. Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink] (the [http://www.gnu.org/software/gettext gettext] package is ''gettext'' and the [[wxMac]] package is ''wxmac'' and ''wxmac-shlibs''),
# Read the documentation at http://fink.sourceforge.net/download to learn how to install [[wxMac]].
# Make ''amule'' dir in your home directory: ''mkdir ~/amule''
# Enter the ''amule'' directory you just created: ''cd ~/amule''
# Get [[aMule]]'s latest source code (aMule 2.0.0-rc7 sourcecode: [http://download.berlios.de/amule/aMule-2.0.0rc7.tar.bz2 http://download.berlios.de/amule/aMule-2.0.0rc7.tar.bz2]) and place it in your ''~/amule'' directory: curl -O http://download.berlios.de/amule/aMule-2.0.0rc7.tar.bz2
# Extract it: ''tar -xjf aMule-2.0.0rc7.tar.bz2''
# Enter [[aMule]]'s sources directory: ''cd aMule-2.0.0rc7''
# Prepare the compilation (thanks to '''one_2_one''' and '''Babboia''' for his test&fix): ''./configure --disable-systray --disable-gtk --with-wx-config=/usr/local/bin/wx-config''
# And compile it: ''make''
# '''Optional:''' You can reduce the size of [[aMule]] from 44MB to 3MB by doing the following (anyway, this will make the [[aMule]] binnary loose debug info, so you'll be unable to report problems to the [[aMule devs|aMule Team]] to make [[aMule]] a better program, which it is not recommended): ''strip src/amule''
# Get back to your ''amule'' directory: ''cd ~/amule''
# Download [http://download.berlios.de/amule/aMule-App-Container.tar.bz2 aMule's app-Container]: ''curl -O http://download.berlios.de/amule/aMule-App-Container.tar.bz2''
# Extract it: ''tar -xjf aMule-App-Container.tar.bz2''
# Copy the ''amule'' binnary to the app-Container directory: ''cp aMule-2.0.0rc7/src/amule amule.app/Contents/MacOS/''
# And move ''amule.app'' directory to your Applications folder: ''mv amule.app /Applications''
# If everything went ok, you can safely remove the downloaded packages:
## Remove [[aMule]]'s sources package: ''rm ~/amule/aMule-2.0.0rc7.tar.bz2''
## Remove the app-Container package: ''rm aMule-App-Container.tar.bz2''
## Optionally remove the extracted [[aMule]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/amule/aMule-2.0.0rc7''
## Optionally, if you if you decided to remove the extracted [[aMule]] sources, remove the ''~/amule'' directory (which should be empty by now): ''rmdir ~/amule''

== Installing [[wxMac]] form sources ==

Only follow this part of the guide if [[wxMac]] is not available through your [http://fink.sourceforge.net Fink] installation or if you really know what you're doing. In any other case, just jump to the next section.

# Create a directory where all the work will be done: ''mkdir ~/wxmac''
# Enter that directory: ''cd ~/wxmac''
# Download [[wxMac]] sources: ''curl -O ftp://biolpc22.york.ac.uk/pub/2.5.3/wxMac-2.5.3.tar.gz''
# Extract the file: ''tar -xzf wxMac-2.5.3.tar.gz''
# Enter the extracted sources' directory: ''cd wxMac-2.5.3''
# Directory ''build'' should already be there. If not, create it with: ''mkdir build''
# Now enter ''build'' directory: ''cd build''
# Prepare the compilation: ''../configure''
# And compile: ''make''
# Now install [[wxMac]] compilation: ''sudo make install''
# Get back to your home directory, you're done: ''cd ~''
# If everything went ok, you can safely remove:
## [[wxMac]]'s sources package: ''rm wxMac-2.5.3.tar.gz''
## Optionally remove the extracted [[wxMac]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/wxmac

== 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 the app-Container failed to extract try running this command instead of the app-Container extraction step: ''mkdir -p amule.app/Contents/MacOS''

*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

2004-11-17T15:38:41Z

80.224.220.41:

The following steps will lead you to install [[aMule]] in your [http://www.apple.com/macosx MacOS X] box.

This HowTo is written to install [[aMule]] 2.0.0-rc7 but should work for any other version. Please note that you should always download the latest [[aMule]] version available.

'''NOTE:''' This document explains how to download files using [http://curl.haxx.se curl]. However, [http://curl.haxx.se curl] might not be installed on your system: either install it (you can use [http://fink.sourceforge.net Fink] to instal it) or download the files with whatever application you want (maybe your web browser), but place then in the directory that's being used on each part of the guide, otherwise the commands that are shown here will not work.

# Install [http://developer.apple.com/tools/xcode Xcode Tools] from http://developer.apple.com/tools/download
# "Getting ADC ID"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"
# Install (or verify installation if already installed) [http://fink.sourceforge.net Fink], since [http://www.gnu.org/software/gettext gettext] and [[wxMac]] are installed along with [http://fink.sourceforge.net Fink], from http://fink.sourceforge.net/download
# Install [http://www.gnu.org/software/gettext gettext] and [[wxMac]] ([[wxMac]] is only available through [http://fink.sourceforge.net Fink] unstable on [http://www.apple.com/macosx MacOS] 10.3. If you are using [http://fink.sourceforge.net Fink] stable or [http://www.apple.com/macosx MacOS] 10.2 or earlier, either upgrade [http://fink.sourceforge.net Fink] to unstable and/or [http://www.apple.com/macosx MacOS] to 10.3, or check the [[#Installing wxMac form sources|Installing wxMac form sources section]] of this document and then go on with this section) through [http://fink.sourceforge.net Fink]. Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink] (the [http://www.gnu.org/software/gettext gettext] package is ''gettext'' and the [[wxMac]] package is ''wxmac'' and ''wxmac-shlibs''),
# Read the documentation at http://fink.sourceforge.net/download to learn how to install [[wxMac]].
# Make ''amule'' dir in your home directory: ''mkdir ~/amule''
# Enter the ''amule'' directory you just created: ''cd ~/amule''
# Get [[aMule]]'s latest source code (aMule 2.0.0-rc7 sourcecode: [http://download.berlios.de/amule/aMule-2.0.0rc7.tar.bz2 http://download.berlios.de/amule/aMule-2.0.0rc7.tar.bz2]) and place it in your ''~/amule'' directory: curl -O http://download.berlios.de/amule/aMule-2.0.0rc7.tar.bz2
# Extract it: ''tar -xjf aMule-2.0.0rc7.tar.bz2''
# Enter [[aMule]]'s sources directory: ''cd aMule-2.0.0rc7''
# Prepare the compilation (thanks to '''Babboia''' for his test&fix): ''./configure --disable-systray --disable-gtk --with-wx-config=/usr/local/bin/wx-config''
# And compile it: ''make''
# '''Optional:''' You can reduce the size of [[aMule]] from 44MB to 3MB by doing the following (anyway, this will make the [[aMule]] binnary loose debug info, so you'll be unable to report problems to the [[aMule devs|aMule Team]] to make [[aMule]] a better program, which it is not recommended): ''strip src/amule''
# Get back to your ''amule'' directory: ''cd ~/amule''
# Download [http://download.berlios.de/amule/aMule-App-Container.tar.bz2 aMule's app-Container]: ''curl -O http://download.berlios.de/amule/aMule-App-Container.tar.bz2''
# Extract it: ''tar -xjf aMule-App-Container.tar.bz2''
# Copy the ''amule'' binnary to the app-Container directory: ''cp aMule-2.0.0rc7/src/amule amule.app/Contents/MacOS/''
# And move ''amule.app'' directory to your Applications folder: ''mv amule.app /Applications''
# If everything went ok, you can safely remove the downloaded packages:
## Remove [[aMule]]'s sources package: ''rm ~/amule/aMule-2.0.0rc7.tar.bz2''
## Remove the app-Container package: ''rm aMule-App-Container.tar.bz2''
## Optionally remove the extracted [[aMule]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/amule/aMule-2.0.0rc7''
## Optionally, if you if you decided to remove the extracted [[aMule]] sources, remove the ''~/amule'' directory (which should be empty by now): ''rmdir ~/amule''

== Installing [[wxMac]] form sources ==

Only follow this part of the guide if [[wxMac]] is not available through your [http://fink.sourceforge.net Fink] installation or if you really know what you're doing. In any other case, just jump to the next section.

# Create a directory where all the work will be done: ''mkdir ~/wxmac''
# Enter that directory: ''cd ~/wxmac''
# Download [[wxMac]] sources: ''curl -O ftp://biolpc22.york.ac.uk/pub/2.5.3/wxMac-2.5.3.tar.gz''
# Extract the file: ''tar -xzf wxMac-2.5.3.tar.gz''
# Enter the extracted sources' directory: ''cd wxMac-2.5.3''
# Directory ''build'' should already be there. If not, create it with: ''mkdir build''
# Now enter ''build'' directory: ''cd build''
# Prepare the compilation: ''../configure''
# And compile: ''make''
# Now install [[wxMac]] compilation: ''sudo make install''
# Get back to your home directory, you're done: ''cd ~''
# If everything went ok, you can safely remove:
## [[wxMac]]'s sources package: ''rm wxMac-2.5.3.tar.gz''
## Optionally remove the extracted [[wxMac]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/wxmac

== 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 the app-Container failed to extract try running this command instead of the app-Container extraction step: ''mkdir -p amule.app/Contents/MacOS''

*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

2004-11-17T14:03:53Z

80.224.220.41:

The following steps will lead you to install [[aMule]] in your [http://www.apple.com/macosx MacOS X] box.

This HowTo is written to install [[aMule]] 2.0.0-rc7 but should work for any other version. Please note that you should always download the latest [[aMule]] version available.

'''NOTE:''' This document explains how to download files using [http://curl.haxx.se curl]. However, [http://curl.haxx.se curl] might not be installed on your system: either install it (you can use [http://fink.sourceforge.net Fink] to instal it) or download the files with whatever application you want (maybe your web browser), but place then in the directory that's being used on each part of the guide, otherwise the commands that are shown here will not work.

# Install [http://developer.apple.com/tools/xcode Xcode Tools] from http://developer.apple.com/tools/download
# "Getting ADC ID"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"
# Install (or verify installation if already installed) [http://fink.sourceforge.net Fink], since [http://www.gnu.org/software/gettext gettext] and [[wxMac]] are installed along with [http://fink.sourceforge.net Fink], from http://fink.sourceforge.net/download
# Install [http://www.gnu.org/software/gettext gettext] and [[wxMac]] ([[wxMac]] is only available through [http://fink.sourceforge.net Fink] unstable on [http://www.apple.com/macosx MacOS] 10.3. If you are using [http://fink.sourceforge.net Fink] stable or [http://www.apple.com/macosx MacOS] 10.2 or earlier, either upgrade [http://fink.sourceforge.net Fink] to unstable and/or [http://www.apple.com/macosx MacOS] to 10.3, or check the [[#Installing wxMac form sources|Installing wxMac form sources section]] of this document and then go on with this section) through [http://fink.sourceforge.net Fink]. Read [http://fink.sourceforge.net/download Fink's installation guide] to learn how to install applications through [http://fink.sourceforge.net Fink] (the [http://www.gnu.org/software/gettext gettext] package is ''gettext'' and the [[wxMac]] package is ''wxmac'' and ''wxmac-shlibs''),
# Read the documentation at http://fink.sourceforge.net/download to learn how to install [[wxMac]].
# Make ''amule'' dir in your home directory: ''mkdir ~/amule''
# Enter the ''amule'' directory you just created: ''cd ~/amule''
# Get [[aMule]]'s latest source code (aMule 2.0.0-rc7 sourcecode: [http://download.berlios.de/amule/aMule-2.0.0rc7.tar.bz2 http://download.berlios.de/amule/aMule-2.0.0rc7.tar.bz2]) and place it in your ''~/amule'' directory: curl -O http://download.berlios.de/amule/aMule-2.0.0rc7.tar.bz2
# Extract it: ''tar -xjf aMule-2.0.0rc7.tar.bz2''
# Enter [[aMule]]'s sources directory: ''cd aMule-2.0.0rc7''
# Prepare the compilation: ''./configure --disable-systray --disable-gtk --enable-embedded_crypto --with-wx-prefix=/usr/local/bin/wx-config''
# And compile it: ''make''
# '''Optional:''' You can reduce the size of [[aMule]] from 44MB to 3MB by doing the following (anyway, this will make the [[aMule]] binnary loose debug info, so you'll be unable to report problems to the [[aMule devs|aMule Team]] to make [[aMule]] a better program, which it is not recommended): ''strip src/amule''
# Get back to your ''amule'' directory: ''cd ~/amule''
# Download [http://download.berlios.de/amule/aMule-App-Container.tar.bz2 aMule's app-Container]: ''curl -O http://download.berlios.de/amule/aMule-App-Container.tar.bz2''
# Extract it: ''tar -xjf aMule-App-Container.tar.bz2''
# Copy the ''amule'' binnary to the app-Container directory: ''cp aMule-2.0.0rc7/src/amule amule.app/Contents/MacOS/''
# And move ''amule.app'' directory to your Applications folder: ''mv amule.app /Applications''
# If everything went ok, you can safely remove the downloaded packages:
## Remove [[aMule]]'s sources package: ''rm ~/amule/aMule-2.0.0rc7.tar.bz2''
## Remove the app-Container package: ''rm aMule-App-Container.tar.bz2''
## Optionally remove the extracted [[aMule]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/amule/aMule-2.0.0rc7''
## Optionally, if you if you decided to remove the extracted [[aMule]] sources, remove the ''~/amule'' directory (which should be empty by now): ''rmdir ~/amule''

== Installing [[wxMac]] form sources ==

Only follow this part of the guide if [[wxMac]] is not available through your [http://fink.sourceforge.net Fink] installation or if you really know what you're doing. In any other case, just jump to the next section.

# Create a directory where all the work will be done: ''mkdir ~/wxmac''
# Enter that directory: ''cd ~/wxmac''
# Download [[wxMac]] sources: ''curl -O ftp://biolpc22.york.ac.uk/pub/2.5.3/wxMac-2.5.3.tar.gz''
# Extract the file: ''tar -xzf wxMac-2.5.3.tar.gz''
# Enter the extracted sources' directory: ''cd wxMac-2.5.3''
# Directory ''build'' should already be there. If not, create it with: ''mkdir build''
# Now enter ''build'' directory: ''cd build''
# Prepare the compilation: ''../configure''
# And compile: ''make''
# Now install [[wxMac]] compilation: ''sudo make install''
# Get back to your home directory, you're done: ''cd ~''
# If everything went ok, you can safely remove:
## [[wxMac]]'s sources package: ''rm wxMac-2.5.3.tar.gz''
## Optionally remove the extracted [[wxMac]] sources (not recommended, since you might want to compile it again someday): ''rm -r ~/wxmac

== Problems and solutions ==

*If the app-Container failed to extract try running this command instead of the app-Container extraction step: ''mkdir -p amule.app/Contents/MacOS''

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