![]() Mode while, at the same time, leaving free of such inconvenience those who can be downloaded normally. Resultant message, but specifically only for the files that actually are somehow limited to be downloaded in free Would it be feasible JD2 handles these kind of cases correctly? I mean, applying the limitation and showing the Note that in none of the cases I tried to use a new IP, or a new proxy connection. Which will somehow remove the incorrectly limtated downloadable files. The "restart" workaround, I simply have to reset a disposable random file I left around just for these cases, Will keep triggering the caution message for the rest of "non-limited" files as well. In this case, after trying to initiate the download queue and even after disabling it, a "limited" file In the second video, I show you an example of what I talked about in point number "2": The non-limited files can be downlaoded normally (either by starting the queue or individually). Then, after restarting JD2 and disabling the "limited file" so it doesn't trigger the limitation again, The "Bandwidth." (or "Skipped - Account is Missing" in other cases) message will be keep showing up. Disabling the problematic file and trying again will have not effect at all If there is at least "one" of the "limited" to download files in the queue, and it is startedīefore any of those who can actually be downloaded ("non-limited" ones), they will be wrongfully **External links are only visible to Support Staff****External links are only visible to Support Staff** In the first video, I show you an example of what I talked about in point number "1": Is there a chance you make JD2 retries to download MEGA's links in such conditions, without having to resort to said workarounds? So, in order to use this workaround but without getting any partially downloaded link reset, I added a "disposable" MEGA link, which I can reset freely, just to trigger the rest of downloads' retries after some of the messages show up. This have the advantage of not having to restart the whole program, but at the expense of reverting the files' progress to "0%". This will last till one of the previously mentioned messages shows up again.Ģ- Resetting any MEGA's link. This way, it will retry to download the files after starting the queue again, or any of the files individually. Under such circumstances, I have found only two things will make JD2 effectively retries to download files:ġ- Restarting JD2. JD2 will not retry downloading any MEGA files, even if I have tried some workaround after seeing the messages, like getting a new IP or trying with a new proxy's IP. ![]() Basically, while in "free mode", each time JD2 stops downloading a file because a "quota" or an "account missing" related message is shown, stopping and restarting the download queue will have not effect at all forcing downloads on spare files neither. Hello, I have realized of this behavior long time ago now and finally had the time to report it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |