maciver

Thanks for the update, we do apreciate that people take the time to say hey we ARE working on it... Keep up the terrific work!

Do we have an estimated release date or more info on this?

lol meaning its dev only then?

Board Message Sorry, an error occurred. If you are unsure on how to use a feature, or don't know why you got this error message, try looking through the help files for more information. The error returned was: Sorry, the link that brought you to this page seems to be out of date or broken.

I agree, the system should verify first, millions of people upgrade pcs every year and dont want to lose imprtant files to curruption due to something that should be an easy fix.

If you both have the same name then it wont allow another connection but if you have different names then you will have multiple slots. Like [420]johndoe01 and johndoe01 are same person but the client will see it as 2 seperate users while johndoe01 and johndoe01 will be seen as one person and wont connect again.

lmao so where do I get 0.3.0.8

I am currently using apex 0.2.2 and my friend is using the newest stable fuldc and he sent me this message Old client detected, disconnecting. User=maciver so something isnt working

I was told by a fuldc dev, it was a problem caused by the apex build being based on strong that is based on an older dc build, whats to stop the next apex and strong builds to add fuldc support and bypass all the pain in the ass. Personally I feel fuldc is a fair client, but thier dev team is too full of themselves. I mean if it isnt directly blocking thier downloads its not a problem, but its ok to block everyone else. How small minded is that.

I know the problem for most people is the new Fuldc++ client... The new versions of Fuldc and some other clients are refusing connections to older clients, and since apex has a strongdc base, that is based off an older dc++ build it sees us as an old client and kills the connection. Here is a link to the topic, then the next version of apex may be able to fix this... http://www.dcdev.net/YnHub/forum/showthread.php?t=5662 Its a shame the assholes over in fuldc dont see this as a problem, but a positive.

There is a new apex tool going around that is giving apex a bad name, it opens the hublist, matches Q on all users in a hub then moves to the next hub then repeats to expoit the fact alot of users dont turn on the option disconnect users who leave hub. The users zip in and zip out in less than a second making it difficult for OPs to ban them, and when we nickban they simply change names, I have had to go thru my logs to ip ban one user. Is there anything out that can combat this? It makes all apex users look bad, and I was just banned in a hub for apex use due to this damn exploit.

Thank you!

Dont know why it happens, but it happens seemingly at random. It only happens after I changed to 0.2.2 exceptioninfo.txt

lol I cant wait myself, I am an op in 3 hubs and cant wait to see what nice tools that will be added...

happened again just now exceptioninfo.txt

Ok just happened again. I was in 6 hubs, chatting in main, downloading at 160kb/s and uploading at 60 kb/s. Just finished typing lol then crashed with exact same exception I posted... Only crashes on .2.2, .2.1 works...

sleeping...

so anyone know what the cause is or how to fix?