Crise

Indeed, I have a feeling many people will miss forums...

Not necessarily...

Hmm, and I supose there is no way to change your mind...

sigh, my beautiful website design is going to go to waste ;)

Few possibilities: http://forums.apexdc.net/index.php?showtopic=2812 I can't guarantee that one of those are the reasons however, all I can say is that the new version aims to be better performance and stability wise as always.

There should be new version out relatively soon...

I agree, actually I think coder is the worst person to beta test his own program...

That's not what I meant... and if you look carefully I have removed the actual links already (removed right after reading that post).

Just as there was a reason for me to ask a patch... I was well aware that greylink (and pelink for that matter) break gpl by not supplying source code and that was the exact reason why I replied the way I did.

Get me a patch for it, and I'll gladly add it as an option... :)

Because when you send pm, only the receiving user will see it, the reason why you normally see your own messages is because the client adds a local copy of your message on it's own for you to see. However since Raw commands are just that, raw protocol commands send directly the local copy of the pm will not be added.

Hey now, other beta testers will get jealous if you tell that since they don't have it yet...

An update will come as soon as we get some testing done...

Well I don't disagree with you, but unfortunately I have no experience with symbian or alike OSes, so I don't think this will happen... at least not without 3rd party developer :)

The "How to Compile" guide has not been updated, because I have made the decision not to support compiling ApexDC in these forums anymore because we do not support any custom versions of ApexDC either. And no patched WTL is not needed anymore...

We made the choice to disable all old versions because there is a bug in them that allows a remote user to crash your copy of the program at will by sending a certain kind of request. (I am aware of one client at least which implants a function that takes advantage of this bug in a way that could allow user to potentially empty hubs with it... as this issue affects to very many versions of DC++).

Yeah, VLD is required for debug builds only, but you can comment out the include (in main.cpp) since you won't be detecting memory leaks now will you...

Use latest official WTL... (wtl.sourceforge.net), and you should also discard all the include files uploaded by Alana, if you installed VS2008 with all the sdks coming with it all of those single file includes (wmp, winfirewall, natupnp etc.) should not be needed, besides the files shipped with VS2008 are most likely newer anyways.

use svn version...

Testing against latest SDC is enough as 1.1.0 is based on it...

mcravener, could it be possible for you to try if ypur observation also holds true for StrongDC, as if so it would be best if this was fixed there... (besides BM knows the multisource code far better than f.ex. I do )

I honestly don't know, you see ApexDC is based on on StrongDC, and as far as I can remember no code regarding network drive recognition has been changed in ApexDC.

I can view all network locations in vista fine with ApexDC, as well as mapped drives...

No one has been arguing, I believe the point in this filelist download time issue is that the remote user who downloads the filelist has no way of choosing which filelist he or she wants... and to some even that 2-3 seconds may matter (and it is not always 2-3 seconds, it all depends on share size -> filelist size and remote users line speed).

Yeah /help in chat, however that list is incomplete one...