If your download is corrupt, running QuickPAR on it
should reveal that and, most likely, correct it. Make
sure you download all of the PAR2 files and use the *.par2
file to run QuickPAR. You can get QuickPAR free at
www.quickpar.co.uk. There's also a tutorial there on how to
use PAR files.
Don't worry about the apparent size problem. First off, a
"gigabyte" means different things depending on what units
are intended (i.e., in multiples of 1000 or 1024 bytes). But
beyond that, a binary post is encoded as characters for the
purpose of conforming to the USENET protocols, which will
only take character based data. The character encoding will
always be larger than the original.
The details are complicated and you can explore them in
more depth by doing some Google searches, if you feel so
inclined. But in the meantime, corruption can be diagnosed
and probably corrected using QuickPar.
I hope that helps!
--bear
|
|