• Content count

  • Joined

  • Last visited

Posts posted by en_dator

  1. the 5 hours thingy (or 50 minutes i think is more correct) is a bug. It occurs when you manually searches too often. If you make sure you dont do searches more ofhten than is set in settings it should not appear like that.

    (I dont know where the bug comes from, but i have seen it too, in earlier version there were a messae "waiting for xxx seconds before searching" now instead this weird time scale for searching has appeared).

  2. Something is seriously wrong, thats for sure.

    Nothing of what you see is normal.

    Every setting should be kept between restarts, thats for sure. So either something is stoping the client from saving the files, or something is removing/corrupting them between runs.

    I have no idea what it could be except the usual spyware/virii checks

    Also make sure that you actually have full access to the folder where Apex is saving its settings (xml-files)

  3. somehow i feel quite out of snappy answers today.

    just give the stoneage man his club back and let the rest of us go on with our business.

    (dc++ 0.306 was released jan 9 2004, would anyone use a antivirus program that is over four years old? or go back to netscape 2 ?)

  4. if you dont get any search results back it can only be because one ore more of these three reasons

    1) the string you search for has no match

    2) your search is blocked by the hub

    3) your do not forward your udp port correctly or its blocked by your own firewall.

    of those i'd say number 3 is the most likely

  5. I think you are using the wrong section in your router settings, to me it sounds like you are using a port trigger setup, that usually doesnt work with dc.

    Instead look if you have something called virtual server or similar where you setup one port at a time. Ther eyou should be able to set a port, a protocol and what internal ip to redirect it to.

  6. just remember,

    if you make the DCPlusPlus.xml files readonly - it will NOT save any changes you do to settings, so you must remember to unlock it when you make changes, else they will be lost after a client restart.

    And - this issue can be solved, you can take my word for it :thumbsup:

  7. as a reporter in a computer magazine once wrote "If you want free ram, take it out and nail it to the wall".

    Free ram is just unused resources.

    But its very nice to hear that WSe7en having much better memory management, I sure could use that :)

  8. in cases like this it would be nice if you included things like your OS and version, but actually in this case it might not matter.

    When you did a system recovery your user id has changed, you need to take ownership of the folder where apex is located, if you are on vista you need to add apex to allowed exeptions again etc.

  9. i have three,

    first try the /rebuild command in your client, it will rebuild you hash data files and should make them smaller if they have old data in them,

    second - defrag your harddrive(s)

    third - if your drives are ide, make sure they are not in PIO mode, they should be in DMA or UDMA mode.

  10. The TLS port is just another TCP port, so what you have to do is forward a second tcp port and put that portnumber into the tls box.

    If you have trouble getting that to work you can disable tls all togheter on the security tab in settings.

  11. it sounds odd that it happened when you upgraded to a new client.

    Ordinarily I would suggest that you check this three things:

    * look in task manager so that you only have one apex client running

    * look in windows firewall settings and make sure that there is a rule for your new apex, and that it is checked (and you should do this even if you have windows firewall disabled)

    * verify your port mappings, if you are behind a router please make sure the settings are still correct.

    but if this is connected with using a new client it might not be the correct advice, still might be a good start

  12. for one thing, this isnt ftp ;)

    and even ftp has a limited path length even if it largely depends on host and client implementation.

    is the path longer than 255 characters? at least that long should the client be able to handle.