[fox88]

NoMiaus, on 22 July 2018 - 06:21 PM, said:

Some colours were changed on the IRC.

That was changed long ago to follow mIRC default colour scheme.
Not in the official version, of course.

NoMiaus, on 22 July 2018 - 06:21 PM, said:

It was easier for new users asking for help.

The changes made in 0.48a (if I recall the version correctly) were not welcomed by help ops as well.
That got slightly better in the next version, but still too much red text in the channel; and triggers also used red.

[KaboomTss]

fox88, on 22 July 2018 - 06:26 PM, said:

NoMiaus, on 22 July 2018 - 06:21 PM, said:

Some colours were changed on the IRC.

That was changed long ago to follow mIRC default colour scheme.
Not in the official version, of course.

NoMiaus, on 22 July 2018 - 06:21 PM, said:

It was easier for new users asking for help.

The changes made in 0.48a (if I recall the version correctly) were not welcomed by help ops as well.
That got slightly better in the next version, but still too much red text in the channel; and triggers also used red.

I am one of those people that help on eMule channels since 2005 so I think I can tell about the IRC part of eMule and users we receive. The first thing is why you change IRC part to be different from the official eMule version while there isn't any need/bug and without asking about opinions visiting eMule IRC help channels? I think while you are not an active IRC user or helper changing IRC stuff on your own is unreasonable because you can't know what is needed. Then these changes will affect everybody that uses IRC.
I don't see also any reason to have two different interfaces of IRC one in official eMule and different looking in the community version - it will cause users complaining and IRC helpers will loose time to talk about color changes, etc. In addition there isn't any improovement for an IRC part because making all just a one coloured text makes it boring, uncomfortable. For example for an user it's easier to read and follow instructions of a helper when nicknames are splited in different colors as it is in the official version. You also forget that something that is not attractive or comfortable in use/easy to use for users is abandoned and left alone. I wouldn't like IRC being abandoned by users just for unfriendly interface design. IRC does a lot good things for the project and especially for eMulers needing support.
Moreover, I've just found a bug on this unofficial version. I don't know how to reproduce it but it happened twice: I opened two channels and after some time both windows channels became white, I was be able to write and send messages to the channels, they didn't appear in my windows but users were be able to see them.

[emule_user_downunder]

Some Support, on 22 July 2018 - 09:12 PM, said:

