AMule Project FAQ - User contributions [en]

FAQ aMule-fr

2004-11-26T13:30:13Z

84.128.98.219:

<center><h4>F.A.Q d' [[aMule_Project_FAQ:About|aMule]]</h4> 
<h2>par [[User:Jacobo221|Jacobo221]] (Traduit et adapté par ''[[User:Thelinuxfr|TheLinuxFr]]'')</h2> 
[[FAQ_aMule|Version in English]] | [[FAQ_aMule-es|Versión en Español]] | [[FAQ_aMule-it|Versione in Italiano]] | '''Version en Français''' | [[FAQ_aMule-de|Deutsche Fassung]]</center>

==Qu'est-ce que aMule ?== 
*aMule est un client multiplateforme pour le réseau d'ED2k. aMule a commencé a être développé en août 2003, comme extension du client xMule, qui est une adaptation du client eMule. aMule est actuellement développé pour Linux, FreeBSD, OpenBSD, Windows, MacOS X... Il convient de noter que les ports de MacOS X et de Windows ne sont pas encore prêts pour l'utilisation générale. aMule est prévu pour être facile à utiliser, compatible avec le réseau ED2K et les clients eMule. Puisque aMule est basé sur les sources d'eMule, les nouveaux dispositifs dans l'eMule sont progressivement appliqués sur aMule.
*Pour tous problèmes, questions, suggestions, bugs, envie de nous rejoindre, vous avez plusieurs moyens à votre disposition, le site http://www.amule.org/ (regroupant le Wiki, le Portail, le Forum et le BugTracker), vous pouvez aussi nous rejoindre sur l'IRC: #amule sur irc.freenode.net

==Configuration rapide d'aMule==
Allez dans Préférences puis: 
*Paramètres généraux:
** Changez de pseudo c'est mieux ;)
** Intégration dans la barre de tâches, c'est bien aussi
** Le reste est explicite, c'est à vous de voir
*Connexions:
** Limite de la bande passante:
*** Récéption: En fonction de votre connexion internet (mettez 0 pour ne pas limiter la vitesse)
*** Emission: 16kb/s maximum pour tout le monde, sauf si vous êtes dégroupé
*** Taille slots: 3kb/s par défaut
** Capacité de la ligne: mettez les même valeurs que pour la limite de bande passante
** Ports Clients:
*** TCP: 4662(par defaut)
*** UDP: 4672(par defaut)
*** !!! Conseillé de changer les ports, par exemple TCP:4242, UDP:4241, car les FAI brident les ports par défaut :p !!!
** Limite maximun de sources par fichier:
*** 800 c'est bien, mais après c'est une histoire de connexion, moi c'est 1000
** Limite de connexion:
*** La encore c'est une histoire de connexion 2000 par défaut
*Répertoires:
** Répertoire Temp et Incoming:
*** Choisissez la destination des deux répertoires(tout bête)
*** Choisissez vos répertoires pour le partage de vos fichiers
<center>'''Voilà aMule est fin prêt, mettez à jour la liste des serveurs(fenêtre serveur> Mise à jour), et c'est parti'''</center>

==Que signifient les couleurs dans la barre de progression ?==
* '''Sur la liste de téléchargement des transferts:'''
** - Rouge: Aucune source n'a été trouvée sur le fichier.
** - Bleu: Au moins une source a été trouvée sur le fichier. Plus le bleu devient foncé plus le nombres de sources valides est important.
** - Jaune: Parties en cours de téléchargement.
** - Noir: Parties déjà téléchargées.
** - Vert: Quand un fichier est en vert cela signifie qu'il est complètement téléchargé et avec succès (il se trouve alors dans le fichier « incoming »). 
*'''Sur la liste détails des transferts (double-clic sur un fichier):'''
** - Noir: Les clients disposent de cette partie et vous non.
** - Blanc: Les clients ne disposent pas de cette partie.
** - Vert: Vous et le client disposez de cette partie.
** - Jaune: Un client est entrain de télécharger cette partie.
*'''Sur la liste d'envois:'''
** - Noir: La partie a été téléchargée et vérifiée. 
** - Gris: Le client ne dispose pas de cette partie.
*'''Sur la fenêtre de partage de dossier:'''
** - Rouge: Il n'y a aucune demande.
** - Bleu: Plus la barre devient bleue, plus le nombre de demandes est élevé.
*'''Sur les fenêtres de recherche:'''
** - Noir: Le fichier n'a qu'une source ou pas beaucoup.
** - Bleu: Le fichier a beaucoup de sources, plus il est bleu, plus il y a de sources.
** - Rouge: Le fichier est déjà dans la file d'attente de téléchargement.
** - Vert: Le fichier a déjà été téléchargé et vous l'avez entièrement.

==Pourquoi suis je connecté en LowID ?==
*Ce problème peut venir de deux sources différentes:
**Vous disposez d'un firewall sur votre poste, alors il faut que vous ouvriez le port TCP 4662, et le port UDP 4672 (ports par défaut d'aMule) de votre firewall.
**Vous disposez d'un firewall de type NAT sur votre réseau local (style [http://ipcop.org Ipcop]), de la même manière il faut que vous ouvriez les ports TCP 4662 et UDP 4672, mais en plus il faut que vous renseigniez l'adresse IP de votre poste aMule.
*En faisant ça vous ne serez plus connecté en LowID, mais en HighID
*Voici les règles à ajouter dans le fichier /etc/shorewall/rules, puis faire: service shorewall restart (sous root),(pour valider les changements)

# AMULE

ACCEPT net fw tcp 4662 - 
ACCEPT fw net tcp 4662 - 
ACCEPT net fw udp 4672 - 
ACCEPT fw net udp 4672 - 
ACCEPT fw net tcp 4661 - 
ACCEPT fw net udp 4665 - 
ACCEPT net fw tcp 4711 -

==Qu'es-ce que les sources A4AF?==
*Pour faire très simple ce sont des sources inutiles pour le fichier en question, mais qui le sont peut-être pour un autre fichier qui se trouve dans votre liste de téléchargement, c'est pour ça qu'elles sont entre (), en quelque sorte elles restent en standby.
**Vous pouvez soit les forcer en faisant un clic droit+Options avancées+ajouter immédiatemment sur le fichier.
**Vous pouvez les mettre en automatique en faisant un clique droit+Options avancées+Auto. 
*Je reviendrai dessus un peu plus tard ;)

==Les icones utilisés dans aMule==
* '''Statuts des sources'''
** http://www.amule.org/dev-up/Source_1.png - Connecté au client et en transfers.
** http://www.amule.org/dev-up/Source_2.png - Connecté au client et en attente de téléchargement.
** http://www.amule.org/dev-up/Source_3.png - Non connecté à ce client.
** http://www.amule.org/dev-up/Source_4.png - Ce client n'a pas de sources valide à partager.
** http://www.amule.org/dev-up/Source_5.png - Statuts inconnu.

* '''eDonkey Clients'''
** http://www.amule.org/dev-up/Client_aMule.png - [[aMule]]
** http://www.amule.org/dev-up/Client_eDonkey.png - [[eDonkey2000]]
** http://www.amule.org/dev-up/Client_eMule.png - [[eMule]]
** http://www.amule.org/dev-up/Client_Friend.png - [[Client]] est votre [[friend|ami]]
** http://www.amule.org/dev-up/Client_Lphant.png - [[lphant]]
** http://www.amule.org/dev-up/Client_MLDonkey.png - [[mlDonkey]]
** http://www.amule.org/dev-up/Client_Shareaza.png - [[Shareaza]]
** http://www.amule.org/dev-up/Client_Unknown.png - [[Client]] inconnu
** http://www.amule.org/dev-up/Client_xMule.png - [[xMule]]

* '''Commentaire du fichier'''
** http://www.amule.org/dev-up/File_Comment.png - Un ou des commentaire(s) du fichier sont positifs (en majorité).
** http://www.amule.org/dev-up/File_Comment_Bad.png - Un ou des commentaires sont négatifs, il s'agit généralement de Fake, faire une vérification dans ce cas la.

