Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[johnsanc]

I keep getting errors that clrmamepro cannot remove files from .7z archives that were packed with torrent7zip outside of clrmamepro.

I tried using 4.017 with 7z.exe version 9.20, 9.28, and 9.38. None of them work.

I then tried using clrmamepro 4.014b with 7z.exe version 9.28 and it works fine. Any thoughts?
 

[Roman]

Does it work when the files are packed with 7z instead of torrent7z? ...then blame torrent7z (which wouldn't be the first time...)

[johnsanc]

Well, it appears that its an issue with the way t7z archives are packed. It worked ok with an archive I packed with 7z 9.38 with LZMA 96 LC4. Any idea why this is?

I know T7Z is a pain to deal with, but unfortunately a ton of people use it and store their sets in T7Z format.

EDIT:
Looks like 7z.exe version 9.22 is the only one that works properly with this version of clrmamepro when scanning torrent7zip archives.

[oddi]

@johnsanc : the last "good" version is 7z 9.28a, 9.22 too work
Me used 9.28a:)

[oxyandy]

johnsanc,
from memory 9.22 doesn't support renames. (but I would need to test to confirm, but wont be testing)
simple test anyway..
In CMP 'Compressor settings' tick rename, go out of those settings ,
then return (Rename now unticked ?) then that 7z.exe does not support renames, CMP tests it and unticks if test fails.
If still ticked then obviously renames are supported by the cmd line 7z.exe you specified..
9.28a does indeed work perfectly..
But, some of us use a different version of 7z (Installed GUI) such as 9.38 in \Program Files\7z (9.38 definitely fails with t7z archives)
End result we want  all CMP 'updated' archives in t7z format.
So, we force CMP to use 9.28a by actually dropping 7z.exe (9.28a) into CMP program's folder,
set CMP's 7z strings to force LZMA (LMZA2 is default otherwise) and force lowest compression (mx=0) cause we want CMP to do it's work quickly,
because once CMP has done it's task, we then manually "Send Folder" to t7z.exe to recompress only the 'updated archives',
end result = full 'updated' t7z'ed set

[liaodahao]

@oxyandy
Hello,
how to change the compression level of zip? there is only 7z and rar option in the compressor setting.

[Roman]

you cant. Internally the highest one is used for any recompression...and of course you can use 7z, zipmax and others to gain 2,3 more bits and bytes.

I always wonder why people care so much about compression...use extremely slow 7z solid parameters etc...in multi tera byte hd storage ages where your itunes collection or your windows temp folder uses more space....

[liaodahao]

@Roman
 I'm sorry I didn't say clearly. I want to use the lowest compression level, not the highest one.

I always recompress roms with torrentzip after rebuliding, so it's actually unnecessary to compress roms with the highest zip compression during rebuilding, the best way is to compress them with the lowest compression to save time, is it right?

[Roman]

The time bottleneck is torrentzip. The few seconds (if at all) you would gain for a lower compression rate is nothing compared a complete repack by an external program. As mentioned, you can't change the compression level setting.

[liaodahao]

I see. Thank you for your answer.

[what2be]

from memory 9.22 doesn't support renames. (but I would need to test to confirm, but wont be testing)
simple test anyway..
In CMP 'Compressor settings' tick rename, go out of those settings ,
then return (Rename now unticked ?) then that 7z.exe does not support renames, CMP tests it and unticks if test fails.
If still ticked then obviously renames are supported by the cmd line 7z.exe you specified..
9.28a does indeed work perfectly..
But, some of us use a different version of 7z (Installed GUI) such as 9.38 in \Program Files\7z (9.38 definitely fails with t7z archives)
End result we want  all CMP 'updated' archives in t7z format.
So, we force CMP to use 9.28a by actually dropping 7z.exe (9.28a) into CMP program's folder,
set CMP's 7z strings to force LZMA (LMZA2 is default otherwise) and force lowest compression (mx=0) cause we want CMP to do it's work quickly,
because once CMP has done it's task, we then manually "Send Folder" to t7z.exe to recompress only the 'updated archives',
end result = full 'updated' t7z'ed set

Actually, the tick test is incorrect, because I have 9.38 of 7z.exe and when I tick the box, exit clrmamepro and then start it again and look under settings its still ticked, which means either 9.38 works (which I doubt) or the tick test has a bug in the code. (upon further testing, its only if I specify my path \Program Files\7z\7z.exe that the tick mark stays.)

Also, is 9.28 some weird release that was never official? I couldn't find it off either sourceforge or the 7z.org website. All i see is 9.20, 9.21, 9.22 and then 9.34. I had to google it and download it. Look at the screenshot..

[Roman]

if the rename checkbox is ticked, the 7z version you're using supports the rename operation...ir does nit mean nit works flawlessly though...there are sone 7z versions which simply have issues....

[what2be]

I just edited my post to make it a bit more clear. I was using 9.38 which OxyAndy said is a version that definitely does NOT work.

[Roman]

No, that's not what he was saying...
You need to differ between: "7zip rename operation supported" and "works fine with crappy t7z"...

7zip got a rename option since something around 9.28...and that's what the tick box is all about.

[oxyandy]

what2be

(9.38 definitely fails with t7z archives)

The cmd line 7z 9.38 detects 'data past the end of archive' with t7z archives, then aborts with an error msg.