adrian_007

about op side and 1.0.1 not exacly - but afaik it's gonna be improved a bit in the next release, i believe... :thumbsup:

if you are interesed, i use eset smart security and with my mod i also have this crash from time to time. but it's pretty random... maybe it's a nod32 problem... but afaik only with sdc++/mods based on.

he already has it.

no need if someone know protocol. he want to get direct connection to user and send to him a message rather than sending it to the hub.

i don't know what cause it, but in adc normal connections sometimes get encrypted and when you want to download sth via that connection you just get a SSLSocket error.

you need a professional edition of visual studio, express edition lacks mfc/atl support. (but it could be used to compile dc++ when it was using vs ^^, you can always play with 0.699) and you need at least stlport 5.2.x afaik (which is still only at svn repo)

stlport svn used? ^^

+ we can pass it - just don't use it, app will release handlers on close - we can't reload dll at runtime i suppose it's because we don't use mscrt dll, it's compiled, or sth else - i haven't investigated it a lot :)

belive it or not but i'll give a chance for ReactOS to take a nice piece of m$ cake in future. afaik it's the only one os developed in this way - to be compatibile with NT, and it's open sauce and by react os, linux will be a huge step closer to support winapi (which sux imo, we need sometimes to use really dirty hacks to make sth working)

there is an extended version - eset smart security :crying:

on big hubs, only hubsofts written in c++ will stay on stage - performance is most important thing... how you can imagine server with a couple adc hubs on i.ex soft in java (dchub - yes, it's great hubsoft, but it's still java...). and about c++ soft, there is adch++ afaik and... ?

someone can make adc version of verlihub, imo then owners will merge easily. or adch++ should be more extended. anyway, from my experience verli is the best hub software. but it's only my opinion.

1. microsoft can fix that buggy system 2. you can change os :(

vista is the problem, and this was already reported :(

magnet link does that job, just open your filelist and copy link to certain file.

yes, in upcoming adc protocol.

im just wondering, for what you want to compile apex dc if you dont know how to prepare environment...

stlport you can get from svn repo. about wtl i can't say too much while i didnt update it from ages but i think you need to change some code, but in wtl.

apexdc is using stlport svn - in stdinc.cpp you should see it... :P

you didn't catch irony in my post also, dc++ is op client too, because via this client we can check connection to user and also his filelist [manually, but who cares?] and even send raw command! [uc for lazy users ]. of course, in my opinion, apex isn't an op client, project is aimed to normal users, but have extended features already implemented in strongdc [with isn't op client, either]... + one new - [from this important] threaded check. however it don't make apex an op client at all. and as i said, ops are normal users too, so why we have to make them life harder and force them to use second client to prevent banning? i'm using my own op client as op and regular client and it works fine :)

and when op is also user, then he have to use second client, right? ...

i can say there was mem leaks in raw manager [occur on exit :crying:; look and compare destructors to see difference] and in favorite manager [same one presented in raw manager], also some minor things like warnings that not all controlls return a value or so.

it's means you can use find() func instead of iter all map, also it should be more mem friendly

mainly it depends on users count, not on no. of connected hubs.

oh and one thing, you've missed UserMap.h file in src... :)