Satan

Did I say I had proof that it was fixed, I said apparently, so get off you damn high horse Toast and stop shouting all over the place.

?? Ok, this should be reported as a bug rather than a feature. It supposedly shouldn't be like that hence no need for this feature.

Apparently the new version fixes this (the one I am currently Beta Testing). We will know for sure when this is released in the near future.

I distinctly remember having to rehash my share with one of the SDC builds. If it wasn't for TTH code then why was it? I have tried this, I dont get an error :S

All users where asked to rehash when BM updated the TTH code, if you choose not to, well thats your choice. But you cannot say that users should not be forced to rehash, if BM didn't fix the buggy TTH code people would complain that its buggy. Sometimes you cant win.... :S

Are these possibly all users who have no rehashed their shares since BM changed the TTH code back in 2.x (something can't remember the v number)? In which case, RTFM, lol :P

Sorry man, i'm not at home at mo and dont have DC on this, i'll take a look for you tomo when I get home and reply then.

Take a look through settings. There should be something to un-check call 'minimise to tray'.

Just out of interest, are the affected users on ADSLMax or 2+ with fastpath on? I only ask because I have had similar problems with fastpath on when my connection was upgraded to 6Meg, when I was on 2Meg the prob never presented itself. Turn FP off and the probs go away....just a thought!

Can I have more info on this, I have not experiencing any such problems.

Why are you asking us, pm the hub owner....

this is not a valid client version....locked.

Search for the How to Get Active Thread.... :roll:

I always thought the -1B refered to what has been added to the your file size within the file list, i.e. in this case, nothing...

Altho all transfer's in Apex are now encrypted so this should be less of a problem. Also PG2 is a nightmare, they are currently being 'bought' by the Anti-P2P agencies and are incorporating duff detections. So technically the people who set out to protect us are actually snitching on us. However, feel free to take the risk yourselves.

+1

Not with ZA running my friend, the Bods have been tryin to sort the ZA/DC conflict's forever, dont know if it'll ever be sorted.

It's unlikely a slot ratio problem, It's more likely the users dont have free slots, look in your download window and you will see exactly what is wrong.

The only way I see for it not to work in those circumstances is that network sharing is not set up correctly in windows. I must say, I have problems with slow hash speed and DC refuses to exit while hashing from the indexed drive. But other than that, network sharing work's fine for me.

ZA is for n00bs. Anyways, it's a DNS Patch released for windows on tuesday that causing these problems. Uninstalling network monitoring software (such as ZA will fix this).

It's probably a hubsoft problem. Rather than Apex. Have you tried another client, can you see the bot's in them?

Ever heard of google? If anyone really wants the client, they will google it. The links dont really matter.

Make sure your DCPlusPlus.xml is read only. Start apex. then refresh file list a few times.

+1,000,000 for this. Very nice.

Well there is a way to ask for help. Quite frankly, i'm not here to answer question's posted by someone who is telling you your client is 'screwed'.