[LorenzoC]

I guess feuds of any sort are another of the classical weak points of Open Source software.
Together with the usual "you don't like it, go developing your own software" and "I've got a bigger d@@k than you" attitude.

This post has been edited by LorenzoC: 21 July 2010 - 07:33 PM

[taz-me]

LorenzoC, on 21 July 2010 - 10:32 PM, said:

"you don't like it, go developing your own software" attitude.

Few last comments from me :

1. It's up to the modders to decide upon their mod changes (unless it violates any rules). Once you've made your point, you are not serving your goal by annoying, repeating the same messages or fighting with the modders or other posters on that mod thread.
2. There are 2 options :
a. There's a mod that suits you - and then if you try to get other mods changed to become alike, you are looking for a specific modder and not a mod.
b. No mod suits you (keep in mind there are a lot of mods) - then you might rethink about starting your own mod, or hiring a modder.

[James R. Bath]

taz-me, on 21 July 2010 - 06:35 PM, said:

BTW: I wouldn't say ICS is randomly picking chunks (I've yet to encounter a better chunks selection method !)

Taz, I'm not sure what set you off, but thanks for that part of the reply. I like ICS too. My comment was about official's selection of chunks, which would be closer to intelligent if it it simply had some of the random nonsense and obscure preview selection code removed. I'll give EMF a run to see how the SF, preview first, and ICS work together.

[Stulle]

probably your apparent disrespect for acknowledged members of the community. but that's just my guess...

[Famerlor]

James R. Bath, on 21 July 2010 - 07:13 PM, said:

LorenzoC, on 21 July 2010 - 10:43 AM, said:

@Famerlor:
Sorry dude, I am sure from your point of view what you wrote has some meaning but from here it has not.

Famerlor and Stulle just randomly spout stuff because that's how eMule selects which chunks to download. Hopefully EMF will correct that so code behavior imitators will have some meaning in their posts.

I have to disappoint you I'm still part of the EMF team and although I really got NO time to code at all ATM I use my very little spare time to keep being informed (i.e. by reading code!) so that I can start coding ASAP when I've got more time (ok and motivation).
And again - eMule does NOT randomly choose chunkz, neither zz-, nor maella-, ICS- or Neo-ChunkChooser does that. Look at the PartFile.cpp.

taz-me, on 21 July 2010 - 07:35 PM, said:

BTW: I wouldn't say ICS is randomly picking chunks (I've yet to encounter a better chunks selection method !)

Nope, it of course isn't. IMO ICS is the best chunk chooser available, judging from my PoV (I still have to get a look at the NeoRareChunks yet).

LorenzoC, on 21 July 2010 - 09:32 PM, said:

I guess feuds of any sort are another of the classical weak points of Open Source software.
Together with the usual "you don't like it, go developing your own software" and "I've got a bigger d@@k than you" attitude.

Lorenzo, since you're a well known respected longtime member of this board, I'll explain you my harsh reaction and hope you'll get my point:
Everybody involved in this mod - incl. Lunedieu / Mondgott - has given his very best. Design included. The design decision was made because this mod is still the board-mod of emulefuture.eu in first place so the design should fit the boards layout when it was created.
Of course "you don't like it, go developing your own software" is normally a stupid statement. But in case of eMule mods it is very valid because it is not too hard to find another mod offering the same or very similar features if there's a specific point annoying you at the currently tested mod.

James R. Bath, on 22 July 2010 - 01:16 AM, said:

My comment was about official's selection of chunks, which would be closer to intelligent if it it simply

Use the board search there are some threads about the cunk chooser in official. Not everybody was happy for the change from maella to zz chunkchooser back when it was done. That's the reason why Xtreme kept the old Maella style additionally to the new zz implementation.

Stulle, on 22 July 2010 - 01:25 AM, said:

probably your apparent disrespect for acknowledged members of the community. but that's just my guess...

I just hope that taz is not James' next victim in his anti-modder campaign...

This post has been edited by Famerlor: 22 July 2010 - 04:46 AM

[LorenzoC]

@taz-me
@Famerlor
People make mistakes, regardless the good will and the efforts.
Like I can be wrong saying EmuleFuture design impairs usability, maybe the decisions made some time ago and the consequences of those decisions should be reconsidered (since some time has passed now) to make Emulefuture better.
Of course I extend the same reasoning to ALL mods that use the same "skinning scheme".
Taz, the reason why I insisted so far is the topic hasn't been discussed YET.
Nobody came explaining guidelines and decisions, why "technically" EmuleFuture design improves Emule's default interface, what are the considered gains and drawbacks, etc.
I've been told EmuleFuture had to recall the board and to differentiate from Emule. Both goals achieved, unfortunately.

[Stulle]

[ot]
CONSEQUENCES WILL NEVER BE THE SAME!



eh... i gotta run!
[/ot]

[pier4r]

[ot]

Stulle, on 22 July 2010 - 10:12 AM, said:

[ot]
CONSEQUENCES WILL NEVER BE THE SAME!



eh... i gotta run!
[/ot]

rotfl.

[/ot]

[James R. Bath]

The summary version of my EMF beta test: It's so bad that I'm cutting my beta test short. It's like using a more annoying, slower version of SharkX 1.7, though it does at least get the file hashing correct.

Things I like:

• SF works well as expected.
  
• The File Header tab in details is nice.
  
• DL preview chunk first seems to actually DL the preview chunk first, though my test period is too short to say for sure.
  
• The IdentifierDesc is completely gone from the log.
  
• It loaded and didn't corrupt the ClientAnalyzer file.

Things that don't work:

• There's no way to disable the auto directory scan/check diskspace "feature". Please force whoever is in charge of this to share multiple directories and at least 1000 files. Better still, just kill it.
  
• IP2country doesn't display country names/codes no matter what the setting, both for users and servers.
  
• SF is still too jumpy with no way to disable trickles.
  
• The "Set client datarate in kB" works more like set minimum number of slots and only has a direct kB effect when set to 0 (SF).

And last and least significantly, I don't care who you got to design the buttons and labels, they suck, and I'm looking at them on a big enough monitor at a high enough resolution where all the text is clearly visible. Sadly, that doesn't help. Give up on the future buttons, focus on the future features. Also, the RAM/CPU meters are a complete waste. If I want to track that, both are already built into Windows and every other OS.

I ran the "NoBoard" version if that means anything.

This post has been edited by James R. Bath: 24 July 2010 - 10:48 AM

[tHeWiZaRdOfDoS]

About IP2Country: did you choose the correct settings and are the proper .csv and .dll files in place (addons directory!) - I tried it and it actually displays everything properly.
About ASFU: I also don't need/like that feature and maybe we'll add a switch for it

[LorenzoC]

I don't know if this helps but I noticed that some mods came without the said above cvs file and they failed to download it automatically (I expected the file to be downloaded with "auto-update" feature enabled). I needed to download the file manually, place it in the config directory, then the mod loaded it and worked correctly (and apparently could auto-update the file after that). I don't remember right now if it was the case of EmuleFuture but for sure I got this issue with Katana.

This post has been edited by LorenzoC: 24 July 2010 - 08:25 PM

[James R. Bath]

The stupid addons folder like SharkX too. That really should be included as part of the install. No, all my ip2country stuff is in the config folder. I did try the manual update but that had no effect. As for ASFU, I really wouldn't mind that as much if there was a timer feature so I could set it to run once a day. Then it would be useful instead of constantly reloading the directories. The "scan" is clearly broken in it. Even if it worked, it would still be annoying and more harmful when using other p2p programs.

[tHeWiZaRdOfDoS]

I've got the same opinion... maybe we'll replace it

[Stulle]

chances are that something is accessing your shared folders all the time or a folder that is above your shared folders. you should much rather figure out what is constantly changing your folder contents then condemning ASFU. it might not appear useful to anyone but since we use Windows inbuilt functions constant reloads - which should not be the case anyway because the default is 120 seconds at the very least - are probably just showing you something else is wrong with your computer setup.

[James R. Bath]

While I'm sure someone somewhere might find Stulle's advice useful, I had considered that possibility long ago and tested to see if something was being updated, reduced the files shared to a single, long stable directory, reduced it to only NTFS, to only FAT32, to only a USB RAM drive, etc. Sadly, I couldn't blame it on my computer setup. Because Stulle wants to talk about advanced computer setup stuff, I'll also mention that I even have the indexing service disabled.

[Stulle]

http://msdn.microsof...417(VS.85).aspx

call is like this:

								dwChangeHandles[curPos] = FindFirstChangeNotification(
									curDir, FALSE,
									FILE_NOTIFY_CHANGE_FILE_NAME | FILE_NOTIFY_CHANGE_DIR_NAME |
									FILE_NOTIFY_CHANGE_SIZE | FILE_NOTIFY_CHANGE_LAST_WRITE |
									FILE_NOTIFY_CHANGE_ATTRIBUTES);

we check shared folders as much as folders above the shared folders. if a parent dir is changed we check if a shared file has been changed. whenever a shared dir has been changed we reload. if there are more than MAXIMUM_WAIT_OBJECTS (iirc 64) dirs we stop ASFU.

again, if something keeps changing your share it will obviously trigger all the time. this could happen if you share your config or temp file for instance.

[James R. Bath]

I don't share my temp folder, so you're saying ASFU is defective because it checks folders that are not shared. Not only defective, but imposing upon the user's system beyond the set limitations. One might call that spyware, or rebrand it Micrsoft .net. Any mods use .net?

This post has been edited by James R. Bath: 25 July 2010 - 05:39 PM

[Stulle]

No and if you read carefully you would very well know. We check for changes within the file system in shared folders and parent folders. If there is a change in a parent folder we check if it was related to a shared folder and if this does not apply the code disregards the change and continues to wait for a change.

No information about the nature of the change is collected or sent to any other client. Thus is the accusation as meaningless and pointless as your usual blabbering. You are trying to make things you don't understand look bad. I wonder how many witches you burnt to the day. And by witches I mean women who can do simple sum operations with two digit numbers.

[Ejack79]

In \AntiLeech\ClientAnalyzer.cpp:

bool CAntiLeechData::AdditionalModThiefCheck(const UINT i)
{
	if(m_pParent /*&& i != AT_MODTHIEF*/)
	{

		... ...

		//uses a CA enabled client... thus it shouldn't be a bad client :)
		static const sDaS strModArr[] = 
		{
//these are *NOT* necessary for the CA to do its work... but they are a nice addon :)
			sDaS(L"Tombstone v", 0),
			sDaS(L"eMuleFuture v", 0),
			sDaS(L"AcKroNiC v", 5.0),
			sDaS(L"SharkX v", 0),
			sDaS(L"zBOOM v", 0.1),
			sDaS(L"beba v", 1.0),
			sDaS(L"Spike2 v", 0.8),
			sDaS(L"AnalyZZUL ", 1.0),
//<<<
			sDaS(L"Tombstone v", 0),
			sDaS(L"Tombstone Xtended v", 0),
		};

		... ...

Why TS checked twice?

[tHeWiZaRdOfDoS]

Well, just a miss