By trial and error. This is what pyReScene tries to do when reconstructing compressed RARs.
There are still lots of bugs in this algorithm and the code for this is experimental.
The -e parameter can't show this info since it isn't stored in the .srr file.
A file ".srr" is created based on the original files from the scene. The file ".srr" could be storing the version of WinRAR used in compression.
Using the WinRAR, or files "rar.exe" or "unrar.exe", or other program, it is possible to know which version of WinRAR was used in a file Compression?
The program "srr.exe" uses trial and error.
But I have all versions of WinRAR. The program was wrong in all attempts!
I dont understand. One of these versions was considered correct at the moment of creation of the file ".srr".
The file ".srr" could be storing the version of WinRAR used in compression.
It isn't. The only version number that is stored, is the minimum version required to extract the compressed files. WinRAR can't do this either afaik. Lots of versions always give the same result (or for certain settings).
The program "srr.exe" uses trial and error.
Yes, but it does not cover all known configurations properly. Certain files will require different behavior. e.g. solid archives or very small files
There are at least 2 observations on how to improve this, but this isn't high on my priority list yet.
The .srr creation does not inherently require unrar. Unrar is only necessary to recurse compressed RAR files (vobsubs). It just backups the meta data in the same way it does for uncompressed archives.
After a HD crash, some files can be recovered and some files can't.
What if for example I have the original .iso of a game, completely fine and also some of the original rars.
Can the original rars help rebuild the archive if a complete rebuild doesn't work?
For example I have game.iso which is 100% good and I have 60/90 rar files that are 100% good with the sfv match.
Is it possible to use the 60 good files to complete the missing 30 rar files in between?
Would be a cool feature if it was possible to use the information of the rars that are good and thus increase the chances/speed of fully rebuilding the release.
I'm going to differentiate two cases: whether or not compression was used.
If no compression is used, and there is no .srr available, and you have the archived contents with original sfv, the tool rerar can be used to try and recreate the original uncompressed files. Having existing RAR volumes can make this process feasible. You can detect a bunch of parameters from a rar.
Since you talk about a .iso game and a reconstruction failure, compression was used. Having the original rars won't provide any additional help. (it can though when only a single volume failed reconstruction and you happen to have that one) Theoretically it could be used to speed up the process, but we'll always have to use rar from WinRAR and compressing it all has to happen anyway. Any speedup would be barely noticeable anyway.
The only thing that needs to happen is making the reconstruction algorithm work for all cases and guess the correct case faster.
There are places where you could try to find the missing files.
I run into this every so often and have never found a work-around.
Example:
Zero_Escape_Virtues_Last_Reward_EUR_3DS-ABSTRAKT.srr
It has 2 Stored Files:
as-vlr.nfo
as-vlr.sfv
It has 3 Archived Files:
file_id.diz
AS-VLR.NFO
AS-VLR.3DS
If I put the correct source file, AS-VLR.3DS, in my srr directory along with its .srr, Zero_Escape_Virtues_Last_Reward_EUR_3DS-ABSTRAKT.srr
I get this error:
G:\SRR\new>srr Zero_Escape_Virtues_Last_Reward_EUR_3DS-ABSTRAKT.srr -z g:\rarout
SRR file created with pyReScene Usenet 1.5.
Re-creating stored file: as-vlr.nfo
Re-creating stored file: as-vlr.sfv
Re-creating RAR file: as-vlr.rar
The file does not exist: G:\SRR\new\file_id.diz.
Is the issue here that whoever created this SRR package did it wrong and omitted the file_id.diz ?
If so, is there a way I can attach the correct file_id.diz file to the .srr when I locate it, so others that stumble across these errored .srr files can still process them?
No, the .srr file was created correctly. You are just missing archived files: after extraction files were deleted.
In the future there might be something to attempt to include these small files to aid reconstruction. (nfo, diz, cue,…)
Something you could try is adding the -f switch:
-f, --fake-file fills RAR with fake data when the archived file isn't found (e.g. no extras) this option implies --no-autocrc When reconstruction succeeds, you only have to replace that one broken file from some other source.
This is a naming convention of how to add these files to the SRR:
http://rescene.wikidot.com/faq#reconstruction
(we want to differentiate them with the files not inside the rars)
Doesn't work for me, but then again - maybe I'm not doing it right. (happens all the time with me, just ask my wife…)
It seems to me the file_id.diz would have to be in the Stored Files list since it is required in order to ReScene the original set.
This is especially a problem with files like file_id.diz since every set that uses it uses the same exact name.
.NFO filenames are (usually) unique to the set, but file_id.diz is not.
Adding the -f didn't work :(
I get:
G:\SRR\new>srr Zero_Escape_Virtues_Last_Reward_EUR_3DS-ABSTRAKT.srr -z g:\rarout -f ab98763d df702e72 file_id.diz G:\SRR\new\as-vlr.rar Traceback (most recent call last): File "C:\pyrescene\rescene\srr.py", line 514, in main File "C:\pyrescene\rescene\srr.py", line 267, in manage_srr File "C:\pyrescene\rescene\main.py", line 1276, in reconstruct File "C:\pyrescene\rescene\main.py", line 1656, in get_rar_data_object File "C:\pyrescene\rescene\main.py", line 1927, in compressed_rar_file_factory KeyError: 'file_id.diz' Unexpected Error: 'file_id.diz'SRR file created with pyReScene Usenet 1.5. Re-creating stored file: as-vlr.nfo Re-creating stored file: as-vlr.sfv Re-creating RAR file: as-vlr.rar File not found, using fake file. Trying to rebuild compressed file AS-VLR.NFO. G:\srr\new> This looks like a bug. Try again, but don't have the file_id.diz file in your G:\SRR\new folder. Maybe then the error won't occur.
PS3:
http://pastebin.com/ssABWq4Y
PC:
http://pastebin.com/V4aaa7gY
"these would be nice to find ;)"
Still no-go, and it seems there are many .3DS archives that are no-good.
They cannot be Re-Scene'ed using this tool as it cannot re-create the file_id.diz file needed to re-create the package :(
this is a well known problem and why this tool is not used very much for console games.
i think 100% of the ABSTRACT srr files are bad and useless as this cannot remake them back into rar files.
the makers of this did not know how file_id.diz files works - so they thinked they can be left out.
the srr files are indeed created badly by the scene groups - it is not really this programs fault that the people that wrote it didnt make it completely idiot proof so the console gamers couldn't screw it up like this.
i guess no one on either side realized that the file_id.diz was needed to re-create the package file - so you are 100% out of luck and all of these .srr files in the database are useless space takers :(
someday someone will need to remove all of these useless entries - but there are literally thousands of unusable files on the .srr database that used file_id.diz that no one tested so i wouldnt hold me breath to wait :)
and sorry my english is not very good yet - im still learning but im old-school programmer and it takes longer :)
I am trying a similar scenario. I have the release unrared. I have a repacked rar set that is damaged. The meta data is complete in all files but the data is damaged. The rar set is compressed and has a recovery record. Recovery did not fix some the damaged rars.
Test:
can srr work to fill the missing data?
I am currently testing the rebuild from a srr created from only the good rars.
If you have all the original data extracted, srr could work to recreate the original archives. It's still a hit and miss though.
OK, thanks for the info.
I gave up trying to get this to work with most all .3DS libraries as it fails more often than it succeeds.
-sm
i think 100% of the ABSTRACT srr files are bad and useless as this cannot remake them back into rar files.
The SRRs themselves are perfectly fine and backup data as intended.
the makers of this did not know how file_id.diz files works - so they thought they can be left out.
It isn't relevant for RAR files. No use to add them to the RARs in the first place. I guess there will be something when I've done ZIP. https://en.wikipedia.org/wiki/FILE_ID.DIZ
the srr files are indeed created badly by the scene groups
Scene groups don't create the SRR files.
i guess no one on either side realized that the file_id.diz was needed to re-create the package file
Wrong. How about the third side that decided to extract the RARs in the first place and threw that info away?
these .srr files in the database are useless space takers
It still gives valuable info.
someday someone will need to remove all of these useless entries - but there are literally thousands of unusable files on the .srr database that used file_id.diz that no one tested so i wouldnt hold me breath to wait
No. It has uses outside your narrow perspective.
and sorry my english is not very good yet - im still learning but im old-school programmer and it takes longer :)
Start by using a spell check instead of apologizing each time you put something on the internet. That's just laziness. Your English is well enough to get your message across, so no need to apologize for that or the internet would be full of apologies ;)
I Tried everything to rebuild an mp3 release. Didn't worked
I installed every software (python, rescene, resce.py, crc, unrar)
But i still get nothing
C:\>cd python27
C:\Python27>python
ActivePython 2.7.10.12 (ActiveState Software Inc.) based on
Python 2.7.10 (default, Aug 21 2015, 12:07:58) [MSC v.1500 64 bit (AMD64)] on wi
n32
Type "help", "copyright", "credits" or "license" for more information.
help
Type help() for interactive help, or help(object) for help about object.
help()
Welcome to Python 2.7! This is the online help utility.
If this is your first time using Python, you should definitely check out
the tutorial on the Internet at …………..
Enter the name of any module, keyword, or topic to get help on writing
Python programs and using Python modules. To quit this help utility and
return to the interpreter, just type "quit".
To get a list of available modules, keywords, or topics, type "modules",
"keywords", or "topics". Each module also comes with a one-line summary
of what it does; to list the modules whose summaries contain a given word
such as "spam", type "modules spam".
help> quit
You are now leaving help and returning to the Python interpreter.
If you want to ask for help on a particular object directly from the
interpreter, you can type "help(object)". Executing "help('string')"
has the same effect as typing a particular string at the help> prompt.
quit()
C:\Python27>python retag.py
python: can't open file 'retag.py': [Errno 2] No such file or directory
C:\Python27>python rasce.py
python: can't open file 'rasce.py': [Errno 2] No such file or directory
C:\Python27>python resce.py
Traceback (most recent call last):
File "resce.py", line 12, in <module>
from rescepy.srr import SRR
File "C:\Python27\rescepy\srr.py", line 7, in <module>
import os,rescene,subprocess
ImportError: No module named rescene
C:\Python27>python resce.py bulldozer.srr
Traceback (most recent call last):
File "resce.py", line 12, in <module>
from rescepy.srr import SRR
File "C:\Python27\rescepy\srr.py", line 7, in <module>
import os,rescene,subprocess
ImportError: No module named rescene
C:\Python27>python resce.py bulldozer.srr —output c:Traceback (most recent call last):
File "resce.py", line 12, in <module>
from rescepy.srr import SRR
File "C:\Python27\rescepy\srr.py", line 7, in <module>
import os,rescene,subprocess
ImportError: No module named rescene
C:\Python27>python resce.py bulldozer.srr —output c:Traceback (most recent call last):
File "resce.py", line 12, in <module>
from rescepy.srr import SRR
File "C:\Python27\rescepy\srr.py", line 7, in <module>
import os,rescene,subprocess
ImportError: No module named rescene
C:\Python27>python resce.py bulldozer.srr —output c:Traceback (most recent call last):
File "resce.py", line 12, in <module>
from rescepy.srr import SRR
File "C:\Python27\rescepy\srr.py", line 7, in <module>
import os,rescene,subprocess
ImportError: No module named rescene
Rescepy wasn't easy to get working on Windows. This was my attempt: http://rescene.wikidot.com/rescepy
This is how you could set up pyReScene to run from source:
http://rescene.wikidot.com/pyrescene-installation
It is probably the easiest for you to run the .exe file.
hi,
first of all, thanks for this amazing application and the hard work behind it!
i have also had issues regarding the small size files (rescene process failed), especially .cue files of older game iso releases, but i have gathered a little experience that might be helpful for fixing this annoying bug in the future.
the older game iso releases contain a cd image file (.bin) and a cue sheet (.cue), the trick is the place of the .cue file within archive.
when the .cue was placed in the first rar fragment (.001), the pysrr (0.6, win) wanted to find proper rar version for it without any success, regardless of trying the final retail versions only, or the full scale rar folder containing the betas too. in both cases "no good rar version found".
i have also tried to use older versions of srr.exe (0.4 win, 0.5 win). strangely, these were able to find a "proper" rar version (2.6), but it seemed to be odd due its overdated version for a f.e. 2003 release like Harbinger-FLT. after matching the .cue with the "proper" rar version, the software continued to look for proper rar version for the .bin file without success, just like before: "no good rar version found".
i wanted to rescene the followings:
The_Lord_Of_The_Rings_War_Of_The_Ring-FLT
Tomb_Raider_4-FLT
Heroes_of_Might_and_Magic_III_Shadow_of_Death-FLT
Harbinger-FLT
their common thing is that all of these games were released by FAiRLiGHT, having the same approach: placing the .cue into the first fragment (.001), thus the rescene process failed everytime due to the lack of proper rar version for the .cue file.
i have also tried to remove the .cue file and fill up its presence with fake files (-f), but the result was the same: the process moved on to the .bin file, but "no good rar version found".
in parallel, i had some DEViANCE and RELOADED releases to rescene, and the process worked every time:
THE.MOVIES.DVD-DEViANCE
The.Movies.Stunts.And.Effects-RELOADED
GHOST.MASTER-DEViANCE
Postal.2.Apocalypse.Weekend-RELOADED
HOMEWORLD-DVNiSO
again, the difference between these releases and the FLT releases is the position of the .cue files within the archive. the last rar fragment contained the .cue file, thus the rescene process started to look for proper rar version for the .bin file first. after detecting the proper version, the archive was created up until the last fragment, into which the .cue file should have been inserted. the rar version detection was started for the .cue file, trying out every single rar version (betas too, so it took for ages…) without success ("no good rar version found"). however, the process moved on: it created the archive fragments up until the last one, and added the .cue file into the last fragment probably "as it is". this resulted in a proper final fragment with proper CRC number, the rescene was successful. (i can upload some pics about the process, if needed.)
i am not an IT guy, so i am just guessing, but maybe the .cue file was inserted into the last rar archive file without any compression or manipulation.
in case of the FLT releases, the pysrr process wants to compress the .cue files the same the .bin files are compressed. this compression alters the first rar volume by altering the cut-point of the .bin arhive, and the rar detection process fails.
is it possible to leave the .cue file out of the rar detection process, by inserting it as it is (unchanged, uncompressed, unmanipulated) into the first volume, and look for proper rar version for the .bin file afterwards up to the rest of the arhive fragment size?
i hope these case studies help you anyhow, and thank you again for everything.
rescene is amazing!
best regards,
zoltan_g
Here again, on 0.6-rc2:
Release is Super_Smash_Bros_v1.5_EUR_MULTi8_3DS-PUSSYCAT
