Understand whole-file SHA-256
A whole-file SHA-256 is a strong pass/fail identity check. If even one byte changes, the whole-file hash changes, but the hash alone cannot show whether the rest of the file is still identical.
NOURFORGE ARCHIVE VERIFY CREATOR · GUIDE
Why create Enhanced Corruption Data?
Preserve chunk-level SHA-256 evidence so Checker can show how much of a changed file still matches the original reference.
Add chunk evidence
Enhanced Corruption Data divides larger files into fixed 16 MiB regions and records a SHA-256 for each region alongside the whole-file SHA-256.
Use Match % after a failure
When Checker receives complete compatible chunk evidence and the whole-file hash does not match, it recalculates the file’s chunks and reports the percentage of reference chunks that still match.
Interpret the result carefully
A high Match % can show that much of the original data remains unchanged; a low percentage indicates broader differences. It is diagnostic evidence, not an automatic repair or a claim that the changed file is usable.
Preserve the enhanced output
Keep the manifest and its enhanced sidecar together, or export Enhanced NourForge Portable Verification Data in TXT or CSV form so the whole-file and chunk records travel in one documented dataset.
Plan the trade-off
Enhanced creation performs additional hashing and stores additional evidence. Use it when later diagnosis is worth the extra creation time and output size.
NEED MORE HELP?
Support is available and feedback is welcome.
Tell us where a guide or workflow can be clearer. Open NourForge Archive Verify Creator support →