[eMule-Web] - eMule 0.30c Xtreme 2.2 [21.01.2005]

Xtreme 2.2
---------------------------------
based on 0.30c + Maella 4.1.08

Download
-----------
Binaries:
ed2k://|file|emuleXtreme2.2.rar|2029...FAD50A27AD8E|/
Sources:
ed2k://|file|emuleXtreme2.2-sources....EAE905907543|/

Mirror:
----------
eMule 0.30c Xtreme 2.2 Binary
eMule 0.30c Xtreme 2.2 Sources
eMule-web.de Mirror (http) Bin & Sources

changelog
------------------
Xtreme 2.2
- new Feature: clients, you try to upload, but connection fail, get a second change. They are put back on uploadqueue, marked with ~~~ and get an uploadslot at their next connection (same handling like LowID)
- new Feature: don't upload on startup without serverconnection. don't accept new upload on lost of internetconnection
- new Feature: advanced Xtreme-Downloadmanager: find best sources
this feature includes 3 features:
- an intelligent dropping wich also drops HQ sources, depending on QR, remote-credits, and avg QR
- dropped clients may not reentering the downloadqueue for 50 minutes
- intelligent swapping, which looks on filepriority and sourcecount to balance the sources between the files, download with highest priority is always prefered
further more, you can now drop and swap manually how much you want, you don't get banned, and you don't get back the dropped sources

- changed: Non SI-Clients get only 80% score
- changed: removed remaining time from transferewindow, now you can see the QR-average
- changed: some timeout settings
- changed: "aksfordownload" - priorities
- changed: method for passive source finding (listensocket, CheckAndAddKnownSource), should take now 2/3 less CPU
- changed: source reask time increased (due to 0.44)
- changed: new method to detect the right NAFC-adapter, works only after receiving a HighID from server, otherwise old method is used

