eMule v0.49b Peizheng.Cn Lite 1.0
2009-03-31
is a traditional mod coded with Visual Studio 2003 / VC 7.1
eMule v0.48a Peizheng.Cn Build 090304 is in the latest dlp v38 (http://bbs.peizheng.cn/viewthread.php?tid=45536&extra=&page=1)
but dlp makers are not that clever to click update check and go website links up to
http://www.peizheng.cn/emule/en/version_check.php?version=1162 no
http://www.peizheng.cn/emule/en/ no
http://www.peizheng.cn/emule/ good
http://bbs.peizheng.cn/viewthread.php?tid=48794&extra=page%3D1
eMule v0.49b Peizheng.Cn Lite 1.0 Build 090331 Core 200
欢迎使用培正电驴精简版。
版本号为：eMule v0.49b Peizheng.Cn Lite 1.0 Build 090331 Core 200
--如果不出什么大问题，这个版本就算做一个了结。不喜欢也可以不用
下载地址：Build 090331
http://www.peizheng.cn/emule/Lite10.rar
090324->090331 仅仅修正上传和下载不能设置速度问题。如果你不在乎这个小缺陷的话，可以不更新。
--以下针对旧版电驴说明--
注意，在您使用前，务必删除电驴已安装目录下面的Config文件夹。最好不要和旧版放在同一个目录
如果你不想重新计算共享文件的话，仅需要删除除了以下文件就可以了：
known2_64.met
known.met
server.met
shareddir.dat
config目录如果不删除，可能会导致你无法下载任何东西，或者是被列入黑名单
---针对旧版电驴说明结束---
上一版本下载地址：Build 090324
http://www.peizheng.cn/emule/Lite10.exe
Lite10.rar 1.89 MB
Lite10.exe 2.94 MB
source 4 new/old special mods:
http://downloads.sourceforge.net/project/emulextreme/DLP/AntiLeech38/antileech-sources.rar?use_mirror=voxelopen file antiLeech.cpp searching emule mods in google search mentioned in the mod names of dlp content in some versions higher.
How to make almost all banned mods in DLP working again if a connected client use any DLP enabled mod:
A prove of conceptFound in 2007
intro:
This what is banable in the DLP are a few old zero upload mods, probably coded to get detected and isolated from others outside there own comm to share. 85 % of all banned mods give upload. All the rest is not detectable in the way the dlp works. See latest Applejuice 0.49c and derivatives. You will realize you ban while using the dlp, sources which give you upload. In other words the dlp ban no more than soft leecher mods.
Argos have an advanced settings for ban control and there exist a customizable dlp like scheme the user can operate. Also giving Analyzer mods a try can not be wrong. Personal I think a mix between argos customizable and analyzer in one mod might be the best solution plus a manual ban button in all lists with ban time set to 24h in opcode.
No predefined modstring lists except comm mods but a suggestion list with instruction how to do proper ban lists, score reduced in steps till complete ban. User experience for example some Thunder versions on high speed networks give upload of your network speed (seen in Japan Thunder users witch giving an excellent upload speed) makes no sense to ban this versions same as by TuoTu, BitComet emule module need to be tested. QQDownload I never got a byte upload from one so I guess its really just a downloader in ed2k network or I need QQDownload too?
ACAT mods since I can remember are commented out in the dlp but all links to the source codes are fakes, same with CHN 7 mod, already by CHN 6 was no way to get the source code. No need to talk about eXcalibur - there is something wrong, the mod is encrypted with a custom build of commercial protector ASProtect (stronger as DVDFab shareware use to protect its compiled binary). The source code links you can try months long if you get a change to download it but you wont get it, the ed2k links to the source codes are fakes.
Playmule as alternative with Low2Low did no fake ed2k source code link up and got banned in the dlp just a months later till today's dlp version.
Korean eMule Mods almost have source codes. Who likes to download the mods will found the source codes on the same way but might be outdated versions.
Comm boost inside maybe, boost to the same or some modstrings, hidden switches? Or something like a certain friendlist boost to a dll port if exist in config folder...
However words like fairness have nothing todo with the dlp creation crap and there makers/supporters.
Ask for the source code of ACATStats.dll on official emule boards and refer to a Official Beta test topic from Xtreme Mod to get the answer include the source code of the dll in its original old and newer version incl. the port to this dll for compiling a supported emule.exe.
TCMod, R-Mod, Viper, Iberica, Hardstyle, The Killer Bean and many more French mods have source codes. Even eChanblardNext but here by eChanblard can figure out why, cause it don't share outside eChanblards comm and have Ads inside.
All of them are banned. Some older Spain mods and German mods too for example Smartmuli (reask svr4src doesn't even work anymore in smartmuli).
It can not be GPL/GNU. I have the feeling a hidden agenda is behind to sort out how they like the mods being banned and not.
Other Coders may have checked it earlier cause I can't find any new so called 'leecher' mods with source codes as it once was a few years back. Now VeryCD did the same and give no source codes any longer next to the compiled binaries.
How to make a banned mod working or how to unban a mod permanent from the DLP:
Advanced computer users can open hexeditor and search inside emule.exe the modname/build version number as written parts in antiLeech.cpp by your favorite mod, change one single letter/sign/number in the compiled binary by position send modname/string. Your mod works again proves all dlp's fail if ban on modname/build versions in a dll on the other client side. Have the other client no manual ban can he only look how his dlp is for nothing good. (suitable for Playmule modname to change as it have low2low; D10T main; TurkMule; FreeCD - all bitcomet emule dll plugins; The Killer Bean; Magic Angelyzer; Hardstyle;... change one or two byte only or try to replace the whole modname with in size matching other one! TUOTU - same same same - change modstr in emule.dll) - Here the list document which is a blacklist done by a few people to change the modstrings by this mods: antiLeech.cpp Don't use usernames such as mods.sub.cc (obsolete no mod exist with it) or others in the list - change them to default http://emule-project.net or anything else!!!!remark: it will not work on mods written in antiLeech.h //tested on spikes2 + shows echanblard comm is coded inside whether a fake or real eChanblard comm, so it shows the ban after changing the modstring to the protocol by 0x84 eChanblard comm. It need by this kind of mods with protocol addon/extension more than just the modstring/name to change inside a compiled emule.exe.
Other things to try use reshacker or pe explorer or any similar stuff and change in emule version info resources the entry lines to a valid other emule version (see on language files) valid emule versions 0.48/.49 [a/b/(c)] using official build numbers.
Ie:
1 VERSIONINFO
FILEVERSION 0,49,2,37
PRODUCTVERSION 0,49,2,37
FILEOS 0x4
FILETYPE 0x1
{
BLOCK "StringFileInfo"
{
BLOCK "040904B0"
{
VALUE "CompanyName", "http://www.emule-project.net"
VALUE "FileDescription", "eMule"
VALUE "FileVersion", "0.49.2 Unicode"
VALUE "InternalName", "emule.exe"
VALUE "LegalCopyright", "Copyright © 2002-2008 Merkur - Read license.txt for more infos."
VALUE "OriginalFilename", "emule.exe"
VALUE "ProductName", "eMule"
VALUE "ProductVersion", "0.49.2 Unicode"
}
}
BLOCK "VarFileInfo"
{
VALUE "Translation", 0x0409 0x04B0
}
}
Or replace this resource with another official mod or oem. Don't use invalid Build versions or dlp shows up on the other client side fake emule version - ban!
So far this 2 ways are the common used solutions if your favorite mod is banned, the modder retired without having a source code and no updated version exist, or u just want to have a mod build unblacklisted from the dlp with a unique modname.
If banned on emule version > see antiLeech.cpp to apply the right method to the banned mod. By most Korean Mods you need all two methods. 1st fill out anything as modname by the empty field inside [ ] in the binary. 2nd give a valid emule version change 0.95g or 0.47f etc.. to a valid 0.48 in version res.
Always test with a second client using the latest dlp if the mod by downloading a testfile don't show banned anymore.
Optional: to customize a own dlp [dll]. Just download the dlp source code comment out what u want or change, add what u like. No need much experience in c++ by compiling this piece of an dll file.
by bad [random]modstring scheme, the WHITE LIST in the dlp begins here:
//WiZaRd Bad Modstring Scheme
CString strMod = CString(modversion);
if( strMod.IsEmpty() ||
(strMod.Find(_T("CHN "))==0 && strMod.GetLength() > 8) ||
(strMod.Find(_T("Apollo"))==0) || //Apollo is a Portugal Mod
(strMod.Find(_T("sivka"))==0)
)
{
;//do nothing
to exclude mods (whitelist them) just add more lines with there modnames to the whitelist section after sivka"))==0)
for example:
(strMod.Find(_T("This Mod Name schould be excluded and White listed!"))==0)
(strMod.Find(_T("MyWhiteListedModname"))==0)
before
)
{
;//do nothing
Another quicker way is to hexedit the antileech dll. Replace by the founded banned modname inside the compiled dll the modname or part of it with FF. Changing just a single letter on the modname works, by banned modversion so it will be a number on the right place.
note : this is the meaning of an individual no more no less.
- British/English 
