This is interesting. (I haven't actually been trying to d/l these
posts since I already have better copies) But I have noticed in the
past that when there are long filenames Agent fails to create an nzb
file. In that case I've generally been able to just d/l the file
directly in Agent.
Anyway, as much as I appreciate the contributions of a poster, these
posts are cumbersome, you can't even see the filenames they're hidden
by the much too long headers (in my version of Agent anyway). Also it
is helpful to indicate something about quality and source (bluray,
dvd, vhs, etc) since often you want to get a better copy of a classic
if that can be determined from the nfo.
And the nfo might be a better place for the cast of the movie than the
headers.
On Tue, 09 Jul 2019 15:16:27 +1000, Lurker@Large.org wrote:
>If you are using Agent version 8 to download posts with long file
>names such as this one, then you may be having trouble.
>
>It has to do with the fact that the file name is well in excess of 100
>characters.
>
>I'm using Win 10 with Agent 8.0 newsreader.
>
>The reason is as follows:
>
>Windows has a path and filename limit of 244 characters. Go here for
>more information http://vlaurie.com/computers2/Articles/filenames.htm
>
>Agent 8.0 has an automatic decoding facility which assembles a file by
>storing the elements until all are present, corrects errors using
>PARs, if it can, and then decoding the archive. Finally it puts the
>decoded file where you requested.
>
>Agent stores the archive elements in a default folder that has the
>following path:
>
>C:\Users\username\my
>documents\attachments\<newsgroup>\<filename>.FILES\<archive element>
>
><newsgroup> is the full newsgroup name ie here it would be
>alt.binaries.multimedia.vintage-film.post-1960\
>
><filename> is the posted filename between the quotes less the unique
>parts such as Part 01, rar etc to give a folder name
>
><archive element> is the filename part in full.
>
>As you can appreciate the path uses quite a few of the 244 available
>characters and it is possible to shorten this if required - see later.
>
>In this case however even shortening the path will not help because
>the file name exceeds 122 characters (spaces count!) and as it gets
>repeated in the path the 244 character limit is exceeded.
>
>When the limit is exceeded the OS truncates the total path and file
>name to the 244 limit.
>
>Unfortunately these truncated characters include the Part nn
>information which identifies the archive element and so each file that
>downloads ends up with a file name identical to an earlier one and
>overwrites it - resulting in a very incomple archive that can not be
>decoded.
>
>Agent allows the user to identify another loacation for the temporary
>files (I'm using C:\Agent_temp\ ) rather than the default which saves
>some characters, but often not enough.
>
>Finally for Straightman.
>
>I'm most appreciative for your continued work with the material you
>are uploading. A very big thank you.
>
>This is my problem and I'll have to accept either an inability to
>access some of that material or a very long winded work around- but if
>it is no trouble for you to limit filenames of the complete work by
>removing the list of actors names from it, then that would be most
>appreciated.
>
>You could include them in a .txt file for those who want this
>information - but it's also readily available with a quick search via
>one of the many search engines using the title ( and year, if
>necessary)
>
>Regards
>
>L@L.
>
>
>---
>This email has been checked for viruses by AVG.
>https://www.avg.com
|
|