AMule Project FAQ - User contributions [en]

AMule problems-it

2007-04-28T17:10:50Z

87.14.231.86:

<center>
<u><h4>[[aMule_Project_FAQ:About|aMule]] Problemi comuni</h4></u>

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

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

== Quando faccio partire aMule mi esce il messaggio "aMule already running: exiting". Posso farlo partire lo stesso? ==

Il messaggio è molto chiaro: [[aMule]] sta già girando. Ma questo non si riferisce al sistema, significa che ''tu'' (il tuo account utente) sta già facendo girare [[aMule]].

Potrebbe sembrare che non ci sia nessuna istanza di [[aMule]] in esecuzione, se c'è stato un crash. Ma qualche volta succede che qualche processo non si chiuda totalmente, rimanendo in uno stato chiamato ''zombi'' o ''defunto''. Per scoprire se questo è il tuo problema, esegui in un terminale ''ps u | grep amule'' e se compare qualche messaggio (a parte quello di grep stesso), allora qualche processo di aMule sta girando a tuo nome. Per ucciderlo, chiudilo normalmente (se puoi) oppure fallo con ''kill -9 <aMile PID>'' oppure con ''killall -9 amule'' oppure prova ad uscire e rientrare (che nella maggior parte dei casi chiuderà tutti i processi di [[aMule]] a meno che tu l'abbia avviato con ''nohup'' o simili).

Se sei sicuro che nessun processo di [[aMule]] stia girando, controlla se esiste un file [[MuleLock_file|muleLock]] nella tua cartella ~/.aMule e cancellalo per ripristinare il funzionamento normale di [[aMule]].

