roho (guest) 30 Jul 2017 20:25
in discussion General discussion / ReScene » Can't Reconstruct Rar files
Hi. I tried but no luck :/ . Thank you for replying. Will soon try on a 64bit Windows
Recent Forum Posts
roho (guest) 30 Jul 2017 20:25
in discussion General discussion / ReScene » Can't Reconstruct Rar files
in discussion General discussion / Other » [SOLVED] Wrong labels for release group rG
I've fixed the current uploads too:
https://www.srrdb.com/browse/group:rg/category:pc/1
https://www.srrdb.com/browse/group:rg/category:apps/1
in discussion General discussion / Other » [SOLVED] Wrong labels for release group rG
I changed the label detection so new uploads will be in their correct categories.
I think there is nothing wrong with that release. Mistakes happen. See also https://scenelingo.wordpress.com/2013/07/09/same-people-different-groups/
Whatever (guest) 15 Jul 2017 17:40
in discussion General discussion / Other » [SOLVED] Wrong labels for release group rG
"iso-rg" are tagged as games.
this seems to be an I_KnoW release
1944.Bitva.V.Ardenach.AClone.NFO.Fix.CZECH-rG
Maybe it's possible to add some more validation between release name and release files?
Releases usually have an nfo file which also includes the release groups name (at least for games),
something like this may proof useful in finding bad releases.
def check_release(name, nfo_name): for s in '-_.': r = name.rfind(s) if r >= 0: return re.search(name[r+1:] + r'\.nfo$', nfo_name, re.IGNORECASE) >>> check_release('1944.Bitva.V.Ardenach.AClone.NFO.Fix.CZECH-rG', 'i_know.nfo') >>> check_release('ABBYY.FineReader.v9.0.0.724.Professional.Edition.Multilanguage-rG', 'rg.nfo') <_sre.SRE_Match object; span=(0, 6), match='rg.nfo'> >>> check_release('2_Live_Crew-2_Live_Crew_Greatest_Hits-1992-RGN', '00-2_live_crew-2_live_crew_greatest_hits-1992-RGN.nfo') <_sre.SRE_Match object; span=(46, 53), match='RGN.nfo'>
preprardir.exe is in the latest download:
https://bitbucket.org/Gfy/pyrescene/downloads/pyReScene-0.6.1-w32.zip
On the command line you run something like this:
preprardir.exe Z:\rar\windows-input Z:\rar\output
Or you look around on this forum a bit and skip this step altogether: http://rescene.wikidot.com/forum/t-2305676/winrar-pack-2-00-5-40
While such packs are useful for many users, there are drawbacks:
- It is in violation of the WinRAR license to distribute only parts of the WinRAR installers;
- The user is not able to tell if the exe files from these packs are tampered with. WinRAR verifies the signature when extracting files from the installers.
You are trying to run 64 bit windows binaries and they fail to run on your 32 bit Windows.
Can you try the -w32.zip downloads from top to bottom?
https://bitbucket.org/Gfy/pyrescene/downloads/
And then tell me which exe files work and which files fail? It seems they aren't all 32 bits like they claim to be.
roho (guest) 10 Jul 2017 21:05
in discussion General discussion / ReScene » Can't Reconstruct Rar files
I'm trying to Reconstruct Rar files but it's showing error and only creates one file of 64 bytes. here the log:
srrGUI: Process running, please wait…
Traceback (most recent call last):
File "E:\pyReScene\rescene\srr.py", line 566, in main
File "E:\pyReScene\rescene\srr.py", line 307, in manage_srr
File "E:\pyReScene\rescene\main.py", line 1301, in reconstruct
File "E:\pyReScene\rescene\main.py", line 1690, in get_rar_data_object
File "E:\pyReScene\rescene\main.py", line 1976, in compressed_rar_file_factory
File "E:\pyReScene\rescene\main.py", line 2101, in init
File "E:\pyReScene\rescene\main.py", line 2230, in search_matching_rar_executable
File "E:\pyReScene\rescene\main.py", line 2725, in custom_popen
File "c:\Python34\lib\subprocess.py", line 859, in init
File "c:\Python34\lib\subprocess.py", line 1112, in _execute_child
OSError: [WinError 216] This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher
SRR file created with pyReScene Auto 0.5.
Re-creating stored file: fan-msbs.nfo
Re-creating stored file: fan-msbs.sfv
Re-creating RAR file: fan-msbs.rar
Trying to rebuild compressed file fan-msbs.iso.
Grabbing large enough data piece size for testing.
srrGUI: Process completed. srr.exe exit code = 255
[END OF LOG]
I've never tried ReScene before. any help would be really appreciated. Thanks in advance.
I have no idea what I am doing on tutorial on reconstructing compressed rar archives.
The other one was fine but python and preprardir? I don't understand what and where is preprardir? The newest release don't have preprardir anywhere and I feel the instructions are unclear.
I honestly felt like I typed in what just worked like 20 times before but yea got it working. Now for real going to bed.
I don't understand what to do I've been trying for about 2 hours now. I have the winrar_pack-4.20.rar.
I'm following the rescene wiki tutorial on reconstructing compressed rar archives
I just don't get what to do, do I run preprardir in cmd prompt? What do I put for input director and output directory? I feel like I'm just missing something simple. I'm trying to rescene a .iso I've only done videos before and I never needed all this. Going to bed frustrated, hopefully I can wake up to some help :-(
Eselter (guest) 03 Jun 2017 00:36
in discussion General discussion / ReScene » WinRAR pack (2.00 - 5.40)
I received this email on May 11:
# name,organisation,country,email,comment
ReScene Feedback,,,ten.rrssrs.enoyreverofsitsopsihtenon|diassa#ten.rrssrs.enoyreverofsitsopsihtenon|diassa,"I Have python 34 installed so ReScene works with XP.
Two PC Python is not on a PC connected to the internet. How to get the source so can be built or used with Python 34.
At the very top of the Downloads page is a link: Download repository. Go to https://bitbucket.org/Gfy/pyrescene/downloads/ and click the link there because it can get outdated.
A year between builds is a lifetime. And it is nearly a year already since last release.
Depends on all the issues that were fixed. It takes some time for me to figure it out each time too. Run from source if you want the latest and greatest.
It would be helpful if you could allow us to download the source from Bitbucket as an archive. That we can feed to Python (show us how) so we can keep up to date.
It's provided by Bitbucket. Have a look at http://rescene.wikidot.com/pyrescene-installation but it includes more than you need.
Or better make more often releases such as at least once a month or sooner for major bugs found.
I won't include email since this is the same for anyone that doesn't want to mess there internet pc with source code stuff and terminals whatever to get source code.
If Bitbucket was Github there wouldn't be an issue since can download from Github source in an archive.
I think Bitbucket is user friendlier.
Hope this helps you understand that not everyone uses ReScene as you would. So able to help us keep up to date with you. After all how can code survive if people are not using the latest build so able to report problems they have noticed so making this code better for all.
The reason for everyone is the reason I don't include email here because this feedback is for everyone not just me alone.
A simple GUI for internet pc woud help to get all files related to any release on srrdb. Input release name and it downloads to folder we have set in the GUI options. This will save time having not to visit srrdb, searching each release we need and downloading individually each file for the release."
You only need to download the .srr fiie. Files will be extracted upon reconstruction or when you do srr.exe -x file.srr to extract them.
My priorities are the historical aspects first: the collection of meta data, the core components. Others have written tools, so check out http://rescene.wikidot.com/downloads
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
I don't think your CPU matters here, the mt option tells rar to use N threads which it should regardless of actual cpu cores.
Even a single core cpu can run multiple threads it's just slower but the output should be the same.
I quote Gfy from this link I posted above:
-mt is a rar.exe switch to force the amount of threads it must use. By default it uses the amount of cores * 2. (due to hyperthreading)
Normally it starts with 1 and goes up automatically, but certain values can provide false positives: while correct early on, it'll fail later.
And about this:
Anyway if your bad r03 file is wrong in the same place as the one I got you can just use a hex editor and change the affected bytes as mentioned in my other post.
Yes it's wrong in the same 5 bytes as yours (I've eventually downloaded the scene release RAR files as well). And, I know I could fix them with a hex editor (thanks anyway).
Someone (guest) 17 May 2017 22:17
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
I don't think your CPU matters here, the mt option tells rar to use N threads which it should regardless of actual cpu cores.
Even a single core cpu can run multiple threads it's just slower but the output should be the same.
Anyway if your bad r03 file is wrong in the same place as the one I got you can just use a hex editor and change the affected bytes as mentioned in my other post.
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
(thanks for trying to help and for confirming)
I've posted above that only with "—mt-set 8" it completed.
This must be because my CPU is an i7, 4 cores x 2 (due to hyperthreading).
With 1, 2, 4, 16 and 32 it would crash with "Unexpected Error: Still not fine :(.".
With 6, 10, 12, 24 it wouldn't find a matching RAR executable.
Also, using 5x RAR executables older than 5.40, didn't help.
Someone (guest) 16 May 2017 21:25
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
Just tried it and couldn't rebuild it, I also get a bad r03 and it only differs in five bytes according to fc
fc /B good_DB2FC440.r03 bad_385555B4.r03
Vergleichen der Dateien good_DB2FC440.r03 und BAD_385555B4.R03
00E47A22: 9C 9D
00E47A23: 3E B0
00E47A24: FD 9E
00E47A25: EC ED
00E47A26: 4F 1F
Someone (guest) 16 May 2017 20:59
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
try larger mt settings (e.g. 10, 12 or 16), sometimes you get some bad parts if the mt setting is not correct
make sure you only have one rar version in your rar directory
also trying an older rar version this may help sometimes although I didn't see this with rar5xx yet
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
Thank you for replying.
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
1. Issues with compressed files is always a pyReScene issue.
2. Only moderators can confirm .srr files. It's done in batch mostly by checking the release names, uploader,…