I already talked with fox before. We can't quite make it the official version because fox decides what changes to put in and we aren't verifying them (and don't have the time to do so in most cases neither unfortunately).

However with fox's consent we will (and already do) link the version on our website, additionally to the last official version. So users can choose themselves if they want a more up-to-date version or stick with the latest official one. The version check will be updated too, but I don't think there will be an update notification for the "community" version. Mhm. Maybe in the future.

Delighted that there has been some updates and a release of software.
I have found the recent beta versions quite stable, and am happy to have the current version out there for people to update to and supersede the versions out there, on the proviso that the current developers (Some Support and fox88) taking an interest will continue to do so (as resources permit) and collaborate.

I refer to my comments in https://forum.emule-...dpost&p=1097937 about GitHub versioning.

The IRC issues above (one a bug, and one a design issue) can possibly be discussed in different threads (such as https://forum.emule-...owtopic=157976) and a consensus reached as to colour schemes, and maybe that can be made an option that can be turned on or off or devise a configurable IRC colour scheme to keep everybody happy.

We don't have to wait another 8 years for the next version. Fix the bugs and roll out the updates/fixes/extensions more frequently I say!

This post has been edited by emule_user_downunder: 23 July 2018 - 05:21 AM

[fox88]

KaboomTss, on 22 July 2018 - 11:50 PM, said:

I don't know how to reproduce it but it happened twice: I opened two channels and after some time both windows channels became white, I was be able to write and send messages to the channels, they didn't appear in my windows but users were be able to see them.

More details, please.
Could you tell the names of those two channels (and IRC server you were connected to, if you remembered)?
Approximately, how long it took to get this display issue?
Were nick lists displayed correctly?
Were channel window completely blank, or old text was still visible?

[KaboomTss]

fox88, on 23 July 2018 - 10:40 AM, said:

Could you tell the names of those two channels (and IRC server you were connected to, if you remembered)?

I had many open channels in that moment that I don't remember them all actually. I remember I had opened two eMule channels that were #eMule-Italian and #eMule-Spanish. Of course it was the official eMule IRC help network that you may connect using ircchat.emule-project.net that is set by default in eMule official version IRC settings.

fox88, on 23 July 2018 - 10:40 AM, said:

Approximately, how long it took to get this display issue?

Issue lasted till i restarted eMule.

fox88, on 23 July 2018 - 10:40 AM, said:

Were nick lists displayed correctly?

Yes.

fox88, on 23 July 2018 - 10:40 AM, said:

Were channel window completely blank, or old text was still visible?

All was blank and not visible.

[fox88]

KaboomTss, thanks for the answers.
So, you had many open channels, but only Italian and Spanish got the issue.
Is this correct?

KaboomTss, on 23 July 2018 - 01:51 PM, said:

you may connect using ircchat.emule-project.net

That would be a random server; not the one you were connected to.
Well, it was not expected that you remembered this.

KaboomTss, on 23 July 2018 - 01:51 PM, said:

Issue lasted till i restarted eMule.

The question was about how long to stay connected before the issue appears.
As for restart, did you try to part and join the channels, or hop?
For me, nothing wrong happened in about 7 hours while having connection to four help channels.

I will try to do more tests.

[NoMiaus]

KaboomTss, on 22 July 2018 - 10:50 PM, said:

Moreover, I've just found a bug on this unofficial version. I don't know how to reproduce it but it happened twice: I opened two channels and after some time both windows channels became white, I was be able to write and send messages to the channels, they didn't appear in my windows but users were be able to see them.

I can confirm this bug, but I don't know how to reproduce it neither. All channel windows became white and the topics also disappear. If you join a new channel, the new channel looks correct but the channels were opened keep in blank until you part from each one and join again or just hop. I had one download in Transfers and I previewed it, not sure if it can be related.



And I found two bugs more. This is what happens if the eMule window isn't maximized and you do it bigger from the top or from the bottom. If you hop the window is restored.



The third one happens when you join #eMule-Italian. The list of nicks showed only 6 users but there were 47. I was using the nickname Testing1 and I don't even appear there.

This post has been edited by NoMiaus: 23 July 2018 - 12:31 PM

[fox88]

Thanks, NoMiaus.
That OperServ line is suspicious.
I never saw it until today, and google tells that +D appeared only in v4 of UnrealIRCd server.
Is this correct?

[NoMiaus]

fox88, on 23 July 2018 - 02:48 PM, said:

Thanks, NoMiaus.
That OperServ line is suspicious.
I never saw it until today, and google tells that +D appeared only in v4 of UnrealIRCd server.
Is this correct?

It was implemented around 2012 after an agreement between the eMule Italian staff and the network staff for security reasons. It's a customized module based in an old one. The mode is set automatically when an eMule user joins the channel. I'm from the MindForge staff so if you've any doubt we can discuss on the #MindForge channel.

[fox88]

NoMiaus, on 23 July 2018 - 03:19 PM, said:

And I found two bugs more. This is what happens if the eMule window isn't maximized and you do it bigger from the top or from the bottom. If you hop the window is restored.

That was useful, thanks.
It would not be surprising if this resize bug is the same as the blank channel log.
Short nick lists were fine, but only the last part remained for longer lists.
There should be no issues with that +D mode.

Now the fix needs at least a small test.

[NoMiaus]

fox88, on 23 July 2018 - 09:28 PM, said:

It would not be surprising if this resize bug is the same as the blank channel log.

It seems fixed now. I'll let you know if it happens again. Thanks!

[SS1900]

At every startup many my shared files are in rehashing ...very boring and frustrating.
With the last build with 2700 shared files 2300 in rehashing.
Win 10 x64 clean installation.

[Riso64Bit]

hello guys,
i have a question for you.Is normal that emule works only whit mediainfo dll x86 version?
W7 x64Bit clean install


I can obtain crash adding a web source to an existent download:
Overlappedsocket ON _https://www.dropbox.com/s/1d710zexdtwjx9f/eMule_0-51a-11_20180725-000339.dmp?dl=1
Overlappedsocket OFF _https://www.dropbox.com/s/3iwmr9zssz9jtag/eMule_0-51a-11_20180725-000714.dmp?dl=1

try to download ubuntu for example ( ubuntu-18.04-desktop-amd64.iso )
now add a source like an official source: http://releases.ubun...sktop-amd64.iso and click add button more than 1 time
and obtain crash (3rd) _https://www.dropbox.com/s/k6ihbn17fopzps2/eMule_0-51a-11_20180725-001409.dmp?dl=1
(another crash 4th _https://www.dropbox.com/s/hrwrsjm06xkmdwp/eMule_0-51a-11_20180725-002230.dmp?dl=1)

from emule log:

Quote

25/07/2018 00:12:44: Starting eMule v0.51a
25/07/2018 00:12:44: Found 467 known shared files
25/07/2018 00:12:44: Credit file loaded, 72 clients are known
25/07/2018 00:12:48: 196310 IP filters loaded
25/07/2018 00:12:50: Web Interface: enabled
25/07/2018 00:12:51: 13 servers in server.met found
25/07/2018 00:12:51: Found 7 part files
25/07/2018 00:12:51: eMule Version 0.51a ready
25/07/2018 00:12:51: Connecting
25/07/2018 00:12:51: Connecting to TV Underground (176.103.48.36:4184 - using Protocol Obfuscation) ...
25/07/2018 00:12:51: Read 200 contacts from file.
25/07/2018 00:12:51: Connected to TV Underground (176.103.48.36:4184), sending login request
25/07/2018 00:12:52: Connecting to eDonkey Server No2 (176.103.56.135:2442 - using Protocol Obfuscation) ...
25/07/2018 00:12:52: Connected to eDonkey Server No2 (176.103.56.135:2442), sending login request
25/07/2018 00:12:52: Warning TV Underground (176.103.48.36:4184) - Your 51970 port is not reachable. Please review your network config.
25/07/2018 00:12:52: Obfuscated connection established on: TV Underground (176.103.48.36:4184)
25/07/2018 00:12:52: New client ID is XXXXXXXXX
25/07/2018 00:13:29: UploadSpeedSense: Done with preparations. Starting control of upload speed. (First 60 seconds will be in fast reaction mode)
25/07/2018 00:13:56: Failed to process URL source "䅌ᘼㅆ�딣廙쩥⑉춝邱ﻳ闄騚鼡䑭嵃䣵앐蜾น▘筷⟠랶殎聤拿惎蜙內ꌷ땏҃蚿䄇쯡돈�↡鐛튕憙も⁄�뽗යෆ㩳楽ޱ鞳煟즴忐珍㐐ᑫ셰ꅞ푤፜労暊ꖝ䵖ԑ᠒ᡪῪꕲꌔ證놤鑈ⱎ�斤跦踏疕ꬽ斸倶촂এ䱴☲縞꒕䛱⏜榑㦗ᰝ⸏湠읯裾馸왥囁큠貌䤤댆훒Ꮽ᪦꾇텫嘐쳓䲕ꌉ㔶ⲡ頻⦿ଐ놟嗵Ԛ饋븫訢誡Ᵹ㔗驺믎ﳱꙖ榓糷⟘冇ⴄ⧧䳴Ჺ䔔堲⯊햰鸊뵕揜﹬ꍻ沒韛㶵볒胞멵瀳ˇ㝕ᬳ顷哓犍謺崓籩ᔂ놦죠꒨᭕垪픘᥵䛽�ﷶꥄ擺奔豱Ⱐ㰇ꡚ骹桗暅ᒖ䟔Œ鐆఻݈Ѐ眵鬷ຸꤑᤐ剾鬍ꓵ㒺魪롄倶㷶뀲㋉蕝줣⢑�Ⴈ暺紿苵秸廛㔘뿜ﭘ뤏̼݁湶㦣꼫⸬͡谌Ⱛ솼겥㋒쟺앃윈捭鑜볩泘癓䃀❫睱最Č�閗䒦ꠂ앖㡒ᬡ떔䖵恩⡖Ъ݂뀧ý黗寣驟禩�팡胜溰챒減䀠㗾셟઼庐渢떊貊妤絣Ძ攍譔﵌꫋狼꧙毲ᨨ쪠瘐䰛鍍栗Ᲊ憋⿂梴樋塢ꍸሿ듂઻ⲿ昻ⓥ鯫悼◕襞聨컕匵蠬姸ृ⿌뵥安⋉㩊跸侽린휰녮鷓臓삙릤鎪৛号썥鉑ꜵ洢풹㐕媍뒳ㆢꃺ㑬䏬Ṳ崓ᡳ껃譛揣赙ᡴ婇쥈鳁珞ᖔ昬喤�귩ᦵ景☪⼛俼덿㹾㻍뀝ᮩ툾嘞菇揢艁ᕑ䷚왆疶禍鈗�䙃幞댵䚢잽爥➭拥풙侩䈍쌑ⅆ灷༢譝쬦Ýࢢ霦ɤⰑ䀴ຌ蓠鋐郎玗t硵쭭�䌓箘ٖ確�⤺魫㮸�커瞁╻빣㙗ꂰኜᚐ祣_〠얿墪쿺盳铵佹㦠䟆䮸聓ꦥ嬆㾦陴䖏뷰䛘ﮒ늆鯕㫵뼼鯫筶䃵殾ꨗ垆嬗ꔼ䑵픠뀄塝⭖潩ℸ鐛뗍涅�豨ࠡ近씎ꓵ훑饧峇潅逳玡ⷜ큕珰翳첞㩙暽Ž烑䩗ᓶఆⷁ됍ទ檒ᴗ압讹✰瀧嫨䃲ꪅޔ抖몱쓻槪⮤柁싡ꢛ䫲슣崶絮䙤ᨼ헦話嚪牯떿प୘荪눥閤Ⓐ䕰ꂞ唰玕饢㖐솟乇ʖ蛯ᯢ鄢厣騢립톫⯐词ꍇ�퍍饙깕㕛牿鷐ﲌ춚晌됄牞㍤돯긴蒍ⵯ䲅嚻鶄䆰㇠䩊ﶙ⧄强䠉꾅쌯糒䫦絎펚娙稶෽㕏ງ㷦�஻멀ꢕ쿏渲軗籭ㅵ⩆䕶懵ꬡ錦覮㔐䲏৲埨쪽敇ﭝ⽝䌍ꄶ㑔鄺惙텁炝阪Ƅ僑ਦʒቂ�蝕葀瞗鑙ᆰ齈뼯䪋롯껯嵪�숋즮響杅뮲�糱滜复堶镣澴堮瑖凐뵯 鹿秃굏⫸夹㉦ᵕ፼쪅垩己㡏䖄勐㫧睠扵ᰣﶢ堝㍪။탔蓴优亭鴀ꋗ퇲ⓧ왈驓犃聁⽫썈ↀ鐛ꥵ䟇튰㒬ᤨຈ獥쯣ệ￪콵쩚ퟲ漽旎捯秫雙ꏆ嶚᷅˃钮უ緼冺屏ﭡ쭒쪯䡆戧᩻䜦┙�㲬莘ᅴ娚�羂ᒷ욿⏭얽ﴰ떡퐄䫹ﰿ䎕ꞇ즱꙳힜퀛∔詬箢⏓섫㝧䫺⡑俢坶⏇鱔썰庯餦獣넧魫㣆Ȟ簍꺒킅鯲窸븪拗흻穎Ṿꦎ벦Პ�裸輛�䷵䩯䭳鰻哃唦御⩷窷梵ꫭᓥ閯ⴲᆁഹ㆜⻺勯했ⓦ艥玾궈⏖ŭ䔆䂦ꑼ퀌鋀㏡䂧⥍敠⒆覰⢊秥꣘앉亽㳑굘Ҡ籁ᡁ齓㫑틞逶⍰∰谭ᎂ쀁㜒芤꯺售聒ꩦఙ썼ຂ鲡헁ꪦ伏ⷫ힥罱嗁貑돬킷
25/07/2018 00:13:59: Failed to process URL source "ꑤ字"
25/07/2018 00:14:04: Failed to process URL source "4"
25/07/2018 00:14:06: Failed to process URL source "駁윞餮亨퐬菾垏㡹�轏≷ꑣ字ꑯ字ꑣ字"
25/07/2018 00:14:06: Failed to process URL source "駁윞餮亨퐬菾垏㡹�轏≷ꑣ字ꑯ字ꑣ字"
25/07/2018 00:14:07: Failed to process URL source "駁윞餮亨퐬菾垏㡹�轏≷ꑣ字ꑯ字ꑣ字"
25/07/2018 00:14:07: Failed to process URL source "駁윞餮亨퐬菾垏㡹�轏≷ꑣ字ꑯ字ꑣ字"
25/07/2018 00:14:08: Failed to process URL source "工诃ࡵ⡨嘀濨菿ࣄ욋䶋擴ඉ"
25/07/2018 00:14:10: Failed to process URL source "䨘莟ﻑĀ￮￮"

on verbose log:

Quote

25/07/2018 00:14:04: SXRecv: Server source response; Count=1, Dropped=0, PossibleSources=1, File="ubuntu-18.04-desktop-amd64.iso"
25/07/2018 00:14:04: SXRecv: Server source response; Count=1, Dropped=0, PossibleSources=1, File="ubuntu-18.04-desktop-amd64.iso"
25/07/2018 00:14:06: SXRecv: Server source response; Count=1, Dropped=0, PossibleSources=1, File="ubuntu-18.04-desktop-amd64.iso"
25/07/2018 00:14:06: SXRecv: Server source response; Count=1, Dropped=0, PossibleSources=1, File="ubuntu-18.04-desktop-amd64.iso"
25/07/2018 00:14:07: SXRecv: Server source response; Count=1, Dropped=0, PossibleSources=1, File="ubuntu-18.04-desktop-amd64.iso"
25/07/2018 00:14:07: SXRecv: Server source response; Count=1, Dropped=0, PossibleSources=1, File="ubuntu-18.04-desktop-amd64.iso"
25/07/2018 00:14:08: SXRecv: Server source response; Count=1, Dropped=0, PossibleSources=1, File="ubuntu-18.04-desktop-amd64.iso"
25/07/2018 00:14:09: SXRecv: Server source response; Count=1, Dropped=0, PossibleSources=1, File="ubuntu-18.04-desktop-amd64.iso"
25/07/2018 00:14:09: SXRecv: Server source response; Count=1, Dropped=0, PossibleSources=1, File="ubuntu-18.04-desktop-amd64.iso"
25/07/2018 00:14:09: SXRecv: Server source response; Count=1, Dropped=0, PossibleSources=1, File="ubuntu-18.04-desktop-amd64.iso"
25/07/2018 00:14:09: SXRecv: Server source response; Count=1, Dropped=0, PossibleSources=1, File="ubuntu-18.04-desktop-amd64.iso"
25/07/2018 00:14:09: SXRecv: Server source response; Count=1, Dropped=0, PossibleSources=1, File="ubuntu-18.04-desktop-amd64.iso"

This post has been edited by Riso64Bit: 24 July 2018 - 10:25 PM

[fox88]

SS1900, on 24 July 2018 - 09:03 PM, said:

At every startup many my shared files are in rehashing ...very boring and frustrating.

It should be one time process.
Are you running 0.51a interchangeably with the 0.50b or earlier?
In that case rehashings would be unavoidable.

Timestanp calculations are a complicated matter, and previously I had rehashings when compiling the same code in different version of Visual Studio.
The goal was to make these calculations independent from VS version, Windows version (and time zone/DST settings).

[fox88]

Riso64Bit, on 25 July 2018 - 12:50 AM, said:

Is normal that emule works only whit mediainfo dll x86 version?

Welcome back.
Yes, applications and dlls should be of the same bitness.

Riso64Bit, on 25 July 2018 - 12:50 AM, said:

I can obtain crash adding a web source to an existent download:

That part of code was not getting much attention so far; but crashes should be fixed.
Thanks for the information.

[Riso64Bit]

fox88, on 25 July 2018 - 10:12 AM, said:

Welcome back.

thanks

with overlappedsocket off i got 1 crash but with autosave DMP file it has created a 0 kb file...
this is a new crash in the same condition https://www.dropbox....203400.dmp?dl=1

Quote

25/07/2018 20:33:58: SXSend (Version 2): Client source request; a.b.c.d 'a.b.c.d' (eMule v0.50b,Connected/None/None), File="B.mkv"
25/07/2018 20:33:58: SXSend (Version 2): Client source request; a.b.c.d 'http://www.adunanza.net' (eMule v0.50a [AdunanzA 3.18],Connected/None/None), File="B.mkv"
25/07/2018 20:33:59: SXSend (Version 2): Client source request; a.b.c.d 'http://www.adunanza.net' (eMule v0.50a [AdunanzA 3.18],Connected/None/None), File="B.mkv"
25/07/2018 20:33:59: SXRecv: Client source response; SX2=Yes, Ver=4, a.b.c.d 'http://emule-project.net' (eMule v0.50a,Connected/None/None), File="B"
25/07/2018 20:33:59: Error: Unknown exception c0000005 in CClientReqSocket::PacketReceived at 7776E486; protocol=eMule opcode=OP_SIGNATURE size=49; Client= 'http://www.adunanza.net' (eMule v0.50a [AdunanzA 3.18],Connected/None/None)
25/07/2018 20:33:59: Error: Unknown exception c0000005 in CClientReqSocket::PacketReceived at 7776E486; protocol=eMule opcode=OP_SIGNATURE size=49; Client= 'http://www.adunanza.net' (eMule v0.50a [AdunanzA 3.18],Connected/None/None)
25/07/2018 20:34:03: Download session started. User: 46.44.197.98 'Cuccureddu08' (eMule v0.50a,OnQueue/None/None) in SetDownloadState(). New State: 0

This post has been edited by Riso64Bit: 25 July 2018 - 09:23 PM

[fox88]

Riso64Bit, on 25 July 2018 - 12:50 AM, said:

I can obtain crash adding a web source to an existent download:

That is a C++ compiler bug. MS might fix it, but in the meantime it could be circumvented.
The bad side: it is unknown if that was the only bug of the kind.

Riso64Bit, on 26 July 2018 - 12:19 AM, said:

this is a new crash in the same condition

Thanks for the dump, will need to look at it later.
Were you using chat (Messages)?

[Riso64Bit]

Quote

Thanks for the dump, will need to look at it later.
Were you using chat (Messages)?

i dont remember that i was connected to a chat, i remember that i was reading data from the content tab of a file.

This post has been edited by Riso64Bit: 26 July 2018 - 09:20 AM

[fox88]

Riso64Bit, on 26 July 2018 - 12:19 PM, said:

i dont remember that i was connected to a chat, i remember that i was reading data from the content tab of a file.

The crash location implies that there were chat tab(s).
Please let me know if there is a way to reproduce this bug.

Also, you should keep overlapped sockets 'off', because it was not doing any good in your configuration.

[Tuxman]

Some Support, on 22 July 2018 - 12:12 PM, said:

I already talked with fox before. We can't quite make it the official version because fox decides what changes to put in and we aren't verifying them (and don't have the time to do so in most cases neither unfortunately).

So there is a risk that the eMule team will release their own eMule 0.51a some day which is entirely different?