Crise

Management
 View profile  See their activity

  • Content count

    3008

  • Joined

  • Last visited

Posts posted by Crise

  3. Posted

    What OS are you running?

    He is running XP, that is not SP3. Because that function is present on all versions of windows we support. What I am curious is whether he can run 1.5.9 without getting that error message.

    Edit: that said, after some investigation unfortunately it seems likely that Microsoft has updated their SDK's in a way that basically disregards compatibility with versions of XP prior to SP3.

  5. Posted

    I have got a small issue with an updated 1.5.11 version. After making a clean install I was left with this message window '>. Now, after putting my old settings back in, opening the Download Queue window and right-clicking over the download queue folder gives me the mouse menu view without the header as here '>.

     

    Otherwise everything seems to be working fine. If it helps, my OS is Win XP Pro Sp3.

    The first message seems to be an an installer issue, will attempt to replicate this on my end. As for the second one that is an issue caused by a code change that seems to have been left in accidentally looks like there will be yet another .11 build sadly (because unfortunately it's not just a visual problem).

  6. Posted

    Update: The release of 1.5.11 has been officially rolled out. Full changelog available now. If you haven't done so yet please head on over to the download page and update your installation of ApexDC right now.

    On April 7th, 2014 OpenSSL released a security advisory concerning CVE-2014-0160 also known as Heartbleed.

    This is a serious security vulnerability in the SSL/TLS library that can result in your private data being compromised without leaving any trace whatsoever. You can check for more specific details from the above links. Most commonly used DC clients are affected by this issue, including ApexDC. Earlier today (April 10th) DC++ released a fixed version but all versions of DC++ from 0.799 to 0.841 and their derivatives are vulnerable. The specific ApexDC versions affected are at least 1.5.3 through 1.5.10.

    It is important to note that even if the DC++ base version differs from those listed above a client may still be vulnerable as long as it uses one of affected versions of OpenSSL. There is currently, however, no easy way for users to tell what specific version of OpenSSL is used by a particular client.

    Reading this you may be thinking: But, I am not using SSL/TLS at all right, because I am only on NMDC hubs. This is actually not necessarily true because a select set of clients, such as StrongDC and its derivatives, including ApexDC implement an unnamed NMDC extension that allows TLS to be used for client to client connections between supporting clients. Thus making these clients also affected by this issue outside of ADC and ADCS..

    Two hours ago, version 1.5.11 of ApexDC was uploaded to SourceForge and is listed as the latest download there. Likewise the download links on this site now also point to those files. Release announcement including full changelog and all that important information will be made available sometime on the 11th, but for now suffice to say 1.5.11 will fix the issue discussed here as well as a set of other issues found in 1.5.10.

    Lee and Crise like this

  7. Posted

    Hi,

    I am having a problem with my apex dc++.

    It is taking too much time to share my files. It is taking like 7 to 8 hours to share 10 gb of files. I checked with my friend and his sharing took just some 20 minutes.Any suggestions...

     

    Going to need a little bit more than that.

     

    Also,  the total share size is not the only factor. It is in theory faster to share 10GiB's consisting of 4-5 large files than the same size made up by several thousand small files. Anything from where (network drive, slow USB drive) the data is to what condition the drive is in (physically or in terms of fragmentation) can be a factor.

  8. Posted

    Will you guys stop developing for XP once Microsoft's support stops?

     

    Or, I should ask, will future Apex updates work with XP once April 2014 rolls around? Even if that answer is "unofficially", I would be happy!

     

    If I could choose as I like I would drop XP support the exact moment Microsoft does, because retaining XP compatibility is a pain. The people who use our binary/slim release know why, because we have to make separate binaries for XP (thanks Microsoft), our installer obfuscates this fact from majority of the users. So that is four binaries per release.

     

    Whatever we will decide to do, I can say with some confidence that 64bit binaries for XP will cease to exist, mostly because 64bit XP is rare, and has always been rare.

     

    The actual action plan regarding XP is to deploy an opt in system for gathering certain anonymous configuration data from users such as their operating system version and a make and model of their CPU. This will allow us to make informed decision on where to go with things like what operating systems to support or what compiler options we can use when deploying builds for future releases. Eventually this might extend to certain configuration options such as whether users use some features or not. Because quite frankly ApexDC has a severe case of "option shock" when it comes to new users. So when it comes to some options we would either like to cut them or make then the default behavior without an associated option (this later part is something that will happen earliest for 2.0).

     

    If it weren't for the fact that we "need" (XP binaries can run on newer windows versions) separate binaries for XP already then we would probably keep supporting XP unofficially, but as it stands even if we do not intentionally break support for XP in terms of used API's the compiler is already making dropping it an appealing option and most likely subsequent releases of the compiler will do it for us because I don't see the next version of msvc supporting XP at all when the last two are already doing it through a separate toolset resulting in the need for specifically targeted binaries (which was added by Microsoft reluctantly to begin with, so I don't see it sticking around in msvc 2014).

  10. Posted

    What version?

    1.5.9 currently has a known issue starting up on some machines. Please try 1.5.8, while this issue will be fixed for next version. If you have a particularly old CPU you may need to use the binaries intended for Windows XP regardless of your version of windows. You can do this by downloading the "slim" binary distribution.

    If you are on XP already our installer will use the correct binaries automatically. If you do not have the latest Visual C++ redistributable installed (2013) the installer will also install that for you. Alternatively you may download and install it from Microsoft directly.

  12. Posted

    Prefixing nicks with supposed connection type/speed has been going on in DC for as long as I can remember.

     

    As for why their nicks otherwise are of similar I can not say, the first thing I would do as a hub owner if I saw multiples of the kind of users you describe is check whether they share obvious viruses (such as small exe files with names that would fit other file types better, or the same thing but zipped). Because those nicks smell randomly generated.

  13. Posted

    My problem is that the queue doesn't get processed despite plenty of availability for sources.

    Often I find apex not downloading anything at all, until I do a search for some of the items in queue than apex starts downloading all the available files at full speed.

    The problem is that I need to be at the PC to do that every now and than so not very practical.

     

    Try tweaking your settings under Downloads > Queue (particularly priority settings, and make sure "automatically search for TTH alternatives" is set to a sane value, ie. not too low, hubs get annoyed when you do that and start ignoring TTH searches). You might also want to try enabling/disabling auto priority and see what that does.

     

    If something you changes resolves it, please let me know... I might need to work on the defaults in this area because this is not the first I have heard of similar problems.

  14. Posted

    For 1) the option is no longer there but the behavior should be same as when that option was enabled on older versions (ie. the option has been removed the persistent search history is still there)

     

    For 2) check your settings under Downloads > Limits (I assume your bandwidth limiting is off, if it isn't then, even if you set the limit higher than your maximum connection speed your speeds will be affected to an extent because of how the limiter is implemented).

     

    Edit: looks like persistent search history was unintentionally deactivated, will be resolved for next version.

  16. Posted

    I have exactly the same problem with version 1.5.9. No start, clean install, WinXP Pro SP3 32bit, shift pressed doesn't help.

    One core of my CPU is chewed 100% while trying to start.

    Do you call it a bug?

     

    For XP, please make sure the binaries you are using are correct (if you used the installer this should already be the case, if not the correct binaries are under the XP directory in the archive).

     

    With the info I have from this topic it is difficult to pinpoint the cause. Does the splash screen get shown at all? if it does, does it show any messages at the bottom of the splash screen before hanging if it does, what was the last message.

  18. Posted

    Is this a new clean install? Or are you migrating something over from another client.

    Did the installer install Visual C++ dependancies on your machine?

    As for different versions you should be able to try with 1.5.7 or newer. Although I can not think of a particular cause for this.

  19. Posted

    Try holding down shift and then launching it while holding it down. Then open your hubs manually from favorites.

     

    How many hubs do you have in your client set to auto connect at start up?

     

    Also does the hanging ApexDC leave behind an exceptioninfo.txt file in its directory, if so please upload it here.

  20. Posted

    That is indeed excessive. After looking into it, It will keep trying to contact the update server more often if it fails to reach it. We will fix that in the next version. :)

     

    That is an understatement, it keeps trying until it succeeds, which is excessive, because the time stamp for an update check is only updated on successful check (a slight oversight on my part).

     

    But using the phrase phone home for a 3 KiB static file download (2 KiB for the xml, 1 KiB for the signature) is hardly appropriate either. There is no data being collected. Well not anymore than you have being collected when you browse this site I'd imagine (which is standard, non-verbose, nginx access logs that are deleted automatically after a few days), the only instance where I ever look at access logs is if php fails without producing a stack trace.

     

    ApexDC does support http proxy as well, although a rather simplistic one but it does work.

     

    If we were interested in user data (without users consent), there would be about a dozen more effective ways do it that couldn't be bypassed as easily as the update check. So the claim that we would obfuscate the update server to achieve this is ridiculous.

     

    The most we might ever be interested in data wise is stuff like what operating system most of our users use, which leads into when we drop XP support for example because keeping it around is a major pain. But really if we had the time and interest to go looking for user information unannounced don't you think we would at least be smart with it and not spam the users system log about it. Common sense is golden. If we ever decide to collect usage statistics it will be entirely opt in and public (it couldn't be any other way anyways since we are open source).

  21. Posted

    It was just an idea, because it would make it easier for Operateros to search for forbidden files, like in ADL Search. That was all it was about! :)

     

    Let me give out a little known fact, searching files through a hub has a protocol level hard limit of 10 or 5 (passive) results per each unique user. So in that sense you should always search for undesired files through ADL search because that goes through the entire share.

  23. Posted

    Maybe it would be possible to add RegExp as filetype in Search as an option! :blink:

     

    While making this happen is possible, it would very much be an ineffective feature addition. Because it would only work between supporting clients and while most existing clients have regex in some capacity in them they would need to support this very specific feature for that to be of any use.

     

    Edit: if you want to push for this to happen I would make the request over at DC++, because one it would need to be drafted and created as an extension to ADC and by DC+ supporting it would also mean wide support in clients.

     

    However, even with all this, it would only be functional within ADC hubs not on your run of them mill NMDC hubs because NMDC protocol development has essentially ceased in favor of ADC.

  24. Posted

    ZPK: First of all your link was wrong and second, you can't download those files without a password anyways.

     

    Also there is a reason why these builds are not generally available. Past experience has shown us that once a build is sent out there it stays out there. Because these versions are early and have a considerable amount of issues, some more severe than others. We would rather not find them hanging out in the open year down the line.

     

    Another reason is that it is more practical, because our version control is not public currently and we are not prepared to keep a full source archive of every uploaded build (for multitude of reasons server resources being one of them) it is currently more manageable to handle GPL on per request basis (ie. make a source archive available when someone with access to said binary requests it, see the GPL, version 2, FAQ or license text for more details).

     

    For the record, currently for non-windows systems access is generally given for anyone requesting it... just that it might take some time :).

    SamuelBift and handythurry like this

  25. Posted

    Thank you very much for this thread, however I had a rough time to find it. It does not come up through the search box.

    I would like to know if there is a location where I can find additional themes.

    If no such location exists, can we have make up one. I also failed to locate the customisation page.

     

    Many thanks to all who put a lo of effort into DC++

     

    http://www.apexdc.net/customise/

     

    That page has not been updated in a while though. There is no real proper central place for themes, because there is no well defined format for them (meaning most clients change things around, so that one clients themes do not work, or only partially work for other clients).