Xtreme settings I



One queue per file (Multiqueue)

Sharing several files, only waiting time, upload priority and credits decide on the position of an requesting client on the waiting list. The result can be that certain files are uploaded quite often, while other files are often left out of consideration, although they've got the same priority. Now Multiqueue simulates one queue per file. Therefore the QR, which is transmitted to the requesting client, shows his position on the waiting list only for this certain file. So if 100 clients inquire one file, the QR is going to be situated somewhere between 1 and 100.
A special algorithm now tries to share the upload among every file equally. So the Xtreme loads a file with 10 waiting clients just as often as one with 1000 waiting clients. That's why you should be aware of the fact that 200 MB shared among 10 clients mean considerably more per client than 200 MB shared among 1000 clients. Therefore it could be advisable to set the upload priority of a rarely requseted file lower when using Multiqueue. Using auto-priority in connection with Multiqueue all files will be set to normal.


Open more slots if needed

This option helps to keep the total upload stable.
Normally the number of upload slots results from uploadlimit / slotspeed, rounded off. If a client is not able to take the desired slotspeed, the upload is first shared among the other slots. As a result the other slots can have a 25% higher slotspeed and so a new slot changes from Trickle to Fullspeed and maybe a new slot will be opened.
You are able to deactivate this algorithm with this option. But it is not recommended! Even if you could avoid that too many slots are opened, it is better to eliminate the cause itself of too many opened slots.


NAFC Full Control U/D Limits

This activates the Network-Adaptor-Feedback-Control, which calculates the uploadlimit according to the whole internet traffic of the network adaptor used by eMule. Using this option you will get a dynamic downloadlimit, if the upload is disturbed by other applications and eMule gets less than 11 kbs.
More information about NAFC in the chapter Xtreme-upload.


Amount based ratio 1:3

This option is only relevant if your uploadlimit comes to less than 11 kbs or it is reduced to that by NAFC. Otherwise this option will be ignored by eMule.
Normally you'll get a download limit if you set your upload limit to less than 11 kbs. If you, for example, set your uploadlimit to 9 kbs, a maximum download of 4 * 9= 36 kbs is possible. It's in the nature of eMule, that especially at the beginning you mostly upload and only later you get a bigger download. So a ratio of 1:4 is hardly possible. But using the amount based (session based) ratio it is different. Even at a small upload you won't get a limited download before a ratio of 1:3 is reached. Only when this ratio is reached the official download limit of 4*Uploadlimit sets in. This feature can be switched off, because some people like to limit their download.



The standard sendbuffer counts 8 192 bytes. This buffer is used by the operating system. If eMule sends a packet it is given into the buffer. With that for eMule it is sent. But only Windows decides at what time it really will be sent.
At a lower sendbuffer eMule is able to keep the upload under control and to keep it stable. At a higher one, eMule leaves more control to Windows, but in return often a bigger slotspeed can be reached.



If anyone really knows his MTU, which can be found out with certain tools, he can reduce his upload overhead a little bit. But be careful: a value adjusted too high would make the upload behaviour even worse. If you are unsure, just keep the adjusted standard value, it works excellent.


Double sendsize

Every sent packet needs an acknoledgement packet (ACK-packet) in return. The idea of a double sendsize is to send two packets (2 * MTU) at once, so that the receiving client only has to send one ACK-packet for both of them in return. The official eMule version always uses this method. But it also has got disadvantages, for example it could lead to an increased overhead on some systems and the time until the next packet can be sent could raise, too, which can result in a loss of performance especially at a small upload.
In the end everyone has to try out on his own, if this option is useful for your system or not.
Recommendation: switch it on at a uploadlimit of >= 50 or a slotspeed of >6.


Remove too frequently blocking sockets

works only if you enabled the option to open more sockets if needed. Now if your uploadslots grow three slots over the minimum-slots Xtreme looks if there is a slot uploading >3 minutes and has a high blocking-ratio. This slot will be removed. This can help to remove clients who stay in their own upload for ages with a poor data acception. But please use this option with caution!


Chunk selection method

Decides on the method how to choose the chunks to be downloaded. The traditional method is Maella, zz is the new one in 0.47c. The main difference is the following: the one by Maella tries to download a different chunk from every client, whereas zz tries to request the same chunk to finish it faster. Furthermore zz takes factors like the current download speed into account.



If this option is activated the ipfilter.dat will be automatically kept on the latest state. This is how this feature works:
- after you enabled the option: by the next restart of the client the ipfilter will be downloaded and the date of this version will be stored
- on the next restart of your client the ipfilter will be checked in the same interval as versions-check (you can set it at general settings). If it is time to do a check Xtreme will connect to the URL you specified at security-settings. After the connection is established Xtreme checks if the version on server is newer than your installed one. If so, your ipfilter will be updated.


