IF the file you have CONTAINs MORE bytes THAN what is shown on the srrDB page for the RElease:
1. META-data has be ADDed to the file
2. The file has EXTRA bytes PADded ONto it — usually at the END of the file.
These ALTER the file’s HASH.
The srr.exe SEEMs to CHECK the bytes when it is SEARCHing for the SOURCE file to RE-scene and RE-sample the release.
If it is NOT the same — it will ASSume this file is NOT the one it is looking for, check the OTHER files when it is FINISHed and UN-able to find a match — it REport an ERRor.
SOLUtion(s):
1. RE-move ALL the meta-data from the file’s property DEtails tab
2. USE a HEX editior to OPEN the file and DElete the extra bytes from the file
└ To RE-store the file, use the “Search” and/or “GO to” option in a hex editor, COPY the file size from the release page to use it as the OFF-set in DECImal mode, RElative to the beginning of the file, HOLD the “Shift”, “Control” keys and press the “End” key to SELECT ALL the data AFTer where the cursor is, delete it and SAVE the file.
This SHOULD give you back the ORIGINal file, CHECK the file hash Against the one on the release page.
IF it MATCHes — you can use srr/srs/srrGUI.exe on it.