- bugfix: an official protocol bug which can cause failed uploadsessions (also a patch on downloading-side for better compatibility with ed2k-protocol
- bugfix: an official bug wich can cause LowID clients to get a second uploadsession after it finished the first one, althought it hasn't enough score

Xtreme 2.1
--------------------------------
based on 0.30c + Maella 4.1.08

Download
-----------
Binaries:
ed2k://|file|Xtreme2.1.rar|2027121|9...854FE9C4D6D9|/
Sources:
ed2k://|file|Xtreme2.1-sources.rar|3...8BD4FE84CEE8|/

Mirror:
----------
eMule 0.30c Xtreme v2.1 Final Binary
eMule 0.30c Xtreme v2.1 Final Sources

eMule-Web - eMule 0.30c Xtreme 2.1-bin.rar
eMule-Web - eMule 0.30c Xtreme 2.1-src.rar

changelog
------------------
Xtreme 2.1 final
- Bugfix: removed a code-part which could cause a crash
- small Fix: a file with only one source, could be painted in red
- small Fix: statistic shows now a download-session-end called "sto" which means "socket time out"

Xtreme 2.0 final
--------------------------------------------

based on 0.30c + Maella 4.1.08

Download
-----------
Binaries:
ed2k://|file|Xtreme2.0final.rar|2027963|6ADF28F7770C7CCAD F6407D54C928F01|/
Sources:
ed2k://|file|Xtreme2.0final-sources.rar|3373476|272FC9614F10B52411C4EB196608DF DB|/

Mirror: (thx skneo)
----------
eMule 0.30c Xtreme v2.0 Final Binary
eMule 0.30c Xtreme v2.0 Final Sources

changelog
------------------
Xtreme 2.0 final
- Bugfix: Crash(freeze) if wrong Client(Leecher) was removed
- New Connection Conrol:
+ 1 minute pause between 2 connection attemps (client state unknown during this time)
+ slow down Connection per 5 secondes, if emule is at the connection limit
+ individual Priority for each client, when you have too many connections. for example, a client with low QR has higher priority, also a client where last asked time is long ago

- chunk selection Patch: better chunk selection for rare files
- removed jiggle
- IP-Filter-Bugfix: now clients are realy filtered
- IP-Filter-temporary-remove-process: temporary Filtered IPs are removed after 12 hours
- Filter 0 Uploaders: after a client caused 3 following failed downloadsessions, it's IP get's filtered. No more upload/download/connection
- mergeKnown (Slugfiller)

Xtreme 2.0 beta 4
--------------------------------------------

based on 0.30c + Maella 4.1.08

Download
-----------
Binaries:
ed2k://|file|Xtreme2.0beta4.rar|1585339|8784766D4E4B669CC 5001306E326DEC7|/
Sources:
ed2k://|file|Xtreme2.0beta4-sources.rar|3431339|2181FB23947E546AB42BE5D6F391A8 1F|/

Mirrors: (thx skneo, platic3, renegade)
----------
http://www.acab-necro.de/emule/index.php
http://www.*****.de/

changelog
------------------
Xtreme 2.0 beta 4
- Bugfix: fix the crashing/freezing problem (thx to Pichuei for finding it)
- UnZip Fix (Pawcio)
- some other possible crashfixes

- improved upload-handling:
- only clients get an uploadslot, which were seen the last 30 minutes.
- increased the MAX_PURGEQUEUETIME from 60 to 80 minutes

Xtreme 2.0 beta 3
--------------------------------------------

based on 0.30c + Maella 4.1.08

Download
-----------
Binaries:
ed2k://|file|Xtreme2.0beta3.rar|1584400|6D56B40DAE1FD3539 EC33E7CD7CDEB22|/
Sources:
ed2k://|file|Xtreme2.0beta3-sources.rar|3430464|BE9368A140AE0E5361C1813277FEEE BA|/

Mirrors:
----------
http://www.acab-necro.de/emule/index.php
http://emule-resource.de.vu
http://www.********.de/

changelog
------------------
Xtreme 2.0 beta 3
new features:
- On the fly optimizer (ewombat)
modified version (the original md4cpy works faster)
- amount based 1:3 ratio (like zz-ratio) if upload < 10 kbs

changes:
- Bugfix: problem with files >2 GB (ikabot)
- Bugfix: Reset works now for Leechermessages
- Bugfix: send only valid sources
- Fix a memory leak (rayita)
- reincluded the crashrpt + better error handling
- added friendhandling to knownclients
- some codeimprovements by Maella
- fixed some other small bugs

Xtreme 2.0 beta 2
--------------------------------------------

based on 0.30c + Maella 4.1.08

Download
-----------
Binaries:
ed2k://|file|Xtreme2.0beta2.rar|1306646|7A343807D2DD1774E 53AF8166040D00D|/
Sources:
ed2k://|file|Xtreme2.0beta2-surces.rar|3713389|58FE1528F1C51CA3C9FA974C8D2ABD0 6|/

Mirrors: (thx all supporters)
---------
http://www.acab-necro.de/emule/index.php
http://www.emule-resource.de.vu

changelog
------------------
- upgrade Maella Code to 0.30c
- some small GUI fixes
- improvement: See on Uploadqueue should now work properly
- [BugFix] Complete Source [morph/SiRoB]
- MoNKi: -FIX: ini.GetFloat needs Language-

Features:
-------------------

- QueueOverflow with Minimumcontingent
For each file you share, a minimum amount of clients are always allowed to get on your uploadqueue.
The minimumcontingent per file is calculated: queuesize/sharedfiles/2
e.g.: queusize=2000, sharedfiles=20 --> minimumcontingent per file= 50
This means, if uploadqueue is full and a client is asking for a file with less than 50 clients are on uploadqueue, the client is allowed to get on queue.

- amount based 1:3 Ratio if upload <10 kbs
This feature is simular to zz-ratio. If your upload is set to less than 10 kbs, you don't have a downloadlimit until reaching a ratio of 1:3. After reaching this ratio, your limits are like at the official emule.
If your upload is set >=10kbs, you don't have any limitation.

- See OnUploadqueue
At the shared filelist panel you see now how many clients are on your uploadqueue for each file.
(Modder: this feature is needed for the new Queueoverflow)

- improved friendhandling
From uploadqueue-list, downloadqueue-list and upload-list you can now Add a friend, remove a friend, open friendslot.
(+ fix: the GUI is updated mmediately, impossible functions are grey)

- new Leecher-Tab
If Verbose is enabled, you see all Leecher and Ban-Messages on an extra Tab
(+ added new leechersignatures, + some small code improvements)

- Xman improved Credit System
This feature is an enhancement of the existing credit system. It rewards clients which gives you a high download. This clients gets a bonus factor.
On the other side, clients you upload much data and the don't give something back to you will get a penalty for the current emule session.

formula for positiv bonus:
bonus=(download-upload)/10485760 - (1.0f/(download/10485760)

The max scoreratio is 10. (like official)

Example:
official version: (with ~ 1 Chunk difference)
download 10MB, Upload 1MB -->scoreratio for this client: 3,46
download 20MB, Upload 11MB -->scoreratio for this client: 3,63
download 30MB, Upload 21MB -->scoreratio for this client: 2,86
download 90MB, Upload 81MB -->scoreratio for this client: 2,22

download 50MB, upload 20MB -->scoreratio for this client: 5,0
download 90MB, upload 50MB -->scoreratio for this client: 3,6
download 120MB, upload 80MB -->scoreratio for this client: 3,0

Xman improved creditsystem: (with ~ 1 Chunk difference)
download 10MB, Upload 1MB -->scoreratio for this client: 3,46 + bonus:0
download 20MB, Upload 11MB -->scoreratio for this client: 3,63 + bonus:0
download 30MB, Upload 21MB -->scoreratio for this client: 2,86 + bonus:0,2
download 90MB, Upload 81MB -->scoreratio for this client: 2,22 + bonus:0,7

download 50MB, upload 20MB -->scoreratio for this client: 5,0 + bonus:2,2
download 90MB, upload 50MB -->scoreratio for this client: 3,6 + bonus:3,7
download 120MB, upload 80MB -->scoreratio for this client: 3,0 + bonus:3,8

a client can get a negativ bonus of 0,1 if you gave him 1 chunk(9,28MB) more this session and also at complete comparsion of download/upload without geting something back
a client can get a negativ bonus of 0,2 if you gave him more than 2 chunk(9,28MB) this session and also at complete comparsion of download/upload without geting something back
(please see the code, I can't explain this very good)

- Xman Full Chunk
This is a compromise of Tarod-Full-Chunk and VQB-Full-Chunk.
Tarod stops the upload when a client request a diffrent chunk. VQB always transfers 9,29MB.
With Tarod it can happen that a user only gets a few Bytes. With VQB your cycling time is to big.
Xman Full Chunk always gives at least 2 MB without looking at the chunk boarder. After 2 MB the upload stops if a new chunks is requestet. The upload also stops after giving ~9,28 MB (~one Chunk).

- Xman Upload reduction
Many people know the problem: if the download is to high they have problems with the upload. This is because every downloaded packet needs an acknowledgement. This acknowledgements make your upload unstable. Because of this many people lower their upload from the beginning. (giving only 10 instead of 14 kbs).
Xman upload reduction looks at the download and reduce the upload softly und slowly when your download increase. If your download decrase the upload increase.
If this feature is enabled you can set a much higher uploadrate.

Recomment Setting: Apply limits to overhead + upload reduction

upload reduction don't work with NAFC full control!
min upload with this feature is always 10kbs!

- CIDE compatible userhash (enkeyDev/Xman)
If you don't have a userhash (prefences.dat) a new one, full CIDE and RSA-SI compatible userhash will be generated. So you can be identified at both systems.

- new Icons
- Xman give at least 1,5 MB (without Full Chunk upload)
- show correct version icons (sharazza, edonkey...) (seen at theblackhand)
- show own credits (VQB)
- show the client with credits at downloadqueue
- manuel droping of sources
- hide overshares (slugfiller)
- Show Requested Files (sivka)
- Anti Leecher-Protection (xrmb/IceCream/Athlazan)

- Patch: faster updating of uploadqueuelist (Xman)
- patch: only send valid sources (on SourceExchange) (Xman)
official client send all sources from downloadque. now only sources are sent, which are asked bevor.
- Xman SharedFiles Sortfix
clients with very low priority are not longer kumping around

+ all features of Maella:

1. [FAF] -Allow Bandwidth Settings in <1KB Incremements-

2. [FAF] -One-queue-per-file- (idea bloodymad)

3. [patch] -Enhanced Chunk Selection- (based on jicxicmic)

4. [patch] -Save/load Sources- enkeyDEV(Ottavio84)

5. [patch] -Enable/Disable source exchange in preference- (Tarod)

6. [patch] -Defeat 0-filled Part Senders- (Idea of xrmb)

7. [patch] -Support for tag ET_MOD_VERSION 0x55 II- (Idea of Statik)

8. [patch] -AntiCrash/AntiFake handling- (Vorlost/Mortillo)

9. [patch] -Accurate measure of bandwidth: eDonkey data + control, network adapter-

10 [patch] -MTU Configuration-

11. [patch] -Minimum Upload Slot-

12. [patch] -Small latency-

13. [patch] -New bandwidth control-

Attention: the upload limit cannot be set to 'unlimited' (with 0) within the preferences.

14. [patch] -Overhead compensation (pseudo full rate control)-

15. [patch] -General Code Improvement/Avoid Heap/Code Fix-

16. [patch] -Extended clean-up II-

17. [fix] -New Timer Management-
The management of the main timer was rewritten. With this refactory, a better superversion of the program's exceptions is possible. The application should not close any more by itself without generating a dump file. This modification should help for the debugging.

18. Divers

[patch] -Fake Search- (sivka)
Check if a file is not listed as a fake.

[patch] -Upload Stop Reason-
[patch] -Download Stop Reason-
Add some information about end of session in the statistic tree (verbose must be activated).

[patch] -Activate Smart Low ID check-
Try to reconnect 3 times to a different server when a LowID is received.

[patch] -Auto-update of Ipfilter.dat- (milobac)
Small facility to download manualy a new version of the IPfilter.dat

[patch] -Close Backdoor-
A client (Hybrid + MLDonkey) might ask a file to gain but download another. When detected, the client will be
put back in the waiting list with a penality.

[patch] -Allow Hybrid to download from eMule-
The Hybrid (v49.4/v49.5) won't be rejected when it asks for block larger than the default allowed size.

[patch] -Spread Request- (idea SlugFiller)
Try to spread the TCP session over the time to avoid some pick in the level of simultaneous connections.
It adds a jitter of +-2 minutes to the default timming of request.

[patch] -Reask sources after IP change- (idea Xman)
Reinitialize all sources after a change of the global IP (e.g. modem disconnected) or a change of lowID to lowID.

[Fix] -Unnecessary Protocol Overload-
Reduce by up to 50% the number of TCP creations to refresh the eDonkey download session. The ping signal is now correctly used and the client takes advantage of existing TCP sessions to perform all refresh operations.

Explanation of the icons:
It's very easy because the icons are self-explanatory.
Yellow Icons --> client has credits (at downloadqueue: you have credits at this client)
blue Icons --> clients without credits