[Some Support]

I have uploaded the current source code for eMule into the project repository on SF. The default branch contains the last stable release, the dev branch all changes since then (which are yet unpublished). I don't think I have to mention that stuff in there will be untested and possibly buggy - but should compile.

The biggest change for 0.50b is currently a rework of the upload / disk IO mechanics to switch to asynchronous operations , allowing to OS to optimize the disk access better and upload much faster on big lines. Otherwise there are some fixes and optimizations.

In general you should not reuse protocol related changes for your mods before they are released, because they might still change and break old versions of the dev branch (there are no major protocol changes currently though). Otherwise just keep in mind that it's untested.

Obviously I don't recommend to use this branch for end users, but since some might want to try anyway I will provide a binary for the current dev code now and then. Here. (current build: 16)

This post has been edited by Some Support: 25 April 2015 - 02:57 PM

[fox88]

Thanks a lot.

[SS1900]

thx

[]Axl[]

GREAT NEWS!!! Thanks!!!

[tHeWiZaRdOfDoS]

Great idea, SS - thx!

[Tuxman]

Wondering why you changed your policy of not releasing "in-development" code. Anyway, already dug through it. Seems nice!

[Some Support]

Tuxman, on 07 August 2013 - 01:31 PM, said:

Wondering why you changed your policy of not releasing "in-development" code.

Because of the large time gaps between releases. When eMule version were released every few months, there wasn't a huge drawback in not publishing the code till then, but now that it is rather years it seems to make more sense to allow viewing and merging it before.

[Tuxman]

I'd assume the opposite. I wish I had had such a huge time gap to merge a mod when 0.47x was current.

But I like the new direction.

[loverboy]

Great news
Thanks a lot

[hooligan3000]

http://www.xup.in/dl,24436511/eMule_0-50b-5_20130808-023114.dmp/
dmp file

[Enig123]

I've got an error message in the log with the new code:

8/7/2013 10:29:39 PM: WSASend() Error: 10022, An invalid argument was supplied.

which seems to originate from the new introduced routine CEMSocket::SendOv().

[fox88]

Server connection behaves oddly in 0.50b.

No configuration changes - only .exe file is replaced. 9 servers.
Loaded eMule and pressed Connect icon.

v0.50a

09/08/2013 23:05:40: Connecting
09/08/2013 23:05:40: Connecting to eMule Security No2 (91.200.42.47:3883 - using Protocol Obfuscation) ...
09/08/2013 23:05:40: Read 200 contacts from file.
09/08/2013 23:05:40: Connected to eMule Security No2 (91.200.42.47:3883), sending login request
09/08/2013 23:05:41: Obfuscated connection established on: eMule Security No2 (91.200.42.47:3883)
09/08/2013 23:05:41: New client ID is 2435001390

v0.50b

09/08/2013 23:21:55: Connecting
09/08/2013 23:21:55: Connecting to PEERATES.NET (88.191.221.121:7111 - using Protocol Obfuscation) ...
09/08/2013 23:21:55: Read 200 contacts from file.
09/08/2013 23:21:55: Connected to PEERATES.NET (88.191.221.121:7111), sending login request
09/08/2013 23:21:55: PEERATES.NET (88.191.221.121:7111) appears to be full
09/08/2013 23:21:55: Connecting to Aigame (117.18.121.3:5000 - using Protocol Obfuscation) ...
09/08/2013 23:21:55: Connected to Aigame (117.18.121.3:5000), sending login request
09/08/2013 23:21:56: Aigame (117.18.121.3:5000) appears to be full
09/08/2013 23:21:56: Connecting to Usenet-Deals.com No1 (91.200.42.119:9939 - using Protocol Obfuscation) ...
09/08/2013 23:21:56: Connected to Usenet-Deals.com No1 (91.200.42.119:9939), sending login request
09/08/2013 23:21:56: Usenet-Deals.com No1 (91.200.42.119:9939) appears to be full
09/08/2013 23:21:56: Connecting to TV Underground No1 (176.103.48.36:4184 - using Protocol Obfuscation) ...
09/08/2013 23:21:56: Connected to TV Underground No1 (176.103.48.36:4184), sending login request
09/08/2013 23:21:57: TV Underground No1 (176.103.48.36:4184) appears to be full
09/08/2013 23:21:57: Connecting to eMule Security No2 (91.200.42.47:3883 - using Protocol Obfuscation) ...
09/08/2013 23:21:57: Connected to eMule Security No2 (91.200.42.47:3883), sending login request
09/08/2013 23:21:57: eMule Security No2 (91.200.42.47:3883) appears to be full
09/08/2013 23:21:57: Connecting to eMule Security No1 (91.200.42.46:1176 - using Protocol Obfuscation) ...
09/08/2013 23:21:57: Connected to eMule Security No1 (91.200.42.46:1176), sending login request
09/08/2013 23:21:57: eMule Security No1 (91.200.42.46:1176) appears to be full
09/08/2013 23:21:57: Connecting to PEERATES.NET (88.190.202.44:7111 - using Protocol Obfuscation) ...
09/08/2013 23:21:57: Connected to PEERATES.NET (88.190.202.44:7111), sending login request
09/08/2013 23:21:57: PEERATES.NET (88.190.202.44:7111) appears to be full
09/08/2013 23:21:57: Connecting to Usenet-Deals.com No2 (77.120.115.66:5041 - using Protocol Obfuscation) ...
09/08/2013 23:21:57: Connected to Usenet-Deals.com No2 (77.120.115.66:5041), sending login request
09/08/2013 23:21:58: Usenet-Deals.com No2 (77.120.115.66:5041) appears to be full
09/08/2013 23:21:58: Connecting to PeerBooter (88.191.228.66:7111 - using Protocol Obfuscation) ...
09/08/2013 23:21:58: Connected to PeerBooter (88.191.228.66:7111), sending login request
09/08/2013 23:21:58: PeerBooter (88.191.228.66:7111) appears to be full
09/08/2013 23:21:58: Connecting to PEERATES.NET (88.191.221.121:7111)...
09/08/2013 23:21:58: Connected to PEERATES.NET (88.191.221.121:7111), sending login request
09/08/2013 23:21:59: Connection established on: PEERATES.NET (88.191.221.121:7111)