Show blocking-ratio

If this option is activated, the blocking-ratio for every client will be shown in the upload window. You'll find more information under Features/Upload.


Retry failed TCP connection attempts

It happens quite often that a client does not react when trying to connect with him. The cause for that can be that this client or his router is overloaded for the moment. With this option the failed connection attempt will be repeated after one minute.
Attention: when using this option more half opened connections are needed!


Process Priority

Decide which priority eMule is supposed to have towards other applications. Assuming that eMule normally does not take up much capacity, but on the other hand it is a real-time application, it is advisable to set it to "above normal" or "high".




Xtreme settings II




The first line shows the current version of the installed antiLeech.dll (DLP). If no antiLeech.dll could be found, a mistake is displayed and the leecher protection is deactivated.
By clicking on "Reload" the antiLeech.dll will be read in anew. This is necessary, if the antiLeech.dll has been updated (see installation).
- Enable Anti-Leecher protection:
by deactivating this option the whole Anti-Leecher protection can be switched off with one click
- Detect wrong Hello-Tag:
some community-mods change the socalled Hello-Tag to identify eachother with the help of this change. Activate this option and this method will be detected.
- Detect bad Tags:
this method (also called SNAFU) detects typical Opcodes sent by Leechermods
- Detect Ghost-Mods:
Anti-Ghost-Mod bans clients, who use typical mod-functions, like e.g. webcache, but do not send a modstring. Assuming that those client possibly got a good reason for not showing their modstring, they are banned with this option.
- Detect Leecher by Modstring:
with this Leechers will be detected by their sent Modstring
- Detect Leecher by UserName:
some Leechers use very typical usernames or at least typical symbols and signs in their username, which will be detected, too.
- Detect Nick-/Modthiefs:
Activate this option and clients who pretend to be the Xtreme-Mod, but really aren't, will be banned. Also clients who steal your nickname are detected and banned.
- Detect Spammers:
clients who are aiming to send spam news to make publicity are banned.
- Detect XS-Explioter:
Activate this and clients that do not answer to source-exchange requests are detected. Those clients won't get any answers to their XS-requests, too.
- Detect emcrypt:
emcrypt is a commercial eMule-mod which is highly infected with spyware and damages the network. Activate this option to detect these clients and reduce their score. In their nickname a little remark will be transmitted to show that they are infected with spyware.


- Community Mods / Nick-/Modthiefs
here you can choose wether detected Community-mods or Nick-/Modthiefs shall be banned or get a reduced score.


Show active downloads bold

If this is activated, recently transmitted files are illustrated bold at the download window.


Use narrow font

If this option is activated eMule will use a more narrow fond at the transfer window. This can improve the overall view if the resolution of your monitor is too low.


Show additional graph-lines

If this is activated, additional overhead lines are shown at the statistics.


Show Funny nick

The major part of all eMule users uses the nick "http://www.emule-project.net". To distinguish these users, the funnynick feature replaces the actual nick by a nick that is calculated through the userhash.


other settings:


more settings at statistics:

In addition to the general settings, the Xtreme offers the possibility of zooming the graphs. This can be helpful if you want to inspect a smaller period of time more detailed.
Furthermore you are able to show the graphs accurate or smooth. In the official eMule version the graphs are pretty smoothed out, but at the Xtreme the standard setting is "accurate".


more settings at files:

Apart from the standard features to save canceled files (canceled.met) and already downloaded files (known.met), the Xtreme offers the option to save the AICH-hashes (known2.met), too. The official eMule saves those AICH-haches generally. The bad thing is, that very soon the known2.met increases. But actually you won't need the AICH-hashes of once downloaded files anymore. If the option to keep AICH-hashes is deactivated, eMule will check which files are still shared when next starting the Xtreme. All AICH-hashes of no longer shared files will be deleted. If you want to share a once shared file renewed, this file is hashed again to reconstruct the AICH-hash.
Tip: when deleting the useless AICH-hashes you do not lose the statistics about once downloaded files, because these values are saved at the known.met.
Recommended setting: deactivate "keep AICH-hashes"


more settings at extended settings:

There you'll find the UPNP (Universal Plug and Play) support at the bottom. If this option is activated, it will automatically try to open and close the ports at the router. Of course Windows and your router have to support this. The second option makes it possible to assign eMule other, at random chosen ports, if the requested ports at the router are already in use.



Elbenwald.de - Lebe Deine Fantasy!