Quote:
Originally Posted by drbits
As I feared, the log contains a lot of information about the extraction, but not the extraction path.
Please post the links for gat109 and I will see if this problem has been fixed in the text version (NIGHTLY). If there is another package you think I should try, please include it.
Note: The move to the custom path only works if the only operation after download is the RAR extraction. If it is a Merge, followed by an extraction, it will not move the file (the unrar program itself does the move).
There is a Feature Request filed to make the custom path a consistent feature, regardless of whether this is an unrar, a merge, or just a single file download. That probably will not be in the next release.
My connection is too slow for me to download 20GB, it would take 5 days, 24 hours per day.
|
Links for gat109:
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
**External links are only visible to Support Staff****External links are only visible to Support Staff**
Due to that file size, it should extract correctly - but it didnt. I dont know why. Im gonna download it again, and see what happends.
EDIT: Nope, gat109 didnt extract to custom path. Other files in the list, with approx the same size, did.