Both times I get high ID.

PS. Some Support, will you open beta forum or we will report bugs and problems here?

[Riso64Bit]

fox88, on 09 August 2013 - 09:27 PM, said:

Server connection behaves oddly in 0.50b.

No configuration changes - only .exe file is replaced. 9 servers.
Loaded eMule and pressed Connect icon.

v0.50a

09/08/2013 23:05:40: Connecting
09/08/2013 23:05:40: Connecting to eMule Security No2 (91.200.42.47:3883 - using Protocol Obfuscation) ...
09/08/2013 23:05:40: Read 200 contacts from file.
09/08/2013 23:05:40: Connected to eMule Security No2 (91.200.42.47:3883), sending login request
09/08/2013 23:05:41: Obfuscated connection established on: eMule Security No2 (91.200.42.47:3883)
09/08/2013 23:05:41: New client ID is 2435001390

v0.50b

09/08/2013 23:21:55: Connecting
09/08/2013 23:21:55: Connecting to PEERATES.NET (88.191.221.121:7111 - using Protocol Obfuscation) ...
09/08/2013 23:21:55: Read 200 contacts from file.
09/08/2013 23:21:55: Connected to PEERATES.NET (88.191.221.121:7111), sending login request
09/08/2013 23:21:55: PEERATES.NET (88.191.221.121:7111) appears to be full
09/08/2013 23:21:55: Connecting to Aigame (117.18.121.3:5000 - using Protocol Obfuscation) ...
09/08/2013 23:21:55: Connected to Aigame (117.18.121.3:5000), sending login request
09/08/2013 23:21:56: Aigame (117.18.121.3:5000) appears to be full
09/08/2013 23:21:56: Connecting to Usenet-Deals.com No1 (91.200.42.119:9939 - using Protocol Obfuscation) ...
09/08/2013 23:21:56: Connected to Usenet-Deals.com No1 (91.200.42.119:9939), sending login request
09/08/2013 23:21:56: Usenet-Deals.com No1 (91.200.42.119:9939) appears to be full
09/08/2013 23:21:56: Connecting to TV Underground No1 (176.103.48.36:4184 - using Protocol Obfuscation) ...
09/08/2013 23:21:56: Connected to TV Underground No1 (176.103.48.36:4184), sending login request
09/08/2013 23:21:57: TV Underground No1 (176.103.48.36:4184) appears to be full
09/08/2013 23:21:57: Connecting to eMule Security No2 (91.200.42.47:3883 - using Protocol Obfuscation) ...
09/08/2013 23:21:57: Connected to eMule Security No2 (91.200.42.47:3883), sending login request
09/08/2013 23:21:57: eMule Security No2 (91.200.42.47:3883) appears to be full
09/08/2013 23:21:57: Connecting to eMule Security No1 (91.200.42.46:1176 - using Protocol Obfuscation) ...
09/08/2013 23:21:57: Connected to eMule Security No1 (91.200.42.46:1176), sending login request
09/08/2013 23:21:57: eMule Security No1 (91.200.42.46:1176) appears to be full
09/08/2013 23:21:57: Connecting to PEERATES.NET (88.190.202.44:7111 - using Protocol Obfuscation) ...
09/08/2013 23:21:57: Connected to PEERATES.NET (88.190.202.44:7111), sending login request
09/08/2013 23:21:57: PEERATES.NET (88.190.202.44:7111) appears to be full
09/08/2013 23:21:57: Connecting to Usenet-Deals.com No2 (77.120.115.66:5041 - using Protocol Obfuscation) ...
09/08/2013 23:21:57: Connected to Usenet-Deals.com No2 (77.120.115.66:5041), sending login request
09/08/2013 23:21:58: Usenet-Deals.com No2 (77.120.115.66:5041) appears to be full
09/08/2013 23:21:58: Connecting to PeerBooter (88.191.228.66:7111 - using Protocol Obfuscation) ...
09/08/2013 23:21:58: Connected to PeerBooter (88.191.228.66:7111), sending login request
09/08/2013 23:21:58: PeerBooter (88.191.228.66:7111) appears to be full
09/08/2013 23:21:58: Connecting to PEERATES.NET (88.191.221.121:7111)...
09/08/2013 23:21:58: Connected to PEERATES.NET (88.191.221.121:7111), sending login request
09/08/2013 23:21:59: Connection established on: PEERATES.NET (88.191.221.121:7111)

Both times I get high ID.

PS. Some Support, will you open beta forum or we will report bugs and problems here?

I have the same identical problem & i can regenerate it:
(under XP sp3)
1 start 0.50b & connect to KAD & server
2 CLOSE (exit) emule WITHOUT disconnect Server & kad connectivity
3 try to reopen a new instance of emule & you obtein this log

[Riso64Bit]

I have the same problem whit older version.
why if you enable the webserver & click "Apply" emule generate an error: "emule can't load templates: ...." ?
Emule try to open "emule.tmpl" under the same folder of eMule.exe but it's not present & "webserver" folder is empty.
can you fix this?

[Some Support]

fox88, on 09 August 2013 - 08:27 PM, said:

PS. Some Support, will you open beta forum or we will report bugs and problems here?

No, it's not a Beta yet. This also means I will not respond/fix everything which seems wrong, as some thing are just untested yet (although I do like to hear about it, so feel free to use this thread).

About the server connection, nothing really changed in this part except the socket handling. I'll check it out.

[xilolee]

I have the same server issue reported by fox88 and riso64bit...

(CryptTCPPaddingLength=234)
With obfuscation disabled, it connects almost immediately.
With obfuscation partially enabled, it shows that behavior, but it connects without obfuscation.
With obfuscation fully enabled, it doesn't connect at all.

I don't know if it's normal, but I can't change the language from English to Italian: it says it is not installed, asking me to download from the website.
I respond yes and it says "Failed to download and install selected language library from hddp://langmirror3.emule-project.org/lang/05015/it_IT.dll!".
IMO, it is strange for sure, given that no string has been changed.

The verbose log shows yet those boring messages "Read IdentifierDesc: 7 - Write IdentifierDesc: 7"

This post has been edited by xilolee: 11 August 2013 - 09:18 AM

[Zangune]

fox88, on 09 August 2013 - 09:27 PM, said:

Server connection behaves oddly in 0.50b.

The same here. It seems too fast to switch to another server to me.

Riso64Bit, on 09 August 2013 - 09:44 PM, said:

Emule try to open "emule.tmpl" under the same folder of eMule.exe but it's not present & "webserver" folder is empty.

eMule.tmpl is in config folder, in webaserver folder there are .gif files and an .ico file.

xilolee, on 10 August 2013 - 01:44 AM, said:

I respond yes and it says "Failed to download and install selected language library from hddp://langmirror3.emule-project.org/lang/05015/it_IT.dll!".

If you click here langmirror3.emule-project.org/lang/05015 you can read

Quote

The requested URL /lang/05015 was not found on this server.

Because nobody translated lang files for eMule 0.50.1.5 also known as eMule 0.50b BETA 3.
In langmirror3 there is not /lang folder.

Quote

ReadCompletetionRoutine: Didn't read requested datacount - wanted: 86448, read: 0
IO Error: GetOverlappedResult: L'evento di I/O sovrapposto non è in uno stato segnalato.

Translation note: second error should be translated as "Overlapped I/O event object not in signaled state".

Both errors causes this

Quote

10/08/2013 9.24.35: Removing client from upload list: IO/Other Error while creating datapacket (see earlier log entries) Client: <omissis> 'http://emule-project.net' (eMule v0.50a,None/Uploading/None) Transferred: 0 secs SessionUp: 0 Bytes QueueSessionPayload: 0 Bytes In buffer: 84.42 KB Req blocks: 0

and 0 upload.

[fox88]

Zangune, on 10 August 2013 - 10:52 AM, said:

Riso64Bit, on 09 August 2013 - 09:44 PM, said:

Emule try to open "emule.tmpl" under the same folder of eMule.exe but it's not present

eMule.tmpl is in config folder

No.
Path to template file is defined in preferences.ini

[fox88]

Some Support, on 09 August 2013 - 11:43 PM, said:

No, it's not a Beta yet.

The log says:

10/08/2013 03:06:43: eMule Version 0.50b BETA3 ready

You could implement ALPHA string for that case.


CPU usage question.

Started eMule and connected to both networks. There are no files to download and no new files to hash, except beta-specific one, of course.
Publishing in KAD should not use much, and there is enough RAM for eMule.
Mostly process explorer shows 1-2% of CPU usage, but I saw frequent spikes to double-digit numbers, and once it was 22%. Which appears to be too high for an idling application.
What could be causing such bursts of required processor power?
Now eMule uploads at ~1MB/s, CPU usage is 5-10% most of the time, and below 15% in the worst case I spotted.

This post has been edited by fox88: 08 March 2015 - 09:26 PM

[fox88]

Crash dump.