Page 1 of 1
corrupted files
Posted: Tue Nov 11, 2003 11:12 pm
by frank
downloaded files numbered 30 or higher in the headers continuously seem to be corrupted. filesize is correct. i get so called 'R'-files instead of 'rar'files.
can any setting cause this problem?
Posted: Tue Nov 11, 2003 11:50 pm
by slotboxed
What do you mean by numbered 30 or higher in the headers? Can you give a specific example so that we could try to duplicate the problem?
Posted: Thu Nov 13, 2003 12:24 am
by frank
r- files are rar files with a damaged archive.
i tried to repair them with winrar repairbox but it didn't work.
rar-archive can be damaged but i found it strange that only downloaded files numbered 30 and up were damaged (at several occasions and in different downloads).
i just wonder if a setting can cause the problem.
Posted: Tue Nov 18, 2003 4:56 am
by slotboxed
I'm still not sure what you mean by the 30 reference.
a) more than 30 pieces to a file, i.e. (*/30) or (*/50)
b) old-style rar naming, i.e. file.r30, file.r31
c) something else
The repair function in WinRAR generally requires you to have a .rev file for every part of a .rar set that is bad (not too many people post these). It's generally easier to use .par, .p01, .p02, etc. -or- par2 files to repair a fileset with a par-checking program (I use fsraid for par files and quickpar for par2 - both are free).
Do you have "Supersedes:*" listed and checked (it should be [and it's the default] - supersedes are commonly used to damage other people's posts) in Properties>Articles>Header kill filter?