Satan

We need to sort the linux version first. Also, considering the cost of bandwidth on mobile devices I doubt it's popularity.

HJT shows nothing abnormal. Try leaving the firewall off, also turning off avast and also disabling UAC. Then check if it works. If it does, re-enable each thing one at a time until the behavior starts again and then you will know which thing caused this problem.

Well consider he is responsible for the client which Apex is built on, i'd say he has a right to decide.

Any point to that post?

Never had this problem. Presumably you have tried deleting the hash files and re-hashing your share from fresh? Also, try loading Apex without them and doing a TTH search for each file. Check if they come up with irratic results. Such as different file names for that same TTH, it may indicate some sort of TTH error. Also, try re-downloading the file's from a different source (perhaps even a different client, torrent etc).

Sorry guys, I missed to PM, i'm in work at mo but I'll have a look this evening when I get home and reply if I can help.

Copy the relevant entrie's from StrongDC's DCPlusPlus.xml.

It's more than likely that DC does not allow this. It will check your IP and notice both are the same, hence no dl. Try a variety of hubs. This is possibly an ADC only feature, also ensure both usename's are different.

Tried adding them manually through DCPlusPlus.xml?

I see your point, and it is valid, however, unless we put some sort of limit on the number of slot's it will swamp the network. You have to realise, DC is not like torrent/limewire/ed2k etc with million's of users for every user (centralised if you like). In most cases the most users you will find in a particular hub is 10000 and taking into the consideration the average number of hubs a user is in in 5, that is 50000 users. Now if all of those user's are using more and more slot's for each file it stand's to reason slot's will run out. We MUST set a limit to avoid this. 10 is a nice round number and as such, I agree whole-heartedly with it. You also should realise, most user's use DC for rare files (the aforementioned client's are more geared for new 'popular' files). I, myself, use DC for rare files (mostly) and as it stand's rarely have 10 active segments. If you want, new files, one at a time, fast, don't use DC for them. I can't agree with this, DC is NOT the fastest network, not by a long shot. Get yourself a demonoid account and use torrent, you will see what speed really is. The intention with DC is not to 'please everyone'. It fulfil's the purpose for which it was original intended. That is, for user's to connect to each other, therefore increasing file base, in a way, MS downloading attracted the speed-a-holic users. But going back to the 'spirit of DC' once more this was never the original intention. But with innovation, come's problem's. This is just a sideline to MS downloading, but MS downloading also brought many positive's, hence why it has survived thus far. Incorrect, the move the MS by DC++ was ALWAYS intended as part of ADC implementation, unfair advantage had nothing to do with it. If it did, it would of arrived MUCH sooner, i.e. MS downloading has been around in DC for years. In that case, what is your hurry? Why not leave DC running overnight, you come back next day, and it's all finished I cannot see a case where this would not work. There are thing's in place to counteract what you say. For example, you can only use 1 slot from a user per hub. So you can't swamp a user with a large queue. Also, a large queue will still only allow so many slot's overall. Secondly, using a lot of slot's for one file will be unfair on others. Each file will only have so many sources. So setting an overall limit will lead to one user having the ability to get a slot from every user with that file, meaning other user's wanting that particular file can't have a slot. Whereas with a large queue, different file's give's more chance of different users. Most people don't use 10 segments unnecessarily. DC already close's slow slots. So this is pretty much null and void. As I said, at present, I have five simultaneous files at mo, using in the region of 3 slots each. I tried to answer this in work, no luck, too busy to answer this. So i've left it till I got home You gotta be honest, it is an extremely long post, (and getting longer), and BM is probably busier than you or I.

Not on a per file/folder basis. You either do it for all files or none at all.

Can ignoring OP's be over-ridden? It's the OP bot's that annoy me with all the adverts. Obviously PM me an answer if so, I can understand you wouldn't want all user's to be able to use this.

Funny how you comment that loads of people are having this problem. Yet we have only recieved a few post's from people having probs. Please dont blame your messed up PC on us.

As BM says, SFV's are man-made, so can be easily adjusted to suit. How do you know you have an original SFV?

For what purpose? Apex already check's for file corruption through the download?

Do you get any messages telling you the ports are in use? Other than that, re-setting the port's or changing port numbers is all I can think of.

Let me guess? Netgear router? Try re-setting to factory setting's and re-doing your services.

Where you using the same queue in each version?

Well Apex will wait your predefined search interval before starting a search so that cant be the prob. Dont think it is anyway. If you have such a large queue that is the reason, unless these files are all huge and in essence the xml file is still small that is. Queuing up thousand's of files will swamp the client as it is opening numerous connections at once.

Right, I will take each point in turn here. You are not 'suffering' from this feature, you have simply missed the point of the DC network. DC was not, as you put it, there to facilitate user's maxing there line's. DC is a community, it is not like torrent where it is there simply to allow users to download hundred's of files. You can chat, queue up hundred's of files, and most importantly SHARE. Hence the reason DC has a share limit for users, it encourages users to share, not like torrent, or limeware etc where everyone leech's and does not give back (sure, torrent 'reward's' sharing, but it does not have hard coding in it to avoid leeching). DC give's the hub owner's the choice (and 99% of them oblige) to inform users they must share x amount to join the hub. Technically, it's more than enough, DC++ up until very recently, allowed 1 slot per file, period. However, this does not mean Apex cannot make good use of your connection. The DC network as I previously said it geared to allow users to queue up multiple files, so if you have 15 files running with 10 slots, this is 150 slots in total. Surely you can easily max out your connection on that? I'm assuming, if you can't you are not downloading popular files as you previously stated. Out code is already optimised to do this, not quite in the way you say, but it does it without swamping the network like RevC. It already adjusts segment size in accordance with the uploader's speed. It also disconnects slow users as your slot's fill up with fast users. If you are downloading popular file's this should work even better. You should in essence end up with 10 sources uploading to you in excess of 100Kb/s each! If you use hub's designed for your connection, even faster. If this is not the case, this is a code error, i.e. a bug, rather than a feature you need implemented. We have previously explored using 15 slots on DC and for good reason removed this feature, so to incoorporate such a feature as this would mean we are going backwards. AFAIK Lee/Crise do not frown on bugmenot account's (altho I am unsure they know what they are) so that shouldn't be a problem. My Pleasure, was nice to have a detailed thread to answer for once.

Weird, I have not experienced this myself. How about on other DC programs, can they find your files?

Can you download ok? Search for other files?

Well I installed it on my downstairs machine, xp system, i'll only be using it very rarely, (it's just a server) so expect a report back in 6 months letting you know my thoughts :(

Try searching more than once, the search code in dc in general is buggy ;)

PG no longer exists in the more recent versions. IPG replaced it.