Fangs404

Member
 View profile  See their activity

  • Content count

    9

  • Joined

  • Last visited

Posts posted by Fangs404

  3. Posted

    You need to use the boot options (dcppboot.xml) to disable the "local mode"

    Read more about it here: http://bazaar.launch...3A/dcppboot.xml (please note, however, that since this is from regular DC++ the option in the installer mentioned does not exists in ours), but otherwise disabling local mode manually will have the effect you are looking for.

    Also eventually we will disable local mode by default but we decided it was best not to do that just yet.

    Good deal. Thanks!

  7. Posted

    None of my mapped network drives show up in the file list where you select what to share. Also when I try to browse for the default download location the Mapped Network Drive does not show up as an option. If I go into windows explorer the Mapped Network Drive appears just fine as drive Z. I am running Windows 7 32-bit.

    I actually just started having this problem today. I have mine mapped to Z: also, and I'm running Win7 64-bit. I was sharing just fine for the last week, but I launched ApexDC++ today (as admin), and all of a sudden, it didn't see the mapped drive. However, when I don't run it as admin, I can see the drive alright.

  9. Posted

    I've been active in the DC community for quite some time now (I co-develop NextHub), and I just stumbled onto ApexDC++ not too long ago after using StrongDC++ for a while. I quite like it, but I have one gripe. Currently, the settings are stored in the Settings directory inside the install directory. I noticed not too long after I began using it that I was experiencing some strange errors. When I closed the hub, it would always ask me if I really wanted to close it even though I repeatedly told it to remember my decision. Then I noticed that I was getting the popular "Error saving hash data" error. I instantly recognized the problem, ran it as administrator, and voila, the problem is fixed.

    The problem is that the settings are being stored in the install directory. The installer naturally installs to %PROGRAMFILES(X86)% (I'm running Windows 7 64-bit Pro). This is fine because that's where it should install. However, administrator access is needed to write to that directory. This isn't a problem during installation, but it is when the settings need to be written/updated. As a computer scientist, I recognized this right away. However, other users on the hubs that I recommend didn't understand why their settings weren't being stored properly.

    There are 3 solutions to this problem:

    - Run the program as administrator at all times (as recommended at http://forums.apexdc...cess-is-denied/).

    - Install the program elsewhere (perhaps to C:\ApexDC++).

    - Save the settings in the correct location (%appdata%\ApexDC++).

    I was shocked to see that a project manager is actually recommending running the program as administrator at all times. This is terrible advice and should absolutely not be carried out because it sets a bad precedent for other developers/users (it's a terrible security hole).

    The 2nd solution might be more viable if it were the default install location for the installer, but it's not. Most users will install a program to the default location given in the installer, and it's expected that the program should fully function from this location. Installing to the root directory is bad practice anyway, so this really isn't a great solution either.

    The third solution is the most appropriate. The program is indeed installed to program files, and the settings are stored in a local user directory where the user is guaranteed to have write access.

    The reason I have placed this thread in bugs is because it really is a bug and needs to be fixed. I hope the developers understand this problem and why changing the settings to %appdata% is the only real solution here. Thanks for the solid software, and I look forward to this being fixed in the future.

    Fangs404 likes this