Crise

I'll get you your response shortly :D

ok, but you should not check for versions as they change like every week... and for developers builds even every other day sometimes... (developers = 4 members + Lee and me, for now)

Well i don't even have the nsis script, because i don't do our installers... and about you wanting to be identical, i prefer not to have too identical mods of ApexDC out there because of the simple fact that then we here can't easily separate them, if problems would pop up...

original plan was to release 0.2.2 on thrusday when Lee would be back. but it might take bit longer...

should not, will take a look edit: was my stupid mistake, fixed (in next ver that is)

this however only affects to testers/subscribers...

did you install over an older DC client install?

that TCP port is in use, change settings or close (the other) application using the port :)

No matter how you put it, this could be considered as harmful feature, and this is why i see it not happening... and if you open 8-10 hubs you should be able to find a fair ammount of files in them...

what were you banned for?

i already did that, see my google link :)

ok then that can't be related to tbi's coding which is a relief to tell the truth...

this is bit of a problem might be related to tbi's code, have you tested if that method still works with SDC++ ? (knowing if that method still works in SDC 2.01 and/or 2.02 is very important to me)

maybe, but i don't think just suddenly dropping connections is good idea (i also haven't taken much of a look at the "exit code" since pwdc) I'll see how it's done atm. and try to come up with better solution, if i can...

if your queue was wiped this is how you restore the downloads: http://forums.apexdc.net/index.php?showtopic=279 (you need to have old dctmp's handy)

you need to make an installer for it, and for that google is your friend :)

how you expect me to do something about it (assuming you speaking about the exe remaining in mem for closing connections)

apexdc.exe remains in memory as long as it takes for it to close all connections... (assuming that i remembered that correctly )

just create directory named compiled in your src dir and you are good to go...

the .bak file doesn't work well as it's overwritten on every launch (as far as i can remember) so when you find out your queue got wiped the .bak file has also already been overwritten... i am not 100% sure if that's how it works, for current versions of SDC (and thus apexdc), but on earlier versions of SDC that was how it would have worked... about your actual problem, i cannot say much since it could be a lot of things going wrong...

now it does :)

Yes i know, and we came to the conclusion that we will release 0.2.2 very shortly :)

We are disccussing (me and Lee are) if we release what i have now (which is on 2.02 base) as 0.2.2 or wait for 0.3.0.

not in all cases, as if other user uses same nick with the one you want to limit... and i'd see it being more acceptable, if it'd be done the way presented in the pic above...

i'll be commenting to only this as converter can't be made, and the incompatibility is with new versions of DC++ too...