• Content count

  • Joined

  • Last visited

Posts posted by patch1

  1. Only verified downloaded data are saved to disk. If remote client doesn't provide full TTH tree (or provides invalid one), then verification will be based on whole TTH root, so it will be processed at the end of whole file.


    I take it that means [T] is all that is really required to support partial file downloads ([C] is not essential)

    Either way it points to a mldonkey problem.

    Currently looking at replacing it with some other perhaps using X11 redirects on the headless server.

  2. Mek

    I think you are spot on the mark.

    The person I was mainly trying to download from was running a new computer / set up. I got confused as a second person I tried to download from also had no [C] with the same result. When I tried a third person it worked as expected, supporting [C].

    As it turns out the new system I was trying to download from is

    A FreeBSD server, which runs a CentOS vm

    The files are shared from the FreeBSD system to the CentOS box by SMB

    The CentOS vm runs mldonkey.

    Debug window shows

    mldonkey "Supports MiniSlots XmlBZList ADCGet TTHF"

    vs ApexDC "Supports MiniSlots XmlBZList ADCGet TTHL TTHF ZLIG"

    Getting the other user to mount the files via another computer running ApexDC enabled [T][Z][C] from that client.

    Interestingly I could then download from the original mldonkey client using [T][C] but the user list then showed that client greyed out. (still with a blue shield)

    So yes it looks like a problem with mldonkey capability or configuration.

    Anyone know a better client for a headless Linux server?

  3. If a download is interrupted for any reason then it goes back to the start of the file even if 12-50% of a 0.7 to 4.5GB file is already downloaded. Stopping and restarting ApexDC reliably demonstrates this.

    I have noticed this behaviour since upgrading to 1.3.4 which I did from the previous version (1.3.3) via the installer, retaining the previous configuration in the process.

    The downloads start with [T] or [T][Z] ie do not contain [C]

    Enable segmented downloads is ticked.

    I couldn't find any other relevant settings but that maybe as I don't know where to look.

    What am I doing wrong or is this normal?


    I am running windows 7

    ApexDC runs from an ordinary users account (not administrator), and the program is installed into the program folder (c:\Program files\ApexDC\).

  4. My gripe is that the application phones home when started, and this behaviour cannot be turned off (by the average user). I know the justification for why the application downloads an XML file at each start-up, but it is still a privacy violation.

    I agree auto update should be able to be readily disabled by the user, ApexDC then having no reason to phone home.

    I use ApexDC only on an internal network, unmetered by my ISP, and strongly prefer ApexDC accesses no addresses outside this private range.

    I enforce this via my PC firewall, which does prevent ApexDC from phoning home atm.

  5. After adding the path shown below in ApexDC++ 1.3.0 share and then choosing "File -> Open own list", file list appears for a moment and then immidiately closes up. O_o

    If I'll make this path on one directory shorter - everything becomes OK, I can now browse my file list.


    I find ApexDC has trouble rehashing (at start up & refresh) what has previously been added.

    Seams to be more an issue with path length, not depth as I have some long directory names without reaching 15 levels deep.

    Sorry, but only a fool can his share in this way. This is totally illogical and such users should be banned for non-organised sharelist.

    And also fools ask what has already been answered twice? three-times?

    Yep, I can remember asking a similar thing in the past and believe I got a similarly useful answer.

    The point is I would prefer not to have my filing system limited by ApexDC limitations.

    None the less I do appreciate the comment which I interpret as

    "As a programmer of much of the code, I can see much better ways to spend my time than on this feature"

  6. However, I believe it can be even more practical, if we could automate the process of adding releses.

    Agree automating display of what is new on a hub is desirable.

    I suspect the ideal solution varies depending how many users are typically logged into a hub.

    If the hub us reasonably large with many users contributing information with considerable overlap, then a release system displaying the information sorted in topic groups is going to be preferred, probably together with a flexible search engine with saved searches. This was also discussed here. The difficulty being how to create a high level categorized display with minimal effort by the person uploading, where the display benefits the downloading user.

    If the hub is relatively small with only a few users adding new content, then it is probably more efficient to have an easy way to display new content from these users since a time I looked in the past. As this is my situation I'm particularly interested in it. See here of which I suspect retaining the information from previously displayed file lists, then displaying differences would provide the most useful display.

  7. sigh please mods close this thread

    I would prefer it isn't.

    The suggestion is posted in a feature request forum.

    We know it keeps the hash tables, so could re-share when they became available. Safe automatic re-sharing when available would probably also require showing the current share as well as potential share in the setup screens.

    It's inclusion would benefit at least some users.

    It has not been implemented yet.

  8. 3. The file will store 5 of his announces in every catagory (Movies,TV Shows,Music,Games,Other), each announce easylly made in xml format or simular [Movies(Announce name, the folder hash string)],[TV show(Announce name, the folder hash string)].... and so on.

    I agree some method of being able to browse new additions to a users share would be very valuable.

    Similar thread looking at time stamps or difference from previously viewed file lists

    Another more automated announcement script

    The fact there are multiple threads suggesting different methods of viewing what is new in another users share suggests there is a genuine need.

    My order of preference for the solutions is

    1) Filter users file list to exclude things that were there when I looked in the past (old file list filter)

    2) Date stamp other users filelist (problem with file list download time & server compatibility)

    3) Computer assisted announcement thread, as described here. (Could work well but required poster to do work of no direct benefit to himself (only other users)

    4) Automated announcement script. (risks large volume low information density - eg different announcement for each file in multi-part object (rar files, .nfo etc).

  9. Thanks Crise

    It was several things

    I run ApexDC as a normal user (no admin privilages)

    While running my usual instance of ApexDC I choose it update at the start up prompt

    ESS detected the application modification, I clicked allow (as normal user)

    Above appeared to cause 2 problems

    Wrong read write privileges for new ApexDC files (fixed by resetting inherit read/write/ modify privileges to all files in ApexDC directory)

    ESET not remembering application change allowance (fixed by restarting computer, login as administrator, run new ApexDC, approve application modification).

  10. Since upgrading to ApexDC 1.2 I can no longer connect to any hubs.

    Works fine if I downgrade to 1.2 beta

    Works if I disable the firewall.

    Anyone found a way of making them work together?

    BTW I'm running XP professional

    ESET ESS V4, Firewall in interactive mode.

    Firewall log occasionally showing "No application listening on the port" Source Target Protocol UDP

  11. 1) Some method of readily finding things added to some ones share since last I looked. I prefer a local store (or database) of filelist contents as this would be a client side change and storage penalty could be customised by user wanting the feature.

    For discussion / details see

    2) If external drive with share content goes offline, try and reconnect next time file list is refreshed or ApexDC is restarted.

    For discussion see

    BTW, this probably should be a poll thread to give some idea of user priorities (which developer could take note or ignore on a case by case basis).

  12. To reduce the flood of traffic, the information could be specified to be announced to a #annouce (for instance) channel, where only this information is passed on. This makes it quite easy to either ignore the information, or passively monitor it. Additionally, it allows new files to move faster throughout the network, which can help people race for quota and similar.

    The problem with an automated system is it would tend to broadcast detail and not concepts.

    For example if a shared a new album with 20 mp3 songs, would that generate 20 new release messages

    Or if a shared a movie with 40 par files would that generate 40+ new release messages.

    If I renamed a high level directory that may generate 1000's of new release messages (unless there is the facility to restrict monitoring to a subset of the share and I'm carefull to not rename folders within this share) - ??complexity and error prone by naive users.

    A possible solution would be only broadcast the highest level directory which was new (so only announce the folder containing the album or movie, not the individual files). Coding this maybe more difficult though as files a added and hashed one at a time. Some sort of time out would be needed to ensure a further files were not being added to the set, prior to additions being announced.

  13. When I have to shut down and restart a external, it is really no big deal for me to do to my share settings and just click back on the folders, they come right back up and don't need to be hashed again.

    I agree it is not hard for me to do, it simply requires me to be there and notice the problem.

    However I run ApexDC on my folks computer (I put a link in the start up folder). I visit there every few weeks.

    As a result "me to be there" is not a trivial requirement.

    Also "notice the problem" should be done much more efficiently by software than a human.

    So I would like to add support for not automatically un-sharing folders which become (temporarily) un-available.

  14. To see what is new I think I would prefer drop down menu in the file list screen enabling ready display of changes since I last looked at that file list. As described

    The reason is an automatic system would be spammed by minor changes to the shared files. For example changing the genre or album art for several mp3 albums would trigger lots of low value traffic. Renaming a root directory may also generate lots of messages depending how the software was written.


    I fully support some way of readily finding out about newly shared files on small hubs. I suppose I just have little experience with the solutions you propose.

  15. you "forget" bzip2 compression

    I suspect the main problem with sending date information is that would be a change to the server side, so not an improvement a client could achieve. Even if a server added it as well their would be a compatability problem as it is a communication protocol change.

    For that reason I would prefer ApexDC implemented an automated way of presenting changes from older file lists. These file lists are already retained, during a session. They can already be retained (optionally) between sessions. What is needed is to present the user with a menu showing the time stamp of saved file lists, enabling us to readily display recent changes.


    This drop down menu would ideally appear when displaying a file list, along side the "subtract list" and "match queue" buttons.

  16. A fresh install makes no difference, turn off UAC to avoid the problem.

    Thank you Satan, you have saved me a lot of pointless experimenting.


    I would support ApexDC being compatible with UAC at some point in the future is it did not place an unreasonable burden on the program.

    Think its the registry keys for magnet links that cause UAC to react if this association only happened once and not every time a clients starts up would UAC react then ?

    A once only confirmation would be good but I suspect it is Microsoft's way of extorting money from software developer's so it may not be easy to avoid.

  17. With your solution the problem is i run apex on a computer that isnt mine, so i cant go changing the login profiles. Usually i just have it running quietly in the background and no one notices :thumbsup: !

    Yep, trying to do the same thing here.

    Vista ultimate, ApexDC 1.1.0, User has admin rights.

    With UAC running get a dialogue box saying untrusted program is trying to gain control of your computer, each time I start ApexDC

    Yeh, uninstall it and remove all references of it from UAC (via registry also) and that'll sort it.

    Does this really work?

    I had a clean install of vista. Loaded ApexDC 1.1.0 and get this behaviour without ever installing any other version.

  18. Not we. You! how many people need to check FL for changes???


    I do regularly as we have a small hub for (un-metered) local sharing


    I agree with the proceeding analysis though --> time stamp at the receiving end

    Your test showed time stamping adds more than my estimates, suggesting file path is transmitted as incremental changes (compressed) and does not include hash results.

    But now I'm confused, how does ApexDC show I already have the file without the 40 character hash codes?

  19. and FL DL time is the most precious thing !!!


    So if adding a date stamp (to entries in the file list) significantly increases the file size & and makes it incompatible, it probably is not the way to go.

    That leave more intelligent manipulation of the file lists already downloaded, or giving up :)

  20. As I said, good feature, but 'bloat'.


    Sorry I'm not explaining myself clearly.

    I had assumed if the option to delete all filelists on exit was retained it would produce no more "bloat" than you currently experience. Of course if you selected that option then you would only be able to see user additions during a single session.


    I really have no particular attachment to this way of doing it, but I just can't think of another way which retains DC compatibility. What approach would you prefer was taken to find & display recent additions to a users file list?

  21. I just DONT LIKE the 'bloat' it will cause. I don't fancy having 10's of 1000's of file list's in my C Drive, I keep it small for a reason, performance.

    Shouldn't really be that bad. The only filelists on your drive would be the recent subset of files you have explicitly chosen to download and view. Better than what occurs if you disable automatic filelist deletion in ApexDc (or most internet browsers temp folder).

    Leaving the option to delete all filelists on exit is probably reasonable, that way users who just search for things they want can minimise hard disk waste.

    But then again it is the functionality I want, not really that concerned about the particular method used. So if anyone can think of a better or different way of achieving the same end, speak up.

  22. I suggested this way to introduce what's new long time ago, but developers simply rejected it.

    I suppose if you mostly use Hubs with 100s of users it would be of no real benefit, a good search capability would be more appropriate.

    However the hub I use has 5-15 regular users and 2-3 prolific downloaders so knowing what is new would be really valuable for me. (Local hub traffic is unmetered with my ISP)

    Some users are trying to do it by analysing filelists with an external program. Not really ideal but perhaps that is all we can do if ApexDC developers are not interested.

  23. It's just a matter of agreement how programs should treat a file attributes. But in fact you miss the point. I had been talking about getting this data from uploader's side, so downloader can sort file-list by date or use some kind of date/time analysis, e.g. for downloading newest files in share.

    For example someone have a folder with 1000 files you like, from which you downloaded all. Next time you go to the same folder and see 1200 files. Assuming that previous files you had deleted or they are not in your share now, how can you know which files you need? If there is a date of creation you can just sort by it and see if there are files created approximately after last visit and download them. At present for such task you need to keep/memorize previous files - which is really inconvenient.

    What you are trying to do is see what is new in the file list since previous times you looked at that user.

    There is another way of getting this display without modifying the file list download.

    ApexDC in fact already has the data it needs to tell you. It is contained in the file lists you downloaded in the past.

    What ApexDC needs to do is keep the last, say 10 (a settable parameter) filelists from each user.

    Then when you are browsing someones file list, ApexDC could have a drop down menu to select "New files since" --> dates/times of old file lists.

    ApexDC could then high lite folders containing new files. Alternatively it could subtract the old file list, automating the process described here

    If this was based on the hash value it would be independent of changed directories & file names