Auteur Topic: Powerpost - limitation creating par2 files from large binaries  (gelezen 438 keer)

dgg

  • Nieuweling
  • *
  • Berichten: 1
    • Bekijk profiel
Powerpost can create par2 files with any block size. Normally the block size will be 384000.   After parts have been downloaded from a newsgroup, most windows people use quickpar to verify and repair the files.   The maximum number of blocks is just over 32000 (a power of 2), and this implies a maximum file size of approximately 12 Gb.   

I just downloaded a BIG set of binaries.  It turns out to be about 14 Gb.   The par has 36370 blocks of 384000.

I think this is a limitation set in the par2 documentation. It's certainly a limit set in quickpar. see http://www.quickpar.org.uk/forum/viewtopic.php?id=1098 or do a google search.

The guy who posted these files is obviously unaware of this problem. Luckily the guy realised after posting, and created a new set of pars using quickpar with a 5 Meg block size and therefore only 2920 parts.   Therefore I can repair one broken part. 

I am not asking for Powerpost to be rebuilt completely - but it would be helpful if it warned users they are setting a par2 block size which will exceed 32000 blocks.

With many thanks for supporting an excellent program,

best wishes,

D

Timothy

  • Forumbeheerder
  • Volwaardig lid
  • *****
  • Berichten: 127
    • Bekijk profiel
    • Powerpost
Re: Powerpost - limitation creating par2 files from large binaries
« Reactie #1 Gepost op: 27 mei 2011, 21:42:45 »
Interesting stuff.
will look into that...

Isis55423

  • Nieuweling
  • *
  • Berichten: 3
    • Bekijk profiel
Re: Powerpost - limitation creating par2 files from large binaries
« Reactie #2 Gepost op: 25 december 2011, 23:14:57 »
Interesting stuff.
will look into that...

Please note that the 'MaxLines_UPPER_BOUND 12345' does not match the Powerpost range of 500-32000.
===================================================
BOOL CProgramSettings::LoadFromRegistry()
{
   CWinApp* pApp = AfxGetApp();
   CString S;
   char szKey[32];
   int k, nSize;

   int   nDefault_BWCap                  = 0;
#define   MaxLines_UPPER_BOUND 12345
   int   nDefault_MaxLines                  = 3000;
===================================================
Also, it would be helpful if the range of 500-32000 were increased to 500-64000.

There are NSP's that will except this limit, and it is really not in the purview of the posting application to set limits that are the province of the NSP.

It has long been the accepted practice in posting to restrict the number of files in any given post to no more than double digits.

Likewise, this same restriction has been applied to the number of articles in any particular file.

Until now, the 4096 KB article size limit has been more than adequate, since a post seldom exceeds 8 GiB, but with the advent of the BD-50 data discs, these limits have proved to be completely inadequate.

Access to the 32K-48K yEnc line count range (4MB-6MB) is necessary to create manageable BD-50 posts.

You wil see some posters who are posting these monsters without even using the currently available settings, i.e., they are using the old Powerpost default of yEnc 1950 (249.6 KB). This creates NZB files that approach 20 MB!

A 20 MB text file is quite large. You wouldn't want to curl up in your favorite chair and read it, since it is approximately four times the size of 'The Complete Works of Shakespeare'.

It also adds a lot of header data to the group in which it is posted. Fifty such posts would add 1.0 GiB to the size of the group... that would be 1.0 GiB of headers you would need to download if you wanted to subscribe your newsreader to that group.