==Une petite Note==
* Plusieurs utilisateur on raporté un problème lors de téléchargement, des ralentissement graphique, plantage... Pour remédier à tous cela, désactivé le mode "Bavard" dans les Préférences > Tweaks. Sinon reportez vous au forum.

 
'''EN COURS DE TRADUCTION ET DE MISE EN PAGE MERCI DE REVENIR''' 
'''Si vous avez des questions sur l utilisation d'aMule pouvant figurer dans cette FAQ mettez-les dans ce [http://forum.amule.org/thread.php?threadid=3947&boardid=43&sid= Forum] Merci

 http://thelinuxfr.org/ | [[User:Thelinuxfr|Thelinuxfr]] 12:43, 20 Nov 2004 (CET)

FAQ aMule-es

2004-11-26T13:29:03Z

84.128.98.219:

<center><h4>F.A.Q de [[aMule]]</h4> 
<h2>por [[User:Jacobo221|Jacobo221]] (Traducido por ''[[User:Kno|KNO]]'')</h2> 
[[FAQ_aMule|Version in English]] | '''Versión en Español''' | [[FAQ_aMule-it|Versione in Italiano]] | [[FAQ_aMule-fr|Version en Français]] | [[FAQ_aMule-de|Deutsche Fassung]]</center>

== ¿Qué es aMule? ==
'''''aMule es un cliente multiplataforma para la red de compatición de archivos ED2K basado en el cliente de windows [[eMule]].''''' 
aMule comenzó en Agosto de 2003 como una variante de [[xMule]], que es una variante de [[lMule]].

Actualmente soporta Linux, FreeBSD, OpenBSD, Windows, MacOS X adn X-Box en ordenadores de 32 y 64 bits. Hay que señalar que las versiones para MacOS X y Windows todavía no están preparadas para el uso general.

[[aMule]] pretende ser tan fácil de usar y con las mismas carácterísticas que [[eMule]] y pretende mantener la mísma estética que [[eMule]], para que los usuarios familiarizados con [[aMule]] o [[eMule]] puedan cambiar entre ellos de forma fácil.

Como [[aMule]] está basado en el código de [[eMule]], las nuevas carácterísticas de [[eMule]] que son añadidas a [[eMule]] pronto lo son también en [[aMule]], así que sus usuarios pueden estár en la cresta de la ola en cuanto a clientes ED2K.

La mejor parte es que está desarrollado por un gran equipo que lo intenta hacer más fácil de usar (si es posible), asi que entra en el canal #amule de irc.freenode.net o visita el [http://www.amule.org/amule foro de amule] si tienes alguna sugerencia, pregunta, fallo, parche o cualquier otra cosa que pienses sobre el.

Si estás interesado en unirte al equípo de desarrollo por favor contacta con nostros a través de el [http://www.amule.org/amule foro de amule] o en el canal de IRC.

== ¿Cómo veo los créditos de un cliente? ==
Puedes ver los créditos de cualquier cliente (los créditos que tu le debes) pinchando con el botón derecho sobre su nombre y seleccionando "Mostrar Detalles". No se muestra un solo valor, si no que puedes ver el total de datos que el cliente te ha enviado o el Modificador de Créditos (DE/SU Modificador). En la misma ventana, si ese cliente está en tu cola de subida, puedes ver su Clasificación y Puntuación.

== ¿Qué significan los colores de la barra de progreso? ==
En la lista de descargas: 
Rojo: Las Partes(Chunks) en rojo, son partes que no se han encontrado en la presente sesión. 
Azul: Las Partes en azul son partes de las que se tiene al menos una fuente. Cuanto mas oscuro es el azul mas fuentes están disponibles. 
Amarillo: Las Partes en amarillo son partes que están siendo descargadas en este mismo momento. 
Negro: Las Partes en negro son partes que ya han sido descargadas y verificadas. 
Verde: Cuando un archivo está en verde, significa que el archivo ha sido completamente descargado y correctamente verificado (asi que debe de estar en el directorio Incoming). 
En la lista de descargas extendida (se puede ver haciendo doble click en una transferencia): 
Negro: Parte que el cliente tiene y tú no. 
Blanco: Parte que el cliente no tiene. 
Verde: Parte que el cliente tiene y tú también. 
Amarillo: Parte que te estás descargando de ese cliente. 
En la lista de subidas: 
Negro: El cliente ha completado y verificado esa parte. 
Gris: El cliente no tiene esa parte.. 
Ten en cuenta que no todos los clientes soportan el decir a otros clientes que partes han completado cuando estan subiendo, asi que algunos clientes no tendrán barra. 
En la ventana de archivos compartidos: 
Rojo: Cuando no se han encontrado fuentes que tengan esa misma parte (a parte de tí, por su puesto). 
Azul: Cuanto más oscuro es el azul, más compartida está esa parte. 
En la ventana de búsqueda: 
Negro: Los archivos en negro son los que solo se ha encontrado una fuente. 
Azul: Los archivos que tienen dos o mas fuentes. Cuanto más oscuro mas fuentes se han encontrado. 
Rojo: Los archivos que ya están en la cola de bajada. 
Verde: Los archivos que ya tienes compartiendo (los has descargado completamente).

== ¿Qué son todos esos iconos? ==
Lea la sección "Icons and what they signify" en la guía [[Getting Started]].

== ¿Qué significan los números entre paréntesis en la ventana de búsqueda? ==
Esos son los clientes que tienen el archvo completo. Incluso si el número entre paréntesis es 0, no singifica que nadie tenga el archivo completo, únicamente quiere decir que nadie ha marcado el archivo como "completado" (muchos clientes no lo hacen). Así pues, es una manera de tener una idea aproximada de cuanta gente tiene el archivo completo, pero no debe tomarse como una cantidad precisa.

== ¿Qué significan todos esos números en la columna de fuentes en la ventana de tráfico? ==
El formato de las fuentes es XX/YY + ZZ (WW) donde 
XX es el número de fuentes disponibles (el número de fuentes desde las que puedes descargar). 
YY es el número de fuentes encontradas (el total de fuentes encontradas). 
ZZ es el número de fuentes a las que se ha pedido otro archivo ("Asked for another file") 
WW es el número de fuentes desde las que se está descargando alguna parte en este momento.

== ¿Qué significan todos esos números en la columna prioridad en la ventana de descargas con una descarga expandida? ==
Esta es la puntuación que tienes para ese archivo. No todos los clientes proporcionan esa información, así que en algunos casos, no se visualizará. 
El número entre parentesis es la cantidad de posiciones que te has "movido" en la cola del cliente. Números '''negativos''' son posiciones que tu has '''ganado''' en la cola y los números '''positivos''' son posiciones que has '''perdido''' desde que fuiste añadido. Fijaté que cuando un número es negativo se visualiza en azul y cuando es positivo se visuliza en rojo.

== ¿Por qué hay dos tasas de transferencia en la lista de subidas? ==
Cuando estás subiendo algún archivo a algún cliente, la lista de subidas muestra la tasa de transferencia (la velocidad en KBps) a la que estás enviando datos a ese cliente. Si, al mismo tiempo, ese cliente te está enviando un fichero (o ficheros), entonces el formato de la tasa de transferencia cambiará a XX/YY donde XX significa la velocidad a la que le estas enviando el fichero e YY es la velocidad a la que te está enviando a él a tí. Si buscas en la lista de descargas encontrarás a ese cliente. 
Esto es útil si estás intentando obtener un archivo raro, poruqe así puede encontrar a los clientes que te están dando datos, y si es un archivo raro, puedes ponerle un slot de amigo, para subir a ese cliente más rápidamente y ganar más créditos en esos clientes (y por consiguiente, bajar más rápido desde ellos).

== ¿Qué es A4AF? ==
A4AF significa en Inglés ''Ask For Another File'' y en español viene a ser algo como ''Pedido Otro Archivo''. Es una manera de optimizar una descarga específica. 
Cuando intentas descargar un archivo, aMule obtiene una lista de clientes que están compartiendo ese archivo. Algunos clientes pueden compartir también algún otro archivos que estás intentando descargar, así que tendrás a ese cliente en dos colas de descarga separadas. 
A4AF intenta eliminar esta situación. ¿Por qué? Porque no puedes descargar dos chunks al mismo tiempo desde el mismo cliente. 
A4AF funciona de la siguiente manera: 
Cuando se obiene la lista de clientes que tienen un determinado archivo, si alguno de estos clientes ya está en otra cola de descargas esos clientes se marcarán como A4AF y se indicará en la columna de fuentes con un '''+ XX''' donde XX el número de clientes en esta situación. 
¿Qué puedes hacer en este momento? 
Puedes favorecer unas descargas (en detrimento de otras) de la siguiente manera: 
Pinchando en una descarga con el botón derecho, en '''Opciones Extendidas''' tienes tres opciones relacionadas con A4AF que te permiten lo siguiente: 
'''Intercambiar todas las fuentes (A4AF) a este archivo''': Si hay algún cliente al que se le ha pedido una parte de otro archivo y tiene también éste, se cancelará esa petición y se le pedirán partes de éste. 
'''Intercambiar todas las fuentes (A4AF) a este archivo (Auto)''': Ejecutará la orden anterior periodicamente, de esta forma si se descubren fuentes nuevas, se asignarán a este archivo. 
'''Intercambiar todas las fuentes (A4AF) a otro archivo''': Al revés de las opciones anteriores, con esta conseguimos que se envien peticiones de los otros archivos en detrimento del seleccionado. 
Esta última opción también se puede establecer en las preferencias, para que se envien todas las fuentes A4AF a otros archivos automaticamente cuando esa fuente no tiene partes necesarias de ese archivo. 

== ¿Cual es la diferencia entre Transferido y Completado en la ventana de Tráfico? ==
Transferido muestra los datos que has recibido de ese archivo. Estos datos hasn sido descargados en un formato comprimido. Una vez que los datos están en tu máquina, amule los procesa y los descomprime. El total de datos útiles que pueden ser usados de los datos recibidos (esto es, las partes de esos datos que son partes reales del archivo que estás intentando descargar y no son cabeceras o cosas de esas) es la cantidad que puedes ver en la columna de Completado.

== ¿Cual es la diferencia entre pausar y parar una descarga? ==
Cuando se pausa una descarga, se rompen todas las conexiones referentes a la descarga pausada con los clientes, de manera que no se transfiera información, pero no se pierden los datos de estos clientes, de manera que, cuando se desee continuar la descarga, aMule tratará de conectar con esos mismo clientes de quienes estaba transfiriendo.
En cambio, cuando se para una descarga, la información sobre esos clientes se pierde, de manera que cuando se desee continuar con la descarga aMule deberá buscar previamente clientes que estén compartiendo ese archivo para después solicitarlo.

== ¿Qué son todos esos archivos que aMule créa la primera vez que se ejecuta? ==
La mayoría son los mismos que los de eMule. Aquí hay una lista del significado de cada uno (ten en cuenta que puedes no tener todos en tu disco duro): 
~/.eMule: Configuración personal de aMule (esto es, cosas como tu Alias, tus directorios Temp e Incoming, tus límites de subida y bajada, etc...). 
~/.aMule/addresses.dat: Contiene la lista de URLs con listas de servidores a comprobar (si está activado en la Preferencias) cada nueva ejecución. 
~/.aMule/amulesig.dat: Este es el archivo que contiene la firma online de aMule, que es el mismo que la firma de eMule (ver onlinesig.dat abajo) pero con información extendida (que incluye alias, bytes descargados y subidos por sesión y totales, la versión de aMule, el tiempo de ejecución de aMule y el número de archivos compartidos). 
~/.aMule/aMule.tmpl: Ésta es la plantilla que usa el servidor web de aMule para crear la página web. 
~/.aMule/aMule-online-sign.png: Este archivo solo existe si CAT ha sido ejecutado alguna vez con el modificador -o y ~/.aMule/casrc ha sido correctamente configurado. Esta imagen contiene detalles del estado de aMule. 
~/.aMule/casrc: Este archivo solo existe si CAS ha sido ejecutado con el modificador -o. Contiene la configuración de la creación de imagenes de CAS. 
~/.aMule/clients.met: Contiene los creditos de los clientes de los que has obtenido datos y su user hash. 
~/.aMule/cryptkey.dat: Contiene la clave RSA única de 384 bits para tu cliente. 
~/.aMule/emfriends.met: Contiene la configuración de la lista de tus amigos. 
~/.aMule/ipfilter.dat: Este archivo contiene los rangos de IPS y los niveles de restriciones que deben ser pasados a ipfilter. 
~/.aMule/Incoming: Por defecto, el directorio donde aMule guardará los archivos completados. 
~/.aMule/known.met: Este archivo guarda el hash y algunos detalles de tus archivos compartidos como el tamaño, la ruta, las estadisticas, etc... 
~/.aMule/known2.met: Este archivo guarda los hashes [[AICH]] verificados de tus archivos compartidos.
~/.aMule/lastversion: Este es solo para que aMule sepa si es la primera vez que arrancas aMule, si tenias aMule instalado de antes y que versión tenias instalada. 
~/.aMule/logfile: Este archivo contiene el log de la última ejecución de aMule. 
~/.aMule/muleconn: Este archivo es un socket para las comunicaciones de aMule. 
~/.aMule/onlinesig: Este es el archivo de firma online compatbile con eMule. Se usa con otras aplicaciones para saber información básica sobre las estadísticas de aMule (si esta conectado, en que servidor está conectado, las tasas de subida y bajada, los clientes en la cola). 
~/.aMule/preferences.dat: Contiene el hash de usuario, que es el valor único que te identifica en la red ED2K y que se usa para evitar trampas con los créditos y con listas de amigos. 
~/.aMule/server.met: Esta es la lista de todos los servidores conocidos y tus preferencias con ellos (prioridad, nombre, ip, puerto e así). 
~/.aMule/shareddir.dat: Guarda las rutas de todos los directorios compartidos. 
~/.aMule/Temp: Por defecto, es el directorio donde aMule guarda las descargas no completadas (archivos temporales). 
~/.aMule/webserver: Este directorio contiene los archivos necesarios para que el servidor web de aMule visualice una bonita página. 
Otros archivos en ~/.aMule/ seguramente son copias de seguridad de los archivos anteriores. 
También, en el directorio Temp (que es ~/.aMule/Temp por defecto pero se puede poner otro en las Preferencias), aMule creará, para cada una de tus descargas: 
*.part: Este archivo contiene las partes descargadas (no los chunks (partes en las que se divide una descarga) ya que los chunks incompletos también se guardan aquí). Como aMule es capaz de descargar desde más de un usuario al mismo tiempo, este archivo tiene el tamaño del archivo completo. Las partes que no han sido descargadas se rellenan con ceros. 
*.part.met: Este archivo contiene información sobre las partes descargadas, los chunks verificados, los valores hash de los chunks que quedan, etc... 
*.part.met.bak: Esto son copias de seguridad de los archivos *.part.met. aMule crea esta copia de seguridad porque sin el fichero *.part.met, no puede llevar a cabo la descarga. Si "desaparece" algún *.part.met, debers renombrar el *.part.met.bak a *.part.met. 
*.part.met.seeds: Este archivo solo existe si has habilitado, en las preferencias, que se guarden algunas fuentes de archivos raros para que se puede intentar conectar a estas fuentes en la próxima ejecución de aMule.

== ¿Puedo usar los ficheros de configuración de eMule y viceversa? ==
La mayor parte de ellos sí. Lo único que no pueden compartir aMule y eMule son la configuración del programa (preferences.ini en eMule y ~/.eMule en aMule). Todos los ficheros relacionados con la red ED2K pueden ser compartidos entre las dos aplicaciones sin mucho esfuerzo copiándolo en el directorio ~/.aMule desde el directorio de eMule y viceversa. Pero tienes que tener en cuenta que algunos archivos en el directorio ~/.aMule son específicos de aMule, como amulesig.dat o aMule.tmpl, así que es mejor mover sólo los archivos que están en los dos directorios.

== ¿Que son todas esas cosas en amulesig.dat y en onlinesig.dat? ==
Supongo que ya habrás leido qué son amulesig.dat y onliesig.dat más arriba. Así que este es el significado de su contenido (ten en cuenta que si aMule se cuelga, el contenido de ambos archivos sea el último estado escrito): 
onlinesig.dat 
Se compone de dos líneas separadas de un carácter de fin de línea (sin carácter de retorno de carro). La primera, cuando aMule está desconectado, contiene un 0 (cero) y nada más, pero cuando aMule está conectado contene un 1 (número uno) seguido por un | (el carácter de tubería) el nombre del servidor al que estás conectado seguido por un caracter de tubería, la IP del servidor al que estamos conectados otro carácter debería y finalmente el puerto al que estás conectado en ese servidor. 
La segunda linea contiene, en este orden, la tasa de descarga, la tasa de subida y el número de usuarios en la cola, con un caracter de tubería ('|') entre ellos . 
La segunda línea '''no''' termina con un carácter de fin de línea.
Cuando aMule se cierrra correctamente la segunda línea contiene la misma estructura pero rellena de ceros, mientras que la primera linea contiene un único cero. 
amulesig.dat 
La firma de aMule es mucho mas poderosa que la de eMule y tiene muchas mas lineas y campos. Su estructura es: 
La primera línea contiene un 0 (cero) si amule está desconectado o ha sido correctamente cerrado, un 1 (número 1) si esta conectado o un 2 si está conectandose (solo desde aMule2.0.0-rc4). 
La segunda, tercera y cuarta lineas contienen el nombre, la IP y el puerto del servidor al que aMule está conectado (en ese orden) o un 0 si se ha cerrado correctamente. Desde la versión aMule2.0.0-rc4 tambíen contendrán 0 si aMule está conectandose. 
La quinta linea contiene una H mayúscula o una L mayúscula dependiendo de si aMule está conectado con ID alta o con ID baja. Si amule está desconectado o se ha cerrado correctamente contiene un cero. De nuevo, desde la versión aMule2.0.0-rc4 tambíen contendrán 0 si aMule está conectándose 
La sexta y séptima líneas contienen la velocidad a la que aMule está descargando y subiendo respectivamente. Desde la versión aMule2.0.0-rc4, ambas líneas contienen "0.0" cuando aMule ha sido cerrado correctamente. 
La octava y novena líneas contienen el número de clientes en la cola de subidas y el total de archivos compartidos respectivamente. Desde la versión aMule2.0.0-rc4, ambas lineas se ponen a cero cuando amule se cierra correctamente.. 
La décima linea contiene el alias del usuario. 
La undécima y duodécima lineas contienen el total de bytes descargados y subidos respectivamente.. 
La decimotercera línea contiene la versión de aMule. 
La decimocuarta y decimoquinta lineas contienen el total de bytes descargados y subidos en la sesión actual respectivamente. Desde la versión aMule2.0.0-rc4, se ponen a 0 cuando aMule está conectándose o se ha cerrado correctamente. 
La decimosexta línea (y última) contiene el tiempo total que amule ha estado funcionando. Estará seguido por un espacio y "secs" "mins" o "hours" dependiendo del valor (la misma abreviación de tiempo que esté configurada en el idioma elegido). Desde la versión aMule2.0.0-rc4, si aMule se está conectando o ha sido correctemante cerrado contendrá 00 seguido de la abreviatura "seg" (o la que corresponda en el idioma elegido). 
La última línea tiene que estar seguida por un caracter de nueva linea('\n').
nata

== Acabo de instalar aMule por primera vez. ¿Cómo lo configuro? ==
Configurar aMule correctamente es cuestion de gustos y depende de muchos factores. Si solo quieres una configuración rápida, continúa leyendo. 
Abre aMule y pincha en el botón de Preferencias. Pon un alias y el lenguaje en el que deseas tener aMule. Cambia a la pestaña Conexión e introduce la capacidad de tu linea. Después introduce el límite de ancho de banda de acuerdo con lo que quieras que use aMule. Cambia a la pestaña Directorios e introduce el directorio para los archivos temporales (donde se guardarán los archivos hasta que se hallan descargado completamente) y donde se guardarán los archivos completados (incoming). Finalmente, seleciona los directorios que quieres compartir. No es recomendable compartir muchos archivos. Lee más abajo "Cuales son las mejores configuraciones para tener una buena tasa de descarga". Para selecionar recursivamente todos los directorios dentro de un directorio concreto, lee [[aMule_problems-es#¿Hay_alguna_manera_de_seleccionar_recursivamente_un_directorio_entero_y_todo_su_contenido?|¿Hay alguna manera de seleccionar un directorio completo y todo su contenido?]].

== ¿Detecta [[aMule_Project_FAQ:About|aMule]] la configuración de [[xMule]] y [[lMule]]? ==
Sí. [[aMule_Project_FAQ:About|aMule]] detecta la configuración de ambos programas y la incorpora como propia pero con diferencias: 
[[lMule] es un proyecto muerto, del que proviene [[aMule_Project_FAQ:About|aMule]]. Como tal, [[aMule_Project_FAQ:About|aMule]] supone que el usuario está reemplazando [[lMule]] por [[aMule_Project_FAQ:About|aMule]], de modo que renombra ~/.lMule a ~/.aMule, conservando así la configuración y archivos de [[lMule]]. Si los directorios temporales y de descarga eran ~/.lMule/Temp y ~/.lMule/Incoming respectivamente, deberá modificarlos en Preferencias por ~/.aMule/Temp y ~/.aMule/Incoming respectivamente. 
[[xMule]] se declaró proyecto muerto en Mayo del 2004 (según una carta publicada por el principal desarrollador de [[xMule]] en la página web, inexistente en la actualidad, [http://www.xmule.org http://www.xmule.org]), sin embargo, por motivos históricos, no se procede de igual manera que con [[lMule]]. En su lugar, se toman los archivos de configuración de [[~/.xMule]] y se emplazan en ~/.aMule de modo que si los directorios temporales y de descarga eran ~/.xMule/Temp y ~/.xMule/Incoming respectivamente, seguirán siéndolos. En ese caso, es recomendable mover esos directorios a ~/.aMule/ y configurar correctamente los emplazamientos en Preferencias.

== ¿Como comienzo mi andadura con aMule? ==
Solo pincha en el botón Conectar. Deberías tener algunos servidores en la lista de servidores. Si no tienes ningún servidor, entonces pincha en el pequeño botón debajo del botón Conectar en la ventana de servidores antes de pinchar en botón Conectar. Despues de un tiempo, amule estará conectado a algún servidor (lo sabrás porque en la esquina inferior izquierda desaparecerá el mensaje de "No Conectado"). Cuando estés conectado, cambia a la ventana de "Busqueda" y busca el fichero que quieras y una vez lo encuentres haz doble click en él. 
Para conocer más sobre el uso de aMule, entra en el canal #amule de irc.freenode.net o pregunta en los [http://www.amule.org/amule foros de amule].

== ¿Cual es la mejor configuración que puedo poner para tener una buena tasa de descarga? ==
Si quieres decir "¿Hay algún limite en la red ED2K?" tienes que ver, que si tu proveedor lo permite, lo mejor que puedes hacer es opner el limite de subida a un mínimo de 10 KBps. Si quieres decir "¿Que es todo eso sobre créditos, tasa y puntuación?" tienes que entender que cuanto más subas, mas bajarás, asi que pon el límite de subida tan alto como puedas, comparte archivos muy conocidos y populares (no compartas mucho (no mas de unos 200 archivos) o serás baneado de algunos servidores por crear mucho tráfico) e intenta compartir archivos pequeños y populares ya que los clientes ED2K dan créditos extras por obtener un archivo pequeño completo. Un buen truco (gracias kaouete) es que cuando estás intentando bajar algun archivo raro o de los que nunca terminan de descargarse, cuando veas que alguien está cogiendote una parte de eser achivo, dale a ese cliente un slot de amito, para que, si intenta coger algo de ti, le de preferencia y obtengas más créditos de ese cliente.

== ¿Hay alguna manera de abrir un archivo de texto y cargar todos los enlaces ed2k del archivo? ==
Sí, la hay. Sencillamente introduce todos loes enlaces ed2k en un archivo de texto, cada enlace en una linea distinta. Ponle al archivo de nombre ''ED2KLinks'' a cotninuación colocalo en el directorio ''~/.aMule'' y aMule automáticamente lo detectará, agregará todos los enlaces ed2k contenidos en él en la cola de descarga y eliminará el archivo.

== ¿Puedo controlar aMule de forma remota, atraves de telnet igual que hago con eDonkey? ==
Si que puedes, pero no exactamente de la misma manera que con eDonkey. Lo primero es iniciar una sesión telnet (o ssh) con el ordenador donde se está ejecutando aMule y una vez dentro, usa amulecmd para tomar el control de aMule. Para iniciar nuevas descargas usa el comando ed2k. Recuerda que amulecmd debe ser configurado. 
Otra interesante utilidad de aMule que te puede interesar es CAS (cuyo comando es <code>cas</code>) que muestra las estadísticas básicas de aMule. 
También, el servidor web de aMule puede ser lo que estas buscando si puedes y no te importa usar un navegador en el cliente. Ten en cuenta que el servidor web de aMule también debe ser configurado.

== ¿Hay alguna forma de arrancar aMule sin interfaz gráfica? ==
Sí. Desde aMule 2.0.0-rc6, existe aMule Deamon, que puede ejecutarse desde la linea de comandos a través del comando ''amuled''. Para controlarlo, usa aMuleWeb, aMuleCMD o cualquier otra aplicación de control remoto para aMule.

De todas maneras, antes de aMule 2.0.0-rc6, [[aMule_Project_FAQ:About|aMule]] era una aplicación monolítica. Esto significa que el código principal y el GUI eran un bloque inseparable (aunque se están haciendo algunos esfuerzos en separar el código principal del GUI).

Así pues, para aquellos que usen una versión antigua de aMule yo que rechacen la idea de usar aMuled (aMule Daemon), hay dos formas de ejecutar aMule desde la línea de comandos, pero ninguna de ellas es un camino directo:

*Usando ''[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]''
*Usando ''[http://www.realvnc.com VNC]''

'''Usando [http://xfree.org/4.4.0/Xvfb.1.html Xvfb]''' 
Debes ejecutar<code>xvfb</code> y entonces ejecutar aMule. Después puedes tomar el control de aMule usando amulecmd y ed2k de la misma manera que si estuvieses accediendo a amule de forma remota con un telnet o ssh (ver más arriba). Si necesitas ayuda con este tema, pregunta en los [http://www.amule.org/amule foros de aMule].

'''Usando [http://www.realvnc.com VNC]''' 
Es posible usar ''vncserver'' en vez de ''Xvfb'' para conseguir un resultado similar. Simplemente es necesario instalar el paquete ''vncserver'' y ejecutar ''vncserver :0 -geometry 1024x768'', seguido de ''export DISPLAY=:0''. Esto arrancará un servidor X oculto, accesible únicamente de forma remota usando un cliente VNC. Una vez el servidor X está en marcha, será necesario un gestor de ventanas para gestionar la ventana de aMule (bueno, no es estrictamente necesario, pero es útil para poder cerrar aMule sin tener que matar el proceso), personalmente recomiendo [http://fluxbox.sourceforge.net FluxBox] debido a sus bajos requerimientos de memoria y CPU. Simplemente hace falta arrancarlo con ''fluxbox &'' y a continuación arrancar aMule con ''amule &''. Ahora ya es posible conectar al servidor VNC y ver la ventana de aMule en nuestro servidor virtual.

Un detalle a tener en cuenta es que si aMule muestra algún diálogo que requiera interacción con el usuario (como el que se muestra nada más instalar el programa), se quedará ahí esperando hasta que alguien se conecte por VNC al servidor X y haga click en ''Aceptar''. Normalmente, ésto es sólo necesario hacerlo una vez (y de paso se puede aprovechar para actualizar la lista de servidores y configurar las preferencias del programa), a partir de ahí aMule arrancará sin necesidad de interacción alguna, simplemente mostrando algunos mensajes informativos al arrancar.

== ¿Puedo ejecutar dos instancias de aMule al mismo tiempo? ==
Si puedes, pero no es recomendado. aMule solo comprueba si el usuario actual está ejecutando alguna instancia de aMule, asi que puedes ejecutar tantas instancias de amule como cuentas de usuario tengas acceso. Para hacer esto, ejecuta <code>xhost +</code> y entonces <code>su</code> como otro usuario y ejecuta aMule desde ese shell. 
Ten cuidado, ya que aMule no puede comprobar si un usuario está ejecutando aMule en otra sesión de X. Asi que, si tu cuenta está ejecutando una instancias de aMule en otra sesión de X, no ejecutes otra instancia de aMule en otra sesión de X o puede que acabes perdiendo la configuración y con partes corruptas.

== ¿Cómo puedo obtener esas bonitas estadísticas que algunos postean en los canales de IRC? ==
Puedes copiar y pegar la salida de CAS (C aMule Statics-Estadisticas de aMule en C) (para ejecutar CAS, pon <code>cas</code>) o si usas xChat como cliente de IRC y tienes el módulo de Perl instalado puedes usar XAS (xChat aMule Statics).

== ¿Qué es Slot Allocation? ==
Cada upload es un slot, así pues, si estás subiendo a cinco clientes al mismo tiempo, tienes cinco slots establecidos. Así pues, el Slot Allocation es el ancho de banda que se reserva para cada cliente al que se sube. 
Por ejemplo, si tu limite de subida es de 20KBps, puedes establecer el Slot Allocation a 2KBps de manera que 10 clientes puedan descargar de tí al mismo tiempo, cada uno de ellos a una velocidad máxima de 2KBps. 
Lease la sección " Why is aMule ignoring the bandwith I set per slot?" en [[AMule_problems-es|Problemas más comunes en aMule]].

== ¿Qué es un puesto reservado de amigo? ==
Un puesto de amigo es un puesto que es asignado a un cliente de la lista de amigos. Un amigo solo puede tener un puesto al mismo tiempo. Cuando un amigo (que tiene habilitado un puesto de amigo) intenta descargarse un archivo de tí, se le asignará una prioridad más alta en las colas de subida, porque el tiene ese puesto siempre asignado. Mientra ese amigo no esté descargando, ese puesto reservado se dará al siguiente cliente en la cola.

== ¿Cual es el verdadero significado de Capacidad en Preferencias? ¿No se debería preocupar aMule únicamente de los Límites? ==
En realidad aMule solo se preocupa de los Límites. La Capacidad solo se usa para visualizar las Estadísticas. Verás: Imagina que tienes una conexión de 100KBps, imagina que quieres establecer el Límite a 40KBps porque tienes un servidor web que necesita un mínimo de 60KBps para satisfacer todas la peticiones. Ahora imagina que descargas canciones indonesias raras y gratuitas. Lo más seguro es que nunca descargas a más de 3KBps. Así que puedes establecer la Capacidad a 5KBps para que los gráficos de las Estadísticas tengan algún significado, ya que la lo pones a 100KBps, el gráfico solo mostrará una linea horizontal sin significado alguno.

== aMule se cuelga mucho. ¿Puede configurarlo para que se reinicie cada vez que se cuelgue? ==
No, no puedes. Pero puedes hacerlo empleando algún script. Algunos de estos scripts incluso detectan cuando aMule se ha bloqueado '''bloqueado''', sin que se haya cerrado, y lo reinician. 
Así pues, probablemente los siguientes scripts estén a la altura de tus necesidades: 
[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]

== ¿Puedo obtener datos de aMule por la entrada standard para pasarlos a GDB o Valgrind? ==
Sí, sí que puedes. Hasta la versión 2.0.0.rc3 de aMule no estaba permitido, pero desde la versión 2.0.0-rc4 puedes hacerlo con el parámetro ''-i'' o ''--enable-stdin''. 
En cualquier caso, la gente con versiones de aMule anteriores a la 2.0.0-rc4 pueden usar [http://www.amule.org/amule/thread.php?threadid=2474 el patch de phoenix para habilitar la entrada standard].

== Como puedo migrar de eMule a aMule sin perder mis créditos? ==
Si ya has leido [[FAQ-es#%C2%BFQu%C3%A9_son_todos_esos_archivos_que_aMule_cr%C3%A9a_la_primera_vez_que_se_ejecuta?|el significado de los archivos de aMule]], probablemente imaginarás la respuesta: 
Coje los archivos ''cryptkey.dat'', ''clients.met'' y ''preferences.dat'' del directorio de configuración de eMule (normalmente, en Windows, es algo como ''C:\Archivos de programa\eMule\config'') y copialos a ''~/.aMule''. A continuaciñon arranc aMule para que lea los archivos. Ya está!

== ¿Qué es toda esta historia sobre el [[rabbit|conejo]]? ==
Ah, si, todo esto empezó... ehm... bien... quiero decir... sigue al [[rabbit|conejo]] blanco;-)

FAQ aMule-it

2004-11-26T13:28:04Z

84.128.98.219:

<center><h4>F.A.Q on [[aMule]]</h4> 
<h2>by [[User:Jacobo221|Jacobo221]] (Tradotto da ''[[User:SNeo|sNeo]]'')</h2> 
[[FAQ_aMule|Version in English]] | [[FAQ_aMule-es|Versión en Español]] | '''Versione in Italiano''' | [[FAQ_aMule-fr|Version en Français]] | [[FAQ_aMule-de|Deutsche Fassung]]</center>

== Che cosè aMule? ==
'''aMule è un client multipiattaforma per la rete di file sharing ed2k, basato sul client windows eMule.''' 
Il progetto aMule inizia nell'Agosto del 2003 come un fork di xMule, che è a sua volta un fork di lMule. 
Correntemente suppurta Linux, FreeBSD, OpenBSD, Windows, MacOS X e X-Box sia sui computer a 32 che a 64 bit. Da notare che i ports su MacOsX e Windows non sono ancora pronti. 
aMule è progettato per essere user-friendly e feature-plenty come eMule e per rimanere fedele al look di eMule, così gli utenti possono intercambiare senza problemi aMule e eMule. 
Da allora aMule è basato sul codice di base di eMule, le nuove caratteristiche di eMule tendono a trovare la loro strada verso aMule subito dopo che sono state incluse in eMule, di modo che gli utenti di aMule possono aspettarsi di avere i clients ED2K più aggiornati. 
E' sviluppato da una grande squadra che rendono aMule il più possibile user-friendly, entra in #amule su irc.freenode.net o visita il forum se hai qualsiasi suggerimenti, domande, problemi, bugs, patch o qualsiasi altra cosa. 
Se sei interessato ad entrare nel team di sviluppo, contattaci attraverso il forum o nel canale IRC.

== Come vedo i crediti del client? ==
Puoi vedere qualsiasi crediti dei client (i crediti che hai nei suoi confronti) cliccando con il destro sul suo nome e selezionando Mostra Dettagli. Non c'è un valore specifico che mostra l'ammontare totale dei dati che il client ti ha mandato o il Modificatore dei Crediti (che è chiamato Modificatore DL/UL). In quella stessa finestra di dialogo, se quel client è nella tua coda di upload, potrai vedere il giudizio e il punteggio di upload. 

== Cosa significano quei colori nella barra del download? ==
Nella barra di download: 
'''Rosso:''' I chunk in rosso sono chunk senza fonti nella sessione corrente. 
'''Blu:''' I chunk in blu sono i chunk con almeno una fonte avviabile. Più è blu e maggiori sono le fonti trovate. 
'''Giallo:''' I chunk in giallo sono i chunk che stanno per essere scaricati in quel momento. 
'''Nero:''' I chunk in nero sono i chunk che sono già stati scaricati e verificati. 
'''Verde:''' Quando un file è in verde significa che è stato completamente scaricato e verificato con successo (e si troverà nella cartella Incoming). 
Nella lista estesa dei trasferimenti (facendo doppio click su un trasferimento): 
'''Nero:''' I chunk che quel client ha e tu no. 
'''Bianco:''' I chunk che quel client non ha. 
'''Verde:''' I chunk che hai in comune con quel client. 
'''Giallo:''' I chunk che quel client ti sta correntemente inviando. 
Nella lista dell'upload: 
'''Nero:''' Quel client ha completato e verificato quel chunk. 
'''Grigio:''' Quel client non ha quel chunk. 
Prendete in considerazione che non tutti i client supportano questa funzione: mostrare le parti scaricate nella barra dell'upload. 
Nella finestra dei file condivisi: 
'''Rosso:''' Quando non ci sono fonti ad avere lo stesso chunk (a parte te). 
'''Blu:''' Più è blu e più è diffuso quel chunk. 
Nelle finestre di ricerca: 
'''Nero:''' I file in nero sono quelli che hanno solo un client 
'''Blu:''' I file in blu sono quelli con due o più client. Più è blu e maggiori sono i client ad avere quel file. 
'''Rosso:''' I file in rosso sono quelli che hai già nella coda dei download. 
'''Verde:''' I file in verde sono quelli che tu stai già condividendo (lo hai già completamente scaricato).

== Cosa sono tutte quelle icone? ==
Guarda la sezione "Icons and what they signify" nella guida [[Getting Started]] (al momento solo in inglese).

== Che significano quei numeri nella finestra di ricerca? ==
Sono i client che hanno il file completo. Se il numero è 0, non significa che nessuno ha il file completo, ma significa solo che nessun client ha assegnato "completato" il file. Questi numeri rendono solo un idea approssimativa di quanti utenti hanno il file completo.

== Cosa significano tutti quei numeri nella colonna delle fonti nella finestra dei trasferimenti? ==
Il formato delle fonti è XX/YY + ZZ (WW) dove: 
'''XX''' sono le fonti avviabili (quelle da cui puoi scaricare). 
'''YY''' sono le fonti trovate (il totale delle fonti trovate). 
'''ZZ''' sono il numero delle fonti "richieste per un altro file". 
'''WW''' sono le fonti da cui stai correntemente scaricando. 

== Cosa sono tutti quei numeri nella colonna priorità della finestra trasferimenti? ==
E' il punteggio che hai con quel client di quel specifico file. Non tutti i client danno queste informazioni quindi in alcuni non viene visualizzato nulla. 
Il numero è l'ammontare di posizioni che ti sei "mosso" attraverso la coda di unpload di quel client. I numeri '''negativi''' stanno per le posizioni che hai "vinto" nella coda da quando sei stato aggiunto mentre i numeri '''positivi''' sono le posizioni che hai '''perso''' da quando sei stato aggiunto. Quando il numero è negativo, è visualizzato in blu, invece quando è negativo è visualizzato in rosso. 

== Perchè ci sono due misuratori di velocità nella finestra dell'upload? ==
Quando stai inviando un file ad un client, la lista dell'upload mostrerà la velocità del trasferimento (espressa in KBps) che stai inviando a quel client. Se, nello stesso tempo, quel client ti sta inviando qualche file, allora il formato del trasferimento cambierà in XX/YY dove XX sta per la velocità che stai inviando a quel client e YY per la velocità che il client sta inviando a te. Se ricerchi nella lista dei trasferimenti dei download troverai quel client. 
Quseto è utile se stai provando a scaricare un file raro da un client, allora puoi aggiungerlo nella tua lista amici così guadagnando crediti e scaricando più velocemente quel file.

== Che cosè A4AF? ==
A4AF sta per Ask For Another File. E' un modo per ottimizzare le fonti su uno specifico download. 
Quando provate a scaricare un file, aMule si ricava la lista dei client che stanno condividendo quel file. Alcuni di questi client possono anche condividiere un altro file che voi state provando a scaricare, quindi avrete quel client in due differenti code di download. 
A4AF prova ad evitare queste situazioni. Perchè? Perchè non potete scaricare due
chunk nello stesso tempo dal medesimo client. Funziona in questo modo, settanto
A4AF in uno specifico download, state chiedendo ad aMule di ricercare qualsiasi client che si trovano in coda in quel download che sta anche in un altra coda di download e rimuoverlo dalle altre code. In questo modo, si avranno molte più fonti su quel file. 
Puoi anche settare in modo che A4AF funzioni in modo opposto, cioè dando le fonti agli altri download.

== Qual'è la differenza tra Trasferiti e Completati nella finestra dei trasferimenti? ==
Trasferiti mostra l'ammontare dei dati che hai ricevuto di quel file. Questi dati sono scaricati in un formato compresso. Una volta che i dati vengono scaricati nella tua macchina, aMule li processa e li decomprime. Il totale utile, cioè quello reale senza contare le corruzioni e la compressione, si vede nella colonna Completati.

== Qual'è la differenza tra fare la pausa e lo stop di un trasferimento? ==
Quando un trasferimento è in pausa, tutte le connessioni relative al file in pausa sono ferme quindi non viene trasmesso nulla, ma le fonti non so cancellate, così quando il trasferimento sarà continuato, aMule proverà a collegarsi a queste fonti da dove stava trasferendo. Invece, quando un trasferimento viene stoppato, anche tutte le fonti vengono rimosse, quando si resuma, aMule inizierà la ricerca delle fonti che condividono quel file.

== Cosa sono tutti quei file che aMule crea quando viene avviato per la prima volta? ==
Molti di loro sono gli stessi di eMule. Qui c'è una lista e il significato di ognuno di loro (tieni presente che non devi necessariamente averli tutti nel tuo hard disk): 
'''~/.eMule:''' configurazione personale di aMule (contenente il tuo nickname, le tue cartelle Temp e Incoming, i tuoi limiti di upload e download, e altro...). 
'''~/.aMule/addresses.dat:''' Contiene una lista di URL di server (se attivo nelle Preferenze) da aggiornare i server all'avvio. 
'''~/.aMule/amulesig.dat:''' Questo è il file OnLineSignature di aMule, che è lo stesso di eMule ma con ulteriori informazioni (come nickname, byte scaricati e inviati nella sessione e in totale, versione di aMule, l'uptime di aMule e il numero dei file condivisi). 
'''~/.aMule/aMule.tmpl:''' Questo è il template che il Webserver di aMule usa per creare la pagina web. 
'''~/.aMule/aMule-online-sign.png:''' Questo file esisterà solo se CAS è stato avviato con l'opzione -o e ~/.aMule/casrc configurato. E' un immagine contenete i dettagli dello stato di aMule. 
'''~/.aMule/casrc:''' Questo file esisterà solo se CAS viene avviato con l'opzione -o. Contiene le impostazioni per la creazione dell'imagine di CAS. 
'''~/.aMule/clients.met:''' Contiene i crediti per i client che ti hanno inviato file e l'user hash di questi client. 
'''~/.aMule/cryptkey.dat:''' Contiene una chiave privata RSA a 384 bit per il tuo client. 
'''~/.aMule/emfriends.met:''' Contiene la lista dei tuo amici. 
'''~/.aMule/ipfilter.dat:''' Questo file contiene i range di ip e i livelli di accesso ristretti che saranno passati a ipfilter. 
'''~/.aMule/Incoming:''' Di default, la cartella dove aMule posiziona i download completati. 
'''~/.aMule/known.met:''' Questo file contiene l'hash e altri dettagli dei tuoi file condivisi come la dimensione, posizione, statisctiche, ecc... 
'''~/.aMule/known2.met:''' Questo file contiene i verificati [[AICH]] hashi dei tuoi file condivisi. 
'''~/.aMule/lastversion:''' Questo è solo per permettere ad aMule di sapere se è la prima volta che stai lanciando aMule, se avevate aMule installato da prima e che versione avevate installato precedentemente. 
'''~/.aMule/logfile:''' Questo file contiene il log dell'ultima esecuzione di aMule. 
'''~/.aMule/muleconn:''' Questo file è un socket per le comunicazioni di aMule. 
'''~/.aMule/onlinesig:''' Questo file è compatibile con l'OnLineSignature di eMule. E' usato dalle altre applicazioni per sapere le informazioni base dello stato di aMule (se è online, su quale server è connesso, la velocità di upload e download, e i client in coda). 
'''~/.aMule/preferences.dat:''' Contiene l'hash dell'utente, che è un valore hash che identifica unicamente te nella rete ED2K ed è usato per evitare la truffa dei crediti e delle liste amici. 
'''~/.aMule/server.met:''' Questa è una lista di server conosciuti e le loro preferenze (priorità, nome, ip, porta e altro). 
'''~/.aMule/shareddir.dat:''' Contiene i path di tutte le cartelle condivise. 
'''~/.aMule/Temp:''' Di default è la cartella dove aMule posiziona i file che sta scaricando (file temporanei). 
'''~/.aMule/webserver:''' Questa cartella contiene i file necessari per il WebServer di aMule per visualizzare una buona pagina Web. 
Altri file su ~/.aMule/ sono i backup di alcuni file. 
Anche, nella cartella Temp (che è ~/.aMule/Temp di default ma puo' essere settata un'altra nelle Preferenze), aMule creerà, per ogni download tre o quattro file): 
'''*.part:''' Questo file contiene le parti scaricate del download. Come aMule sa scaricare da più di un utente allo stesso tempo, questo file ha la dimensione del file completo. Le parti non scaricate sono formate da zeri. 
'''*.part.met:''' Questo file contiene le informazioni delle parti scaricate del download, i chunk verificati, il valore hash dei chunk rimanenti, ecc... 
'''*.part.met.bak:''' Questi sono backup del file *.part.met. Se qualche file *.part.met scompare, puoi rinominare il *.part.met.bak in *.part.met. 
'''*.part.met.seeds:''' Questo file esisterà solo se hai attivato, nelle Preferenze, il salvataggio delle fonti dei file rari, così proverà a connettersi a queste fonti nel successivo avvio di aMule.

== Posso usare i file e le impostazioni di eMule e viceversa? ==
Molti di loro si. Gli unici che non puoi condividere tra aMule ed eMule sono i file di configurazione del programma (preferences.ini in eMule e ~/.eMule in aMule). Tutti i file relativi alla rete ED2K possono essere condivisi tra le due applicazioni con solo lo sforzo di copiare i file in ~/.aMule alla cartella di eMule e viceversa. Ma tieni presente che alcuni file in ~/.aMule sono specifici per aMule, come amulesig.dat o aMule.tmpl, dunque è meglio muovere solo questi file che stanno in entrambe le cartelle di aMule e eMule.

== Cosè tutta quella roba in amulesig.dat e onlinesig.dat? ==
Credo che hai già letto sopra cosa siano i file amulesig.dat e onlinesig.dat. Dunque, qui viene spiegato il loro contenuto (tieni presente che se aMule crasha, il contenuto di entrambi i file sarà lo stato dell'ultima scrittura): 
onlinesig.dat 
E' composto da due linee. 
La prima, quando aMule è offline, conterrà uno 0 (zero) e niente altro, ma quando aMule è online, conterrà un 1 (numero uno) seguito da | (il carattere pipe) poi il nome del server in cui si è correntemente connessi seguito dal carattere pipe, poi l'ip del server e il pipe e in finale la porta del server. 
La seconda linea contiene, in questo ordine, velocità di download, di upload e il numero degli utenti in coda, con un carattere pipe ('|') tra ognuno di loro. 
La seconda linea non termina con un carattere di newline ('\n'). 
Quando aMule è chiuso la seconda linea contiene la stessa struttura ma con degli zero. 
amulesig.dat 
Il file signature di aMule è molto più potente di quello di eMule e ha molte linee come campi. La sua struttura è: 
La prima linea conterrà uno 0 (zero) se aMule è disconnesso o completamente chiuso, un 2 se è in fase di connessione (solo da aMule 2.0.0-rc4), o un 1 (numero 1) se è online. 
La seconda, terza e quarta linea contengono the il nome, l'ip e la porta del server dove aMule è connesso (in questo ordine) o un zero se è offline. Da aMule 2.0.0-rc4 conterrà anche uno 0 quando lo stato di aMule è in connessione o è completamente chiuso. 
La quinta linea conterrà una lettera H o una L dipende se aMule è connesso con un alto o un basso ID. Se aMule è disconnesso o chiuso, questa linea conterrà uno zero. Da aMule 2.0.0-rc4 conterrà uno 0 anche se è in fase di connessione. 
La sesta e la settima linea contiene rispettivamente la velocità che aMule sta scaricando e inviando. Da aMule 2.0.0-rc4 entrambe le linee contengono "0.0" quando aMule è pienamente chiuso. 
L'ottava e la nona linea contengono rispettivamente il numero dei client della coda di upload e l'ammontare dei file condivisi. Da aMule 2.0.0-rc4 entrambe le linee sono settate a zero quando aMule è completamente chiuso. 
La decima linea contiene il nickname dell'utente. 
L'undicesima e dodicesima linea contengono rispettivamente l'ammontare totale dei byte scaricati e inviati. 
La tredicesima contiene la versione di aMule. 
La quattordicesima e quindicesima linea contengono rispettivamente l'ammontare dei byte scaricati e inviati nella sessione corrente. 
Da aMule 2.0.0-rc4, entrame le linee saranno 0 se si è in fase di connessione o se il client è completamente chiuso. 
La sedicesima (e ultima) linea contiene l'ammontare del tempo che aMule è in esecuzione. E' seguito da uno spazio tra i valori "sec" min" o "ore" (o altre abbrevazioni della tua configurazione del linguaggio). Da aMule 2.0.0-rc4, se si sta connettendo o è pianamente chiuso conterrà 00 seguito da dall'abbrevazione "sec". 
L'ultima linea deve essere seguita dal carattere di new line ('\n'). 

== Ho appena installato aMule per la prima volta. Come lo configuro? ==
Configuare aMule correttamente dipende da molti fattori. Se desideri solo una configurazione iniziale, allora continua a leggere. 
Apri aMule e clicca su Preferenze. Scegli un nickname e il linguaggio di aMule. Poi clicca sul tab Connessione e inserisci la Capacità della tua linea. Poi immetti i limiti di banda, il massimo che vuoi dare per l'uso di aMule. Poi seleziona il tab Directory e seleziona le cartelle per i file temporanei (dove i file staranno prima di essere completamente scaricati) e i file completati. Infine, seleziona le cartelle che vuoi condividire. E' raccomandato non condividere troppi file. Leggi a riguardo "Quali sono le migliori impostazioni per avere un buon download?". Per selezionare ricorsivamente tutte le cartelle di una certa cartella, leggi [[aMule_problems#Is there any way to recursively select a whole directory and it's contents?|Is there any way to recursively select a whole directory and it's contents?]]. 

== aMule toccherrà i mie file xMule e lMule? Cosa dovrei fare? ==
aMule prende in considerazione automaticamente entrambi i file di configurazione di lMule e di xMule, ma in modi diversi: 
lMule è stato interrotto molti anni fa, aMule capisce che stai sovrascrivendo lMule con aMule, infatti rinomina la cartella ~/.lMule in ~/.aMule. Se usavi ~/.lMule/Temp e ~/.lMule/Incmoing rispettivamente come cartella temporanea e di download, dovresti cambiare i path nelle Preferenze a ~/.aMule/Temp e ~/.aMule/Incoming. 
xMule è morto ufficialmente nel Maggio 2004, ma per ragioni storiche, aMule rimarrà la cartella ~/.xMule. Questo significa che i file che stavi scaricando rimarranno nella cartella ~/.xMule se prima li stavi scaricando li, quindi aMule ha toccato i file di configurazione di xMule. Puoi rimanere in questo modo le impostazioni, oppure spostare le cartelle ~/.xMule/Temp e ~/.xMule/Incoming in ~/.aMule e cambiare le Preferenze.

== Come inizio la mia esperienza con aMule? ==
Cliccando sul bottone Connetti. Avrai alcuni server in lista nella finestra Server . Se non hai server nella lista, allora clicca sul piccolo bottone tra il bottone Connetti e la finestra dei Server prima di cliccare su Connetti. Dopo poco, aMule sarà connesso ad un server (lo saprai perchè in basso a destra apparirrà il messaggio). Quando connesso, vai nella finestra Ricerca e cerca il file che vuoi e quando l'hai trovato, cliccaci due volte sopra per il download. 
Per usi generali di aMule, joina su #amule in irc.freenode.net o chiedi sul [http://www.amule.org/amule/ forum].

== Quali sono le migliori impostazioni per avere un buon download? ==
Se il tuo provider te lo permette, la miglior cosa è settare un minimo di 10 kbps nel limite dell'upload, questo perchè più invii e più scarichi. Condividi file popolari (non condividere troppi file, non più di 200, o sarai bannato da alcuni server dato che crei troppo traffico) e prova a condividere file famosi di piccole dimensioni. Un buon suggerimento (grazie a kaouete) quando stai provando a scaricare qualche file raro o "mai completato", quando nessuno ti sta inviando qualche chunk di quel file, dai a quei client lo slot amico, così se prova a scaricare qualcosa da te, guadagnerai crediti su quel client e potrai scaricare il tuo file facilmente e velocemente.

== C'è un modo per aprire un file di testo e caricare tutti i link ed2k dal file? ==
Si. Basta inserire tutti i link ed2k che vuoi scaricare in file di testo, ogni link ed2k in una linea separata. Nomina quel file ED2KLinks e posizionalo in ~/.aMule e aMule automaticamente lo rileverà, aggiungendo tutti quei link e poi cancellerà il file.

== Posso controllare aMule in remoto attraverso telnet nello stesso modo con cui faccio con eDonkey? ==
Si lo puoi fare, ma non esattemente nello stesso modo che si fa con eDonkey. Avvia una normale sessione telnet (o ssh) con il computer host (dove è avviato aMule) e usa amulecmd per controllare aMule. Per iniziare un nuovo download basta usare il comando ed2k. Ricorda che amulecmd deve essere configurato. 
Un'altro tool che è molto interessante è CAS (il comando è cas) che visualizza alcune statistiche di aMule. 
Inoltre, aMule WebServer è molto utile se hai la possibilità di usare un web browser sul computer client. Tieni presente che aMule WebServer deve essere configurato.

== C'è qualche modo per avviare aMule senza l'interfaccia grafica? ==
aMule è un'applicazione monolitica, Questo significa che il core e la GUI fanno parte di uno stesso blocco (ci sono già alcuni sforzi nel suddividere il core dalla GUI). Anche se, è possibile avviare aMule da linea di comando ma non è un modo diretto. Potresti avviare xvfb e poi avviare aMule, in seguito puoi prendere il controllo di aMule usando amulecmd e ed2k nello stesso modo in cui stessi entrando in aMule in remoto attraverso telnet. 
Piccolo esempio: 
Avvia Xvfb: 
<code>Xvfb :1 -screen 0 640x480x16 &</code> 
Setta lo schermo per usare aMule: 
<code>export DISPLAY=:1</code> 
Poi avvia aMule: 
<code>amule &</code> 
Nota: Dopo aver dato <code>export DISPLAY=:1</code>, tutte le applicazioni grafiche lanciate da quella shell si apriranno nello schermo di Xvfb. Per evitare questo, puoi avviare aMule con il seguente comando, così si avvierà solo aMule: 
<code>DISPLAY=:1 amule &</code> 
Se hai bisogno di aiuto su questo problema, chiedi sul forum di aMule. 

== Posso avviare due aMule nello stesso tempo? ==
Si puoi, anche se non è consigliato. aMule controllerà solo se lo stesso utente abbia avviato un'altro processo di aMule, dunque puoi avviare tanti processi di amule quanti account di utenti hai accesso. Facendo questo, basta solo avviare 'xhost +' e poi su con un altro utente e avviare aMule da quella shell. 
Da notare, che aMule non può controllare se un utente sta avviando aMule su un altro schermo X. Così, se il tuo account ha già avviato aMule in uno schermo X, non avviare un altro aMule su un altro schermo X o potrai perdere le configurazioni e corrompere i chunk. 

== Come posso prendere le statistiche di aMule che alcune persone postano sui canali IRC? ==
Puoi copiare e incollare l'output di CAS (C aMule Statics) (per eseguire CAS, avvia cas) oppure, se usi xChat come client IRC e hai il mudulo Perl installato, puoi usare XAS (xChat aMule Statics). 

== Che cosè l'allocazione slot? ==
Ogni upload è uno slot, se state inviando a cinque client nello stesso tempo, avete stabilito cinque upload slot. L'ammontare dell'allocazione slot è la banda che sarà data per ogni slot. 
Un esempio, se il tuo limite di upload è di 20KBps, potete settare l'allocazione slot a 2KBps questo farà si che ci saranno 10 client a scaricare da voi nello stesso tempo, ognuno di loro avrà un massimo di 2KBps. 
Guarda la sezione "Why is aMule ignoring the bandwith I set per slot?" nella FAQ
"aMule common problem".

== Che cosè uno slot amico? ==
Uno slot amico è uno slot che assegna un client nella lista amici. Solo un amico per volta può avere uno slot. Ogni volta che quell'amico (che ha lo slot amico attivo) prova a scaricare un file da te, avrà la massima priorità nella coda dell'upload, da allora ha quel slot sempre assegnato. Mentre quell'amico non sta scaricando, quello slot assegnato sarà dato al client con la più alta priorità nella coda upload, come previsto. 

== Che cosa sono le Capacità della Linea nelle Preferenze? Non dovrebe bastare il Limite di Banda? ==
aMule in realtà si preoccupa soltanto dei Limiti di Banda. Le Capacità della linea servono solo per le statistiche. Vediamo: immagina di avere una connessione da 100KBps, e vuoi settare il Limite a 40KBps perchè hai un web server che necessita un minimo di 60KBps. Adesso immagina di scaricare una canzone libera indonesiana rara. Sicuramente non supereresti i 3Kbps. Così, potresti settare la Capacità di linea a 5KBps e il grafico in Statistiche avrebbe un qualche significato che invece non potrà avere se la Capacità di linea è settato a 100KBps dato che si vedrebbe una linea quasi inpercettibile. 

== Posso prendere dei dati dallo standard input e passarli a GDB o Valgrind? ==
Si. Su aMule 2.0.0-rc3 questo non si poteva fare, ma con la versione aMule 2.0.0-rc4 puoi farlo con il parametro ''-i'' o ''--enable-stdin''. 
Comunque, con versioni precedenti alla rc4 si può usare [http://www.amule.org/amule/thread.php?threadid=2474 phoenix's aMule stdin patch].

== aMule è crashato. Posso settarlo in modo che si riavvii dopo ogni crash? ==
No, non puoi. Ma potresti usare qualche script che ti permette di farlo. 
[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]
 

== Cosè la storia sul coniglio bianco? ==
Ah, si, tutto ha inizio... ehm... bene... segui il coniglio bianco ;)

FAQ aMule

2004-11-26T13:27:14Z

84.128.98.219: link to german translation added

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

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

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

[[aMule]] is intended to be as user-friendly and feature-plenty as [[eMule]] and to remain faithful to the look of [[eMule]], so users familiar with either [[aMule_Project_FAQ:About|aMule]] or [[eMule]] will be able switch between the two easily.

Since [[aMule_Project_FAQ:About|aMule]] is based upon the [[eMule]] codebase, new features in [[eMule]] tend to find their way to [[aMule]] soon after their inclusion in [[eMule]], so users of [[aMule_Project_FAQ:About|aMule]] can expect to ride the cutting-edge of [[FAQ_eD2k-Kademlia|ED2k]] clients.

The best part is, that it's developed by a great team which is even more user-friendly than [[aMule_Project_FAQ:About|aMule]] itself (if possible), so please join #amule on irc.freenode.net or visit the [http://www.amule.org/amule forums], if you have any suggestions, questions, problems, bugs, patches or what else you might think of.

If you are interested in joining the development team, please contact us either through the [http://www.amule.org/amule forums] or in the IRC channel.

== How do I view a client's credits? ==
You can see any client's credits (the credits you owe him) by right clicking on it's name and selecting Show Details. There is no specific value shown so you can either view the total amount of data that client has sent you or the Credits Modifier (which is called DL/UL Modifier). On that same dialog window, if that client is on your upload queue, you'll be able to view it's rate and score on you.

== What do those colors in the progress bar mean? ==
On the downloading transfers list: 
Red: Chunks in red are chunks with no sources on current session found. 
Blue: Chunks in blue are chunks with at least one available source. The more solid blue it is, the more sources available have been found. 
Yellow: Chunks in yellow are chunks which are being downloaded at this very moment. 
Black: Chunks in black are chunks which have been already downloaded and verified. 
Green: When a file is in green it means that it's been completely downloaded and successfully verified (so, it'll be in the Incoming folder). 
On the expanded transfers list (can be viewed by double-clicking a transfer): 
Black: Chunks which that client has and you don't have. 
White: Chunks which that client doesn't have. 
Green: Chunks which that client has and you have, too. 
Yellow:Chunks which that client is currently uploading to you. 
On the uploading transfers list: 
Black: That client has completed and verified that chunk. 
Grey: That client doesn't have that chunk. 
Have in mind that not all clients support telling other clients which parts they have already completed when uploading, so some clients might have no bar at all. 
On the shared files window: 
Red: When there's no source found to have that same chunk (apart from you, of course). 
Blue: The more solid the blue is, the more spread that chunk is. 
On the search windows: 
Black: Files in black are those which only a client has been found to have. 
Blue: Files in blue are those which two or more clients have been found to have. The more solid the blue is, the more clients have been found to have it. 
Red: Files in red are those which are already in the downloading queue. 
Green: Files in green are those which you are already sharing (you completely downloaded it).

== What are all these icons? ==
See section "Icons and what they signify" in the [[Getting Started]] guide.

== What do those numbers in brackets in the search window mean? ==
Those are the clients who are known to have the complete file. Even if the number in brackets is 0, it doesn't mean that no one has the complete file, it juts means that no client has marked the shared file as "completed" (lots of clients don't do so). So, it's a way to have an idea of how many people have the complete file, but not the definitive way.

== What do all those numbers in the sources column in the transfers window mean? ==
The sources format is XX/YY + ZZ (WW) where 
XX stands for the amount of available sources (the amount of sources found you can download from). 
YY stands for the amount of found sources (the total amount of sources found) 
ZZ stands for the number of "Asked for another file" sources 
WW stands for the amount of sources from who you are currently downloading some chunk of that file.

== What do all those numbers in the priority column in the extended transfers window mean? ==
That's the queue position you have on that client for that specific file. Not all clients provide such information, so in some cases, nothing is displayed. 
The number in brackets is the amount of positions you have "moved" through that client's upload queue. '''Negative''' numbers stand for positions you have '''won''' in the queue since you were added while '''positive''' numbers mean positions you've '''lost''' since since you were added. Notice that when that number is negative, it is displayed blue, while when it's positive, it's displayed red.

== Why are there two transfer rates in the uploading transfer list? ==
When you are uploading some file to some client, the uploading transfer list will show the transfer rate (speed in KBps) in which you are uploading to that client. If, at the same time, that client is uploading to you some file (or files), then the transfer rate's format will change to XX/YY where XX stands for the speed in which you are uploading to that client and YY will stand for the speed in which that client is uploading to you. If you search in the downloading transfers list you'll find that client. 
This is useful if you are trying to get a rare file, since you can which file that client is uploading to you and, if it's the rare file, you can set him a friend slot so that you upload to that client faster and gain more credits on that clients (and consequently, download faster from the client).

== What is A4AF? ==
A4AF stands for ''Ask For Another File''. It is a way to optimize the resources on a specific download. 
When you try to download a file, aMule gets a list of clients who are sharing that file. Some of this clients might also share some other file which you are also trying to download and, so, you might have that client in two separate download queues. 
A4AF tries to avoid this situations. Why? Because you can't download two chunks at the same time from the same client. So, by setting A4AF in a specific download, you are telling aMule to search for any client in that file's download queue who is also in some other file's download queue and remove it from that other download queue. This way, you'll get more sources on that file. 
You can also set a specific download to apply A4AF in the opposite way, that is, to give sources to the other downloads. This should be done on downloads which are not to be downloaded with too much hurry or which should be downloaded after some other similar file has been downloaded (in a series of files, for example). 
This also can be seen as a way of establishing preferences in downloads.

When the request swapping is done, the Queue Rank will be maintained.

'''NOTE:''' A source with a QR lower than 50 in the download with the higher priority will never be swapped. This is done this way to ensure it starts downloading from it.

== What is the difference between Transfered and Completed in the Transfers window? ==
Transfered shows the amount of data you have received concerning that file. This data is downloaded in a compressed format. Once the data gets to your machine, aMule processes it and decompresses it. The total useful data that can be taken from that received data (that is, the parts of that data which are actually real parts of the file you are trying to download and not headers or such stuff) is the amount that can be viewed in the Completed column.

== What is the difference between pausing and stopping a transfer? ==
When a transfer is paused, all connections related to the paused transfer are broken with the other clients so that no data is transfered, but sources aren't dropped, so that when the transfer is resumed, [[aMule_Project_FAQ:About|aMule]] will try to connect to those sources it was transferring from.
Instead, when a transfer is stopped, all sources are dropped so, when it's resumed, [[aMule_Project_FAQ:About|aMule]] will start searching for clients who are sharing that file.

== What are all those files [[aMule_Project_FAQ:About|aMule]] creates the first time it is run? ==
Most them are the same as [[eMule|eMule]]'s. Here is a list and the meaning of each of them (have in mind that you might not have all of them on your hard disk): 
~/.eMule: aMule's personal configuration (that is, things such as you nickname, your Temp and Incoming directories, your upload and download limits, and such...). 
~/.aMule/addresses.dat: Contains a list of serverlist URLs to check (if enabled in Preferences) for new servers on startup. 
~/.aMule/amulesig.dat: This is [[aMule_Project_FAQ:About|aMule]]'s [[signature|OnLineSignature]] file, which is the same as [[eMule|eMule]]'s [[signature|signature]] (see onlinesig.dat below) but with extended information (extended information includes nickname, session and total downloaded and uploaded bytes, [[aMule_Project_FAQ:About|aMule]] version, [[aMule_Project_FAQ:About|aMule]] uptime and number of shared files). 
~/.aMule/aMule.tmpl: This is the template file which [[amuleweb|aMule WebServer]] uses to create the web page. 
~/.aMule/aMule-online-sign.png: This file will only exist if CAS has been run sometime with the -o switch and ~/.aMule/casrc was successfully configured. It is an image containing details on [[aMule_Project_FAQ:About|aMule]]'s status. 
~/.aMule/casrc: This file will only exist if [[CAS|CAS]] has been run sometime with the -o switch. It contains the settings for the [[CAS|CAS]] image creation. 
~/.aMule/clients.met: Contains the public hashes of other known clients along with the credits it owes each of them. 
~/.aMule/cryptkey.dat: It contains the unique 384 bit private RSA key of your client. 
~/.aMule/emfriends.met: Contains your friends list configuration 
~/.aMule/ipfilter.dat: This file contains the IP ranges and access levels restrictions which will be passed to ipfilter. 
~/.aMule/Incoming: By default, the directory where [[aMule_Project_FAQ:About|aMule]] stores the completed downloads. 
~/.aMule/known.met: This file stores the hashes and some details of your shared files like size, path, statics, etc... 
~/.aMule/known2.met: This file stores the verified [[AICH]] hashes of your shared files. 
~/.aMule/lastversion: This is only for [[aMule_Project_FAQ:About|aMule]] to know if it's the first time you're starting [[aMule_Project_FAQ:About|aMule]], if you had [[aMule_Project_FAQ:About|aMule]] installed before and which version you had installed previously. 
~/.aMule/logfile: This file contains the log of the last [[aMule_Project_FAQ:About|aMule]] execution. 
~/.aMule/muleconn: This file is a socket for [[aMule_Project_FAQ:About|aMule]] communications. 
~/.aMule/onlinesig: This is an [[eMule|eMule]] compatible [[signature|OnLineSignature]] file. It's used by other applications to know basic information on [[aMule_Project_FAQ:About|aMule]]'s stat (if it's online, which server it's connected to, upload and download rate, and clients in queue). 
~/.aMule/preferences.dat: Contains the public key of your client, also known as user hash. 
~/.aMule/server.met: This is a list of all known servers and you're preferences on them (priority, name, ip, port and such). 
~/.aMule/shareddir.dat: Stores the paths to all shared directories. 
~/.aMule/Temp: By default, the directory where [[aMule_Project_FAQ:About|aMule]] stores the not completed downloads (temporary files). 
~/.aMule/webserver: This directory contains the necessary files for aMule WebServer to display a nice Web page. 
Other files on ~/.aMule/ are most surely backups of some of the above files. 
Also, on the Temp directory (which is ~/.aMule/Temp by default but can be set to any other on Preferences), [[aMule_Project_FAQ:About|aMule]] will create, for each download three or four files): 
*.part: This file contains the downloaded parts (not chunks, since not completed chunks are also stored here) of the download. As [[aMule_Project_FAQ:About|aMule]] is able to download from more than one user at the same time, this file has the size of the complete file. The missing parts are filled with zeros. 
*.part.met: This file contains information on the downloaded parts of the download, the verified chunks, the hash values of the remaining chunks, etc... 
*.part.met.bak: This are backups of the *.part.met files. Every now and then aMule creates this backups since without the *.part.met file, a download has no meaning for aMule. If any *.part.met file "disappeared, you should rename the *.part.met.bak to *.part.met. 
*.part.met.seeds: This file only exists if you have enabled to store the IPs of sources of rare files in the preferences, so that [[aMule_Project_FAQ:About|aMule]] can try to connect to these sources again after a restart.

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

Moving the half downloaded files is easy: just place them from your [[eMule]] temp directory (by default ''C:\Program files\eMule\Temp'' into ''~/.aMule/Temp'' or whatever your temp directory is in your [[aMule]] configuration.

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

== I just installed [[aMule_Project_FAQ:About|aMule]] for the first time. How do I set it up? ==
Setting up aMule properly is just a matter of tastes and depends on many factors. If you just wish a quick startup configuration, then continue reading. 
Open [[aMule_Project_FAQ:About|aMule]] and click on the Preferences button. Set a nickname and the language in which you wish to have [[aMule_Project_FAQ:About|aMule]]. Then switch to the Connection tab and input your Line Capacities. Then input the Bandwidth Limits according to the maximum amount of bandwidth you want [[aMule_Project_FAQ:About|aMule]] to use. Then switch to the Directories tab and set a directory for both the temporary files (where files will be stored until they are completely downloaded) and the completed files. Finally, select the directories which you want to share. It is not recommended to share too much files. Read bellow "What are the best settings I can set to have a nice download rate". To select recursively all directories inside a certain directory read [[aMule_problems#Is there any way to recursively select a whole directory and its contents?|Is there any way to recursively select a whole directory and its contents?]].

== Will [[aMule_Project_FAQ:About|aMule]] handle my [[xMule]] and [[lMule]] files? What should I do? ==
[[aMule_Project_FAQ:About|aMule]] automatically handles both [[lMule]] and [[xMule]]'s configuration files, but in different ways: 
[[lMule]] has been discontinued for several years now, so [[aMule_Project_FAQ:About|aMule]] understands that you are replacing [[lMule]] with [[aMule_Project_FAQ:About|aMule]], so it renames ~/.lMule folder to ~/.aMule. If you used ~/.lMule/Temp and ~/.lMule/Incoming as your temporal and downloading directories respectively, you should change the paths in Preferences to ~/.aMule/Temp and ~/.aMule/Incoming respectively. 
[[xMule]] is officially dead since May 2004 (official [[xMule]]'s death announcement on [[xMule]] forums by its main developer at, the now non-existent web page, [http://www.xmule.org http://www.xmule.org]), but for historical reasons, [[aMule_Project_FAQ:About|aMule]] will remain the ~/.xMule directory with its name and just copy from it its configuration files. This means that the files you were downloading will remain in the ~/.xMule directory if they were downloading there, but since [[aMule_Project_FAQ:About|aMule]] has handled [[xMule]]'s configuration files, it will use still use it. You can either live with that, or move directories ~/.xMule/Temp and ~/.xMule/Incoming into ~/.aMule and change directories in Preferences.

== How do I start my [[aMule_Project_FAQ:About|aMule]] experience? ==
Just click on the Connect button. You should have some servers listed on the Servers window, though. If you have no servers listed, then click on the little button below the Connect button in the Servers window before clicking the Connect button. After some time, [[aMule_Project_FAQ:About|aMule]] will be connected to some server (you'll know because in the lower right corner the "Not connected" message will disappear). When connected, switch to the Search window and search for the file you want and once you find the file you want, double-click on it. 
For general [[aMule_Project_FAQ:About|aMule]] usage, join [[aMule_Project_FAQ:About|aMule]] #amule in irc.freenode.net or ask in forums at [http://www.amule.org/amule http://www.amule.org/amule]

== What are the best settings I can set to have a nice download rate? ==
If you understood "Is there any limit on the [[FAQ_eD2k-Kademlia|ED2K]] network?" then you might have seen that, if your provider allows you, the best is to have the upload limit set to a minimum of 10 KBps. Also, if you understood "What is all that credits, rate and score stuff about?", you might also understand that the more you upload, the more you download, so take the upload limit up as much as you can, share well known and popular files (don't share too much (not more than approximately 200 files) or you'll get banned from some servers for giving too much traffic) and try to share small-sized popular files since some [[FAQ_eD2k-Kademlia|ED2K]] clients give extra credits for providing them a whole small-sized files. A good tip (thanks to kaouete) when you are trying to download some rare or "never completing" file, is, whenever you see someone uploading to you some chunk of that file, give that client a friend slot so that, if it tries to download something from you, it gets preference and you gain credits on that client.

== Is there a way to open a text file and load all the ed2k links from the file? ==
Yes, there is. Just place all the ed2k links you want to download in a text file, each ed2k link in a separate line. Name that file ''ED2KLinks'' then place it in ''~/.aMule'' and aMule will automatically detect it, add all those ed2k links to download and remove the file. 
You might want to read [[ED2KLinks_file|this]] to know more about this file.

== Can I manage [[aMule_Project_FAQ:About|aMule]] remotely through telnet in the same way I do with [[eDonkey2000|eDonkey]]? ==
Yes you can, but not exactly in the same way as you do with [[eDonkey2000|eDonkey]]. Just start a normal telnet (or ssh) session with the host computer (the one running [[aMule_Project_FAQ:About|aMule]]) and, once in, use amulecmd to take control over [[aMule_Project_FAQ:About|aMule]]. To start new downloads just use the [[ed2k_command|ed2k command]]. Remember [[aMuleCMD]] must be configured. 
Another aMule utility that might be of your interest is [[CAS]] (which's command is <code>cas</code>) which will show basic [[aMule_Project_FAQ:About|aMule]] statistics. 
Also, [[amuleweb|aMule WebServer]] might be what you are looking for if you can and don't mind using a web browser on the client computer. Have in mind that aMule WebBrowser must also be configured.

== Is there any way to start [[aMule_Project_FAQ:About|aMule]] with no graphical interface? ==

Yes. Since aMule 2.0.0-rc6, you can use aMule Daemon, which can be executed on the command line by typing ''amuled''. To control it, use either aMuleWeb, aMuleCMD or any other such application for remotely controlling aMule.

Anyway, up to aMule 2.0.0-rc6, [[aMule_Project_FAQ:About|aMule]] was a monolithic application. This means that core and GUI were whole inseparable block.

So, for those using an old aMule version or who refuse to use aMuled (aMule Daemon), there are still two walkarounds to run [[aMule_Project_FAQ:About|aMule]] on command line but they're not direct ways:
*Through ''[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]''
*Through ''[http://www.realvnc.com VNC]''

'''Through ''[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]:''' 
You should run <code>[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]</code> and then run aMule in it. Afterwards you can take control over [[aMule_Project_FAQ:About|aMule]] using [[aMuleCMD]] and [[ed2k_command|ed2k]] in the same way as you would if you were accessing [[aMule_Project_FAQ:About|aMule]] remotely over telnet (see above).

Short example: 
Run [http://xfree.org/4.4.0/Xvfb.1.html Xvfb]: 
<code>Xvfb :1 -screen 0 640x480x16 &</code> 
Set display to use for amule: 
<code>export DISPLAY=:1</code> 
Then run [[aMule_Project_FAQ:About|aMule]]: 
<code>amule &</code> 
Note: After running <code>export DISPLAY=:1</code>, all graphical applications launched from that shell will be opened in [http://xfree.org/4.4.0/Xvfb.1.html Xvfb]'s display. To avoid this, you can run [[aMule_Project_FAQ:About|aMule]] with the following command, so that only [[aMule_Project_FAQ:About|aMule]] runs there: 
<code>DISPLAY=:1 amule &</code> 
'''INFO:''' See the [[Screen]] page to know more about the [[Screen]] command

'''Through ''[http://www.realvnc.com VNC]:''' 
It's also possible to use ''vncserver'' instead of [http://xfree.org/4.4.0/Xvfb.1.html Xvfb] to achieve something similar. Just install ''vncserver'' and execute ''vncserver :0 -geometry 1024x768'' followed by ''export DISPLAY=:0''. This will create a hidden [http://xfree.org X] server, accessible only remotely using a [http://www.realvnc.com VNC] client. Once the [http://xfree.org X] server is running, you will need a window manager to manage [[aMule]] window (well, it's not really needed, but it's useful if you want to be able to close [[aMule]] without simply killing it), I recommend [http://fluxbox.sourceforge.net FluxBox] due to its low CPU and memory requirements. Just start it with ''fluxbox &'' and then run [[aMule]] with ''amule &''. Now you can connect to the [http://www.realvnc.com VNC] server and see the [[aMule]] window.

Keep in mind that if [[aMule]] shows any dialog that requires user input (like the one showed the first time [[aMule]] is executed), it will get stuck there until someone connects to the [http://www.realvnc.com VNC] server and clicks ok in the dialog. Usually, this should only need to be done once (and this connection may be used to update the serverlist and set the preferences), from then on [[aMule]] will start without user interaction, showing only some informational messages at startup.

If you need help on this issue, search [[aMule_Project_FAQ:About|aMule]]'s [http://www.amule.org/amule forums] or join #amule [[IRC]] channel at irc.freenode.net and ask.

== Can I run two [[aMule_Project_FAQ:About|aMule]] instances at the same time? ==
Yes you can, although it is not recommended. [[aMule_Project_FAQ:About|aMule]] will only check if the concurrent user is running some [[aMule_Project_FAQ:About|aMule]] instance, so you can run as many [[aMule_Project_FAQ:About|aMule]] instances as user accounts you have access to. To do this, just run <code>xhost +</code> and then <code>su</code> as another user and run aMule from that shell. 
Be aware, since [[aMule_Project_FAQ:About|aMule]] can't check if a user is running [[aMule_Project_FAQ:About|aMule]] on another X display. So, if your account is already running some [[aMule_Project_FAQ:About|aMule]] instance in some other X display, do not run another [[aMule_Project_FAQ:About|aMule]] instance on another X display or you might end up with lost configuration settings and corrupt chunks.

== How can I get those nice [[aMule_Project_FAQ:About|aMule]] statics some people post on the IRC channels? ==
You can either copy and paste [[CAS]]'s (C [[aMule_Project_FAQ:About|aMule]] Statics) output (to execute [[CAS]], run <code>cas</code>) or, if you use xChat as your IRC client and have the Perl module installed, you could use [[XAS]] (xChat [[aMule_Project_FAQ:About|aMule]] Statics).

== What is slot allocation? ==
Each upload is a slot, so, if you are uploading to five clients at the same time, you have five upload slots established. So, the amount of slot allocation is the bandwidth which each slot will be given. 
As an example, if your upload limit is 20KBps, you can set slot allocation to 2KBps which means 10 clients will be able to download from you at the same time, each of them at a maximum transfer rate of 2KBps. 
See section "Why is aMule ignoring the bandwidth I set per slot?" in [[AMule_problems|aMule common problem's FAQ]].

== What is a friend slot? ==
A friend slot is just a slot which is assigned to a client in the friends list. Only one friend can have a slot at the same time. Whenever that friend (who has the friend slot enabled) tries to download a file from you, it will be given highest priority in the uploads queue, since it has that slot always assigned. While that friend isn't downloading, that assigned slot will be given to the client with the highest priority in the upload queue, as expected.

== What is the real point on setting up Line Capacities in Preferences? Shouldn't [[aMule_Project_FAQ:About|aMule]] only care for the Bandwidth Limits? ==
aMule really only cares for the Bandwidth Limits. Line Capacities are only set for the Statics display. Let's see: Imagine you have a 100KBps connection, imagine you want to set the Limit at 40KBps because you have a web server which needs a minimum of 60KBps to serve all the petitions. Now imagine you download rare indonesian free songs. You most surely never download at more than 3KBps ever. So, you could set Line Capacities at 5KBps so that the graph at Statics has some meaning, since if you set it up as a 100KBps connection, the graph will show an horizontal line with no meaning at all.

== aMule is crashing quite often here. Can I set it to restart every time it crashes? ==
No, you can't. But you can have scripts to do so. Some of these scripts even work if aMule '''hangs''' but doesn't '''crash'''. 
The following scripts might suit your needs: 
[http://www.amule.org/amule/thread.php?threadid=1232 http://www.amule.org/amule/thread.php?threadid=1232] 
[http://www.amule.org/amule/thread.php?threadid=542 http://www.amule.org/amule/thread.php?threadid=542] 
[http://deepthought.ena.si/mulerunner http://deepthought.ena.si/mulerunner]

== Can I have aMule get data from the standard input to pass it to GDB or Valgrind? ==
Yes, you can. Up to aMule 2.0.0-rc3 this wasn't allowed, but as of version 2.0.0-rc4 you can with the parameter ''-i'' or ''--enable-stdin''. 
Anyway, people with aMule versions previous to 2.0.0-rc4 can use [http://www.amule.org/amule/thread.php?threadid=2474 phoenix's aMule stdin patch].

== How can I switch to aMule from eMule without loosing my credits? ==
If you already read [[FAQ_aMule#What_are_all_those_files_aMule_creates_the_first_time_it_is_run?|about the meaning of aMule's files]], you might already know what you have to do: 
Get ''cryptkey.dat'', ''clients.met'' and ''preferences.dat'' files from eMule's config directory (usually, under Windows, something like ''C:\Program files\eMule\config'') and copy them into ''~/.aMule''. Now start aMule so it reads those files. You're done!

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

FAQ aMule-de

2004-11-26T13:25:37Z

84.128.98.219: preliminary translation

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

== Was ist denn dieses ominöse [[aMule_Project_FAQ:About|aMule]] eigentlich? ==
'''''[[aMule]] ist ein plattformunabhängiger Client für das [[FAQ_eD2k-Kademlia|eDonkey/eMule Filesharing Netzwerk]], entstanden im August 2003 aus einer Abspaltung von [[xMule]], das wiederum eine Abspaltung von [[lMule]], das wiederum eine Portierung des nur-windoof Clients [eMule]] ist.''''' 

Im Moment ist es unter GNU/Linux, FreeBSD und OpenBSD, MacOSX, Windoof und der X-Box sowohl auf 32- als auch 64bit Systemen lauffähig. Die Windoof-Version ist allerdings noch nicht wirklich für den produktiven Einsatz geeignet.

Es ist beabsichtigt, dass [[aMule]] genauso funktionell und einfach zu benutzen ist, wie [[eMule]] und auch genauso aussieht, so dass Nutzer, die mit einem der beiden vertraut sind, ohne Schwierigkeiten zwischen beiden wechseln können.

Da [[aMule_Project_FAQ:About|aMule]] auf den Quellen von [[eMule]] basiert, finden neue Funktionen sehr schnell ihren Platz in [[aMule]], nachdem sie in [[eMule]] eingebaut wurden, so dass auch die Nutzer von [[aMule_Project_FAQ:About|aMule]] sicher sein können, sich immer an der Spitze der Entwicklung der [[FAQ_eD2k-Kademlia|ED2k]] Clients zu befinden.

Nicht unwichtig ist, dass es von einem großartigen Team entwickelt wird, dass (sogfern das überhaupt möglich ist), vielleicht noch nutzerfreundlicher und -bezogener ist, als [[aMule_Project_FAQ:About|aMule]] selbst. Daher schauen Sie auch mal bei #amule auf irc.freenode.net vorbei oder besuchen Sie [http://www.amule.org/amule unsere Foren], wenn Sie Fragen oder Probleme haben, oder einfach nur einen guten Vorschlag, was man besser machen könnte.

Möchten Sie vielleicht sogar dem Entwicklerteam beitreten, melden Sie sich bitte in den Foren oder im IRC.

== Wie kann man sich die Credits eines Clients ansehen? ==
Man kann sich die Credits eines Clients (was man ihm schuldet) ansehen, wenn man auf seinen Namen rechts klickt und Details anzeigen auswählt. Die Credits haben keinen bestimmten Wert, man kann sich entweder die gesamtübertragene Datenmenge, die man von diesem Clients bekommen hat, ansehen oder den Credit Modifikator (DL/UL Modifikator). Das Fenster zeigt auch, wenn der Client in der Uploadwarteschlange steht, seine Position und seine Bewertung.

== Was bedeuten diese ganzen Farben in der Fortschrittsanzeige? ==
In der Liste der Downloads: 
Rot: Für Blöcke in rot wurden in der aktuellen Sitzung noch keine Quellen gefunden. 
Blau: Blöcke in blau haben mindestens eine nutzbare Quelle, je dunkler das Blau ist, desto mehr Quellen gibt es. 
Gelb: Gerade in diesem Moment heruntergeladenen Blöcke werden gelb dargestellt. 
Schwarz: Schwarze Blöcke wurden bereits fertig heruntergeladen und überprüft. 
Grün: Sobald eine Datei komplett fertiggestellt ist, wird sie grün dargestellt (und ist dann im Eingangsverzeichnis zu finden). 
Auf der ausführlichen Downloadliste (aufzurufen durch Doppelklick auf einen einzelnen Transfer): 
Schwarz: Der Client hat diesen Block, wir aber noch nicht. 
Weiß: Diesen Block hat der Client nicht. 
Grün: Wir haben diesen Block beide. 
Gelb: Dieser Block wird gerade von diesem Client zu uns heraufgeladen. 
Auf der Uploadliste: 
Schwarz: Diesen Block hat der Client fertiggestellt und überprüft. 
Grau: Der Client hat diesen Block nicht. 
Beachten Sie, dass nicht alle Clients die Fähigkeite haben, anderen beim Upload zu sagen, welche Teile sie bereits haben, daher haben manche Clients keine Anzeige der einzelnen Blöcke. 
Bei den freigegebenen Dateien: 
Rot: Außer uns gibt es keine andere Quelle dieses Blocks. 
Blau: Umso dunkler das Blau ist, umso mehr Clients haben diesen Teil. 
Auf der Suchseite: 
Schwarz: Für schwarze Dateien wurde nur ein Clients gefunden, der sie hat. 
Blau: Dateien in blau haben mindestens zwei Quellen, je dunkler das Blau, desto mehr. 
Rot: Rote Dateien befinden sich bereits in der Downloadliste 
Grün: Bereits vollständig heruntergeladene Dateien werden auch hier in grün dargestellt.

== Was bedeuten diese ganzen Icons? ==
Schauen Sie im Abschnitt "Icons und was sie uns sagen wollen" im Artikel [[Wie alles begann]] nach.

== Was bedeuten die Zahlen in Klammern im Suchfenster? ==
Sie zeigen die Zahl der Clients an, die bekanntermaßen die Datei vollständig haben. Aber auch wenn die Anzahl 0 ist, heißt das noch lange nicht, dass keiner sie komplett hat, nur, dass sie keiner als "komplett" markiert hat (viele Clients tun dies). Trotzdem kann man so einen Eindruck davon gewinnen, wieviele Leute die Datei vollständig haben, auch wenn es keine Gewissheit ist.

== Was bedeuten die ganzen Zahlen in der Quellen-Spalte in der Transferliste? ==
Das Format der Quellenangabe ist XX/YY + ZZ (WW), wobei 
XX für die Anzahl der verfügbaren Quellen steht (von denen man downloaden kann), 
YY für die Gesamtanzahl an gefundenen Quellen steht, 
ZZ für die Anzahl der Quellen, die "nach einer anderen Datei gefragt" worden und 
WW für die Anzahl der Quellen steht, von denen wir gerade einen Block herunterladen.

== Wofür stehen die Zahlen in der Spalte Priorität in der aufgeklappten Downloadliste? ==
Das ist die Warteschlangenposition, die man beim jeweiligen Client einnimmt. Nicht alle Clients geben diese an, daher steht in manchen Fällen dort einfach nichts. 
Die Zahl in Klammern gibt die Positionen an, die man sich schon in der Warteschlange des Clients *bewegt* hat. '''Negative''' Zahlen stehen für '''vorangeschrittene'' Positionen, '''positive''' für verlorene. Wenn negativ, wird die Zahl blau dargestellt, bei positiv rot.

== Warum werden in der Uploadliste zwei Geschwindigkeiten angegeben? ==
Wenn man zu einem Client hochlädt, zeigt die Uploadliste die Geschwindigkeit (in Kilobyte pro Sekunde) zu diesem Client an, wenn nun, zur gleichen Zeit, dieser Client auch zu uns hochlädt, verändert sich die Anzeige zu XX/YY, wobei XX für unsere und YY für seine Uploadgeschwindigkeit steht. Wenn man in der Downloadliste sucht, wird man diesen Client finden. 
Dies ist besonders nützlich, wenn man versucht, eine seltene Datei zu bekommen, da man sehen kann, was der Client zu einem hochlädt und, wenn es die gesuchte Datei ist, ihm einen Uploadplatz für Freunde vergeben kann, so dass man schneller zu ihm hochlädt, man damit mehr Credits bekommt und folglich auch schneller von ihm herunterladen kann.

== Was ist A4AF? ==
A4AF bedeutet ''nach anderer Datei gefragt''. Damit werden die Ressourcen eines bestimmten Downloads optimiert. 
Wenn man eine Datei downloaded, holt sich aMule eine Liste aller Clients, die diese Datei haben. Einige davon haben möglicherweise auch andere Dateien, die man herunterladen möchte, daher kann man einen Client bei mehreren separaten Downloads haben. 
A4AF versucht, dies zu vermeiden. Warum? Man kann nicht zwei Blöcke zur gleichen Zeit vom gleichen Client herunterladen. Durch das Aktivieren von A4AF sagt man aMule, nach Clients zu suchen, die sowohl bei dieser als auch bei anderen Dateien in der Downloadliste stehen, und sie bei den anderen zu entfernen. Dadurch bekommt man für diese Datei mehr Quellen. 
Man kann auch einen Download auf das Gegenteil setzen, um A4AF andersherum anzuwenden, also Quellen an andere Downloads abzugeben. Das sollte für Dateien getan werden, die nicht so dringend sind, oder erst nach einer anderen ähnlichen Datei heruntergeladen werden sollen (z.B. bei einer Serie von Dateien). 
Man kann das als eine Möglichkeit, persönliche Vorliegen in den Downloads einzustellen, ansehen.

Wenn eine Quelle gewechselt wird, bleibt der Platz in der Warteschlange dabei erhalten.

'''HINWEIS:''' Quellen mit einem Warteschlangenplatz kleiner als 50 beim Download mit der höheren Priorität werden niemals ausgewechselt. Damit wird sichergestellt, dass der Download auch beginnt.

== Wo ist der Unterschied zwischen "übertragen" und "fertiggestellt" in der Downloadliste? ==
Übertragen ist die Gesamtmenge an Daten, die man für die ausgewählte Datei erhalten hat. Die Daten sind komprimiert, sobald sie ankommen, werden sie von aMule verarbeitet und entpackt. Die Gesamtmenge an Nutzdaten (also die Teile, die wirklich zur Datei gehören, alles andere sind Header, Prüfsummen usw.) kann in der Spalte Fertiggestellt abgelesen werden. can be viewed in the Completed column.

== Was ist der Unterschied zwischen Pausieren und Stoppen eines Downloads? ==
Wen ein Download pausiert, werden alle Verbindungen die zu diesem Download gehören getrennt so dass keine Daten mehr übertragen werden, die Quellen werden aber beibehalten, bei der Wiederaufnahme wird aMule also versuchen, die Quellen wieder zu kontaktieren.
Wird ein Download gestoppt, werden auch die Quellen verworfen, bei der Wiederaufnahme wird aMule als von neuem beginnen, Clients zu finden, die diese Datei haben.

== Wofür sind die ganzen Dateien, die aMule beim ersten Start anlegt? ==
Most them are the same as [[eMule|eMule]]'s. Here is a list and the meaning of each of them (have in mind that you might not have all of them on your hard disk): 
~/.eMule: aMule's personal configuration (that is, things such as you nickname, your Temp and Incoming directories, your upload and download limits, and such...). 
~/.aMule/addresses.dat: Contains a list of serverlist URLs to check (if enabled in Preferences) for new servers on startup. 
~/.aMule/amulesig.dat: This is [[aMule_Project_FAQ:About|aMule]]'s [[signature|OnLineSignature]] file, which is the same as [[eMule|eMule]]'s [[signature|signature]] (see onlinesig.dat below) but with extended information (extended information includes nickname, session and total downloaded and uploaded bytes, [[aMule_Project_FAQ:About|aMule]] version, [[aMule_Project_FAQ:About|aMule]] uptime and number of shared files). 
~/.aMule/aMule.tmpl: This is the template file which [[amuleweb|aMule WebServer]] uses to create the web page. 
~/.aMule/aMule-online-sign.png: This file will only exist if CAS has been run sometime with the -o switch and ~/.aMule/casrc was successfully configured. It is an image containing details on [[aMule_Project_FAQ:About|aMule]]'s status. 
~/.aMule/casrc: This file will only exist if [[CAS|CAS]] has been run sometime with the -o switch. It contains the settings for the [[CAS|CAS]] image creation. 
~/.aMule/clients.met: Contains the public hashes of other known clients along with the credits it owes each of them. 
~/.aMule/cryptkey.dat: It contains the unique 384 bit private RSA key of your client. 
~/.aMule/emfriends.met: Contains your friends list configuration 
~/.aMule/ipfilter.dat: This file contains the IP ranges and access levels restrictions which will be passed to ipfilter. 
~/.aMule/Incoming: By default, the directory where [[aMule_Project_FAQ:About|aMule]] stores the completed downloads. 
~/.aMule/known.met: This file stores the hashes and some details of your shared files like size, path, statics, etc... 
~/.aMule/known2.met: This file stores the verified [[AICH]] hashes of your shared files. 
~/.aMule/lastversion: This is only for [[aMule_Project_FAQ:About|aMule]] to know if it's the first time you're starting [[aMule_Project_FAQ:About|aMule]], if you had [[aMule_Project_FAQ:About|aMule]] installed before and which version you had installed previously. 
~/.aMule/logfile: This file contains the log of the last [[aMule_Project_FAQ:About|aMule]] execution. 
~/.aMule/muleconn: This file is a socket for [[aMule_Project_FAQ:About|aMule]] communications. 
~/.aMule/onlinesig: This is an [[eMule|eMule]] compatible [[signature|OnLineSignature]] file. It's used by other applications to know basic information on [[aMule_Project_FAQ:About|aMule]]'s stat (if it's online, which server it's connected to, upload and download rate, and clients in queue). 
~/.aMule/preferences.dat: Contains the public key of your client, also known as user hash. 
~/.aMule/server.met: This is a list of all known servers and you're preferences on them (priority, name, ip, port and such). 
~/.aMule/shareddir.dat: Stores the paths to all shared directories. 
~/.aMule/Temp: By default, the directory where [[aMule_Project_FAQ:About|aMule]] stores the not completed downloads (temporary files). 
~/.aMule/webserver: This directory contains the necessary files for aMule WebServer to display a nice Web page. 
Other files on ~/.aMule/ are most surely backups of some of the above files. 
Also, on the Temp directory (which is ~/.aMule/Temp by default but can be set to any other on Preferences), [[aMule_Project_FAQ:About|aMule]] will create, for each download three or four files): 
*.part: This file contains the downloaded parts (not chunks, since not completed chunks are also stored here) of the download. As [[aMule_Project_FAQ:About|aMule]] is able to download from more than one user at the same time, this file has the size of the complete file. The missing parts are filled with zeros. 
*.part.met: This file contains information on the downloaded parts of the download, the verified chunks, the hash values of the remaining chunks, etc... 
*.part.met.bak: This are backups of the *.part.met files. Every now and then aMule creates this backups since without the *.part.met file, a download has no meaning for aMule. If any *.part.met file "disappeared, you should rename the *.part.met.bak to *.part.met. 
*.part.met.seeds: This file only exists if you have enabled to store the IPs of sources of rare files in the preferences, so that [[aMule_Project_FAQ:About|aMule]] can try to connect to these sources again after a restart.

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

Moving the half downloaded files is easy: just place them from your [[eMule]] temp directory (by default ''C:\Program files\eMule\Temp'' into ''~/.aMule/Temp'' or whatever your temp directory is in your [[aMule]] configuration.

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

== I just installed [[aMule_Project_FAQ:About|aMule]] for the first time. How do I set it up? ==
Setting up aMule properly is just a matter of tastes and depends on many factors. If you just wish a quick startup configuration, then continue reading. 
Open [[aMule_Project_FAQ:About|aMule]] and click on the Preferences button. Set a nickname and the language in which you wish to have [[aMule_Project_FAQ:About|aMule]]. Then switch to the Connection tab and input your Line Capacities. Then input the Bandwidth Limits according to the maximum amount of bandwidth you want [[aMule_Project_FAQ:About|aMule]] to use. Then switch to the Directories tab and set a directory for both the temporary files (where files will be stored until they are completely downloaded) and the completed files. Finally, select the directories which you want to share. It is not recommended to share too much files. Read bellow "What are the best settings I can set to have a nice download rate". To select recursively all directories inside a certain directory read [[aMule_problems#Is there any way to recursively select a whole directory and its contents?|Is there any way to recursively select a whole directory and its contents?]].

== Will [[aMule_Project_FAQ:About|aMule]] handle my [[xMule]] and [[lMule]] files? What should I do? ==
[[aMule_Project_FAQ:About|aMule]] automatically handles both [[lMule]] and [[xMule]]'s configuration files, but in different ways: 
[[lMule]] has been discontinued for several years now, so [[aMule_Project_FAQ:About|aMule]] understands that you are replacing [[lMule]] with [[aMule_Project_FAQ:About|aMule]], so it renames ~/.lMule folder to ~/.aMule. If you used ~/.lMule/Temp and ~/.lMule/Incoming as your temporal and downloading directories respectively, you should change the paths in Preferences to ~/.aMule/Temp and ~/.aMule/Incoming respectively. 
[[xMule]] is officially dead since May 2004 (official [[xMule]]'s death announcement on [[xMule]] forums by its main developer at, the now non-existent web page, [http://www.xmule.org http://www.xmule.org]), but for historical reasons, [[aMule_Project_FAQ:About|aMule]] will remain the ~/.xMule directory with its name and just copy from it its configuration files. This means that the files you were downloading will remain in the ~/.xMule directory if they were downloading there, but since [[aMule_Project_FAQ:About|aMule]] has handled [[xMule]]'s configuration files, it will use still use it. You can either live with that, or move directories ~/.xMule/Temp and ~/.xMule/Incoming into ~/.aMule and change directories in Preferences.

== How do I start my [[aMule_Project_FAQ:About|aMule]] experience? ==
Just click on the Connect button. You should have some servers listed on the Servers window, though. If you have no servers listed, then click on the little button below the Connect button in the Servers window before clicking the Connect button. After some time, [[aMule_Project_FAQ:About|aMule]] will be connected to some server (you'll know because in the lower right corner the "Not connected" message will disappear). When connected, switch to the Search window and search for the file you want and once you find the file you want, double-click on it. 
For general [[aMule_Project_FAQ:About|aMule]] usage, join [[aMule_Project_FAQ:About|aMule]] #amule in irc.freenode.net or ask in forums at [http://www.amule.org/amule http://www.amule.org/amule]

== What are the best settings I can set to have a nice download rate? ==
If you understood "Is there any limit on the [[FAQ_eD2k-Kademlia|ED2K]] network?" then you might have seen that, if your provider allows you, the best is to have the upload limit set to a minimum of 10 KBps. Also, if you understood "What is all that credits, rate and score stuff about?", you might also understand that the more you upload, the more you download, so take the upload limit up as much as you can, share well known and popular files (don't share too much (not more than approximately 200 files) or you'll get banned from some servers for giving too much traffic) and try to share small-sized popular files since some [[FAQ_eD2k-Kademlia|ED2K]] clients give extra credits for providing them a whole small-sized files. A good tip (thanks to kaouete) when you are trying to download some rare or "never completing" file, is, whenever you see someone uploading to you some chunk of that file, give that client a friend slot so that, if it tries to download something from you, it gets preference and you gain credits on that client.

== Is there a way to open a text file and load all the ed2k links from the file? ==
Yes, there is. Just place all the ed2k links you want to download in a text file, each ed2k link in a separate line. Name that file ''ED2KLinks'' then place it in ''~/.aMule'' and aMule will automatically detect it, add all those ed2k links to download and remove the file. 
You might want to read [[ED2KLinks_file|this]] to know more about this file.

== Can I manage [[aMule_Project_FAQ:About|aMule]] remotely through telnet in the same way I do with [[eDonkey2000|eDonkey]]? ==
Yes you can, but not exactly in the same way as you do with [[eDonkey2000|eDonkey]]. Just start a normal telnet (or ssh) session with the host computer (the one running [[aMule_Project_FAQ:About|aMule]]) and, once in, use amulecmd to take control over [[aMule_Project_FAQ:About|aMule]]. To start new downloads just use the [[ed2k_command|ed2k command]]. Remember [[aMuleCMD]] must be configured. 
Another aMule utility that might be of your interest is [[CAS]] (which's command is <code>cas</code>) which will show basic [[aMule_Project_FAQ:About|aMule]] statistics. 
Also, [[amuleweb|aMule WebServer]] might be what you are looking for if you can and don't mind using a web browser on the client computer. Have in mind that aMule WebBrowser must also be configured.

== Is there any way to start [[aMule_Project_FAQ:About|aMule]] with no graphical interface? ==

Yes. Since aMule 2.0.0-rc6, you can use aMule Daemon, which can be executed on the command line by typing ''amuled''. To control it, use either aMuleWeb, aMuleCMD or any other such application for remotely controlling aMule.

Anyway, up to aMule 2.0.0-rc6, [[aMule_Project_FAQ:About|aMule]] was a monolithic application. This means that core and GUI were whole inseparable block.

So, for those using an old aMule version or who refuse to use aMuled (aMule Daemon), there are still two walkarounds to run [[aMule_Project_FAQ:About|aMule]] on command line but they're not direct ways:
*Through ''[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]''
*Through ''[http://www.realvnc.com VNC]''

'''Through ''[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]:''' 
You should run <code>[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]</code> and then run aMule in it. Afterwards you can take control over [[aMule_Project_FAQ:About|aMule]] using [[aMuleCMD]] and [[ed2k_command|ed2k]] in the same way as you would if you were accessing [[aMule_Project_FAQ:About|aMule]] remotely over telnet (see above).

Short example: 
Run [http://xfree.org/4.4.0/Xvfb.1.html Xvfb]: 
<code>Xvfb :1 -screen 0 640x480x16 &</code> 
Set display to use for amule: 
<code>export DISPLAY=:1</code> 
Then run [[aMule_Project_FAQ:About|aMule]]: 
<code>amule &</code> 
Note: After running <code>export DISPLAY=:1</code>, all graphical applications launched from that shell will be opened in [http://xfree.org/4.4.0/Xvfb.1.html Xvfb]'s display. To avoid this, you can run [[aMule_Project_FAQ:About|aMule]] with the following command, so that only [[aMule_Project_FAQ:About|aMule]] runs there: 
<code>DISPLAY=:1 amule &</code> 
'''INFO:''' See the [[Screen]] page to know more about the [[Screen]] command

'''Through ''[http://www.realvnc.com VNC]:''' 
It's also possible to use ''vncserver'' instead of [http://xfree.org/4.4.0/Xvfb.1.html Xvfb] to achieve something similar. Just install ''vncserver'' and execute ''vncserver :0 -geometry 1024x768'' followed by ''export DISPLAY=:0''. This will create a hidden [http://xfree.org X] server, accessible only remotely using a [http://www.realvnc.com VNC] client. Once the [http://xfree.org X] server is running, you will need a window manager to manage [[aMule]] window (well, it's not really needed, but it's useful if you want to be able to close [[aMule]] without simply killing it), I recommend [http://fluxbox.sourceforge.net FluxBox] due to its low CPU and memory requirements. Just start it with ''fluxbox &'' and then run [[aMule]] with ''amule &''. Now you can connect to the [http://www.realvnc.com VNC] server and see the [[aMule]] window.

Keep in mind that if [[aMule]] shows any dialog that requires user input (like the one showed the first time [[aMule]] is executed), it will get stuck there until someone connects to the [http://www.realvnc.com VNC] server and clicks ok in the dialog. Usually, this should only need to be done once (and this connection may be used to update the serverlist and set the preferences), from then on [[aMule]] will start without user interaction, showing only some informational messages at startup.

If you need help on this issue, search [[aMule_Project_FAQ:About|aMule]]'s [http://www.amule.org/amule forums] or join #amule [[IRC]] channel at irc.freenode.net and ask.

== Can I run two [[aMule_Project_FAQ:About|aMule]] instances at the same time? ==
Yes you can, although it is not recommended. [[aMule_Project_FAQ:About|aMule]] will only check if the concurrent user is running some [[aMule_Project_FAQ:About|aMule]] instance, so you can run as many [[aMule_Project_FAQ:About|aMule]] instances as user accounts you have access to. To do this, just run <code>xhost +</code> and then <code>su</code> as another user and run aMule from that shell. 
Be aware, since [[aMule_Project_FAQ:About|aMule]] can't check if a user is running [[aMule_Project_FAQ:About|aMule]] on another X display. So, if your account is already running some [[aMule_Project_FAQ:About|aMule]] instance in some other X display, do not run another [[aMule_Project_FAQ:About|aMule]] instance on another X display or you might end up with lost configuration settings and corrupt chunks.

== How can I get those nice [[aMule_Project_FAQ:About|aMule]] statics some people post on the IRC channels? ==
You can either copy and paste [[CAS]]'s (C [[aMule_Project_FAQ:About|aMule]] Statics) output (to execute [[CAS]], run <code>cas</code>) or, if you use xChat as your IRC client and have the Perl module installed, you could use [[XAS]] (xChat [[aMule_Project_FAQ:About|aMule]] Statics).

== What is slot allocation? ==
Each upload is a slot, so, if you are uploading to five clients at the same time, you have five upload slots established. So, the amount of slot allocation is the bandwidth which each slot will be given. 
As an example, if your upload limit is 20KBps, you can set slot allocation to 2KBps which means 10 clients will be able to download from you at the same time, each of them at a maximum transfer rate of 2KBps. 
See section "Why is aMule ignoring the bandwidth I set per slot?" in [[AMule_problems|aMule common problem's FAQ]].

== What is a friend slot? ==
A friend slot is just a slot which is assigned to a client in the friends list. Only one friend can have a slot at the same time. Whenever that friend (who has the friend slot enabled) tries to download a file from you, it will be given highest priority in the uploads queue, since it has that slot always assigned. While that friend isn't downloading, that assigned slot will be given to the client with the highest priority in the upload queue, as expected.

== What is the real point on setting up Line Capacities in Preferences? Shouldn't [[aMule_Project_FAQ:About|aMule]] only care for the Bandwidth Limits? ==
aMule really only cares for the Bandwidth Limits. Line Capacities are only set for the Statics display. Let's see: Imagine you have a 100KBps connection, imagine you want to set the Limit at 40KBps because you have a web server which needs a minimum of 60KBps to serve all the petitions. Now imagine you download rare indonesian free songs. You most surely never download at more than 3KBps ever. So, you could set Line Capacities at 5KBps so that the graph at Statics has some meaning, since if you set it up as a 100KBps connection, the graph will show an horizontal line with no meaning at all.

== aMule is crashing quite often here. Can I set it to restart every time it crashes? ==
No, you can't. But you can have scripts to do so. Some of these scripts even work if aMule '''hangs''' but doesn't '''crash'''. 
The following scripts might suit your needs: 
[http://www.amule.org/amule/thread.php?threadid=1232 http://www.amule.org/amule/thread.php?threadid=1232] 
[http://www.amule.org/amule/thread.php?threadid=542 http://www.amule.org/amule/thread.php?threadid=542] 
[http://deepthought.ena.si/mulerunner http://deepthought.ena.si/mulerunner]

== Can I have aMule get data from the standard input to pass it to GDB or Valgrind? ==
Yes, you can. Up to aMule 2.0.0-rc3 this wasn't allowed, but as of version 2.0.0-rc4 you can with the parameter ''-i'' or ''--enable-stdin''. 
Anyway, people with aMule versions previous to 2.0.0-rc4 can use [http://www.amule.org/amule/thread.php?threadid=2474 phoenix's aMule stdin patch].

== How can I switch to aMule from eMule without loosing my credits? ==
If you already read [[FAQ_aMule#What_are_all_those_files_aMule_creates_the_first_time_it_is_run?|about the meaning of aMule's files]], you might already know what you have to do: 
Get ''cryptkey.dat'', ''clients.met'' and ''preferences.dat'' files from eMule's config directory (usually, under Windows, something like ''C:\Program files\eMule\config'') and copy them into ''~/.aMule''. Now start aMule so it reads those files. You're done!

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