Big Muscle

it is bug in NOD's imon library

but "Sql" in hub 1 is me, "Sql" in hub 2 is my friend and John is Sql from hub 3 but only with different nickname. What then? According to your proposal we could disconnect Sql from hub 1 and Sql from hub 2. So 2 totally different users would be disconnected and one same user with different nicknames would still eat your slots :D

yes in ADC, no in NMDC

it checks after each XXX kB where XXX is the size of TTH block. TTH block size depends on file size but is minimally 64kB.

TTH is checked during transfer, so it's impossible to download corrupted file. But if file is really corrupted then: a) source file was corrupted too and you just downloaded this corrupted file you have bug in your PC and file got corrupted after downloading and sending it to OS

and windows' convert program won't change file allocation size. So it can have different performance than normal NTFS format.

yes, it's true, but... ... you can see that your crash happened many times, so try to search for a topic with a crash which happens many times. Then you can open exception.txt and check some string - for example "MerkleCheckOutputStream" but you can select different string from call stack and compare it with found crash. Yup and you see that it's almost same :lol:

why do people report same crash again and again? this crash has already been discussed many many times and I also wrote the workaround for it. So why not read before posting?

just a note "convert" cmd doesn't format anything. It just converts the drive without data loss.

maybe, I have a workaround for the crash. Try /rebuild in mainchat and if it doesn't help, then delete HashIndex and HashData files in your Settings directory.

if it is bug in all DC++ mods, it doesn't mean that it can't be fixed!

converting is ok, but don't forget to defragment with some cool defrag program (i.e. O&O Defrag)

it's crash in windows library only, so it's windows bug and don't report it here :)

why it's not logical? if there had been an option to disable it, then everyone could disable it and it would eat too much slots, then this feature wouldn't have a sense. So it's logical that it can't be disabled.

it's not bug, but feature to avoid eating all slots in the network

yes, it's possible to happen, but it's not probable to happen. oh, I hope you understand what I mean, it¨s strange to say it in English ) but ok, stop off-topic and return to original topic

ifmn: read again what I wrote. I didn't write that there can't be a TTH collision. I wrote there can't be TTH+size collision and it's verified and different file with same TTH and same size has never appeared. I already read this page. "Collisions were announced in SHA-0, MD4, MD5, HAVAL-128, and RIPEMD" where's TTH? :)

just show me one case of different files with same TTH and same size yes, we can but it takes a really long time to generate big files to match TTH :D

no, it's not... if two different files have same TTH, they have different size :)

in this case, you can close search window and the search request will be removed from queue

no, there's not a probability of collision because we use also size check, so it will always work :D

but it can happen and we don't play at "probability is low, so it can sometimes work"

yes, hub in TransferView is just a guess from last ConnectToMe, but there is one thing... if user A tries to connect, then user B with same nick tries to connect and this user B connects faster, the user A will be dropped and hub of B will be displayed as hub of A. It¨s just current implementation of NMDC protocol.

nevermind... both users can have same IP.. but what I don't know is whether they can have also same port. edit: yes, they can have same port, if they are passive users

searches can't be paused neither aborted. Once you search for something, it will send you the search result until there are no other matches. And results will be send also if you close the search result.