Se nessuna delle soluzioni è adatta per te, puoi eseguire un'altra istanza di [[aMule]] come altro utente (se puoi entrare con un altro nome utente, chiaramente).
Leggi [FAQ_aMule#Can_I_run_two_aMule_instances_at_the_same_time?|Can I run two aMule instances at the same time?]].

== aMule parte ma non compare la schermata, anche se funziona. Cosa sta succedendo? ==

Questo succede di solito quando imposti il tipo di integrazione nel vassoio di sistema a ''Minimizza nel vassoio'' (da Preferenze -> Generale). Questo fa partire [[aMule]] minimizzato.

Per recuperare la schermata di aMule, modifica ''~/.aMule/amule.conf'' e cerca ''StartupMinimized=1'' Cambia questa riga a ''StartupMinimized=0''.
Questo script farà il lavoro per te:

''sed s/StartupMinimized=1/StartupMinimized=0/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf''

Quando farai partire [[aMule]] la prossima volta imposta la giusta integrazione nel vassoio dalle Preferenze, per riuscire a minimizzare [[aMule]] senza che venga nascosto.

Se per qualche motivo questo metodo non funziona, prova a cambiare l'integrazione nel vassoio manualmente, togliendo la crocetta dall'opzione ''Abilita icona vassoio''. Per farlo, apri ''~/.aMule/amule.conf'' e imposta il valore di ''DesktopMode='' a ''4''. Questo script farà il lavoro per te:

''sed s/DesktopMode=[0-9]/DesktopMode=4/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf''

'''NOTA:''' Nelle versioni di [[aMule]] precedenti a 2.0.0rc4, imposta a ''1'' invece di ''4'' perché il file delle preferenze è stato cambiato.

== aMule parte ma non si connette/si comporta in modo strano/si blocca ogni pochi secondi/ecc...? ==

Le versioni di aMule fino alla 2.0.0-rc3 non devono essere linkate ai wxWidgets 2.5.x e neanche al GTK2, anche se qualche distribuzione lo fa. Assicurati che non sia il tuo caso. In caso di incertezza, spedisci il tuo backtrace a [http://www.amule.org/amule/board.php?boardid=33 aMule's Backtraces forum] oppure vai sul canale IRC di aMule #amule at irc.freenode.net

== Dove sono i miei file scaricati? ==

Di default, aMule memorizza i file completati in ''~/.aMule/Incoming'' ma siccome la cartella ''~/.aMule'' è nascosta (inizia con un punto), il tuo file manager potrebbe non visualizzarla. Assicurati di impostare il file manager a visualizzare le cartelle nascoste.

Di default i file in corso di scaricamento sono in ''~/.aMule/Temp'', per cui anche in questo caso per vederli occorre impostare il file manager.

== Perché aMule richiede così tante risorse CPU all'avvio? ==

aMule sta calcolando gli hash dei nuovi file che ha trovato nelle cartelle condivise.

Se aMule occupa sempre molta CPU anche quando nessun nuovo file è stato aggiunto o modificato nelle cartelle condivise, allora c'è qualcosa che non va.

Nelle versioni di aMule precedenti la 2.0.0-rc3 questo succedeva quando la cartella Temp, Incoming o qualsiasi cartella condivisa era in una partizione FAT32. Ora questo non succede più.

Inoltre nelle versioni di aMule precedenti la 2.0.0-rc4, i filesystem con codifica UTF-8 (per esempio con SUSE 9.1) potrebbero presentare problemi quando qualche file o cartella condivisa contiene un carattere speciale. Se questo è il tuo problema, c'è un rimedio (grazie '''nachbarnebenan'''): dopo che aMule ha calcolato gli hash dei file condivisi (cioè quando smette di occupare la CPU) chiudi aMule e codifica ~/.aMule/known.met in UTF-8 (lo puoi fare con ''[http://www.gnu.org/directory/recode.html recode]'' con il seguente comando: ''recode u8 ~/.aMule/known.met''). Questo va fatto ogni volta che un file viene aggiunto o modificato nelle cartelle condivise. Forse è meglio aggiornare aMule all'ultima versione.

Se niente finora ti ha aiutato, è successo qualcosa al file ''known.met'' , forse qualche programma esterno o qualche altro utente lo ha rovinato. E' meglio cancellarlo, far partire aMule e lasciare che ricalcoli tutti gli hash dei file.

== Adesso aMule parte, ma mi dice "Nessun server valido nella lista dei server" ==

Hai abilitato l'opzione "Connetti automaticamente solo ai server statici". Cancella questa opzione oppure metti qualche server nella lista statica.

Per togliere l'opzione, vai a Preferenze -> Server -> Connetti automaticamente solo ai server statici

Per aggiungere un server alla lista statica, vai alla finestra Server e fai clic destro sul server che vuoi aggiungere alla lista. Poi scegli "Aggiungi alla lista statica" e ripeti il procedimento per tutti i server che vuoi mettere nella lista statica.

== Perché ogni tanto all'improvviso aMule ha pochi/nessun server nella lista? ==

Hai probabilmente abilitato le opzioni
Preferenze -> Server -> Rimuovi i server dopo X tentativi
Preferenze -> Connessione -> Riconnetti dopo perdita connessione

Se è così, hai probabilmente perso la connessione di rete (Internet o LAN) per un periodo di tempo, per cui aMule ha perso la connessione al server ED2K ed ha cercato di connettersi ad altri server fino a quando sono stati tutti cancellati dalla lista (dopo X tentativi ciascuno).

Per risolvere il problema, disabilita l'opzione "Rimuovi i server dopo X tentativi". Disabilitare questa opzione è sicuro nella maggior parte dei casi.
Probabilmente non vorrai disabilitare l'altra opzione "Riconnetti dopo perdita" per cui lasciala abilitata.

== aMule si connette al server, ma ottiene sempre un ID basso. Perché? Posso farci qualcosa? ==

Possono esserci tre ragioni:
*Qualche porta necessaria è chiusa nel tuo firewall. Leggi [[FAQ_eD2k-Kademlia-it#What_is_LowID_and_HighID?|questo]] e controlla [http://www.amule.org/testport.php qui] se le porte sono aperte.
*Il server è molto occupato o forse mal configurato, per cui ti da un [[Low-ID]]. Non puoi fare nient'altro che cercare di riconnetterti o cercare un altro server.
*Alcuni ISP proibiscono l'uso di applicazioni P2P come aMule, non permettendo il traffico tramite le usuali porte P2P. In questi casi, configura aMule per usare qualche altra porta. Sarebbe ancora meglio se fosse una porta usata di solito per qualche altro servizio. Con qualche ISP ha funzionato sulla porta TCP 25600.

== [[aMule]] si è interrotto mentre completava un file e ora non lo completa mai (anche se è scaricato al 100%). Come lo completo? ==

Questa è facile: Chiudi [[aMule]]. Adesso vai nella cartella Temp (di solito
''~/.aMule/Temp'') e scrivi questo comando:

''touch ./*''

Poi fai ripartire [[aMule]] e lascialo completare i file.

== I just lost a download. Is there any way I can recover it? ==

This is strange to happen, but it might, although in most cases it is the result of some non-aMule-related stuff going weird (or user's fault).<br>
Two things may have happened. Either *.part.met files were deleted, or *.part files were deleted.

If *.part files have disappeared, the only solution is to restart the downloads from the beginning (if *.part.met files are still there, aMule will restart the downloads on next start). However this should '''never''' happen unless the user directly deleted them.

If *.part.met files have disappeared but *.part files are still in the Temp directory, then search if *.part.met.bak are also in the Temp directory. If they are, then just rename ''*.part.met.bak'' files to ''*.part.met'' just by running:

''for file in *.part.met.bak; do mv -f "$file" "${file%.bak}; done''

Still, it could happen that, although you have the *.part files, neither *.part.met nor *.part.met.bak files exist any longer. In this case, you would have two ways ways to work out of this:

Either, use [http://www.bigwillystyle42.com/mfr/ MetFileRegenerator] (Java needed) to reconstruct the *.part.met files.

Or, search again on aMule for the files you were downloading and rename their part number in the *.part.met files to the ones it used to have. For example, if you were downloading ''aMule_1.2.6.tar.gz'' and that was being downloaded in Temp directory as ''008.part'', then that file used to have it's corresponding ''008.part.met'' file and, probably, it's ''008.part.met.bak'' file. But this two latter files have mysteriously disappeared. Then search again on aMule for ''aMule_1.2.6.tar.gz'' and start downloading it. Close aMule and you'll have this new download as, for example, ''011.part'' file in the Temp directory. Of course, this download will have it's ''011.part.met'' file. Well, rename ''011.part.met'' to ''008.part.met'' and then delete ''011.part'' (and ''011.part.met.bak'' if it existed). Now start aMule and you will have recovered the download from the point it was before the *.part.met files disapeared.

== Why does aMule suddenly become unresponsive to the mouse although it's not hanged? ==

It sometimes happens that you left a dialog window somewhere hidden in the desktop. aMule is waiting for that window to be closed, so it becomes unresponsive until you click OK, Cancel, or whatever you have to click.

So, make sure there's no aMule dialog left around in '''any workspace'''.

== Why are some files in my shared folders not shown in the Shared Folders window? ==

This could happen if you added this files after aMule has been started. Press the "Reload" button on Shared Folders window and it should find the new files and hash them (this may take some CPU time).

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

== I always get a message about addresses.met when I start aMule. What's wrong? ==

This happens when you enable the option Preferences -> Servers -> "Auto-update serverlist at startup" and you have no serverlists' urls in ''addresses.dat''. You can either add some to ''addresses.dat'' by adding them at Preferences -> Servers -> List or just disable Preferences -> Servers -> "Auto-update serverlist at startup" if you don't really need it.

== I sometimes get a message on the log about credits being lost. Should I be worried? ==

No, you don't need to be worried. Credits for a client are deleted after 150 days (more or less 5 months) without "seeing" that client. Also, bad clients might lose their credits too. So those messages are just for debug information, you shouldn't worry about them.

== What should I do if I lose my ''cryptkey.dat'' file? ==

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

== Why is Upload/Download limit always back to 0 after every restart? ==

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

== Why is aMule ignoring the bandwidth I set per slot? ==

The bandwidth set to each slot can be set in Preferences, but it will be ignored if the bandwidth set per slot doesn't allow at least three connections at the same time.

So, the maximum speed allowed per slot is '''BandwidthLimit/3'''.

Please do '''NOT''' confuse '''Bandwidth limit''' with '''Bandwidth Capacity'''. Read [[FAQ_aMule#What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?|What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] since the meaning of the Bandwidth Capacity setting is not intuitive.

Also, if [[aMule]] detects that, after having set all the slots for uploading, still some bandwidth is left before getting to the Bandwidth Limit, it will allow another slot and divide all the slot bandwidths to so use the same amount of bandwidth.

Example:
*Bandwidth Limit: 7 KBps
*Slot allocation: 2 KBps

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

== Why can't I set aMule's download limit to more than X? ==

To keep the ED2K network alive, all ED2K clients have an upload/download limits ratio hardcoded which, depending on the upload limit set, is:
*<u>From 0KBps to 3KBps:</u>
*DownloadLimit can't be more than UploadLimit*3
*<u>From 4KBps to 9KBps:</u>
*DownloadLimit can't be more than UploadLimit*4
*<u>UploadLimit values over 9KBps:</u>
*There's <b>no</b> DownloadLimit limitation.

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

== I set Upload Limit to 0KBps, but aMule is still transferring. What did I do wrong? ==

Setting Upload limit to 0KBps will not stop transfers, instead, ''0'' value means '''unlimited''', so, it's right the opposite of you're trying to do. There's no way to stop aMule from uploading files, and that's the same on all ED2K clients (eMule, eDonkey, etc). Allowing people not to upload would bring the ED2K network to it's end.

Even if you don't share any directory, the Temp directory will '''always''' be shared, so that files that you are downloading are shared with other clients.

== Why am I getting "Too many connections" messages on the terminal? ==

This happens when you set a very high value at Preferences -> Connections -> "Connection limits" -> "Max connections". If this value is as almost as big as the the amount of connections your system allows you to have, then aMule will fail to establish connections and display those messages (have in mind that other applications may also have some connections established).

On Windows 9x/ME platforms there is a limit of 100 TCP connections so, although you might set aMule to establish more than 100 connections, it will be unable to do so. You can change Windows's TCP connections limit by editing the Windows Register ('''Start -> Run -> regedit.exe''') and setting (you'll most surely have to add the value since in most cases it doesn't exist):

''HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections'' (which is a String type and it's value must be a 32-bit number).

== My progress bars have lost most of their 3D effect and look more ugly now. Can I turn its look back? ==

In most aMule versions setting the progress bar style to the most right on Preferences -> "GUI tweaks" is the way to have the progress bar have the best 3D effect. But in versions 2.0.0-rc4 to 2.0.0-rc6 the best 3D effect is given when the style bar is set to the middle. Setting it to the most right would give the progress bar a flat look while setting it to the most left will give it a dark look.

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

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

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

== Why can't I preview a file? ==

First of all you must know that [[aMule]] only allows to preview video files.

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

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

== Why isn't [[aMule]]'s Preview working at all with MPlayer? ==

Since aMule 2.0.0-rc4 Preview command isn't being run in the same terminal as aMule. As a result, your Preview program may fail to start. This is the case of MPlayer. If you need a terminal to run your Preview player, use some command like ''xterm -e <preview-app>'' i.e.:

''xterm -T "aMule preview" -iconic -e mplayer -idx''

== After exitting MPlayer on Preview, my aMule keeps locked? ==

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

== Why is ''Transfered'' a smaller number than ''Completed''? ==

It's a common mistake to think it should be bigger or, at least, equal.

Please read [[FAQ_aMule#What_is_the_difference_between_Transfered_and_Completed_in_the_Tranfers_window?|What is the difference between Transfered and Completed in the Tranfers window?]] to know more about this.

== aMule always slows down my computer when it completes a download. Is this a normal behaviour? ==

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

== Is there any way to recursively select a whole directory and its contents? ==

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

And that's it.

== I downloaded a file and it got corrupted somehow by my hard disk or some external application once completed. Can I avoid redownloading the whole of it? ==

If you still have the [[ed2k_link|ed2k:// link]], start the download again and when a whole chunk (9.28MB) has been downloaded (any chunk), close [[aMule]], rename the corrupted file to the filename the current download has (something like ''002.part''), touch the corrupted file (i.e.: ''touch ~/.aMule/Temp/002.part*'') and restart [[aMule]].

[[aMule]] will detect the completed chunks and the corrupted ones, and will only download the chunks which got corrupted.

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

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

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

== Downloaded files don't get the permissions I set in Preferences. Why? ==

aMule must follow the permissions it is allowed to set by ''umask''. ''umask'' sets the permissions which applications should '''not''' be allowed to assign files.

Therefore, if you set, for example, file permissions to ''664'' in aMule's Preferences, and umask's value (check it by running ''umask'') is ''022'', aMule will create files with permissions ''644'' (that is, ''664'' - ''022'' = ''644'').

== aMule fails to create files/shows file descriptor errors. What's going on? ==

This should never happen. If it happens chances are you have the resources limits very low, so aMule is denied to create/open new files. Run ''ulimit -a'' to check your resources limits. Read ''man ulimit'' to learn how to set the limits as you want them, and remember that this has to be set on every system restart (probably your distribution provides a configuration file which sets this automatically).

AMule problems-de

2007-04-28T16:55:09Z

87.14.231.86:

<center>
<u><h4>[[aMule-de|aMule]] - Allgemeine Probleme</h4></u>

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

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

== Wenn ich aMule starten möchte, bekomme ich in der Konsole die Meldung "aMule already running: exiting". Kann ich aMule trotzdem starten? ==

Die Meldung ist sehr eindeutig: [[aMule-de|aMule]] läuft bereits. Das bezieht sich aber nicht auf das gesamte System, vielmehr darauf, daß '''du''' (dein User-Account) [[aMule-de|aMule]] bereits ausführst.

Es könnte den Anschein haben, als ob keine Instanz von [[aMule-de|aMule]] läuft, wenn er bei dir abgestürzt ist. Allerdings geschieht es gelegentlich, daß einige Prozesse nicht vollständig beendet wurden, und nun als sogenannter ''Zombie'' oder auch in einem ''unkontrollierten'' Zustand beibehalten werden. Um herauszufinden, ob dieses Problem vorliegt, führe ''ps u | grep amule'' aus, und wenn irgendeine Ausgabe (abgesehen von der grep-Ausgabe selbst) erscheint, dann läuft unter deinem Account ein anderer aMule-Prozess. Um ihn zu beenden, schließe ihn wie gewohnt (falls möglich), oder lösche ihn mit ''kill -9 <aMule-PID>'' oder ''killall -9 amule'', oder logge dich aus, und wieder ein (was in den meisten Fällen alle [[aMule-de|aMule]]-Prozesse beendet, sofern man [[aMule-de|aMule]] nicht mit ''nohup'' oder etwas ähnlichem aufgerufen hat).

Falls nichts davon für dich zutrifft, kannst du als anderer Benutzer eine weitere Instanz von [[aMule-de|aMule]] laufen lassen (vorausgesetzt, du kannst dich mit einem anderen Account einloggen). Lies [[FAQ_aMule-de#Kann_ich_zwei_Instanzen_von_aMule_zur_gleichen_Zeit_laufen_lassen?| Kann ich zwei Instanzen von aMule zur gleichen Zeit laufen lassen?]].

== aMule startet, aber wird nicht angezeigt, obwohl er gut funktioniert. Was geht da vor? ==

Das geschieht üblicherweise, wenn man die Art der Systrayintegration in Allgemeine Einstellungen -> Verschiedene Optionen auf ''minimiert starten'' gestellt hat, wodurch [[aMule-de|aMule]] minimiert startet.

Um die GUI wiederherstellen zu können, muß man die ''~/.aMule/amule.conf'' editieren, dort nach ''StartupMinimized=1'' suchen, und die Zeile in ''StartupMinimized=0'' ändern. Das folgende Script nimmt einem diese Arbeit ab:

''sed s/StartupMinimized=1/StartupMinimized=0/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf''

Stelle nach einem Neustart von [[aMule-de|aMule]] dann in den Einstellungen die richtige Art der Sytray-Integration ein, sodaß du amule minimiert starten kannst, ohne daß er versteckt wird.

Falls dies alles nicht hilft, dann versuche, die Systray-Integration durch das Ausschalten der Option "Tray-Icon aktivieren" manuell auf den Standardwert zu setzen. Dazu stelle den Wert ''DesktopMode='' in der ''~/.aMule/amule.conf'' auf ''4''. Das folgende Script erledigt das für dich:

''sed s/DesktopMode=[0-9]/DesktopMode=4/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf''

'''ANMERKUNG:''' Bei [[aMule-de|aMule]]-Versionen vor 2.0.0rc4, solltest du diesen Wert auf ''1'' statt auf ''4'' einstellen, weil die Speicherung der Voreinstellungen etwas geändert wurde.

== aMule verbindet nie/verhält sich seltsam/stürzt nach einigen Sekunden ab/etc...? ==

aMule-Versionen bis zu 2.0.0-rc3 sollten nicht gegen wxWidgets 2.5.x oder GTK2 gelinkt werden, obwohl einige Linuxdistributionen dazu neigen. Bitte vergewissere dich, daß dies bei dir nicht der Fall ist. Falls du dir nicht sicher bist, paste dein Rückverfolgungsprotokoll ins [http://www.amule.org/amule/board.php?boardid=33 aMule Backtrace-Forum], oder besuche den aMule-Chat #amule auf irc.freenode.net

== Wo sind meine runtergeladenen Dateien? ==

In der Grundeinstellung speichert aMule die fertiggestellten Dateien in ''~/.aMule/Incoming'', aber weil ''~/.aMule'' ein verstecktes Verzeichnis ist, zeigt dein Dateimanager es möglicherweise nicht an. Vergewissere dich, daß bei deinem Dateimanager das Anzeigen versteckter Dateien eingeschaltet ist.

Als Vorgabe werden Dateien, die gerade runtergeladen werden, in ''~/.aMule/Temp'' abgelegt, deshalb nochmal, dies ist ein verstecktes Verzeichnis, und der Dateimanager muß so eingestellt sein, daß er es anzeigen kann.

== Warum verbraucht aMule beim Starten so viel Prozessorleistung? ==

Das geschieht, weil [[aMule-de|aMule]] neugefundene Dateien in den freigegebenen Verzeichnissen neu hasht.

Wenn [[aMule-de|aMule]] immer beim Starten sehr viel Rechenleistung braucht, obwohl in den freigegebenen Verzeichnissen keinerlei neue Dateien hinzugefügt oder in irgendeiner Weise verändert wurden, dann ist etwas nicht richtig.

Bei den aMule-Versionen vor 2.0.0-rc3 konnte dies geschehen, wenn Temp, Incoming, oder irgendein freigegebenes Verzeichnis auf einer FAT32-Partition lag. Seit aMule 2.0.0-rc3 passiert dies jedoch nicht mehr.

Weiterhin konnten bei aMule-Versionen vor 2.0.0-rc4 Dateisysteme mit UTF-8-Kodierung (konnte bekanntlich bei SuSE 9.1 passieren) Probleme bereiten, sobald eine Datei oder ein Verzeichnis im Pfad der freigegebenen Verzeichnisse ein bestimmtes Zeichen enthalten war. Falls dies dein Problem sein sollte, hier eine Schritt-für-Schritt-Anleitung (danke '''nachbarnebenan'''): Nachdem aMule alle freigegebenen Dateien gehasht hat (was der Fall ist, wenn die hohe CPU-Beanspruchung aufhört), schließe aMule, und kodiere die ~/.aMule/known.met in UTF-8 (das geht mit dem Programm ''[http://www.gnu.org/directory/recode.html recode]'' durch Ausführung des Befehls: ''recode u8 ~/.aMule/known.met''). Das sollte man immer machen, sobald eine Datei irgendeinem freigegebenen Verzeichnis hinzugefügt, oder bearbeitet wird. Deshalb ist es am besten, auf die aktuellste aMule-Version zu aktualisieren.
Falls das alles nichts hilft, könnte irgendwas mit der Datei ''known.met'' nicht stimmen, die möglicherweise durch irgendwelche Fremdprogramme, oder durch den Benutzer zerstört wurde. Am bestenlöscht man die dann, startet aMule neu, und läßt ihn alle Dateien nei hashen.

== So, aMule startet jetzt, aber weshalb gibt er die Meldung "Keine gültigen Server zum Verbinden in der Serverliste gefunden" aus? ==

Weil du die Option "Automatisches Verbinden nur zu Servern aus der statischen Liste" aktiviert hast. Deaktiviere sie, oder füge der statischen Liste einige Server hinzu.

Um diese Funktion zu deaktivieren, gehe in die Einstellungen -> Server -> "Automatisches Verbinden nur zu Servern aus der statischen Liste"

Um der statischen Liste einen Server hinzuzufügen, öffne das Serverfenster, und klicke mit der rechten Maustaste auf einen Server, den du der statischen Liste hinzufügen möchtest. Dann wähle "Markiere Server als statisch", und verfahre so mit jedem weiteren hinzuzufügenden Server.

== Warum hat aMule plötzlich keine/nur noch ganz wenige Server in seiner Serverliste? ==

Möglicherweise sind diese Optionen aktiviert: Unter Einstellungen -> Server -> "Entferne tote Server nach X Versuchen" und Einstellungen -> Verbindung -> "Wiederverbinden nach Trennung".

Falls das der Fall ist, wurde vermutlich die Internetverbindung (oder LAN etc.) für eine zeitlang getrennt, sodaß aMule gemerkt hat, daß er nicht mehr mit einem eD2k-Server verbunden ist, und er versuchte deshalb, sich mit anderen Servern zu verbinden, und zwar solange, bis dann alle Server entfernt waren (jeder nach X Versuchen).

Um dieses Problem zu lösen, deaktiviere die Option "Entferne tote Server nach X Versuchen". Das Ausschalten der Option "Entferne tote Server nach X Versuchen" ist meistens sicher. Vermutlich möchtest du nicht "Wiederverbinden nach Trennung" deaktivieren, also lasse es an.

== aMule verbindet zu einem Server, aber bekommt nur eine niedrige ID. Warum? - Und, kann ich etwas dagegen tun? ==

Das kann aus dreierlei Gründen der Fall sein:
*Irgendein benötigter Port in deiner Firewall ist nicht geöffnet. Lies [[FAQ_eD2k-Kademlia-de#Was_sind_niedrige_und_hohe_IDs?|dies hier]], um zu erfahren, was zu tun ist, und überprüfe [http://www.amule.org/testport.php hier], ob deine Ports offen sind.
*Der Server ist ziemlich ausgelastet oder schlecht konfiguriert, und gibt dir deshalb eine [[Low_ID]]. In diesem Fall kann man nichts dagegen tun, außer, sich erneut zu verbinden, oder sich mit einem anderen Server zu verbinden.
*Einige ISPs verbieten die Verwendung von P2P-Programmen wie aMule, und erlauben deshalb keinen Datenverkehr über bekannte P2P-Ports. In diesem Fall stelle aMule so ein, daß er auf einem anderen Port läuft. Es wäre sogar besser, wenn es sich dabei um einen bekannten Port handeln würde, der normalerweise für einen anderen Zweck benutzt wird. Es ist bekannt, daß es bei einigen ISPs mit dem TCT-Port 25600 klappt.

== [[aMule-de|aMule]] wurde beim Fertigstellen einer Datei unterbrochen, und stellt sie jetzt nie fertig (obwohl sie zu 100% runtergeladen wurde). Wie kann man sie fertigstellen? ==

Das ist einfach: [[aMule-de|aMule]] beenden. Nun in das Tempverzeichnis (Standard: ''~/.aMule/Temp'') wechseln, und dort den folgenden Befehl ausführen:

''touch ./*''

Zum Schluß [[aMule-de|aMule]] ausführen, und ihn die Dateien komplettieren lassen.

== Ich habe soeben einen Download verloren. Kann ich den irgendwie wiederherstellen? ==

Es ist merkwürdig, daß so etwas passiert, aber es könnte, obwohl es meistens das Ergebnis irgendwelcher nicht-aMule-bezogener Dinge ist, die sich eigenartig verhalten (oder ein Anwenderfehler).<br>
Zweierlei kann passiert sein: Entweder wurden *.part.met-Dateien, oder *.part-Dateien gelöscht.

Falls *.part-Dateien verschwunden sind, ist die einzige Lösung, die Dateien wieder von Anfang an neu runterzuladen (falls die *.part.met-Dateien noch vorhanden sind, macht aMule das beim nächsten Neustart von selbst). Allerdings sollte sowas '''niemals''' passieren, außer, der Benutzer hat sie direkt gelöscht.

Falls die *.part.met-Dateien verschwunden sind, aber die *.part-Dateien noch im Temp-Verzeichnis vorhanden sind, dann schau nach, ob noch die dazugehörige *.part.met.bak im Temp-Verzeichnis gibt. Falls ja, dann benenne die ''*.part.met.bak'' einfach wie folgt in ''*.part.met'' um:

''for file in *.part.met.bak; do mv -f "$file" "${file%.bak}; done''

Es kann vorkommen, daß man zwar die *.part-Dateien hat, aber es weder *.part.met, noch *.part.met.bak-Dateien dazu gibt. In diesem Fall können zwei Wege zum Erfolg führen:

Entweder, verwende den [http://www.bigwillystyle42.com/mfr/ MetFileRegenerator] (Java erforderlich), um die *.part.met-Dateien neu zu erzeugen.

Oder suche nochmal im aMule nach den Dateien, die du runtergeladen hattest, und benenne ihre part-Nummer in diejenige *.part.met-Dateien um, die sie haben sollten.

Wenn du zum Beispiel ''aMule_1.2.6.tar.gz'' runtergeladen hattest, und der im Tempverzeichnis ''008.part'' hieß, dann sollten normalerweise auch die dazugehörigen Dateien ''008.part.met'' und vermutlich seine ''008.part.met.bak'' im Tempverzeichnis liegen. Aber die beiden letzteren Dateien sind auf ungeklärte Art und Weise verschwunden. Dann suche erneut im aMule nach ''aMule_1.2.6.tar.gz'', und beginne damit, ihn runterzuladen. Beende den aMule wieder, und du hast diesen neuen DOwnload als, sagen wir mal, ''011.part'' im Tempverzeichnis. NAtürlich wird dieser Download seine ''011.part.met'' haben. Nun benenne diese ''011.part.met'' in ''008.part.met'' um, und lösche dann die ''011.part'' (und die ''011.part.met.bak'', falls vorhanden). Jetzt starte aMule neu, und du hast den Download von dem Zeitpunkt aus wiederhergestellt, an dem er war, bevor die *.part.met-Dateien verschwanden.

== Warum reagiert aMule plötzlich nicht mehr auf die Maus, obwohl er sich nicht aufgehängt hat? ==

Das geschieht manchmal, wenn man noch ein Dialogfenster im Hintergrund auf der Arbeitsoberfläche geöffnet hat. aMule wartet darauf, daß dieses Fenster geschlossen wird, und reagiert deshalb solange nicht, bis man OK, Abbrechen, oder was auch immer zu bestätigen ist, angeklickt hat.

Deshalb solle man sich vergewissern, daß kein Dialog auf '''irgendeiner Arbeitsoberfläche''' eine Eingabe erwartet.

== Warum werden einige Dateien in meinen Freigabeverzeichnissen nicht im Fenster der freigegebenen Dateien angezeigt? ==

Das kann passieren, wenn man die Dateien hinzugefügt hat, wenn aMule bereits läuft. Nach Drücken des Aktualisierungsknopfes im Fenster der freigegebenen Dateien sollte er sie aber finden und neu hashen (was etwas Prozessorzeit beanspruchen kann).

Allerdings kam es bei einigen Releases dazu, daß einige Dateien nach einem aMuleneustart aus dem Fenster der freigegebenen Verzeichnisse verschwunden waren, obwohl sie sich in den freigegebenen Verzeichnissen befanden. Dann hilft nur, die ''~/.aMule/known.met'' zu löschen, um sie wieder zu sehen, was natürlich dann beim nächsten aMulestart wahrscheinlich etwas Rechenzeit verlangt, weil die alle neu gehasht werden müssen.

== Ich bekomme immer eine Meldung über eine addresses.met, wenn ich aMule starte. Was ist das nun wieder? ==

das passiert, wenn du unter Einstellungen -> Server -> "Serverliste beim Start automatisch aktualisieren" eingeschaltet hast, aber keine Serverlistenadressen in der ''addresses.dat'' drinstehen. Du kannst entweder über Einstellungen -> Server -> Liste welche in die ''addresses.dat'' einfügen, oder einfach den Menüpunkt "Serverliste beim Start automatisch aktualisieren" deaktivieren, wenn du ihn nicht wirklich brauchst.

== Manchmal erhalte ich eine Nachricht im Log, daß Credits gelöscht wurden. Sollte ich besorgt sein? ==

Nein, du brauchst nicht beunruhigt zu sein. Die Credits eines Clients werden nach 150 Tagen (ungefähr fünf Monate) gelöscht, wenn der in der Zwischenzeit nicht "gesehen" wurde. Weiterhin verlieren schlechte Clients ebenfalls ihre Credits. Daher sind solche Meldungen einfach nur Debuginformationen, du solltest dich nicht weiter darum kümmern.

== Was kann ich machen, wenn ich meine ''cryptkey.dat'' verloren habe? ==

Der Verlust dieser Datei bedeutet, daß du all deine Credits verloren hast. Sorry. Weil du jetzt wieder damit anfangen mußt, neue Credits zu sammeln, mußt du die ''~/.aMule/preferences.dat'' löschen, andernfalls kannst du keine Credits von [[client|clients]] bekommen, die dich schonmal vorher identifiziert haben (bevor die cryptkey.dat verlorenging).

== Warum steht das Upload/Download-Limit nach jedem Neustart immer wieder auf "0"? ==

Das passierte bei aMule-Versionen vor 2.0.0-rc4, wenn man versuchte, einen Upload- oder Download-Wert in den Bandbreiteneinstellungen zu wählen, der höher war, als der Upload- oder Download-Wert bei den Kapazitäten. Seit Version 2.0.0-rc4 ist das aber beseitigt (lies [[FAQ_aMule-de#Warum_sollte_man_die_maximalen_Leitungskapazitäten_in_den_Einstellungen_angeben?_Sollten_aMule_denn_nicht_nur_die_Bandbreiten-Beschränkungen_interessieren?| Warum sollte man die maximalen Leitungskapazitäten in den Einstellungen angeben? Sollten aMule denn nicht nur die Bandbreiten-Beschränkungen interessieren?]] zum besseren Verständnis), und sollte nicht mehr passieren.

== Warum ignoriert aMule die eingestellte Bandbreite per Slot? ==

Die Bandbreiteneinstellung pro Slot kann in den Einstellungen vorgenommen werden, wird aber ignoriert, wenn die Bandbreite pro Slot nicht mindestens drei Verbindungen zur selben Zeit gewährleistet.

Deshalb ist die erlaubte Höchstgeschwindigkeit pro Slot '''Bandbreitenlimit/3'''.

Bitte verwechsle '''NICHT''' das '''Bandbreitenlimit''' mit den '''Bandbreitenkapazitäten'''. Lies [[FAQ_aMule-de#Warum_sollte_man_die_maximalen_Leitungskapazitäten_in_den_Einstellungen_angeben?_Sollten_aMule_denn_nicht_nur_die_Bandbreiten-Beschränkungen_interessieren?| Warum sollte man die maximalen Leitungskapazitäten in den Einstellungen angeben? Sollten aMule denn nicht nur die Bandbreiten-Beschränkungen interessieren?]], weil die Bedeutung der Bandbreiteneinstellungen nicht intuitiv ist.

Wenn [[aMule-de|aMule]] außerdem feststellt, daß, nachdem alle Uploadslots eingestellt sind, noch Bandbreite verfügbar ist, bevor das Limit erreicht wird, erlaubt er einen weiteren Slot, und teilt die Bandbreite dann gleichmäßig auf alle Slots auf.

Beispiel:
*Bandbreitenlimit: 7 kB/s
*Slotzuweisung: 2 kB/s

Wenn [[aMule-de|aMule]] die Slots für einige Clients einrichtet, bemerkt er nach der Vergabe des dritten Slots, daß keine weiteren 2kB/s verfügbar sind, weil das Limit 7 beträgt, aber immer noch 1kB/s übrig ist, bevor das Bandbreitenlimit erreicht wird. Deshalb vergibt er, statt dem letzten Slot eine Verbindung mit 1kB/s zu geben (und die anderen bei 2kB/s zu belassen), an alle vier Slots je eine Verbindung von 1,8kB/s Bandbreite.

== Warum kann ich aMules Downloadlimit nicht höher als X einstellen? ==

Um das eD2k-Netzwerk am Leben zu erhalten, haben alle eD2k-Clients eine Upload/Downloadlimit-Ratio fest einprogrammiert, die vom eingestellten Uploadlimit abhängig ist:

*<u>Von 0kB/s bis 3kB/s:</u>
*DownloadLimit kann nicht höher sein als Uploadlimit*3
*<u>Von 4kB/s bis 9kB/s:</u>
*DownloadLimit kann nicht höher sein als UploadLimit*4
*<u>UploadLimit-Werte über 9kB/s:</u>
*<b>Keine</b> DownloadLimit-Beschränkung.

Vorsicht beim Einstellen von 0kB/s als Uploadlimit. Es könnte nicht das bedeuten, was du meinst, daß es ist. Lies [[AMule_problems-de#Ich_stelle_die_Uploadbegrenzung_auf_0kB/s_ein,_aber_aMule_überträgt_immer_noch._Was_mache_ich_falsch?|Ich stelle die Uploadbegrenzung auf 0kB/s ein, aber aMule überträgt immer noch. Was mache ich falsch?]], um sicherzugehen, daß du verstehst, was gemeint ist.

== Ich stelle die Uploadbegrenzung auf 0kB/s ein, aber aMule überträgt immer noch. Was mache ich falsch? ==

Das Einstellen des Uploadlimits auf 0kB/s beendet nicht die Datenübertragung, sondern der Wert ''0'' bedeutet '''unbegrenzt''', sozusagen genau das Gegenteil dessen, was du zu tun versuchst. Es gibt keine Möglichkeit, um aMule daran zu hindern, Dateien hochzuladen, und das ist bei anderen eD2k-Clients (eMule, eDonkey, etc) ebenfalls so. Leuten zu erlauben, nichts hochzuladen, würde das Ende des eD2k-Netzwerkes bedeuten.

Sogar, wenn du keine Dateien freigibst, wird das Temp-Verzeichnis '''immer'' freigegeben, sodaß Dateien, die man gerade runterlädt, für andere Clients freigegeben sind.

== Warum bekomme ich in der Konsole die Meldung "Zu viele Verbindungen"? ==

Das passiert, wenn du einen zu hohen Wert unter Einstellungen -> Verbindungen -> "Verbindungseinstellungen" -> "Maximale Verbindungen" eingestellt hast. Wenn dieser Wert fast die bei deinem System mögliche Verbindungsanzahl erreicht, kann aMule keine Verbindungen mehr aufbauen, und gibt diese Meldung aus (beachte, daß andere Anwendungen ebenfalls aufgebaute Verbindungen benötigen könnten).

Auf Systemen mit Windows 9x/ME beträgt das Limit 100 TCP-Verbindungen, deshalb kann aMule auch nicht mehr als eben diese 100 Verbindungen aufbauen, obwohl du ihn bielleicht so eingestellt hast, daß er dies tun müßte. Du kannst die Begrenzung der TCP-Verbindungen unter Windows ändern, indem du die Registry bearbeitest ('''Start -> Ausführen -> regedit.exe'''), und dort einstellst (du wirst mit ziemlicher Sicherheit den Wert hinzufügen müssen, da er meistens gar nicht existiert):

''HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections'' (das ist ein String, dessen Wert als 32-Bit-Zahl angebenen werden muß.

== Meine Fortschrittsbalken haben fast keinen 3D-Effekt mehr, und sehen ziemlich hässlich aus. Kann ich das wieder rückgängig machen? ==

In den meisten aMule-Versionen wird der beste 3D-Effekt daduech erzielt, indem man den Schieber unter Einstellungen -> GUI-Einstellungen ganz nach rechts stellt. Aber in Versionen 2.0.0-rc4 bis 2.0.0-rc6 wurde der beste 3D-Effekt erzeugt, wenn der Stil-Schieber in der Mitte stand. Ihn an den äußersten rechten Rand zu stellen, ergab einen flachen Fortschrittsbalken, während er bei einer Einstellung zum äußersten linken Rand dunkler wurde.

== All meine Downloads stehen plötzlich auf Pause, und ich kann sie nicht fortsetzen. Was passiert da? ==

Überprüfe, ob auf dem Dateisystem, in dem das Temp-Verzeichnis liegt, genug freier Plattenplatz vorhanden ist. Falls dort genug Platz ist, überprüfe, ob mehr frei ist, als in Einstellungen -> Dateien -> "Min. Festplattenplatz" eingestellt ist.

Der Festplattenplatz, den [[aMule-de|aMule]] mindestens verlangt, beträgt 9.28 MB, weil [[aMule-de|aMule]] soviel benötigt, um einen [[FAQ_eD2k-Kademlia-de#Was_ist_ein_Chunk?|Chunk]] runterladen zu können.

== Warum habe ich keine Dateivorschau? ==

Zuerst solltest du wissen, daß [[aMule-de|aMule]] nur eine Vorschau für Videodateien erlaubt.

Zur Dateivorschau braucht [[aMule-de|aMule]] zwei Dinge:
*Die Datei muß eine bekannte Videodateiendung im Dateinamen haben
*Du mußt die ersten 256KBs der Datei runtergeladenhaben

Manchmal geschieht es trotzdem, daß eine Dateivorschau möglich wäre, aber [[aMule-de|aMule]] diese nicht zuläßt. Dann gehe in das Tempverzeichnis, und schau sie dir manuell an, falls möglich und erwünscht.

== Warum klappt die Dateivorschau von [[aMule-de|aMule]] überhaupt nicht mit MPlayer? ==

Seit aMule 2.0.0-rc4 wird der Vorschaubefehl nicht mehr im gleichen Terminal wie aMule ausgeführt. Demzufolge kann dein Vorschauprogramm nicht starten. Dies ist bei MPlayer der Fall. Falls du ein Terminal brauchst, um MPlayer auszuführen, verwende einen Befehl wie ''xterm -e <preview-app>'', z.B.:

''xterm -T "aMule preview" -iconic -e mplayer -idx''

== Nach dem Beenden der Vorschau mit MPlayer bleibt aMule gesperrt? ==

Die Vorschau sperrte normalerweise den aMule absichtlich bis zum Erreichen der Version 2.0.0-rc4. Daraus folgte, daß Leute, die den MPlayer verwendeten, unter einem Fehler im MPlayer zu leiden hatten, der beim Schließen des MPlayer-Hauptfensters den Hauptprozess im Hintergrund weiter geöffnet ließ. Man konnte diesen Fehler im MPlayer bei Versionen vor 2.0.0-rc4 umgehen, indem man den MPlayer durch Betätigen der'''Q'''-Taste beendete. Auf jeden Fall ist es besser, aMule auf die letzte Version zu aktualisieren.

== Warum steht bei ''Übertragen'' eine kleinere Zahl, als bei ''Fertiggestellt''? ==

Es ist ein weitverbreiteter Fehler, anzunehmen, daß sie größer, oder zumindest gleichgroß sein sollte.

Bitte lies [[FAQ_aMule-de#Wo_ist_der_Unterschied_zwischen_%C3%BCbertragen_und_fertiggestellt_in_der_Downloadliste?|Wo ist der Unterschied zwischen "übertragen" und "fertiggestellt" in der Downloadliste?]], um mehr darüber zu erfahren.

== aMule macht meinen Rechner beim Fertigstellen eines Downloads immer so langsam. Ist das normal? ==

Ja, das ist es. Wenn aMule einen Download fertigstellt, prüft er, ob dieser nicht beschädigt ist. Obgleich dies auch schon während des Downloads geprüft wird (durch Hashwertüberprüfung der einzelnen [[FAQ_eD2k-Kademlia-de#Was_ist_ein_Chunk?|Chunk]]s), hasht aMule, sobald die Datei komplett runtergeladen ist, alle [[FAQ_eD2k-Kademlia-de#Was_ist_ein_Chunk?|Chunk]]s, um zu prüfen, ob die zuvor runtergeladenen Teilstücke nicht irgendwie inzwischen, während der Rest der Datei runtergeladen wurde, durch den Benutzer oder externe Anwendungen zerstört wurden

== Gibt es eine Möglichkeit, ein komplettes Verzeichnis mitsamt seinem Inhalt rekursiv auszuwählen? ==

Ja, die gibt es. Und sie ist einfach:
*Bei [[aMule-de|aMule]] 2.0.0-rc4 oder höher, ein Rechtsklick auf das Icon des Verzeichnisses, das du rekursiv auswählen möchtest.
*Bei [[aMule-de|aMule]] 1.x und bis zu (einschließlich) 2.0.0-rc3, während des Anklickens die STRG-Taste (CTRL) gedrückt halten.

Fertig.

== Ich habe eine Datei runtergeladen, die jetzt irgendwie durch meine Festplatte oder eine externe Anwendung beim Fertigstellen beschädigt wurde. Kann ich es irgendwie vermeiden, die gesamte Datei erneut runterzuladen? ==

Wenn du noch den [[ed2k_link|ed2k:// link]] hast, dann beginne den Download nochmal, bis du (irgend)einen kompletten [[FAQ_eD2k-Kademlia-de#Was_ist_ein_Chunk?|Chunk]] (9.28MB) davon runtergeladen hast, beende [[aMule-de|aMule]], benenne die kaputte Datei in den Dateinamen des gerade runtergeladenen Downloads (irgendetwas wie ''002.part'') um, leere die kaputte Datei (z.B..: ''touch ~/.aMule/Temp/002.part*'') und starte [[aMule-de|aMule]] neu.

[[aMule-de|aMule]] wird die fertigen und die zerstörten [[FAQ_eD2k-Kademlia-de#Was_ist_ein_Chunk?|Chunks]] erkennen, und nur die kaputten erneut runterladen.

== Was sollte man über die Verwendung von Netzlaufwerken mit [[aMule-de|aMule]] wissen? ==

Beim Verwenden von NFS-Mounts (Network File System) mit [[aMule-de|aMule]] vergewissere dich, daß du die Einbindung für diese Laufwerke (diejenigen von dem Computer, der runtergefahren wird) mit dem Rechner, auf dem [[aMule-de|aMule]] läuft, gelöst hast, weil sonst [[aMule-de|aMule]] einfach solange hängenbleibt, bis die Einbindung zu diesen Netzwerklaufwerken wieder besteht. Wie merkt man das? Wenn du [[aMule-de|aMule]] über Nacht laufen läßt, dir am nächsten Tag die Statistiken anschaust, dort gerade Linien (nicht Null) bei den Statistiken über [[Download]]/[[Upload]]/[[Connect-de|Connect]] siehst, und diese Linien dann nach dem Mounten der NFS-Laufwerke gegen Null abfallen, und dann wieder ein normales Verhalten zeigen, ist das ein Anzeichen dafür. Zusätzlich sollte man [[aMule-de|aMule]] nach dem Lösen der NFS-Laufwerkseinbindung zu einem Rechner, der runtergefahren werden soll, die freigegebenen Dateien '''neu laden''' lassen.

''All das habe ich während meiner frustrierenden Erlebnisse an unzähligen Tagen ohne nächtliche Downloads bemerkt ;) ... --[[User:PedroAlgarvio|PedroAlgarvio]] 00:25, 15 Jun 2005 (CEST)''

== Die runtergeladenen Dateien haben nicht die eingestellten Zugriffsrechte. Warum? ==

aMule muß sich an die Berechtigungen halten, die er laut ''umask'' setzen darf. ''umask'' bestimmt die Zugriffsrechte, die Dateien '''nicht''' durch Anwendungen zugewiesen werden sollen.

Wenn beispielsweise beim aMule die Dateizugriffsrechte in den Voreinstellungen auf ''664'' eingestellt sind, und der Wert von ''umask'' (überprüfe ihn, indem du ''umask'' ausführst) ''022'' beträgt, wird aMule deshalb Dateien mit den Zugriffsrechten ''644'' anlegen (weil ''664'' - ''022'' = ''644'' ist).

== aMule kann keine Dateien erzeugen/gibt Filedesciptor-Fehler aus. Was ist los? ==

Das sollte niemals passieren. Falls es geschieht, ist es sehr wahrscheinlich, daß die Begrenzung der zugewiesenen Ressourcen zu gering sind, sodaß es aMule verweigert wird, Dateien neu zu erzeugen/zu öffnen. Führe ''ulimit -a'' aus, um deine Ressourceneinstellung zu überprüfen. Lies ''man ulimit'', um zu lernen, wie die Ressourcenbegrenzungen nach deinen Vorstellungen eingestellt werden, und denke daran, daß dies bei jedem Systemstart geschehen muß (wahrscheinlich liefert deine Distribution eine Konfigurationsdatei mit, die das automatisch einstellt).

AMule problems-hu

2007-04-28T16:54:43Z

87.14.231.86:

<center>
<u><h4>[[aMule_Project_FAQ:About|aMule]] - gyakori problémák</h4></u>

<h2>eredeti változat: ''[[User:Jacobo221|Jacobo221]]''</h2>

[[AMule_problems|English]] | [[AMule_problems-es|Español]] | [[AMule_problems-nl|Nederlands]] | '''Magyar''' | [[AMule_problems-de|German]] | [[AMule_problems-it|Italiano ]]
</center>

== Ezt a hibaüzenetet kapom az [[aMule-hu|aMule]] indításakor a konzolban: "aMule already running: exiting". El tudom indítani valahogy? ==

Az üzenet egyszerű: az [[aMule-hu|aMule]] már fut a gépeden. Egészen pontosan azon felhasználó alatt, akitől indítani próbálod.

Előfordulhat, hogy láthatóan nem fut a program, ha előtte lefagyott. Ilyenkor ún. ''zombi'', vagy ''defunct'' szálak jönnek létre, így a rendszer úgy érzékeli, a program még fut. A ''ps u | grep amule'' parancs kiadásával ellenőrizheted ez-e a helyzet. Ha a grep szálán kívül mást is mutat, a ''kill -9 <az_aMule-PID_száma>'' vagy ''killall -9 amule'' parancsokkal próbálhatod meg lelőni őket, de az is előfordulhat, hogy ki kell jelentkezned, majd újra be.

Ha a fentiek egyike sem felel meg, indíthatsz új klienst is, de csak más felhasználó alatt. Olvasd el az [[FAQ_aMule#Can_I_run_two_aMule_instances_at_the_same_time?]] oldalt, hogyan.

== Az aMule elindul, de nem látszik az ablak, miközben a háttérben rendben fut. Mi történt?==

Ez olyankor szokott megtörténni, mikor a Beállítások -> Általános fülön a "Tálca ikon engedélyezése" mellett az "Indítás minimalizálva opció be van jelölve. Ilyenkor a program a tálcára kicsinyítve fut, de esetleg ott nem látszik.
Hogy visszakapd eredeti állapotában, keresd meg a ''StartupMinimized=1'' sort az ''~/.aMule/amule.conf'' fileban, és írd át ''StartupMinimized=0''-ra, vagy használd a következő parancsot:

''sed s/StartupMinimized=1/StartupMinimized=0/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf''

A következő indítás után, állítsd be megfelelően a "Systray Integration" kapcsolót, hogy legközelebb a program tényleg feltűnjön a tálcán.

Ha a fentiek valami okból kifolyólag nem működnek, próbáld meg kézzel megváltoztatni a systray integration módját. Ehhez az előző fileban keresd meg a "DesktopMode=" sort, és állítsd vissza az alapértelmezett értékre, "4"-re, hasonlóan az előzőhöz pl.:

''sed s/DesktopMode=[0-9]/DesktopMode=4/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf''

''A fenti probléma a frissebb verziók, és wxWidgets 2.5 vagy 2.6 használata esetén nem fordul elő, a "Systray integration" opció meg sem jelenik a Beállításokban. A ''DesktopMode'' automatikusan kerül beállításra, ha az ablakkezelő támogatja a funkciót.''

'''MEGJEGYZÉS:''' Az [[aMule-hu|aMule]] 2.0.0rc4 előtti verzióiban ''1''-re kell állítani a ''DesktopMode""-ot, ''4''. Azóta változott az opció sematikája.

== Az aMule elindul, de sosem kapcsolódik, furcsán viselkedik, folyton lefagy, stb. ==

A 2.0.0-rc3-as verzióig bezárólag az [[aMule]]t nem szabad a wxWidgets 2.5.x-es verziójával, sem GTK2vel használni, néhány disztró mégis megteszi. Győződj meg róla, nem erről van-e szó. Ha nem egyértelmű, rakd fel a [[Backtraces|backtrace]] kimenetét az [http://www.amule.org/amule/board.php?boardid=33 aMule's Backtraces forum]ra, vagy érdeklődj [[IRC]]n.

== Hol vannak a letöltött filejaim? ==

Alapbeállítások mellet a program a kész fileokat az ''~/.aMule/Incoming'' könyvtárba rakja. Mivel az ''~/.aMule'' rejtett könyvtár, előfordulhat, hogy a filekezelőd nem mutatja, be kell állítanod a rejtett állományok megjelenítésére.

Ugyan ez vonatkozik a letöltés alatt álló fileokra is, ezek alapból az ''/.aMule/Temp'' könyvtárba kerülnek.

== Miért terheli annyira a processzort az aMule indulás után ==

Ez azért történik/történhet, ha a program hashelni kezdi az új fileokat a megosztott könyvtárban.

Ha mindig ezt csinálja, új állományok hozzáadása nélkül is, akkor valami gond van.

Az [[aMule-hu|aMule]] 2.0.0-rc3-as előtti verzióinál ez akkor történik általában, ha a Temp, Incoming vagy a megosztott könyvtárak valamelyike FAT32es partición foglal helyet. Az rc3-as verziótól felfelé ez a hiba nem jelentkezik.

Az [[aMule-hu|aMule]] 2.0.0-rc4-nél korábbi verziókban viszont (legfőképp SuSE 9.1 alatt) az UTF-8as kódolású filerendszerek esetén, ha valamelyik megosztott könyvtár speciális karaktert tartalmaz, szintén okozhatja ezt a problémát. Erre egy megoldás (köszönet érte '''nachbarnebenan'''nak):

miután a program befejezte a fileok hashelését (azaz, mikor már nem használja a CPUt), zárd be az [[aMule]]t és kódold át az ''~/.aMule/known.met'' filet UTF-8-ba (ezt megteheted a ''[http://www.gnu.org/directory/recode.html recode]'' programmal így: ''recode u8 ~/.aMule/known.met''). Ezt minden alkalommal meg kell ismételned, mikor megváltozik a megosztott fileok könyvtárának tartalma, szóval inkább használj újabb verziót.

Ha a fentiek egyike sem állja meg a helyét/használ, akkor tényleg valami zűr lehet a ''known.met'' fileal, külső beavatkozás hatására talán. A legbiztosabb, ha kitörlöd, és megvárod, míg az [[aMule]] újrahashel mindent.

== Az aMule elindul, de ezt az üzenetet írja ki: "Nem találtam érvényes kiszolgálót a kiszolgálólistában, amihez kapcsolódni lehetne" ==

Ez azért van, mert bejelölted az "Automatikus kapcsolódás kizárólag az állandó kiszolgálókhoz" opciót. Kapcsold ezt ki, vagy adj meg szervereket állandó kiszolgálónak. Hogy kikapcsold, menj a Beállítások -> Kiszolgáló részhez, és vedd ki a pipát a parancs elől. Szervereket az állandó listához adni a jobb klikkre előbukkanó menü "Kiszolgáló(k) megjelölése állandóként" ponttal tudsz, a szerverlistánál.

== Az aMule kapcsolódik ugyan a szerverhez, de mindig Low ID-t kapok, miért? és mit tudok tenni ez ellen? ==

Ennek három oka lehet:
*A szükséges portok nincsenek nyitva a tűzfaladon. olvasd el a [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?]] oldalt, hogy mit kell tenned, majd látogass el [http://www.amule.org/testport.php ide], ellenrőrizni, minden rendben van-e.
*A szerver túlterhelt, vagy rosszul van konfigurálva, ezért ad neked [[Low ID]]t. Nincs mit tenni ebben a helyzetben, hacsaknem újracsatlakozni, vagy másik szervert használni.
*Néhány szolgáltató tiltja a filemegosztó programok használatát, nem engednek adatforgalmat át a szokványos portokon. Ebben az esetben át kell állítanod a az alapértelmezett portokat, legjobb olyan, népszerű értékekre, amit más programok általában használnak. A 25600 TCP port a visszajelzések szerint a legtöbb esetben megfelelő.

== Az [[aMule-hu|aMule]] futása megszakadt, miközben egy filet véglegesített, így mostmár sosem akarja befejezni (annak ellenére, hogy a teljes file letöltődött). Hogyan tudom megoldani a problémát? ==

Lépj ki az [[aMule-hu|aMule]]ból, majd menj az ideiglenes mappába (általában '~/.aMule/Temp') és add ki a következő parancsot:

''touch ./*''

Indítsd el újra az [[aMule-hu|aMule]]t, és várd meg, míg véglegesíti az állományt.

== Eltűnt egy/több/minden letöltésem. Van mód arra, hogy visszaszerezzem? ==

Nem jellemző, hogy ez megtörténik, de ha mégis, valószínű, hogy valami [[aMule-hu|aMule]]tól független dolog az oka (pl. a felhasználó).

Két dolog történhetett, Vagy a *.part.met fileok , vagy a *.part fileok törlődtek.

Ha a *.part fileok tűntek el, nincs mit tenni, előlről kell kezdeni a letöltést (ha a *.part.met fileok még megvannak, a program automatikusan megkezdi a töltést a következő indításnál. Habár, ennek '''soha''' nem kéne megtörténnie, hacsak a felhasználó ki nem törli ezeket az állományokat).

Ha a *.part.met fileok vesztek el, a a *.part fileok még megvannak az ideiglenes könyvtárban, nézd meg, megvannak-e a *.part.met.bak állományok. Ha igen, csak nevezd át őket, leválasztva a ''.bak'' részt, pl így:

''for file in *.part.met.bak; do mv -f "$file" "${file%.bak}; done''

Rosszabb esetben, ha a .bak fileok is elvesztek, de a *.part állományok rendelkezésre állnak, két lehetőséged van:

Használhatod a [http://www.bigwillystyle42.com/mfr/ MetFileRegenerator], Java alapú programot hogy újraépítsd őket,
vagy keress rá újra a letöltésekre, majd nevezd át a megfelelő *.part.met fileokat, az előzőek számára. Azaz:

ha az ''aMule_1.2.6.tar.gz''t töltötted, és ez az ideiglenes könytárban ''008.part'' néven volt, ennek megvolt a megfelelő ''008.part.met'' és ''008.part.met.bak'' fileja, ám ez a kettő valahogy eltűnt. Keress rá megint az ''aMule_1.2.6.tar.gz''re és kezd el tölteni. Zárd be a programot, ez az új töltés megjelenik az ideiglenes könyvtárban pl. ''011.part'' néven, és meglesz a ''011.part.met'' is. Egyszerűen nevezd át a ''011.part.met''et ''008.par.met''re, és töröld ki a ''011.part''ot (valamint a ''011.part.met.bak''ot, ha létezik). indítsd el az [[aMule-hu|aMule]]t, és máris onnan folytatódik a letöltés, ahol a file eltűnése előtt tartott.

== Miért nem reagál hirtelen a program az egérre, ha nem is fagyott le? ==

Előfordul, hogy egy be nem zárt dialógusablak valahol elbújt a desktopon. Az [[aMule-hu|aMule]] arra vár, hogy ezt az ablakot bezárják, és addig nem reagál semmit, amíg ez meg nem történik.

Szóval, nézz körül, rendesen, '''minden''' munkaasztalon.

== Miért nem jelenik meg minden file a megosztottak között, ha mégis ott van? ==

Ez akkor történhet, ha az állomány a program indítása után került a megosztott könyvtárba. Nyomd meg a kis zöld ('megoszott fájlok frissítése') gombot a Megosztott Fájlok lapon, ekkor a hashingelés után a fileok bekerülnek a listába.

Habár, néhány régebbi verzióban előfordult, hogy fileok tűntek el a megosztott listából, ilyenkor az egyetlen lehetőség a ''~/.aMule/known.met'' törlése. Ilyenkor, persze a következő indításkor minden állományt újra kell hashelnie a programnak.

== Az aMule minden idításakor valami üzenetet kapok az addresses.met fileról. Mi a gond? ==

Ez akkor fordul elő, ha kijelölted a Beállítások -> Kiszolgáló -> "Kiszolgáló lista automatikus frissítése indításkor" kapcsolót, de nincs egyetlen szerverlista címe sem az ''addresses.dat'' fileban. Vagy adj hozzá legalább egyet a Beállítások -> Kiszolgáló -> Lista gomb lenyomásával, vagy egyszerűen kapcsold ki ezt a funkciót, ha nincs rá szükséged.

== Néha a logban elveszett kreditekről olvasok. Aggódnom kéne? ==

Nem, nem kell. A 150 napja (nagyjából 5 hónap) nem "látott" kliensek kreditjei törlődnek, ahogyan a hamisaké is. Ezek az üzenetek csak a hibakeresés miatt kerülnek a logba, nem kell velük törődnöd.

== Mit kell tennem, ha elveszett a ''cryptkey.dat'' fileom? ==

Ezen file elvesztése azt jelenti, hogy elveszted az összes kredited. Sajnálom. Mivel ez olyan, mintha elölről kezdenél mindent, ki kell törölnöd az ''~/.aMule/preferences.dat'' filet, különben azok a [[client|clients]], akik ezidáig ismertek, nem fognak majd azonosítani.

== Miért ugrik vissza minden indításnál a Feltöltési/Letöltési limit 0-ra? ==

Ez a 2.0.0-rc4 előtti verzióknál fordul elő, ha Le- vagy Feltöltési limit magasabb értékre van állítva, mint Sávok kapacitása. Mivel a 2.0.0-rc4-es verzióban ez ki lett javítva (olvasd el a [[FAQ_aMule#What_is_the_real_point_on_setting_up_Line_Capacities_in_Preferences?_Shouldn't_aMule_only_care_for_the_Bandwidth_Limits?|What is the real point on setting up Line Capacities
in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] cikket, hogy megértsd, miért), többet nem kéne megtörténnie.

== Miért nem veszi figyelembe az aMule a Slot kiosztásom? ==

A sávszélesség slotonkénti mértékét be lehet állítani a Beállításokban, de ezt csak akkor veszi figyelembe a program, ha ez legalább három kapcsolatot lehetővé tesz egy időben.

Azaz, a Slot kiosztás legnagyobb értéke a Sávszélességi korlát harmada. Lehetőleg ne keverd össze a '''Sávszélességi korlátok''' és a '''Sávok kapacitása''' értékeket. Olvasd el a [[FAQ_aMule#What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?|What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] cikket, mert a '''Sávok kapacitása''' érték nem egészen az, mint aminek elsőre hangzik!
Valamint, a feltöltési slotok kiosztása után, ha marad még felhasználható sávszélesség (a beállított limit szerint), a program mégegy slotot fog nyitni, és egységesen elosztja a vonal kapacitását.

Például:
*Sávszélességi korlát: 7 KBps
*Slot kiosztás: 2 KBps

Mikor a program három slotot nyitott, már nem tud még egyet, 2KB/s-mal, mert a korlát 7 KB/s, de még van 1 KB/s a vonalból a limitig. Ezért mégegy slotot fog nyitni, és ahelyett, hogy ennek 1 KB/s sebességet biztosítana (és a többieknek meghagyná a 2-t), mindenki 1.8 KB/s sebességgel tölthet le.

== Miért nem tudom a Letöltési korlátot nagyobb értékre állítani, mint X? ==

Az ED2K hálózat életben tartásának érdekében, a feltöltési/letöltési arány szigorúan szabott, és a feltöltési korláttól a következő mértékben függ:
*<u>0KB/s-tól 3KB/s-ig:</u> A Letöltési korlát nem lehet nagyobb, mint a Feltöltési korlát * 3
*<u>4KB/s-tól 9KB/s-ig:</u> A Letöltési korlát nem lehet nagyobb, mint a Feltöltési korlát * 4
*<u>9KB/s felett:</u> <b>Nincs</b> Letöltési korlát

Figyelj oda ha 0KB/s-ra állítod a Feltöltési limitet, olvasd el a [[AMule_problems-hu#Beállítom a Feltöltési korlátot 0KB/s-ra, de az aMule még mindig tölt. Mit csinálok rosszul?|Beállítom a Feltöltési korlátot 0KB/s-ra, de az aMule még mindig tölt. Mit csinálok rosszul?]] cikket, hogy biztosan tudd, mit teszel.

== Beállítom a Feltöltési korlátot 0KB/s-ra, de az aMule még mindig tölt. Mit csinálok rosszul? ==

A Feltöltési limit 0KB/s-ra állítása nem megállítja az adatforgalmat, ebben az esetben a ''0'' a ''végtelen''t jelenti, pont az ellenkezőjét, mint amit csinálni próbálsz. Nem tudod úgy beállítani az aMulet, hogy az ne töltsön felfelé, ahogyan egyik ED2K kliensen (eMule, edonkey stb.) sem. Megengedni a felhasználóknak, hogy ne töltsenek fel, a hálózat végéhez vezetne.

Szintén, ha nem osztasz meg semmit, az Ideiglenes könytár '''mindig''' meg lesz osztva, így a fileokat, amit te töltesz mások is elérik tőled.

== Miért kapok "Too many connections" (Túl sok kapcsolat) hibaüzenetet a terminálban? ==

Ez akkor történik, ha magasabb értéket állítasz be a Beállítások -> Kapcsolat -> "Kapcsolódási korlát" -> "Max kapcsolatok" alatt, mint amennyit az operációs rendszered engedélyez, így az aMule nem tud ennyit létrehozni (tartsd észben, hogy más programok is hozhatnak létre kapcsolatokat, így foglalva a "helyet").

A Windows 9x/ME rendszereken ez 100 TCP kapcsolatra van korlátozva. Ezt megváltoztatni a Windows Registryjében tudod ('''Start menü -> Futtatás -> regedit.exe'''), általában egy új változó létrehozásával (eredetileg nem szokott ilyen lenni), név szerint ''HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections'', ami String típus, és 32-bites szám kell legyen.

== A folyamatjelzőm elvesztette a 3D hatását, és nagyon csúnyán néz ki. Vissza tudom állítani valahogy? ==

A legtöbb aMule verzióban, a folyamatjelző csík 3D hatását a Beállítások -> GUI finomhangolások -> "Folyamatjelző stílus" csúszka jobbra állításával lehet elérni. Viszont a 2.0.0-rc4 és 2.0.0-rc6 verziók között, a legjobb hatás a csúszka középre állításával nyerhető, itt a bal oldal sötét, a jobb lapos hatást jelent.

== Minden letöltésem megakadt, és nem tudom őket elindítani. Mi történik? ==

Ellenőrizd, van-e elég szabad hely a merevlemezen/partíción, ahol az Ideiglenes könyvtár található. Ennek legalább annyinak kéne lennie, mint a Beállítások -> Fájlok -> "Min. szabad lemezterület értéke".

Az aMule számára szükséges minimális terület 9.28MB, mivel ennyi egy [[FAQ_ed2k#What_is_a_chunk?]] mérete.

== Miért nem működik az Előnézet MPlayerrel? ==

A 2.0.0-rc4-es verzió óta az előnézet parancs nem egy terminálon fut az aMulellal. Emiatt néhány program nem indul el, mint például az MPlayer. Ha ezt, vagy más, hasonló gondokkal küszködő lejátszót szeretnél használni, külön terminált kell futtatnod neki az ''xterm -e <lejátszóprogram>'' paranccsal, pl:

''xterm -T "aMule preview" -iconic -e mplayer -idx''

== Az MPlayert használva előnézethez, az aMule nem reagál? ==

Az előnézet, a 2.0.0-rc4-es verzióig direkt "lezárta" az aMulet. E miatt az MPlayert használók, a program egy hibája miatt (ami az MPlayert hagyja tovább futni, az ablak bezárása után), nem tudtak hozzáférni az aMulehoz. A megoldás, ha a lejátszóból a '''Q''' gomb lenyomásával lépsz ki, de mégjobb, ha a legújabb aMule verziót telepíted.

== Miért kisebb az ''Átmásolva'' értéke, mint a ''Befejezett''é? ==

Gyakori félreértés, hogy ennek nagyobbnak kéne lenni, de legalábbis egyenlőnek.
Olvasd el a [[FAQ_aMule#What_is_the_difference_between_Transfered_and_Completed_in_the_Tranfers_window?|What is the difference between Transfered and Completed in the Tranfers window?]] cikket, hogy megértsd, miért nem így van.

== Az aMule mindig leterheli a gépem, mikor véglegesít egy letöltést. Ez normális? ==

Igen, az. Mikor az aMule véglegesít egy letöltést, ellenőrzi, nem hibás-e a file. Habár ezt töltés közben is rendszeresen megteszi (minden chunk átesik hash-próbán), mikor az egész állomány lent van, minden chunk hashe ellenőrzésre kerül megint, hátha valami okból kifolyólag megsérült tárolás közben.

== Ki tudok jelölni egymásba ágyazott könyvtárakat egyszerre a megosztások között? ==

Igen, és egyszerűen:
* Az aMule 2.0.0-r4, vagy annál frissebb verzióiban jobb klikkel a könyvtár ikonján a fában.
* Az aMule 1.x és 2.0.0-rc3 közti verzióiban a CTRL gomb nyomva tartása mellett, bal kattintással a könyvtáron

== Letöltöttem egy filet, de meghibásodott a merevlemezemen. El tudom valahogy kerülni, hogy újra le kelljen tölteni? ==

Ha még megvan az [[ed2k_link|ed2k:// link]], indítsd el újra a letöltést, és amint lejött egy egész chunk (9.28 MB), zárd be az aMulet, nevezd át a hibás filet az éppen letöltés alatt álló nevére (mondjuk ''002.part''), használd a touch parancsot (pl.: ''touch ~/.aMule/Temp/002.part*''), és indítsd újra a programot.

Az aMule látni fogja, hogy a teljes file megvan, ellenőrzi azt, és újra letölti a hibás részeket.

== Mire kell figyelni, ha NFS mountokat használsz aMulellal? ==

Ha a megosztásodban szerepel olyan könyvtár, ami NFSel van csatolva (mount), mindenképpen győződj meg róla, hogy lecsatoltad (umount) őket, mielőtt a távoli gép leáll, különben az aMule egészen addig nem csinál majd semmit, míg azok a könyvtárak újra elérhetőek nem lesznek. Szintén figyelj arra, hogy minden lecsatolás után frissítsd a megosztott fileok listáját. ''[[User:PedroAlgarvio|PedroAlgarvio]] 00:25, 15 Jun 2005 (CEST)''

AMule problems-nl

2007-04-28T16:54:21Z

87.14.231.86:

<center>
<u><h4>Veel voorkomende problemen met [[aMule_Project_FAQ:About|aMule]]</h4></u>

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

[[AMule_problems|English]] | [[AMule_problems-es|Español]] | '''Nederlands''' | [[AMule_problems-hu|Magyar]] | [[AMule_problems-de|German]] | [[AMule_problems-it|Italiano ]]
</center>

== Ik krijg de melding "aMule already running: exiting" op de terminal als ik aMule start. Kan ik het toch starten? ==

Deze melding is duidelijk: aMule draait al. Dit gaat niet over het hele systeem, maar dat '''u''' (uw account) al aMule draait.

U kunt denken dat aMule niet draait, omdat het gecrashed is. Maar het komt voor dat sommige processen niet helemaal gesloten worden, in plaats daarvan blijven ze in een status bekend als ''zombie'' of ''defunct''. Om te zien of dit uw probleem is, draai ''ps u | grep amule'' en als het uitvoer toont, draait er nog een aMule proces met uw account. Om het af te sluiten, sluit het handmatig (indien mogelijk) of sluit het met ''kill -9 <aMule-PID>'' of ''killall -9 amule'' of log uit en log opnieuw in (wat, meestal, ook alle aMule processen zou moeten sluiten, behalve als u aMule hebt gestart met ''nohup'' of iets dergelijks).

Als geen van de bvenstaande oplossingen u aanspreken, kunt u nog een aMule draaien als een andere gebruiker (uiteraard alleeen als u in kunt loggen met een ander accout). Lees [[FAQ_aMule#Kan_ik_twee_instanties_van_aMule_tegelijkertijd_draaien?|Kan ik twee instanties van aMule tegelijkertijd draaien?]].

== aMule start maar wordt nooit getoond, hoewel het goed werkt. Wat is er aan de hand? ==

Dit kan voorkomen als u een verkeerd type van SysTray kies in Voorkeuren -> Algemeen - > "Systray Integratie" en u stelt aMule in om te minimaliseren naar de tray en u stelt aMule in om geminimaliseerd te starten. U heeft dus echt de tijd genomen om dit te veroorzaken, nietwaar?

Om dit op te lossen, moet u het bestand ''~/.eMule'' bewerken en zoeken naar ''StartupMinimized=1'' en als u het gevonden heeft, moet u dat veranderen in ''StartupMinimized=0''. Het volgende script doet dat automatisch voor u:

''sed s/StartupMinimized=1/StartupMinimized=0/ ~/.eMule > ~/.eMule.temp && mv -f ~/.eMule.temp ~/.eMule''

Als u de volgende keer aMule start stel de correcte SysTray integratie in bij Voorkeuren zodat u "Start geminimaliseerd" kunt aanvinken zonder dat u aMule kwijt raakt.

Als het bovenstaande om de een of andere reden niet heeft gewerkt, kunt u proberen om handmatig de Systray integratie te veranderen in de standaard instelling "Geen systray integratie". Om dat te doen, stelt u de ''DesktopMode='' waarde in ''~/.eMule'' op ''4''. Het volgende script doet dat automatisch voor u:

''sed s/DesktopMode=[0-9]/DesktopMode=4/ ~/.eMule > ~/.eMule.temp && mv -f ~/.eMule.temp ~/.eMule''

'''LET OP:''' Bij [[aMule]] versies ouder dan 2.0.0rc4 moet u het instellen op ''1'' in plaats van op ''4'' omdat het opslaan van de Voorkeuren iets gewijzigd is.

== aMule start maar verbindt nooit/gedraagt zich vreemd/crashed de hele tijd/etc...? ==

aMule versies tot 2.0.0-rc3 moeten niet gelinked worden tegen wxWidgets 2.5.x of GTK2 hoewel sommige Linux distributies diet wel doen. Controleer dit om er zeker van te zijn dat dit niet het geval is. Als u het niet zeker weet plak uw backtrace op [http://www.amule.org/amule/board.php?boardid=33 aMule's Backtraces forum] of kom op aMule's IRC kanaal #amule op irc.freenode.net

== Waar zijn mijn gedownloade bestanden? ==

aMule bewaart complete bestanden standaard in ''~/.aMule/Incoming'' maar, omdat de ''~/.aMule''directory verborgen is, kan het zijn dat uw bestandsbeheerder het niet toont. Zorg ervoor dat u uw bestandsbeheerder hebt ingesteld om verborgen bestanden te tonen.

Standaard worden bestanden die gedownload worden geplaatst in ''~/.aMule/Temp'', alweer, dit is een verborgen directory en de bestandsbeheerd moet ingesteld zijn om verborgen bestanden te tonen.

== Waarom is het CPU gebruik van aMule zo hoog bij het starten? ==

Dit is omdat aMule nieuw bestanden in de Gedeelde Directories aan het hashen is.<br> Als aMule altijd een hoog CPU gebruik heeft bij het starten en er zijn geen nieuwe bestanden toegevoegd of veranderd in de Gedeelde Directories, dan is er iets mis.

Bij aMule versies ouder dan 2.0.0-rc3 kon dit voorkomen als de tijdelijke, binnekomende of een Gedeelde Directory op een FAT32 partitie staat. Vanaf aMule 2.0.0-rc3 komt dit niet meer voor.

In aMule versies ouder dan 2.0.0-rc4 kon dit ook voorkomen bij bestandssystemen met UTF-8 codering (dit probleem is bekend bij SuSE 9.1) als een bestand of directory in de Gedeelde Directories een speciaal teken bevat. Als dit uw probleem is is er een manier om dit te omzeilen (dank aan '''nachbarnebenan'''): nadat aMule alle gedeelde bestanden heeft gehashed (dat is, als het stopt met veel CPU tijd te gebruiken), sluit aMule en codeer ~/.aMule/known.met met UTF-8 codering (dit kunt u doen met het programma ''[[http://www.gnu.org/directory/recode.html recode]'' door het volgende commando te draaien: ''recode u8 ~/.aMule/known.met''). Dit moet gedaan worden als een bestand is toegevoegd of veranderd in een Gedeelde Directory. Dus, de beste oplossing is om te upgraden naar de nieuwste aMule versie.

Als geen van de bovenstaande oplossingen helpt, is er iets serieus mis met het bestand ''known.met'', waarschijnlijk heeft een extern programma of een gebruiker dit veroorzaakt. De beste oplossing is om het bestand te verwijderen, aMule te starten en alle bestanden opnieuw te laten hashen.

== aMule start nu, maar waarom toont het deze melding: "Geen geldige servers om mee te verbinden in de serverlijst gevonden"? ==

Dat is omdat u de optie "Auto verbindt alleen met servers op de statische lijst". Dus, scakel dat uit of voeg wat servers toe aan de statische lijst.

Om die optie uit te schakelen, ga naar Voorkeuren -> Servers -> "Auto verbindt alleen met servers op de statische lijst"

Om een server toe te voegen aan de statische lijst, ga naar de Servers tab en klik met de rechtermuisknop op de server die u wilt toevoegen aan de statische lijst. Kies dan voor "Voeg toe aan statisch" en doe dit met alle servers die u wilt toevoegen aan de statische lijst.

== aMule verbindt met de server, maar het krijgt altijd een Laag ID. Waarom? en, kan ik er wat aan doen? ==

Dit kan drie oorzaken hebben:
*Een benodigde poort is niet geopend in uw firewall. Lees [[FAQ_eD2k-Kademlia#Wat_is_Laag_ID_en_Hoog_ID?|dit]] om te weten te komen wat u kunt doen en controleer [http://www.amule.org/testport.php hier] of de poorten open zijn.
*De server is erg druk of misschien slecht geoconfigureerd, dus geeft het u een Laag ID. Hier kunt u niets aan dan, behalve opnieuw verbinden of een andere server proberen.
*Sommige ISPs verbieden het gebruik van p2p programma's, zoals aMule, door het verkeer via populaire p2p poorten niet toe te staan. In deze gevallen moet u aMule zo configureren dat het een andere poort gebruikt. Het beste als het een populaire poort is gebruikt voor iets anders. Het is bekend dat het bij sommige ISPs werkt met TCP poort 25600.

== [[aMule]] werd onderbroken tijdens het completeren van een bestand en nu wordt het nooit gecompleteerd (hoewel het voor 100% is gedownload). Hoe kan ik het completeren? ==

Dit is makkelijk: Sluit [[aMule]]. Ga naar de Temp directory (standaar, ''~/.aMule/Temp'') en draai het volgende commando:

''touch ./*''

Start dan [[aMule]] en let het de bestanden completeren.

== Ik ben net een download kwijtgeraakt. Kan ik het terug halen? ==

Dit komt niet vaak voor, maar het kan, hoewel het meestal het resultaat is van niet-aMule-gerelateerd iets (of een fout van de gebruiker).

Er kunnen twee dingen gebeurd zijn. De *.part.met bestanden zijn verwijderd, of de *.part bestanden zijn verwijderd.

Als de *.part bestanden verdwenen zijn, is de enige oplossing om de downloads opnieuw te starten (als de *.part.met bestanden er nog zijn, zal aMule de downloads starten bij de volgende keer dat u aMule start). Dit zou echter '''nooit''' mogen voorkomen tenzij de gebruiker ze verwijderd heeft.

Als de *.part.met bestanden verdwenen zijn maar de *.part bestanden nog in de Temp directory zijn, kij of de *.part.met.bak bestanden ook nog in de Temp directory zijn. Als ze er nog zijn, hernoem de ''*.part.met.bak'' bestanden naar ''*.part.met'' door het volgende commando te draaien:

''for file in *.part.met.bak; do mv -f "$file" "${file%.bak}; done''

Het kan voorkomen dat, hoewel u de *.part bestanden hebt, de *.part.met en de *.part.met.bak bestanden niet meer bestaan. In dit geval zijn er twee manieren om dit op te lossen:

Gebruik de [http://www.bigwillystyle42.com/mfr/ MetFileRegenerator] (Java benodigd) om de *.part.met bestanden aan te maken.

Of, zoek op aMule naar de bestanden die u aan het downloaden was en hernoem hun part getal naar de *.part.met bestanden die de oude had. Bijvoorbeeld, als u ''aMule_1.2.6.tar.gz'' aan het downloaden was en die werd gedownload in de Temp directory als ''008.part'', dan horen bij dat bestand ook de bestanden ''008.part.met'' en waaarschijnlijk ''008.part.met.bak''. Maar de laatstgenoemde twee bestanden zijn op mysterieuze manier verdwenen. Zoek dan op aMule naar ''aMule_1.2.6.tar.gz'' en begin dat te downloaden. Sluit aMule en u heeft een nieuwe download, bijvoorbeeld, ''011.part'' in de Temp directory. Dit bestand heeft een bijbehorend ''011.part.met'' bestand. Hernoem ''011.part.met'' naar ''008.part.met'' en verwijder dan ''011.part'' (en ''011.part.met.bak'' als het bestaat). Start nu aMule en u heeft de download hersteld tot het punt waarop het was toen de *.part.met bestanden verdwenen.

== Waarom reageert aMule ineens niet meer op de muis hoewel het niet hangt? ==

Het komt voor dat u een dialoog venster ergens verborgen liet op de desktop. aMule wacht tot dat venster gesloten is, dus reageert het niet meer tot u klikt op OK, Cancel of waar u op moet klikken.

Dus, zorg er voor dat er geen aMule dialoog venster over is in '''een workspace'''.

== Waarom worden sommige bestanden in mijn gedeelde directories niet getoond in de Gedeelde Directories tab? ==

Dit kan voorkomen als u deze bestanden hebt toegevoegd nadat aMule gestart is. Druk op de "Opnieuw laden" knop in de Gedeelde Directories tab en het zou de nieuwe bestanden moeten vinden en ze hashen (dit kan wat CPU tijd vergen).<br>
Echter, in sommige versies is het voorgekomen dat na het herstarten van aMule, sommige bestanden verdwijnen van de Gedeelde Directories tab howel ze in de gedeelde directories zijn. In deze gevallen is de enige manier om ze terug te krijgen om het bestand ''~/.aMule/known.met'' te verwijderen, maar, natuurlijk, worden alle gedeelde bestanden opnieuw gehashed bij de volgende start van aMule, en dat neemt waarschijnlijk wat tijd in beslag.

== Ik krijg altijd een bericht over addresses.met als ik aMule start. Wat is er mis? ==

Dit komt voor als u de optie Voorkeuren -> Server -> "Auto-update serverlijst bij het opstarten" aanzet en u heeft geen serverlijst urls in ''addresses.dat''. U moet er of wat toevoegen aan ''addresses.dat'' door ze toe te voegen bij Voorkeuren -> Server -> Lijst of u moet de optie Voorkeuren -> Server -> "Auto-update serverlijst bij het opstarten" uitzetten als u het niet nodig hebt.

== Ik zie soms een bericht in de log over credits die kwijt geraakt zijn. Moet ik me zorgen maken? ==

Nee, u hoeft u geen zorgen te maken. Credits voor een client worden verwijderd als die client 150 dagen (ongeveer 5 maanden) niet wordt "gezien". Slecte clients kunnen ook hun credits verlizen. Deze berichten zijn slechts debug informatie, u moet zich er geen zorgen over maken.

== Wat moet ik doen als ik het bestand ''cryptkey.dat'' kwijt raak? ==

Het verliezen van dat bestand zorgt er voor dat u al uw credits verliest, sorry. ALS u weer credits wilt ontvangen vanaf dit moment, verwijder dan ook ''~/.aMule/preferences.dat''. Als u dat niet doet, kunt u geen credits meer verzamelen van de [[client]]s die u ooit (voor het verliezen van het bestand ''cryptkey.dat) geïdentificeerd hebbben.

== Waarom wordt de Upload/Download grens altijd teruggezet naar 0 na elke herstart? ==

Dit komt voor op aMule versies voor 2.0.0-rc4 als u probeert om een Upload of Download grens waarde hoger dan de Upload op Download Capaciteit waarde in te stellen. Sinds versie 2.0.0-rc4 is dit opgelost (lees [[FAQ_aMule#What_is_the_real_point_on_setting_up_Line_Capacities_in_Preferences?_Shouldn't_aMule_only_care_for_the_Bandwidth_Limits?|What is the real point on setting up Line Capacities
in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] om te begrijpen waarom) en zou niet meer moeten voorkomen.

== Waarom negeert aMule de banbreedte die ik instel per slot? ==

De bandbreedte per slot kan ingesteld worden bij Voorkeuren, maar het wordt genegeerd als de bandbreedte per slot niet minimaal drie verbindingen tegelijkertijd toestaat.

Dus, de maximuale snelheid toegestaan per slot is '''BandbreedteGrens/3'''.

Verware '''Bandbreedte grens''' '''NIET''' met ''Bandbreedte Capaciteit''. Lees [[FAQ_aMule#What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?|What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] omdat de betekenis van de Bandbreedte Capaciteit niet intuitief is.

Verder, als [[aMule]] ontdekt dat, na het instellen van alle sloten voor het uploaden, bandbreedte over blijft voor de Bandbreedte Grens is bereikt, zal het nog een slot toestaan en de totale hoeveelheid bandbreedte verdelen over alle sloten.

Voorbeeld:
*Bandbreedte Grens: 7 kBps
*Slot allocatie: 2 kBps

Als [[aMule]] de sloten ingesteld heeft om te uploaden naar andere clients, ontdekt het dat er na drie sloten minder dan 2 kBps over is, omdat de grens 7 kBps is, maar er is nog 1 kBps over voor de Bandbreedte Grens wordt bereikt. Dus, zal het nog ene slot toestaan om te uploaden en, in plaats van het geven van 1 kBps voor dat laatste slot (en de rest met 2 kBps), geeft het alle vier de sloten 1,8 kBps.

== Waarom kan ik aMules download grens niet hoger instellen dan X? ==

Om het ED2K netwerk levend te houden, hebben alle ED2K clients een upload/download verhouding ingebouwd, afhankleik van de upload grens is de download grens:
*<u>Van 0 kBps tot 3 kBps:</u> DownloadGrens kan niet hoger worden dan UploadGrens*3
*<u>Van 4 kBps tot 9 kBps:</u> DownloadGrens kan niet hoger worden dan UploadGrens*4
*<u>UploadGrens hoger dan 9 kBps:</u> Er is <b>geen</b> DownloadGrens beperking

Wees voorzichtig met het kiezen van 0 kBps als Upload Grens. Het betekent misschien niet wat u bedoelt. Lees [[AMule_problems-nl#Ik_heb_de_Upload_Grens_ingesteld_op_0kBps,_maar_aMule_is_nog_steeds_aan_het_overdragen._Wat_deed_ik_verkeerd?|Ik heb de Upload Grens ingesteld op 0kBps, maar aMule is nog steeds aan het overdragen. Wat deed ik verkeerd?]] om er voor te zorgen dat u de betekenis daarvan begrijpt.

== Ik heb de Upload Grens ingesteld op 0kBps, maar aMule is nog steeds aan het overdragen. Wat deed ik verkeerd? ==

De Upload grens instellen op 0kBps stop niet de overdrachten, in plaats daarvan, ''0'' betekent '''onbegrensd''', dus is het precies het tegenovergestelde van wat u probeert te doen. U kunt aMule niet stoppen om bestanden te uploaden, en dat is hetzelfde bij alle ED2K clients (eMule, eDonkey, etc). Mensen toestaan niet te uploaden betekent het einde van het ED2K netwerk.

Zelfs als u geen een directory deelt, wordt de Temp directory '''altijd''' gedeeld, zo dat bestanden die u download gedeeld worden met ander clients.

== Waarom zie ik het bericht "Te veel verbindingen" op de terminal? ==

Dit komt voor als u een hele hoge waarde hebt ingesteld in Voorkeuren -> Vebinding -> "Verbinding grenzen" -> "Max verbindingen". Als deze waarde bijna even groot is als het aantal verbindingen wat uw systeem u toe staat, dan kan aMule niet alle verbindingen maken en deze berichten tonen (bedenk dat andere programma's ook verbindingen gemaakt kunnen hebben).

Bij Windows 9x/ME is er een grens van 100 TCP verbindingen dus, hoewel u aMule kunt instellen om meer dan 100 verbindingen te maken, kan het dat niet. U kunt de TCP verbindingen grens van Windows wijzigen door het Windows Register te bewerken ('''Start -> Uitvoeren -> regedit.exe''') en verander (waarschijnlijk moet u deze waarde toevoegen omdat het meestal niet bestaat):

''HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections'' (dat is van type String en de waarde is een 32-bit getal).

== Mijn voortgangsindicatoren zijn het meeste van hun 3D effect kwijt en zijn er lelijker uit nu. Kan ik het oude uiterlijk terug krijgen? ==

Bij oude aMule versies (voor 2.0.0-rc4) kon u door de Voortgangsindicator Stijl schuif in Voorkeuren -> "GUI Tweaks" zo ver mogelijk naar rechts te schuiven de voortgangsindicator het meeste 3D effect geven. Vanaf 2.0.0-rc4 krijgt u het meeste 3D effect als de Stijl schuif in het midden staat. Zo ver mogelijk rechts geeft de voortgangsindicator een plat uiterlijk terwijl het zover mogelijk links een donker uiterlijk heeft.

== Al mijn downloads zijn ineens gepauzeerd en ik kan ze niet verder laten gaan. Wat is er aan de hand? ==

Controleer of er vrije schijfruimte is op het bestandssysteem waar de Temp directory staat. Als die er is, controleer of er meer vrije schijfruimte is dan de minimale hoeveelheid vrije schijfruimte ingesteld bij Voorkeuren -> Bestanden -> "Min schijfruimte".

== Waarom werkt Voorbeeld niet? ==

Sinds aMule 2.0.0-rc4 wordt het Voorbeeld commando niet meer gedraait in dezelfde terminal als aMule. Het resultaat daarvan is dat uw Voorbeeld programma mogelijk niet start. Dit is het geval bij bijv. MPlayer. U heeft een terminal nodig om uw Vorbeeld speler te draaien, gebruik een commando als ''xterm -e <preview-prog>'' bijv:

''xterm -T "aMules voorbeeld" -iconic -e mplayer -idx''

== Nadat ik MPlayer van Voorbeeld heb afgesloten reageert aMule niet meer ==

Tot aMule versie 2.0.0-rc4 werd aMule opzettelijk geblokkeerd tijdens Voorbeeld. Het gevolg daarvan was dat mensen die MPlayer gebruikten last hadden van een bug in MPlayer die op de achtergrond door bleef draaien als het hoofd MPlayer venster gelosten werd. Om deze bug te omzeilen bij aMule versies eerder dan 2.0.0-rc4 moet u MPlayer afsluiten met de '''Q''' toets. Het beste is echter om aMule te upgraden tot de laatste versie.

== Waarom is ''Overgebracht'' minder dan ''Compleet''? ==

Het is een bekend misverstand om te denken dat het meer of, op zijn minst, gelijk moet zijn.

Less [[FAQ_aMule#What_is_the_difference_between_Transfered_and_Completed_in_the_Tranfers_window?|What is the difference between Transfered and Completed in the Tranfers window?]] om meer te weten te komen hierover.

== aMule vertraagd mijn computer altijd als het een download compleet heeft gedownload. Is dit normaal gedrag? ==

Ja dat is het. Als aMule een download compleet heeft gedownload controleert het op het niet beschadigd is. Hoewel dit al gecontroleerd wordt tijdens het downloaden (door de hash waarden van de blokken te controleren), als het bestand compleet gedwonload is hasht aMule alle blokken om te controleren dat de blokken die al gedownload waren niet beschadigd zijn geraakt door de gebruiker of door een extern programma terwijl de rest van het bestand gedownload werd.

== Is er een manier om recursief een hele directory en zijn inhoud te selecteren? ==

Ja, die is er. En het is simpel:
*Bij [[aMule]] 2.0.0-rc4 of nieuwer, klik met de rechtermuisknop op het pictogram voor de directory die u recursief wilt selecteren
*Bij [[aMule]] 1.x tot en met 2.0.0-rc3, houd de CTRL toets ingedrukt terwijl u op de directory klikt.

Dat is het.

== Ik heb een bestand compleet gedownload en het is op de een of andere manier beschadigd geraakt. Kan ik voorkomen dat ik het hele bestand opnieuw moet downloaden? ==

Als u de [[ed2k_link|ed2k:// link]] nog heeft, start de download opnieuw en als een heel blok (9,28MB) gedownload is (elk blok is goed), sluit [[aMule]], hernoem het beschadigde bestand naar de bestandsnaam die de huidige download heeft (iets als ''002.part''), touch het beschadigde bestand (''touch ~/.aMule/Temp/002.part*'') en start [[aMule]] opnieuw.

[[aMule]] ontdekt de complete blokken en de beschadigde, en zal alleen de beschadigde blokken downloaden.

AMule problems-es

2007-04-28T16:53:53Z

87.14.231.86:

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

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

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

== Me da un mensaje "aMule already running: exiting" en un terminal cuando arranco aMule. ¿Podré arrancarlo de todas formas? ==

Este mensaje es muy claro: aMule ya esta arrancado. Pero no se refiere al sistema entero, si no que '''tú''' (tu cuenta de usuario) ya está ejecutando aMule.

Puedes pensar de todas formas que no hay ningún aMule ejecutandose, ya que se colgó. Pero sucede que a veces, algunos procesos no se cierran del todo, quedandose en un estado conocido como ''zombie'' o ''defunc''. Para saber si éste es tu problema ejecuta ''ps u | gre amule'' y si te enseña algo, entonces hay algún otro proceso de aMule ejecutandose con tu cuenta. Para matarlo, puedes cerrarlo normalmente (si puedes) o matarlo con ''kill -9 <aMule_PID>'' o ''killall -9 amule'' o cerrar sesión y entrar de nuevo en el sistema (que en muchos casos mata los procesos de aMule, exepcto si lo has ejecutado con ''nohup'' o algo parecido).

Si nada de ésto te sirve, puedes ejecutar otro aMules como otro usuario (si puedes entrar en el sistema con otra cuenta, por supuesto). Lee [[FAQ-es#¿Puedo_ejecutar_dos_instancias_de_aMule_al_mismo_tiempo?|¿Puedo ejecutar dos instancias de aMule al mismo tiempo?]].

== aMule arranca pero no se muestra, de todas formas está funcionando bien. ¿Qué está pasando? ==

Esto puede pasar si configuras incorrectamente el tipo de SysTray en Preferencias -> General -> "Integración en Icono del Sistema" y configuras que aMule se minimize en el tray y que arranque minimizado. Asi que te tomaste algo de tiempo en hacerlo, ¿no?

Para recuperar el GUI de aMule, edita ''~/eMule'', busca ''StartupMinimized=1'' y cambialo por ''StartupMinimized=0''. El siguiente script lo puede hacer por tí (en linux)

''sed s/StartupMinimized=0/StartupMinimized=1/ ~/.eMule > ~/.eMule.temp && mv -f ~/.eMule.temp ~/.eMule''

La próxima vez que arranques amule, configura correctamente la integración con el icono del sistema en las Preferencias para que puedas "Arrancar Minimizado" sin tener aMule oculto.

Si por alguna razón lo de arriba no funciona, intenta cambiando manualmente la interación con el icono del sistema al valor por defecto "Sin integación en icono del sistema". Para ahcer eso pone el valor ''1'' a ''DesktopMode='' en ''~/.eMule''. El siguiente script lo puede hacer por tí:

''sed s/DesktopMode=[0-9]/DesktopMode=1/ ~/.eMule > ~/.eMule.temp && mv -f ~/.eMule.temp ~/.eMule''

== aMule arranca pero nunca se conecta y se congela o cuelga cada pocos segundos etc... ==

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

== ¿Donde están mis ficheros descargados? ==

Por defecto, aMule guarda los ficheros completados en ''~/.aMule/Incoming'' pero como este directorio es un directorio oculto, puede que tu navegador de ficheros puede no mostrarlo. Asegurate de que el navegador de ficheros muestra los ficheros ocultos.

Por defecto, los ficheros que estan siendo descargados se colocan en ''~/.aMule/Temp'', asi que de nuevo, este es un directorio oculto y el navegador de ficheros tiene que ser configurado para que muestre los ficheros ocultos.

== ¿Por qué aMule se come tanta CPU al arrancar? ==

Esto ocurre porque aMule esta realizando el hash de los nuevos ficheros encontrados en los directorios compartidos.

Si aMule siempre se come mucha CPU al arrancar y no hay ficheros nuevos o modificados en tus directorios compartidos es que algo va mal.

En versiones anteriores a la 2.0.0-rc3 esto solía pasar cuando se tenia el Temp, el Incoming o algún Directorio compartido en una partición FAT32. Desde aMule 2.0.0-rc3 esto no pasa.

También, en versiones anteriores a la 2.0.0-rc4 en sistemas de ficheros con codificación UTF-8 (se sabe que pasa con SuSE 9.1) puede haber problemas cuando algun fichero o directorio en los Directorios Compartidos contienen caractéres especiales. Si este es tu problema hay un manera de solucionarlos (gracias '''nachbarnebenan'''): después de que aMule haya realizado el hash de todos los ficheros compartidos (esto es, cuando haya parado de consumir casi toda tu CPU), cierra aMule y codifica ~/.aMule/known.met con codificación UTF-8 (puedes hacer ésto con la aplicación ''[http://www.gnu.org/directory/recode.html recode]'' ejecutando el siguiento comando: ''recode u8 ~/.aMule/known.met''). Esto lo debes hacer cada vez que añadas o modifiques algún fichero en algún Directorio Compartido. Así que la mejor opción es actualizar a la última versión de aMule.

Si nada de lo anterior te sirve, entonces algo está yendo rematadamente mal en el fichero ''known.met'', probablemente algún programa o usuario externo lo rompe. La mejor opción es borrarlo y reiniciar aMule dejandole que haga el rehash de nuevo.

== Bueeeno, ahora aMule arranca, pero ¿Porque me saca este mensaje: "No hay servidores válidos en la lista de servidores" cuando si que los hay? ==

Esto es por que has activado la opción "Autoconectar sólo a servidores fijos". Así que desactívala o añade algún servidor a lista de servidores fijos.

Para desactivar esta opción, ve a Preferencias -> Servidor -> "Autoconectar sólo a servidores fijos".

Para añadir un servidor a la lista de fijos, ve a la ventana de Servidores y pincha con el botón derecho en el servidor que quieres añadir a la lista de servidores fijos. Entonces selecciona "Añadir a la lista de servidors fijos" y haz lo mismo para todos los servidores que quieras añadir a la lista de servidores fijos.

== aMule se conecta a los servidores, pero siempre obtiene LowID. ¿Por que? Y, ¿Puedo hacer algo al respecto? ==

Esto puede pasar por tres razones:
*Te falta abrir alguno de los puertos en tu router/firewall. Lee [[FAQ_eD2k-Kademlia-es#%C2%BFQu%C3%A9_es_ID_baja_e_ID_alta?|esto]] para saber como lo puedes hacer.
*El servidor esta ocupado o está mal configurado, y por eso obtienes LowID. Lo único que puedes hacer es reconectarte o conectarte a otro servidor.
*Algunos ISP limitan las aplicaciones del tipo P2P, como aMule, no permitiendo el tráfico a través de sus puertos más corrientes. En este caso configura aMule para que use cualquier otro puerto.

Para conocer si se tiene abiertos o no los puertos, se puede visitar la [http://www.amule.org/testport.php página de tests de puertos].

== [[aMule]] se interrumpió cuando completaba un archivo y ahora nunca lo completa (aunque está descargado al 100%). ¿Como puedo completarlo? ==

Este es fácil: Cierra [[aMule]]. Ahora ve al directorio Temp (por defecto, ''~/.aMule/Temp'') y ejecuta el siguiente comando:

''touch ./*''

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

== Perdí una descarga. ¿Hay alguna manera de recuperarla? ==

Es extraño que esto suceda, pero es posible, aunque en la mayoría de los casos es porque algo no relacionado con aMule ha fallado (o por culpa del usuario).

Han podido pasar dos cosas. O bien los ficheros *.part.met o los *.part han sido borrados.

Si han desaparecido los *.part, la única solución es comenzar la descarga desde el principio (si aún existen los *.part.met aMule comenzará las descargas la próxima vez que lo arranques). Sin embargo esto '''nunca''' debería haber pasado si el usuario no los hubiera borrado.

Si los *.part.met han desaparecido pero los *.part continuan en el directorio temporal, comprueba si los *.part.met.bak existen en el directorio. Si existen, solo renombra los ''*.part.met.bak'' a ''*.part.met'' ejecutando:

''for file in *.part.met.bak; do mv -f "$file" "${file%.bak}; done''

También puede pasar que aunque tengas los ficheros *.part, ni los ficheros *.part.met ni los *.part.met.bak existan. En este caso, tendrías dos opciones:

Usa [http://www.bigwillystyle42.com/mfr/ MetFileRegenerator] (requiere Java) para reconstruir los ficheros *.part.met.

O, vuelve a buscar en aMule los ficheros que estabas descargando y renombra sus ficheros *.part.met files a los que estabas usando. Por ejemplo, si estabas descargando ''aMule_1.2.6.tar.gz'' en el directorio temporal como ''008.part'', este fichero debería tener su correspondiente fichero ''008.part.met'' y, probablemente, su fichero ''008.part.met.bak''. Pero estos dos ficheros han desaparecido misteriosamente. Vuelve a buscar en aMule ''aMule_1.2.6.tar.gz'' y comienza a descargarlo. Cierra aMule y tendrás esta nueva descarga como, por ejemplo, ''011.part'' en el directorio temporal. Obviamente esta descarga tendrá su fichero ''011.part.met''. Renombra ''011.part.met'' a ''008.part.met'' y borra el fichero ''011.part'' (y ''011.part.met.bak'' si es que existe). Arranca aMule y habrás recuperado la descarga desde donde se encontraba antes de que los ficheros *.part.met hubieran desaparecido.

== ¿Por qué aMule de repente no responde al ratón apesar de que no esta colgado? ==

A veces pasa que dejas una ventana abierte y escondida en algún sitio del escritorio. [[aMule]] espera a que esa ventana se cierre, asi que no responde hasta que pinches en OK, Candel o donde tengas que pinchar.

Así que asegurate de que no hay ninguna ventana de [[aMule]] en '''ningún Escritorio'''.

== ¿Por qué algunos archivos en mi carpeta de compartidos no se muestran en la ventana de ''Archivos Compartidos''? ==

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

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

== Siempre tengo un mensaje sobre addresses.met cuando inicio aMule. ¿Qué está mal? ==

Esto pasa cuando activas la opción Preferencias -> Servidor -> "Actualizar automaticamente la lista de servidores al iniciar" y no tienes direcciones de listas de servidores en el fichero ''addresses.dat''. Puedes añadir alguna a ''addresses.dat'' en Preferencias -> Servidor -> Lista o simplemente deshabilitar Preferencias -> Servidor -> "Actualizar automaticamente la lista de servidores al iniciar" si no lo necesitas.

== A veces tengo un mensaje en el log sobre perdida de créditos. ¿Debería preocuparme? ==

No, no deberias preocuparte. Los creditos para un cliente se borran despues de 150 dias (mas o menos 5 meses) sin "ver" a ese cliente. También se borran los créditos de los clientes "malos" (leechers). Estos mensajes son únicamente información de depurado, así que no te preocupes por ellos.

== ¿Qué debo hacer si pierdo mi archivo ''cryptkey.dat''? ==

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

== ¿Por qué mis Límites de Subida/Descarga vuelven siempre a 0 despues de cada reinicio? ==

Esto pasaba en versiones de aMule anteriores a la 2.0.0-4c4 cuando intentabas poner un valor de Límite de Subida o Descarga mayor que los valores de Capacidad de Subida y Descarga.

En cualquier caso, está arreglado desde la versión 2.0.0-rc4 (lee [[FAQ_aMule-es#¿Cual es el verdadero significado de Capacidad en Preferencias? ¿No se debería preocupar aMule únicamente de los Límites?|¿Cual es el verdadero significado de Capacidad en Preferencias? ¿No se debería preocupar aMule únicamente de los Límites?]] para entender por qué) y no debería pasar más.

== ¿Por qué está amule ignorando el ancho de banda que configuro por slot? ==

El ancho de banda por cada slot se configura en las Preferencias, pero será ignorado si el ancho de banda por slog do permite al menos tres conexiones al mismo tiempo.

Así, que la máxima velocidad por slot es '''LímiteSubida/3'''.

Por favor, '''NO''' confundas '''Límite Subida''' con '''Capacidad de Subida'''.
Lee [[FAQ_aMule-es#¿Cual es el verdadero significado de Capacidad en Preferencias? ¿No se debería preocupar aMule únicamente de los Límites?|¿Cual es la utilidad de el valor Capacidad en las Preferencias?]] ya que el significado de Capacidad de Subida no es intuitivo.

== ¿Por que no puedo configurar el límite de descarga a un valor mayor que X? ==

Para que la red ED2K siga funcionando, todos los clientes ED2K tienen programados unos límites que, dependiendo en la limitación de la subida, son:

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

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

== He configurado el límite de subida a 0KBps, pero aMule sigue transferiendo. ¿Que he hecho mal? ==

Configurar el límite de subida a 0KBps no detiene la transferencia, sino que, ''0KBps'' significa '''ilimitado''', vamos, justo lo contrario a lo que tu quieres hacer. No hay manera de evitar que aMule suba ficheros, y esto es igual para todos los clientes ED2K (eMule, eDonkey, etc). Permitir que la gente no suba nada llevaría a la red ED2K a su final.

Incluso si tú no compartes ningún directorio, el directorio Temp '''siempre''' se comparte, por lo tanto los ficheros que tú te estas bajando se comparten con otros clientes.

== ¿Por qué estoy teniendo un mensaje de "Too many connections" (Demasiadas conexiones) en el terminal? ==

Esto pasa cuando configuras un valor muy alto en Preferencias -> Conexión -> Límites -> "Conexiónes Máximas". Si este valor es mayor que el valor de conexiones que permite tu sistema, aMule fallará al establecer conexiones y mostrará estos mensajes (ten en cuenta que otras aplicaciones pueden tener conexiones abiertas).

En Windows 9x/Me hay un límite de 100 conexiones TCP, así que debes configurar aMule para que no establezca mas de 100 conexiones TCP, ya que no podrá estableceras. Puedes cambiar el límite de conexiones de Windows editando el Registro ('''Inicio -> Ejecutar -> regedit.exe''') y configurando (seguramente tengas que añadir el valor, ya que normalmente no existe):

''HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections''<br>
(que es un de tipo String y su valor debe ser un número de 32-bits).

== Mi barra de progreso casi todo su efecto 3D y se ve muy fea. ¿Puedo ponerla como antes? ==

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

== De repente todas mis descargas se han parado y no puedo reiniciarlas. ¿Qué está pasando? ==

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

== ¿Por qué no puedo previsualizar un archivo? ==

Ante todo debes saber que aMule solo permite previsualizar archivos de video.

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

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

== ¿Por qué no está funcionando la Previsualización con MPlayer? ==

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

== Despues de salir del MPlayer en una Previsualización, mi amule se queda bloqueado ==

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

== ¿Por qué lo ''Transferido'' es menor que lo ''Completado''? ==

Es un error común pensar que debería ser mayor, o al menos, igual.

Por favor lee [[FAQ_aMule-es#¿Cual es la diferencia entre Transferido y Completado en la ventana de Tráfico?|¿Cuál es la diferencia entre Transferido y Complatado en la ventana de Tráfico?]] para saber más sobre ésto.

== aMule siempre hace que mi ordenador vaya lento cuando completa una descarga. ¿Es esto un normal? ==

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

== ¿Es posible seleccionar un directorio completo y su contenido de forma recursiva? ==

Si. Y es fácil: Mientras haces pinchas en el directorio, pulsa la tecla CTRL.

Y ya está

== He descargado un archivo y se ha estropeado de alguna manera, por mi disco duro o por alguna apliación externa, despues de terminarlo. ¿Podría evitar tener que descargarme todo el archivo de nuevo? ==

Si aun tienes el [[ed2k_link|enlace ed2k://]], comienza a descargarlo de nuevo y cuando tengas un chunk completo (9.28MB) cierra [[aMule]], renombra el archivo corrupto al nombre temporal de la actual descarga (algo como ''002.part''), haz touch sobre el archivo corrupto (por ejemplo: ''touch ~/.aMule/Temp/002.part*'') y reinicia [[aMule]].

[[aMule]] detectará los chunks completos y los estropeados, y solo descargará los chunks que estén estropeados.

AMule problems

2007-04-28T16:53:28Z

87.14.231.86:

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

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

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

== I get an "aMule already running: exiting" message on the terminal when starting aMule. Will I be able to start it anyways? ==

The message is very clear: [[aMule]] is already running. But this doesn't refer to the entire system, rather that '''you''' (your user account) is already running [[aMule]].

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

If you are certain that there are no [[aMule]] processes,check if a [[MuleLock_file|muleLock]] file exists in your ~/.aMule directory ,and then delete it to restore the normal behaviour of [[aMule]].

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

== aMule starts but is never shown but works fine. What's going on? ==

This commonly happens when you set the type of systray integration, in Preferences -> General -> Misc Options, to ''Minimize to trayicon'' which starts [[aMule]] minimized.

To be able to recover aMule's GUI, edit ''~/.aMule/amule.conf'' and search for ''StartupMinimized=1'' and once you find it, change that line to ''StartupMinimized=0''. The following script will do that for you:

''sed s/StartupMinimized=1/StartupMinimized=0/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf''

When you next start [[aMule]] set the correct systray integration in Preferences so that you can enable "Start minimized" without having [[aMule]] hidden.

If, for some reason, the above didn't work, try changing the Systray integration manually to the default by unchecking the "Enable tray icon'' option. To do so, set the ''DesktopMode='' value in ''~/.aMule/amule.conf'' to ''4''. The following script will do that for you:

''sed s/DesktopMode=[0-9]/DesktopMode=4/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf''

'''NOTE:''' On [[aMule]] versions previous to 2.0.0rc4, you should set it to ''1'' instead of ''4'' since the Preferences storage changed a little.

== aMule starts but is never connecting/behaving very weird/crashing almost every few seconds/etc...? ==

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

== Where are my downloaded files? ==

By default, aMule stores completed files in ''~/.aMule/Incoming'' but, since ''~/.aMule'' directory is a hidden directory, your file manager might not show it. Make sure you have enabled your file manager to show hidden files.

By default, files being downloaded are placed in ''~/.aMule/Temp'', so again, this is a hidden directory and the file managed must be configured to show hidden files.

== Why is aMule taking so much CPU resources at start-up? ==

This happens because aMule is hashing new files found on the Shared Directories.

If aMule is always taking a lot of CPU at startup and no new files have been added or modified in any way in the Shared Directories, then something is wrong.

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

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

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

== So now aMule starts, but why is it displaying this message: "No valid servers to connect in serverlist found"? ==

That's because you enabled the option "Auto connect to servers the static list only". So, disable it or add some server to the static list.

To disable that option, go to Preferences -> Servers -> "Auto connect to servers the static list only"

To add a server to the static list, go to the Servers window and right-click on the server you want to add to the static list. Then select "Add to static" and do this exact process wit all the servers you want to add to the static list.

== Why does it happen that sometimes aMule suddenly has no/few servers in is server list? ==

You probably have enabled the options Preferences -> Servers -> "Remove dead server after X retries" and Preferences -> Connection -> "Reconnect on loss".

If so, most probably you lost internet (or lan, etc) connection for a period of time so aMule noticed it was not connected to the ed2k server anymore and went trying to connect to other servers until all servers were removed (after trying X times each).

To solve this problem, disable the "Remove dead server after X retries" option. Disabling the option "Remove dead server after X retries" is safe in most cases. You most probably don't want to disable the "Reconnect on loss" option, so keep it enabled.

== aMule connects to server, but it is always given Low-ID. Why? and, can I do something about it? ==

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

== [[aMule]] was interrupted while completing a file and it is now never completing it (although it's 100% downloaded). How can I complete it? ==

This one is easy: Close [[aMule]]. Now go into the Temp directory (by default, ''~/.aMule/Temp'') and run the following command:

''touch ./*''

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

== I just lost a download. Is there any way I can recover it? ==

This is strange to happen, but it might, although in most cases it is the result of some non-aMule-related stuff going weird (or user's fault).<br>
Two things may have happened. Either *.part.met files were deleted, or *.part files were deleted.

If *.part files have disappeared, the only solution is to restart the downloads from the beginning (if *.part.met files are still there, aMule will restart the downloads on next start). However this should '''never''' happen unless the user directly deleted them.

If *.part.met files have disappeared but *.part files are still in the Temp directory, then search if *.part.met.bak are also in the Temp directory. If they are, then just rename ''*.part.met.bak'' files to ''*.part.met'' just by running:

''for file in *.part.met.bak; do mv -f "$file" "${file%.bak}; done''

Still, it could happen that, although you have the *.part files, neither *.part.met nor *.part.met.bak files exist any longer. In this case, you would have two ways ways to work out of this:

Either, use [http://www.bigwillystyle42.com/mfr/ MetFileRegenerator] (Java needed) to reconstruct the *.part.met files.

Or, search again on aMule for the files you were downloading and rename their part number in the *.part.met files to the ones it used to have. For example, if you were downloading ''aMule_1.2.6.tar.gz'' and that was being downloaded in Temp directory as ''008.part'', then that file used to have it's corresponding ''008.part.met'' file and, probably, it's ''008.part.met.bak'' file. But this two latter files have mysteriously disappeared. Then search again on aMule for ''aMule_1.2.6.tar.gz'' and start downloading it. Close aMule and you'll have this new download as, for example, ''011.part'' file in the Temp directory. Of course, this download will have it's ''011.part.met'' file. Well, rename ''011.part.met'' to ''008.part.met'' and then delete ''011.part'' (and ''011.part.met.bak'' if it existed). Now start aMule and you will have recovered the download from the point it was before the *.part.met files disapeared.

== Why does aMule suddenly become unresponsive to the mouse although it's not hanged? ==

It sometimes happens that you left a dialog window somewhere hidden in the desktop. aMule is waiting for that window to be closed, so it becomes unresponsive until you click OK, Cancel, or whatever you have to click.

So, make sure there's no aMule dialog left around in '''any workspace'''.

== Why are some files in my shared folders not shown in the Shared Folders window? ==

This could happen if you added this files after aMule has been started. Press the "Reload" button on Shared Folders window and it should find the new files and hash them (this may take some CPU time).

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

== I always get a message about addresses.met when I start aMule. What's wrong? ==

This happens when you enable the option Preferences -> Servers -> "Auto-update serverlist at startup" and you have no serverlists' urls in ''addresses.dat''. You can either add some to ''addresses.dat'' by adding them at Preferences -> Servers -> List or just disable Preferences -> Servers -> "Auto-update serverlist at startup" if you don't really need it.

== I sometimes get a message on the log about credits being lost. Should I be worried? ==

No, you don't need to be worried. Credits for a client are deleted after 150 days (more or less 5 months) without "seeing" that client. Also, bad clients might lose their credits too. So those messages are just for debug information, you shouldn't worry about them.

== What should I do if I lose my ''cryptkey.dat'' file? ==

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

== Why is Upload/Download limit always back to 0 after every restart? ==

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

== Why is aMule ignoring the bandwidth I set per slot? ==

The bandwidth set to each slot can be set in Preferences, but it will be ignored if the bandwidth set per slot doesn't allow at least three connections at the same time.

So, the maximum speed allowed per slot is '''BandwidthLimit/3'''.

Please do '''NOT''' confuse '''Bandwidth limit''' with '''Bandwidth Capacity'''. Read [[FAQ_aMule#What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?|What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] since the meaning of the Bandwidth Capacity setting is not intuitive.

Also, if [[aMule]] detects that, after having set all the slots for uploading, still some bandwidth is left before getting to the Bandwidth Limit, it will allow another slot and divide all the slot bandwidths to so use the same amount of bandwidth.

Example:
*Bandwidth Limit: 7 KBps
*Slot allocation: 2 KBps

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

== Why can't I set aMule's download limit to more than X? ==

To keep the ED2K network alive, all ED2K clients have an upload/download limits ratio hardcoded which, depending on the upload limit set, is:
*<u>From 0KBps to 3KBps:</u>
*DownloadLimit can't be more than UploadLimit*3
*<u>From 4KBps to 9KBps:</u>
*DownloadLimit can't be more than UploadLimit*4
*<u>UploadLimit values over 9KBps:</u>
*There's <b>no</b> DownloadLimit limitation.

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

== I set Upload Limit to 0KBps, but aMule is still transferring. What did I do wrong? ==

Setting Upload limit to 0KBps will not stop transfers, instead, ''0'' value means '''unlimited''', so, it's right the opposite of you're trying to do. There's no way to stop aMule from uploading files, and that's the same on all ED2K clients (eMule, eDonkey, etc). Allowing people not to upload would bring the ED2K network to it's end.

Even if you don't share any directory, the Temp directory will '''always''' be shared, so that files that you are downloading are shared with other clients.

== Why am I getting "Too many connections" messages on the terminal? ==

This happens when you set a very high value at Preferences -> Connections -> "Connection limits" -> "Max connections". If this value is as almost as big as the the amount of connections your system allows you to have, then aMule will fail to establish connections and display those messages (have in mind that other applications may also have some connections established).

On Windows 9x/ME platforms there is a limit of 100 TCP connections so, although you might set aMule to establish more than 100 connections, it will be unable to do so. You can change Windows's TCP connections limit by editing the Windows Register ('''Start -> Run -> regedit.exe''') and setting (you'll most surely have to add the value since in most cases it doesn't exist):

''HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections'' (which is a String type and it's value must be a 32-bit number).

== My progress bars have lost most of their 3D effect and look more ugly now. Can I turn its look back? ==

In most aMule versions setting the progress bar style to the most right on Preferences -> "GUI tweaks" is the way to have the progress bar have the best 3D effect. But in versions 2.0.0-rc4 to 2.0.0-rc6 the best 3D effect is given when the style bar is set to the middle. Setting it to the most right would give the progress bar a flat look while setting it to the most left will give it a dark look.

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

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

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

== Why can't I preview a file? ==

First of all you must know that [[aMule]] only allows to preview video files.

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

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

== Why isn't [[aMule]]'s Preview working at all with MPlayer? ==

Since aMule 2.0.0-rc4 Preview command isn't being run in the same terminal as aMule. As a result, your Preview program may fail to start. This is the case of MPlayer. If you need a terminal to run your Preview player, use some command like ''xterm -e <preview-app>'' i.e.:

''xterm -T "aMule preview" -iconic -e mplayer -idx''

== After exitting MPlayer on Preview, my aMule keeps locked? ==

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

== Why is ''Transfered'' a smaller number than ''Completed''? ==

It's a common mistake to think it should be bigger or, at least, equal.

Please read [[FAQ_aMule#What_is_the_difference_between_Transfered_and_Completed_in_the_Tranfers_window?|What is the difference between Transfered and Completed in the Tranfers window?]] to know more about this.

== aMule always slows down my computer when it completes a download. Is this a normal behaviour? ==

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

== Is there any way to recursively select a whole directory and its contents? ==

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

And that's it.

== I downloaded a file and it got corrupted somehow by my hard disk or some external application once completed. Can I avoid redownloading the whole of it? ==

If you still have the [[ed2k_link|ed2k:// link]], start the download again and when a whole chunk (9.28MB) has been downloaded (any chunk), close [[aMule]], rename the corrupted file to the filename the current download has (something like ''002.part''), touch the corrupted file (i.e.: ''touch ~/.aMule/Temp/002.part*'') and restart [[aMule]].

[[aMule]] will detect the completed chunks and the corrupted ones, and will only download the chunks which got corrupted.

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

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

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

== Downloaded files don't get the permissions I set in Preferences. Why? ==

aMule must follow the permissions it is allowed to set by ''umask''. ''umask'' sets the permissions which applications should '''not''' be allowed to assign files.

Therefore, if you set, for example, file permissions to ''664'' in aMule's Preferences, and umask's value (check it by running ''umask'') is ''022'', aMule will create files with permissions ''644'' (that is, ''664'' - ''022'' = ''644'').

== aMule fails to create files/shows file descriptor errors. What's going on? ==

This should never happen. If it happens chances are you have the resources limits very low, so aMule is denied to create/open new files. Run ''ulimit -a'' to check your resources limits. Read ''man ulimit'' to learn how to set the limits as you want them, and remember that this has to be set on every system restart (probably your distribution provides a configuration file which sets this automatically).

AMule problems-it

2007-04-28T16:52:07Z

87.14.231.86:

<center>
<u><h4>[[aMule_Project_FAQ:About|aMule]] Problemi comuni</h4></u>

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

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

== Quando faccio partire aMule mi esce il messaggio "aMule already running: exiting". Posso farlo partire lo stesso? ==

Il messaggio è molto chiaro: [[aMule]] sta già girando. Ma questo non si riferisce al sistema, significa che ''tu'' (il tuo account utente) sta già facendo girare [[aMule]].

Potrebbe sembrare che non ci sia nessuna istanza di [[aMule]] in esecuzione, se c'è stato un crash. Ma qualche volta succede che qualche processo non si chiuda totalmente, rimanendo in uno stato chiamato ''zombi'' o ''defunto''. Per scoprire se questo è il tuo problema, esegui in un terminale ''ps u | grep amule'' e se compare qualche messaggio (a parte quello di grep stesso), allora qualche processo di aMule sta girando a tuo nome. Per ucciderlo, chiudilo normalmente (se puoi) oppure fallo con ''kill -9 <aMile PID>'' oppure con ''killall -9 amule'' oppure prova ad uscire e rientrare (che nella maggior parte dei casi chiuderà tutti i processi di [[aMule]] a meno che tu l'abbia avviato con ''nohup'' o simili).

Se sei sicuro che nessun processo di [[aMule]] stia girando, controlla se esiste un file [[MuleLock_file|muleLock]] nella tua cartella ~/.aMule e cancellalo per ripristinare il funzionamento normale di [[aMule]].

Se nessuna delle soluzioni è adatta per te, puoi eseguire un'altra istanza di [[aMule]] come altro utente (se puoi entrare con un altro nome utente, chiaramente).
Leggi [FAQ_aMule#Can_I_run_two_aMule_instances_at_the_same_time?|Can I run two aMule instances at the same time?]].

== aMule parte ma non compare la schermata, anche se funziona. Cosa sta succedendo? ==

Questo succede di solito quando imposti il tipo di integrazione nel vassoio di sistema a ''Minimizza nel vassoio'' (da Preferenze -> Generale). Questo fa partire [[aMule]] minimizzato.

Per recuperare la schermata di aMule, modifica ''~/.aMule/amule.conf'' e cerca ''StartupMinimized=1'' Cambia questa riga a ''StartupMinimized=0''.
Questo script farà il lavoro per te:

''sed s/StartupMinimized=1/StartupMinimized=0/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf''

Quando farai partire [[aMule]] la prossima volta imposta la giusta integrazione nel vassoio dalle Preferenze, per riuscire a minimizzare [[aMule]] senza che venga nascosto.

Se per qualche motivo questo metodo non funziona, prova a cambiare l'integrazione nel vassoio manualmente, togliendo la crocetta dall'opzione ''Abilita icona vassoio''. Per farlo, apri ''~/.aMule/amule.conf'' e imposta il valore di ''DesktopMode='' a ''4''. Questo script farà il lavoro per te:

''sed s/DesktopMode=[0-9]/DesktopMode=4/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf''

'''NOTA:''' Nelle versioni di [[aMule]] precedenti a 2.0.0rc4, imposta a ''1'' invece di ''4'' perché il file delle preferenze è stato cambiato.

== aMule parte ma non si connette/si comporta in modo strano/si blocca ogni pochi secondi/ecc...? ==

Le versioni di aMule fino alla 2.0.0-rc3 non devono essere linkate ai wxWidgets 2.5.x e neanche al GTK2, anche se qualche distribuzione lo fa. Assicurati che non sia il tuo caso. In caso di incertezza, spedisci il tuo backtrace a [http://www.amule.org/amule/board.php?boardid=33 aMule's Backtraces forum] oppure vai sul canale IRC di aMule #amule at irc.freenode.net

== Dove sono i miei file scaricati? ==

Di default, aMule memorizza i file completati in ''~/.aMule/Incoming'' ma siccome la cartella ''~/.aMule'' è nascosta (inizia con un punto), il tuo file manager potrebbe non visualizzarla. Assicurati di impostare il file manager a visualizzare le cartelle nascoste.

Di default i file in corso di scaricamento sono in ''~/.aMule/Temp'', per cui anche in questo caso per vederli occorre impostare il file manager.

== Perché aMule richiede così tante risorse CPU all'avvio? ==

aMule sta calcolando gli hash dei nuovi file che ha trovato nelle cartelle condivise.

Se aMule occupa sempre molta CPU anche quando nessun nuovo file è stato aggiunto o modificato nelle cartelle condivise, allora c'è qualcosa che non va.

Nelle versioni di aMule precedenti la 2.0.0-rc3 questo succedeva quando la cartella Temp, Incoming o qualsiasi cartella condivisa era in una partizione FAT32. Ora questo non succede più.

Inoltre nelle versioni di aMule precedenti la 2.0.0-rc4, i filesystem con codifica UTF-8 (per esempio con SUSE 9.1) potrebbero presentare problemi quando qualche file o cartella condivisa contiene un carattere speciale. Se questo è il tuo problema, c'è un rimedio (grazie '''nachbarnebenan'''): dopo che aMule ha calcolato gli hash dei file condivisi (cioè quando smette di occupare la CPU) chiudi aMule e codifica ~/.aMule/known.met in UTF-8 (lo puoi fare con ''[http://www.gnu.org/directory/recode.html recode]'' con il seguente comando: ''recode u8 ~/.aMule/known.met''). Questo va fatto ogni volta che un file viene aggiunto o modificato nelle cartelle condivise. Forse è meglio aggiornare aMule all'ultima versione.

Se niente finora ti ha aiutato, è successo qualcosa al file ''known.met'' , forse qualche programma esterno o qualche altro utente lo ha rovinato. E' meglio cancellarlo, far partire aMule e lasciare che ricalcoli tutti gli hash dei file.

== Adesso aMule parte, ma mi dice "Nessun server valido nella lista dei server" ==

Hai abilitato l'opzione "Connetti automaticamente solo ai server statici". Cancella questa opzione oppure metti qualche server nella lista statica.

Per togliere l'opzione, vai a Preferenze -> Server -> Connetti automaticamente solo ai server statici

Per aggiungere un server alla lista statica, vai alla finestra Server e fai clic destro sul server che vuoi aggiungere alla lista. Poi scegli "Aggiungi alla lista statica" e ripeti il procedimento per tutti i server che vuoi mettere nella lista statica.

== Why does it happen that sometimes aMule suddenly has no/few servers in is server list? ==

You probably have enabled the options Preferences -> Servers -> "Remove dead server after X retries" and Preferences -> Connection -> "Reconnect on loss".

If so, most probably you lost internet (or lan, etc) connection for a period of time so aMule noticed it was not connected to the ed2k server anymore and went trying to connect to other servers until all servers were removed (after trying X times each).

To solve this problem, disable the "Remove dead server after X retries" option. Disabling the option "Remove dead server after X retries" is safe in most cases. You most probably don't want to disable the "Reconnect on loss" option, so keep it enabled.

== aMule connects to server, but it is always given Low-ID. Why? and, can I do something about it? ==

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

== [[aMule]] was interrupted while completing a file and it is now never completing it (although it's 100% downloaded). How can I complete it? ==

This one is easy: Close [[aMule]]. Now go into the Temp directory (by default, ''~/.aMule/Temp'') and run the following command:

''touch ./*''

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

== I just lost a download. Is there any way I can recover it? ==

This is strange to happen, but it might, although in most cases it is the result of some non-aMule-related stuff going weird (or user's fault).<br>
Two things may have happened. Either *.part.met files were deleted, or *.part files were deleted.

If *.part files have disappeared, the only solution is to restart the downloads from the beginning (if *.part.met files are still there, aMule will restart the downloads on next start). However this should '''never''' happen unless the user directly deleted them.

If *.part.met files have disappeared but *.part files are still in the Temp directory, then search if *.part.met.bak are also in the Temp directory. If they are, then just rename ''*.part.met.bak'' files to ''*.part.met'' just by running:

''for file in *.part.met.bak; do mv -f "$file" "${file%.bak}; done''

Still, it could happen that, although you have the *.part files, neither *.part.met nor *.part.met.bak files exist any longer. In this case, you would have two ways ways to work out of this:

Either, use [http://www.bigwillystyle42.com/mfr/ MetFileRegenerator] (Java needed) to reconstruct the *.part.met files.

Or, search again on aMule for the files you were downloading and rename their part number in the *.part.met files to the ones it used to have. For example, if you were downloading ''aMule_1.2.6.tar.gz'' and that was being downloaded in Temp directory as ''008.part'', then that file used to have it's corresponding ''008.part.met'' file and, probably, it's ''008.part.met.bak'' file. But this two latter files have mysteriously disappeared. Then search again on aMule for ''aMule_1.2.6.tar.gz'' and start downloading it. Close aMule and you'll have this new download as, for example, ''011.part'' file in the Temp directory. Of course, this download will have it's ''011.part.met'' file. Well, rename ''011.part.met'' to ''008.part.met'' and then delete ''011.part'' (and ''011.part.met.bak'' if it existed). Now start aMule and you will have recovered the download from the point it was before the *.part.met files disapeared.

== Why does aMule suddenly become unresponsive to the mouse although it's not hanged? ==

It sometimes happens that you left a dialog window somewhere hidden in the desktop. aMule is waiting for that window to be closed, so it becomes unresponsive until you click OK, Cancel, or whatever you have to click.

So, make sure there's no aMule dialog left around in '''any workspace'''.

== Why are some files in my shared folders not shown in the Shared Folders window? ==

This could happen if you added this files after aMule has been started. Press the "Reload" button on Shared Folders window and it should find the new files and hash them (this may take some CPU time).

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

== I always get a message about addresses.met when I start aMule. What's wrong? ==

This happens when you enable the option Preferences -> Servers -> "Auto-update serverlist at startup" and you have no serverlists' urls in ''addresses.dat''. You can either add some to ''addresses.dat'' by adding them at Preferences -> Servers -> List or just disable Preferences -> Servers -> "Auto-update serverlist at startup" if you don't really need it.

== I sometimes get a message on the log about credits being lost. Should I be worried? ==

No, you don't need to be worried. Credits for a client are deleted after 150 days (more or less 5 months) without "seeing" that client. Also, bad clients might lose their credits too. So those messages are just for debug information, you shouldn't worry about them.

== What should I do if I lose my ''cryptkey.dat'' file? ==

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

== Why is Upload/Download limit always back to 0 after every restart? ==

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

== Why is aMule ignoring the bandwidth I set per slot? ==

The bandwidth set to each slot can be set in Preferences, but it will be ignored if the bandwidth set per slot doesn't allow at least three connections at the same time.

So, the maximum speed allowed per slot is '''BandwidthLimit/3'''.

Please do '''NOT''' confuse '''Bandwidth limit''' with '''Bandwidth Capacity'''. Read [[FAQ_aMule#What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?|What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] since the meaning of the Bandwidth Capacity setting is not intuitive.

Also, if [[aMule]] detects that, after having set all the slots for uploading, still some bandwidth is left before getting to the Bandwidth Limit, it will allow another slot and divide all the slot bandwidths to so use the same amount of bandwidth.

Example:
*Bandwidth Limit: 7 KBps
*Slot allocation: 2 KBps

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

== Why can't I set aMule's download limit to more than X? ==

To keep the ED2K network alive, all ED2K clients have an upload/download limits ratio hardcoded which, depending on the upload limit set, is:
*<u>From 0KBps to 3KBps:</u>
*DownloadLimit can't be more than UploadLimit*3
*<u>From 4KBps to 9KBps:</u>
*DownloadLimit can't be more than UploadLimit*4
*<u>UploadLimit values over 9KBps:</u>
*There's <b>no</b> DownloadLimit limitation.

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

== I set Upload Limit to 0KBps, but aMule is still transferring. What did I do wrong? ==

Setting Upload limit to 0KBps will not stop transfers, instead, ''0'' value means '''unlimited''', so, it's right the opposite of you're trying to do. There's no way to stop aMule from uploading files, and that's the same on all ED2K clients (eMule, eDonkey, etc). Allowing people not to upload would bring the ED2K network to it's end.

Even if you don't share any directory, the Temp directory will '''always''' be shared, so that files that you are downloading are shared with other clients.

== Why am I getting "Too many connections" messages on the terminal? ==

This happens when you set a very high value at Preferences -> Connections -> "Connection limits" -> "Max connections". If this value is as almost as big as the the amount of connections your system allows you to have, then aMule will fail to establish connections and display those messages (have in mind that other applications may also have some connections established).

On Windows 9x/ME platforms there is a limit of 100 TCP connections so, although you might set aMule to establish more than 100 connections, it will be unable to do so. You can change Windows's TCP connections limit by editing the Windows Register ('''Start -> Run -> regedit.exe''') and setting (you'll most surely have to add the value since in most cases it doesn't exist):

''HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections'' (which is a String type and it's value must be a 32-bit number).

== My progress bars have lost most of their 3D effect and look more ugly now. Can I turn its look back? ==

In most aMule versions setting the progress bar style to the most right on Preferences -> "GUI tweaks" is the way to have the progress bar have the best 3D effect. But in versions 2.0.0-rc4 to 2.0.0-rc6 the best 3D effect is given when the style bar is set to the middle. Setting it to the most right would give the progress bar a flat look while setting it to the most left will give it a dark look.

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

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

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

== Why can't I preview a file? ==

First of all you must know that [[aMule]] only allows to preview video files.

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

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

== Why isn't [[aMule]]'s Preview working at all with MPlayer? ==

Since aMule 2.0.0-rc4 Preview command isn't being run in the same terminal as aMule. As a result, your Preview program may fail to start. This is the case of MPlayer. If you need a terminal to run your Preview player, use some command like ''xterm -e <preview-app>'' i.e.:

''xterm -T "aMule preview" -iconic -e mplayer -idx''

== After exitting MPlayer on Preview, my aMule keeps locked? ==

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

== Why is ''Transfered'' a smaller number than ''Completed''? ==

It's a common mistake to think it should be bigger or, at least, equal.

Please read [[FAQ_aMule#What_is_the_difference_between_Transfered_and_Completed_in_the_Tranfers_window?|What is the difference between Transfered and Completed in the Tranfers window?]] to know more about this.

== aMule always slows down my computer when it completes a download. Is this a normal behaviour? ==

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

== Is there any way to recursively select a whole directory and its contents? ==

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

And that's it.

== I downloaded a file and it got corrupted somehow by my hard disk or some external application once completed. Can I avoid redownloading the whole of it? ==

If you still have the [[ed2k_link|ed2k:// link]], start the download again and when a whole chunk (9.28MB) has been downloaded (any chunk), close [[aMule]], rename the corrupted file to the filename the current download has (something like ''002.part''), touch the corrupted file (i.e.: ''touch ~/.aMule/Temp/002.part*'') and restart [[aMule]].

[[aMule]] will detect the completed chunks and the corrupted ones, and will only download the chunks which got corrupted.

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

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

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

== Downloaded files don't get the permissions I set in Preferences. Why? ==

aMule must follow the permissions it is allowed to set by ''umask''. ''umask'' sets the permissions which applications should '''not''' be allowed to assign files.

Therefore, if you set, for example, file permissions to ''664'' in aMule's Preferences, and umask's value (check it by running ''umask'') is ''022'', aMule will create files with permissions ''644'' (that is, ''664'' - ''022'' = ''644'').

== aMule fails to create files/shows file descriptor errors. What's going on? ==

This should never happen. If it happens chances are you have the resources limits very low, so aMule is denied to create/open new files. Run ''ulimit -a'' to check your resources limits. Read ''man ulimit'' to learn how to set the limits as you want them, and remember that this has to be set on every system restart (probably your distribution provides a configuration file which sets this automatically).

AMule problems-it

2007-04-28T16:31:21Z

87.14.231.86:

<center>
<u><h4>[[aMule_Project_FAQ:About|aMule]] Problemi comuni</h4></u>

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

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

== Quando faccio partire aMule mi esce il messaggio "aMule already running: exiting". Posso farlo partire lo stesso? ==

Il messaggio è molto chiaro: [[aMule]] sta già girando. Ma questo non si riferisce al sistema, significa che ''tu'' (il tuo account utente) sta già facendo girare [[aMule]].

Potrebbe sembrare che non ci sia nessuna istanza di [[aMule]] in esecuzione, se c'è stato un crash. Ma qualche volta succede che qualche processo non si chiuda totalmente, rimanendo in uno stato chiamato ''zombi'' o ''defunto''. Per scoprire se questo è il tuo problema, esegui in un terminale ''ps u | grep amule'' e se compare qualche messaggio (a parte quello di grep stesso), allora qualche processo di aMule sta girando a tuo nome. Per ucciderlo, chiudilo normalmente (se puoi) oppure fallo con ''kill -9 <aMile PID>'' oppure con ''killall -9 amule'' oppure prova ad uscire e rientrare (che nella maggior parte dei casi chiuderà tutti i processi di [[aMule]] a meno che tu l'abbia avviato con ''nohup'' o simili).

Se sei sicuro che nessun processo di [[aMule]] stia girando, controlla se esiste un file [[MuleLock_file|muleLock]] nella tua cartella ~/.aMule e cancellalo per ripristinare il funzionamento normale di [[aMule]].

Se nessuna delle soluzioni è adatta per te, puoi eseguire un'altra istanza di [[aMule]] come altro utente (se puoi entrare con un altro nome utente, chiaramente).
Leggi [FAQ_aMule#Can_I_run_two_aMule_instances_at_the_same_time?|Can I run two aMule instances at the same time?]].

== aMule parte ma non compare la schermata, anche se funziona. Cosa sta succedendo? ==

Questo succede di solito quando imposti il tipo di integrazione nel vassoio di sistema a ''Minimizza nel vassoio'' (da Preferenze -> Generale). Questo fa partire [[aMule]] minimizzato.

Per recuperare la schermata di aMule, modifica ''~/.aMule/amule.conf'' e cerca ''StartupMinimized=1'' Cambia questa riga a ''StartupMinimized=0''.
Questo script farà il lavoro per te:

''sed s/StartupMinimized=1/StartupMinimized=0/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf''

Quando farai partire [[aMule]] la prossima volta imposta la giusta integrazione nel vassoio dalle Preferenze, per riuscire a minimizzare [[aMule]] senza che venga nascosto.

Se per qualche motivo questo metodo non funziona, prova a cambiare l'integrazione nel vassoio manualmente, togliendo la crocetta dall'opzione ''Abilita icona vassoio''. Per farlo, apri ''~/.aMule/amule.conf'' e imposta il valore di ''DesktopMode='' a ''4''. Questo script farà il lavoro per te:

''sed s/DesktopMode=[0-9]/DesktopMode=4/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf''

'''NOTA:''' Nelle versioni di [[aMule]] precedenti a 2.0.0rc4, imposta a ''1'' invece di ''4'' perché il file delle preferenze è stato cambiato.

== aMule starts but is never connecting/behaving very weird/crashing almost every few seconds/etc...? ==

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

== Where are my downloaded files? ==

By default, aMule stores completed files in ''~/.aMule/Incoming'' but, since ''~/.aMule'' directory is a hidden directory, your file manager might not show it. Make sure you have enabled your file manager to show hidden files.

By default, files being downloaded are placed in ''~/.aMule/Temp'', so again, this is a hidden directory and the file managed must be configured to show hidden files.

== Why is aMule taking so much CPU resources at start-up? ==

This happens because aMule is hashing new files found on the Shared Directories.

If aMule is always taking a lot of CPU at startup and no new files have been added or modified in any way in the Shared Directories, then something is wrong.

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

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

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

== So now aMule starts, but why is it displaying this message: "No valid servers to connect in serverlist found"? ==

That's because you enabled the option "Auto connect to servers the static list only". So, disable it or add some server to the static list.

To disable that option, go to Preferences -> Servers -> "Auto connect to servers the static list only"

To add a server to the static list, go to the Servers window and right-click on the server you want to add to the static list. Then select "Add to static" and do this exact process wit all the servers you want to add to the static list.

== Why does it happen that sometimes aMule suddenly has no/few servers in is server list? ==

You probably have enabled the options Preferences -> Servers -> "Remove dead server after X retries" and Preferences -> Connection -> "Reconnect on loss".

If so, most probably you lost internet (or lan, etc) connection for a period of time so aMule noticed it was not connected to the ed2k server anymore and went trying to connect to other servers until all servers were removed (after trying X times each).

To solve this problem, disable the "Remove dead server after X retries" option. Disabling the option "Remove dead server after X retries" is safe in most cases. You most probably don't want to disable the "Reconnect on loss" option, so keep it enabled.

== aMule connects to server, but it is always given Low-ID. Why? and, can I do something about it? ==

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

== [[aMule]] was interrupted while completing a file and it is now never completing it (although it's 100% downloaded). How can I complete it? ==

This one is easy: Close [[aMule]]. Now go into the Temp directory (by default, ''~/.aMule/Temp'') and run the following command:

''touch ./*''

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

== I just lost a download. Is there any way I can recover it? ==

This is strange to happen, but it might, although in most cases it is the result of some non-aMule-related stuff going weird (or user's fault).<br>
Two things may have happened. Either *.part.met files were deleted, or *.part files were deleted.

If *.part files have disappeared, the only solution is to restart the downloads from the beginning (if *.part.met files are still there, aMule will restart the downloads on next start). However this should '''never''' happen unless the user directly deleted them.

If *.part.met files have disappeared but *.part files are still in the Temp directory, then search if *.part.met.bak are also in the Temp directory. If they are, then just rename ''*.part.met.bak'' files to ''*.part.met'' just by running:

''for file in *.part.met.bak; do mv -f "$file" "${file%.bak}; done''

Still, it could happen that, although you have the *.part files, neither *.part.met nor *.part.met.bak files exist any longer. In this case, you would have two ways ways to work out of this:

Either, use [http://www.bigwillystyle42.com/mfr/ MetFileRegenerator] (Java needed) to reconstruct the *.part.met files.

Or, search again on aMule for the files you were downloading and rename their part number in the *.part.met files to the ones it used to have. For example, if you were downloading ''aMule_1.2.6.tar.gz'' and that was being downloaded in Temp directory as ''008.part'', then that file used to have it's corresponding ''008.part.met'' file and, probably, it's ''008.part.met.bak'' file. But this two latter files have mysteriously disappeared. Then search again on aMule for ''aMule_1.2.6.tar.gz'' and start downloading it. Close aMule and you'll have this new download as, for example, ''011.part'' file in the Temp directory. Of course, this download will have it's ''011.part.met'' file. Well, rename ''011.part.met'' to ''008.part.met'' and then delete ''011.part'' (and ''011.part.met.bak'' if it existed). Now start aMule and you will have recovered the download from the point it was before the *.part.met files disapeared.

== Why does aMule suddenly become unresponsive to the mouse although it's not hanged? ==

It sometimes happens that you left a dialog window somewhere hidden in the desktop. aMule is waiting for that window to be closed, so it becomes unresponsive until you click OK, Cancel, or whatever you have to click.

So, make sure there's no aMule dialog left around in '''any workspace'''.

== Why are some files in my shared folders not shown in the Shared Folders window? ==

This could happen if you added this files after aMule has been started. Press the "Reload" button on Shared Folders window and it should find the new files and hash them (this may take some CPU time).

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

== I always get a message about addresses.met when I start aMule. What's wrong? ==

This happens when you enable the option Preferences -> Servers -> "Auto-update serverlist at startup" and you have no serverlists' urls in ''addresses.dat''. You can either add some to ''addresses.dat'' by adding them at Preferences -> Servers -> List or just disable Preferences -> Servers -> "Auto-update serverlist at startup" if you don't really need it.

== I sometimes get a message on the log about credits being lost. Should I be worried? ==

No, you don't need to be worried. Credits for a client are deleted after 150 days (more or less 5 months) without "seeing" that client. Also, bad clients might lose their credits too. So those messages are just for debug information, you shouldn't worry about them.

== What should I do if I lose my ''cryptkey.dat'' file? ==

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

== Why is Upload/Download limit always back to 0 after every restart? ==

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

== Why is aMule ignoring the bandwidth I set per slot? ==

The bandwidth set to each slot can be set in Preferences, but it will be ignored if the bandwidth set per slot doesn't allow at least three connections at the same time.

So, the maximum speed allowed per slot is '''BandwidthLimit/3'''.

Please do '''NOT''' confuse '''Bandwidth limit''' with '''Bandwidth Capacity'''. Read [[FAQ_aMule#What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?|What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] since the meaning of the Bandwidth Capacity setting is not intuitive.

Also, if [[aMule]] detects that, after having set all the slots for uploading, still some bandwidth is left before getting to the Bandwidth Limit, it will allow another slot and divide all the slot bandwidths to so use the same amount of bandwidth.

Example:
*Bandwidth Limit: 7 KBps
*Slot allocation: 2 KBps

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

== Why can't I set aMule's download limit to more than X? ==

To keep the ED2K network alive, all ED2K clients have an upload/download limits ratio hardcoded which, depending on the upload limit set, is:
*<u>From 0KBps to 3KBps:</u>
*DownloadLimit can't be more than UploadLimit*3
*<u>From 4KBps to 9KBps:</u>
*DownloadLimit can't be more than UploadLimit*4
*<u>UploadLimit values over 9KBps:</u>
*There's <b>no</b> DownloadLimit limitation.

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

== I set Upload Limit to 0KBps, but aMule is still transferring. What did I do wrong? ==

Setting Upload limit to 0KBps will not stop transfers, instead, ''0'' value means '''unlimited''', so, it's right the opposite of you're trying to do. There's no way to stop aMule from uploading files, and that's the same on all ED2K clients (eMule, eDonkey, etc). Allowing people not to upload would bring the ED2K network to it's end.

Even if you don't share any directory, the Temp directory will '''always''' be shared, so that files that you are downloading are shared with other clients.

== Why am I getting "Too many connections" messages on the terminal? ==

This happens when you set a very high value at Preferences -> Connections -> "Connection limits" -> "Max connections". If this value is as almost as big as the the amount of connections your system allows you to have, then aMule will fail to establish connections and display those messages (have in mind that other applications may also have some connections established).

On Windows 9x/ME platforms there is a limit of 100 TCP connections so, although you might set aMule to establish more than 100 connections, it will be unable to do so. You can change Windows's TCP connections limit by editing the Windows Register ('''Start -> Run -> regedit.exe''') and setting (you'll most surely have to add the value since in most cases it doesn't exist):

''HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections'' (which is a String type and it's value must be a 32-bit number).

== My progress bars have lost most of their 3D effect and look more ugly now. Can I turn its look back? ==

In most aMule versions setting the progress bar style to the most right on Preferences -> "GUI tweaks" is the way to have the progress bar have the best 3D effect. But in versions 2.0.0-rc4 to 2.0.0-rc6 the best 3D effect is given when the style bar is set to the middle. Setting it to the most right would give the progress bar a flat look while setting it to the most left will give it a dark look.

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

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

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

== Why can't I preview a file? ==

First of all you must know that [[aMule]] only allows to preview video files.

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

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

== Why isn't [[aMule]]'s Preview working at all with MPlayer? ==

Since aMule 2.0.0-rc4 Preview command isn't being run in the same terminal as aMule. As a result, your Preview program may fail to start. This is the case of MPlayer. If you need a terminal to run your Preview player, use some command like ''xterm -e <preview-app>'' i.e.:

''xterm -T "aMule preview" -iconic -e mplayer -idx''

== After exitting MPlayer on Preview, my aMule keeps locked? ==

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

== Why is ''Transfered'' a smaller number than ''Completed''? ==

It's a common mistake to think it should be bigger or, at least, equal.

Please read [[FAQ_aMule#What_is_the_difference_between_Transfered_and_Completed_in_the_Tranfers_window?|What is the difference between Transfered and Completed in the Tranfers window?]] to know more about this.

== aMule always slows down my computer when it completes a download. Is this a normal behaviour? ==

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

== Is there any way to recursively select a whole directory and its contents? ==

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

And that's it.

== I downloaded a file and it got corrupted somehow by my hard disk or some external application once completed. Can I avoid redownloading the whole of it? ==

If you still have the [[ed2k_link|ed2k:// link]], start the download again and when a whole chunk (9.28MB) has been downloaded (any chunk), close [[aMule]], rename the corrupted file to the filename the current download has (something like ''002.part''), touch the corrupted file (i.e.: ''touch ~/.aMule/Temp/002.part*'') and restart [[aMule]].

[[aMule]] will detect the completed chunks and the corrupted ones, and will only download the chunks which got corrupted.

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

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

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

== Downloaded files don't get the permissions I set in Preferences. Why? ==

aMule must follow the permissions it is allowed to set by ''umask''. ''umask'' sets the permissions which applications should '''not''' be allowed to assign files.

Therefore, if you set, for example, file permissions to ''664'' in aMule's Preferences, and umask's value (check it by running ''umask'') is ''022'', aMule will create files with permissions ''644'' (that is, ''664'' - ''022'' = ''644'').

== aMule fails to create files/shows file descriptor errors. What's going on? ==

This should never happen. If it happens chances are you have the resources limits very low, so aMule is denied to create/open new files. Run ''ulimit -a'' to check your resources limits. Read ''man ulimit'' to learn how to set the limits as you want them, and remember that this has to be set on every system restart (probably your distribution provides a configuration file which sets this automatically).

FAQ eD2k-Kademlia-it

2007-04-28T15:49:19Z

87.14.231.86:

<center>
<u><h4>F.A.Q. di eD2k-Kademlia</h4></u>

<h2>(Tradotto da ''[[User:SNeo|SNeo]]'' & floyte)</h2>

[[FAQ_eD2k-Kademlia|English]] | [[FAQ_eD2k-Kademlia-es|Español]] | '''Italiano''' | [[FAQ_eD2k-Kademlia-de|Deutsche]] | [[FAQ_ed2k-fr|Français]] | [[FAQ_eD2k-Kademlia-nl|Nederlands]] | [[FAQ_eD2k-Kademlia-pl|Polish]] | [[FAQ_eD2k-Kademlia-ru|Russian]]
</center>

== Che cosè ED2K? ==

ED2K è un protocollo originariamente usato dal client P2P (Peer-to-Peer) eDonkey2000, da dove viene il nome. E' un protocollo basato sul sistema client-server, con l'abilità di scambiare fonti tra i client.

La rete ED2K si basa sui server non come reti quali Kazaa, significa che la prima cosa da fare quando avvii aMule è collegarsi a un server (manualmente o automaticamente).

Una volta connesso su un server, il client può ricercare, o localmente (al server in cui si è connesso) o globalmente (a tutti i server), qualsiasi file,e i server a cui è stata inviata la richiesta forniranno al client una lista con tutti i file che corrispondono ai criteri di ricerca.

Se un utente comincia un download, il client chiederà al server le fonti, che saranno fornite dal server sotto forma di indirizzi IP dei client che hanno comunicato al server di avere il file specificato.

== Che cosè Kademlia? ==

Traduzione e binari per amule-cvs presenti su [http://gift.altervista.org/index_it.php?section=50 questo sito]

== Kademlia è come Overnet? ==

== Che cosè un chunk? ==

Nel protocollo ED2K, per evitare di condividere file rovinati, ogni file viene diviso in varie parti chiamate chunks; in seguito ad ogni chunk viene dato un hash (leggi sotto cos'è un hash). Ogni chunk è di 9,28 MB, quindi un file di 15MB verrà diviso in due chunk (9,28 MB + 5,72 MB), un file di 315 KB sarà in un solo chunk e un file di 100 MB sarà diviso in 11 chunk (10x9,28 MB + 7,2 MB)

== Che cosè un hash? ==

Dividendo ogni file in chunk (vedi sopra) si evita il problema di scaricare un intero file rovinato, in quanto solo il chunk rovinato dovrà essere scaricato di nuovo. C'è bisogno però di un metodo per identificare i chunk rovinati. Questo viene fatto con gli hash MD4.

Un hash MD4 è un numero unico che viene dato ad ogni chunk ed è il risultato di una operazione matematica su ogni singolo bit del chunk. Questo significa che modificando un solo bit nel chunk si ottiene un hash totalmente diverso.
Il client deve verificare l'integrità di ogni parte del file mentre lo scarica.

Ogni chunk viene dotato di un hash, ma in più per avere un hash per il file, tutti gli hash dei chunk vengono concatenati uno dopo l'altro nell'ordine del file (hash_chunk1 + hash_chunk2 + hash_chunk3 + ...) e sulla stringa risultante viene calcolato l'hash.
In questo modo, ogni file nella rete ED2K ha un identificativo univoco. L'hash del file non viene calcolato sul file, ma sugli hash dei suoi pezzi.

In realtà si deve conoscere sia l'hash del file che la sua dimensione. Queste informazioni sono contenute negli URL di ED2K che si trovano in molti posti.

Ecco un esempio:

ed2k://|file|eMule0.42f-Sources.zip|2407949|CC8C3B104AD58678F69858F1F9B736E9|/

Le parti che interessano sono la quinta, "2407949", che è la dimensione del file in byte, e l'ultima,"CC8C3B104AD58678F69858F1F9B736E9", che è l'hash memorizzato come numero esadecimale di 32 caratteri.

Il nome del file è irrilevante nel processo di identificazione del file.

== Perchè dopo una ricerca, certi file che sono gli stessi appaiono come file differenti tra i risultati, sebbene abbiano lo stesso nome? ==

== Che cosè il Basso e Alto ID? ==

== Quali porte devo configurare in un firewall o in un router per avviare aMule?
==

Si deve distinguere tra connessioni in entrata e in uscita. Normalmente, tutte le porte di un router sono aperte per l'invio di dati (connessione in uscita).

Quindi in questo caso normale, devi solo configurare le porte per le connessioni in ingresso:

aMule funziona anche senza porte specificamente aperte, ma non otterresti un ID alto in questo caso. Come detto sopra, per ottenere un ID alto la porta 4662 TCP (oppure quella impostata nelle preferenze) deve essere in ascolto (cioè aperta nel firewall e inoltrata dal router).

A parte quella porta, per avere un uso ottimale di ED2K, altre due porte dovrebbero essere in ascolto: le porte UDP 4672 e 4665 (cioè portaTCP +3). Entrambe possono essere cambiate nelle preferenze a qualsiasi altro valore.

== Perché Kademlia dice ancora che è "firewalled"? ==

Se stai usando Kad e il tuo router fa il NAT (Traslazione Indirizzi di Rete) dovresti evitare che il router trasferisca la porta in uscita UDP numero 4672.
Questo dovrebbe funzionare se hai già un ID alto ma lo stato di Kad è "firewalled".

== Che cosa fa esattamente ogni porta? ==

Siccome quasi tutte le porte possono essere configurate a qualsiasi altro numero, faremo l'elenco delle impostazioni di default. La direzione del traffico è dal punto di vista del cliente (tu):

* 4661 TCP (uscita): porta su cui ascolta il server (definita dal server)
* 4662 TCP (uscita e ingresso): trasferimenti diretti tra clienti
* 4665 UDP (uscita e ingresso): usata per le ricerche globali sui server e per le interrogazioni globali sulle fonti. E' sempre uguale a PORTA_TCP+3
* 4672 UDP (uscita e ingresso): protocollo eMule esteso, punteggi di coda, File Reask Ping, Kad. Kad sarà 'firewalled' se il NAT (Network Address Translation) sposta questo numero di porta.
* 4711 TCP: porta WebServer in ascolto.
* 4712 TCP: porta connessione esterna. Usata per far comunicare aMule con altre applicazioni come WebServer aMule o con aMuleCMD.

== C'è qualche limitazione nella rete ED2K? ==

Traduzione e binari per amule-cvs presenti su [http://gift.altervista.org/index_it.php?section=50 questo sito]

== Nella finestra ricerca, che filtro si usa per ogni tipo di file? ==

== Che cosè una fonte? ==

== Che cosè tutta quella roba sui crediti, velocità e punteggio? ==

Tutti e tre i concetti hanno a che fare col modo in cui la rete ED2K stabilisce le preferenze sulle code di invio.

Il punteggio è il valore più importante: il client con il punteggio più alto sarà il prossimo a cui verrà dato uno slot di invio. Il valore del punteggio è assegnato così: punteggio = velocità x tempo_di_attesa_secondi / 100.
Così per capire il calcolo dobbiamo vedere cos'è la velocità.

La velocità la possiamo pensare come una preferenza obbiettiva. Cioè la preferenza che viene data ad un client senza preoccuparsi di quanto tempo ha aspettato. Quando un client viene aggiunto alla coda di invio, gli viene data una velocità di 100. Questo valore si modifica in questo modo:

A seconda dei crediti, la velocità viene moltiplicata da 1 a 10. A seconda della priorità del file, viene moltiplicata da 0,2 a 1,8 (Release 1,8 Alto 0,9 Normale 0,7 Basso 0,6 Bassissimo 0,2).
Gli utenti con un software molto vecchio che sovraccaricano il traffico di rete vengono penalizzati moltiplicando per 0,5

I clienti banditi ottengono immediatamente zero (cioè la loro velocità viene moltiplicata per 0).

Questi tassi di moltiplicazione si chiamano "modificatori". I clienti con un valore di modificazione appena superiore a uno saranno segnati col giallo nell'icona.

Ci rimangono solo i crediti. I crediti sono il prezzo da pagare per scaricare file da uno specifico utente. I crediti si scambiano tra i due clienti, non sono globali, quindi non si possono vedere anche se puoi sapere quanti crediti gli altri clienti hanno su di te (cioè quanti crediti gli devi). Siccome i crediti sono gestiti da chi invia, potrebbe capitare di inviare file a un cliente che non gestisce i crediti per cui tu non guadagni nessun credito su di lui, anche se lui guadagna crediti su di te dato che il tuo software gestisce i crediti.
I crediti sono memorizzati nel file clients.met

Il modificatore dei crediti usato dalla velocità è il minore di questi due:
(totale_inviato x 2) / totale_ricevuto oppure radiceq(totale_inviato+2)
I totali sono misurati in MB.

Se il risultato è minore di 1, viene impostato a 1 e se è maggiore di 10 è impostato a 10. In più, se il totale spedito è meno di 1MB, il modificatore è impostato a 1 e se il totale scaricato è zero il modificatore è impostato a 10.

== Che cosè uno slot? ==
Quando si invia un file, la banda di invio (che può variare in dipendenza dal limite di invio o del limite naturale di banda della connessione) sarà suddivisa in slot. Ogni slot è una quantità di Kbps che verrà assegnata ad ogni cliente che cerca di scaricare da te.

FAQ eD2k-Kademlia-it

2007-04-28T15:46:08Z

87.14.231.86:

<center>
<u><h4>F.A.Q. di eD2k-Kademlia</h4></u>

<h2>(Tradotto da ''[[User:SNeo|SNeo]]'')</h2>

[[FAQ_eD2k-Kademlia|English]] | [[FAQ_eD2k-Kademlia-es|Español]] | '''Italiano''' | [[FAQ_eD2k-Kademlia-de|Deutsche]] | [[FAQ_ed2k-fr|Français]] | [[FAQ_eD2k-Kademlia-nl|Nederlands]] | [[FAQ_eD2k-Kademlia-pl|Polish]] | [[FAQ_eD2k-Kademlia-ru|Russian]]
</center>

== Che cosè ED2K? ==

ED2K è un protocollo originariamente usato dal client P2P (Peer-to-Peer) eDonkey2000, da dove viene il nome. E' un protocollo basato sul sistema client-server, con l'abilità di scambiare fonti tra i client.

La rete ED2K si basa sui server non come reti quali Kazaa, significa che la prima cosa da fare quando avvii aMule è collegarsi a un server (manualmente o automaticamente).

Una volta connesso su un server, il client può ricercare, o localmente (al server in cui si è connesso) o globalmente (a tutti i server), qualsiasi file,e i server a cui è stata inviata la richiesta forniranno al client una lista con tutti i file che corrispondono ai criteri di ricerca.

Se un utente comincia un download, il client chiederà al server le fonti, che saranno fornite dal server sotto forma di indirizzi IP dei client che hanno comunicato al server di avere il file specificato.

== Che cosè Kademlia? ==

Traduzione e binari per amule-cvs presenti su [http://gift.altervista.org/index_it.php?section=50 questo sito]

== Kademlia è come Overnet? ==

== Che cosè un chunk? ==

Nel protocollo ED2K, per evitare di condividere file rovinati, ogni file viene diviso in varie parti chiamate chunks; in seguito ad ogni chunk viene dato un hash (leggi sotto cos'è un hash). Ogni chunk è di 9,28 MB, quindi un file di 15MB verrà diviso in due chunk (9,28 MB + 5,72 MB), un file di 315 KB sarà in un solo chunk e un file di 100 MB sarà diviso in 11 chunk (10x9,28 MB + 7,2 MB)

== Che cosè un hash? ==

Dividendo ogni file in chunk (vedi sopra) si evita il problema di scaricare un intero file rovinato, in quanto solo il chunk rovinato dovrà essere scaricato di nuovo. C'è bisogno però di un metodo per identificare i chunk rovinati. Questo viene fatto con gli hash MD4.

Un hash MD4 è un numero unico che viene dato ad ogni chunk ed è il risultato di una operazione matematica su ogni singolo bit del chunk. Questo significa che modificando un solo bit nel chunk si ottiene un hash totalmente diverso.
Il client deve verificare l'integrità di ogni parte del file mentre lo scarica.

Ogni chunk viene dotato di un hash, ma in più per avere un hash per il file, tutti gli hash dei chunk vengono concatenati uno dopo l'altro nell'ordine del file (hash_chunk1 + hash_chunk2 + hash_chunk3 + ...) e sulla stringa risultante viene calcolato l'hash.
In questo modo, ogni file nella rete ED2K ha un identificativo univoco. L'hash del file non viene calcolato sul file, ma sugli hash dei suoi pezzi.

In realtà si deve conoscere sia l'hash del file che la sua dimensione. Queste informazioni sono contenute negli URL di ED2K che si trovano in molti posti.

Ecco un esempio:

ed2k://|file|eMule0.42f-Sources.zip|2407949|CC8C3B104AD58678F69858F1F9B736E9|/

Le parti che interessano sono la quinta, "2407949", che è la dimensione del file in byte, e l'ultima,"CC8C3B104AD58678F69858F1F9B736E9", che è l'hash memorizzato come numero esadecimale di 32 caratteri.

Il nome del file è irrilevante nel processo di identificazione del file.

== Perchè dopo una ricerca, certi file che sono gli stessi appaiono come file differenti tra i risultati, sebbene abbiano lo stesso nome? ==

== Che cosè il Basso e Alto ID? ==

== Quali porte devo configurare in un firewall o in un router per avviare aMule?
==

Si deve distinguere tra connessioni in entrata e in uscita. Normalmente, tutte le porte di un router sono aperte per l'invio di dati (connessione in uscita).

Quindi in questo caso normale, devi solo configurare le porte per le connessioni in ingresso:

aMule funziona anche senza porte specificamente aperte, ma non otterresti un ID alto in questo caso. Come detto sopra, per ottenere un ID alto la porta 4662 TCP (oppure quella impostata nelle preferenze) deve essere in ascolto (cioè aperta nel firewall e inoltrata dal router).

A parte quella porta, per avere un uso ottimale di ED2K, altre due porte dovrebbero essere in ascolto: le porte UDP 4672 e 4665 (cioè portaTCP +3). Entrambe possono essere cambiate nelle preferenze a qualsiasi altro valore.

== Perché Kademlia dice ancora che è "firewalled"? ==

Se stai usando Kad e il tuo router fa il NAT (Traslazione Indirizzi di Rete) dovresti evitare che il router trasferisca la porta in uscita UDP numero 4672.
Questo dovrebbe funzionare se hai già un ID alto ma lo stato di Kad è "firewalled".

== Che cosa fa esattamente ogni porta? ==

Siccome quasi tutte le porte possono essere configurate a qualsiasi altro numero, faremo l'elenco delle impostazioni di default. La direzione del traffico è dal punto di vista del cliente (tu):

* 4661 TCP (uscita): porta su cui ascolta il server (definita dal server)
* 4662 TCP (uscita e ingresso): trasferimenti diretti tra clienti
* 4665 UDP (uscita e ingresso): usata per le ricerche globali sui server e per le interrogazioni globali sulle fonti. E' sempre uguale a PORTA_TCP+3
* 4672 UDP (uscita e ingresso): protocollo eMule esteso, punteggi di coda, File Reask Ping, Kad. Kad sarà 'firewalled' se il NAT (Network Address Translation) sposta questo numero di porta.
* 4711 TCP: porta WebServer in ascolto.
* 4712 TCP: porta connessione esterna. Usata per far comunicare aMule
con altre applicazioni come WebServer aMule o con aMuleCMD.

== C'è qualche limitazione nella rete ED2K? ==

Traduzione e binari per amule-cvs presenti su [http://gift.altervista.org/index_it.php?section=50 questo sito]

== Nella finestra ricerca, che filtro si usa per ogni tipo di file? ==

== Che cosè una fonte? ==

== Che cosè tutta quella roba sui crediti, velocità e punteggio? ==

Tutti e tre i concetti hanno a che fare col modo in cui la rete ED2K stabilisce le preferenze sulle code di invio.

Il punteggio è il valore più importante: il client con il punteggio più alto sarà il prossimo a cui verrà dato uno slot di invio. Il valore del punteggio è assegnato così: punteggio = velocità x tempo_di_attesa_secondi / 100.
Così per capire il calcolo dobbiamo vedere cos'è la velocità.

La velocità la possiamo pensare come una preferenza obbiettiva. Cioè la preferenza che viene data ad un client senza preoccuparsi di quanto tempo ha aspettato. Quando un client viene aggiunto alla coda di invio, gli viene data una velocità di 100. Questo valore si modifica in questo modo:

A seconda dei crediti, la velocità viene moltiplicata da 1 a 10. A seconda della priorità del file, viene moltiplicata da 0,2 a 1,8 (Release 1,8 Alto 0,9 Normale 0,7 Basso 0,6 Bassissimo 0,2).
Gli utenti con un software molto vecchio che sovraccaricano il traffico di rete vengono penalizzati moltiplicando per 0,5

I clienti banditi ottengono immediatamente zero (cioè la loro velocità viene moltiplicata per 0).

Questi tassi di moltiplicazione si chiamano "modificatori". I clienti con un valore di modificazione appena superiore a uno saranno segnati col giallo nell'icona.

Ci rimangono solo i crediti. I crediti sono il prezzo da pagare per scaricare file da uno specifico utente. I crediti si scambiano tra i due clienti, non sono globali, quindi non si possono vedere anche se puoi sapere quanti crediti gli altri clienti hanno su di te (cioè quanti crediti gli devi). Siccome i crediti sono gestiti da chi invia, potrebbe capitare di inviare file a un cliente che non gestisce i crediti per cui tu non guadagni nessun credito su di lui, anche se lui guadagna crediti su di te dato che il tuo software gestisce i crediti.
I crediti sono memorizzati nel file clients.met

Il modificatore dei crediti usato dalla velocità è il minore di questi due:
(totale_inviato x 2) / totale_ricevuto oppure radiceq(totale_inviato+2)
I totali sono misurati in MB.

Se il risultato è minore di 1, viene impostato a 1 e se è maggiore di 10 è impostato a 10. In più, se il totale spedito è meno di 1MB, il modificatore è impostato a 1 e se il totale scaricato è zero il modificatore è impostato a 10.

== Che cosè uno slot? ==
Quando si invia un file, la banda di invio (che può variare in dipendenza dal limite di invio o del limite naturale di banda della connessione) sarà suddivisa in slot. Ogni slot è una quantità di Kbps che verrà assegnata ad ogni cliente che cerca di scaricare da te.

FAQ eD2k-Kademlia-it

2007-04-28T13:40:12Z

87.14.231.86: