Print

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

[Carbon]

As MAME supports now .7zipped files and I wanted to move to merged sets (this will free about 20 GB on my internal hard disk), I replaced my ROMs with a fresh set from PD.

But verifying the set (even when using an external .dat file instead of the MAME executable as recommanded on PD's site), ClrMAME now complains about wrong names (they aren't), missing ROMs (they're present) and superfluous ROMS.

Maybe this is caused as I'm using ClrMAME on a Mac using WINE? Anybody had success with a similar setup to mine?

[Roman]

If cmpro complains about wrong names you got wrong names. If it complains about missing roms, you have missing roms.

Missing files in general could be also caused by bad/corrupt archives...which is a pretty common problem, especially when non-standard compression tools are used.

It would be good to show an example output (scan results tree window) and the archive file in question.

[Carbon]

I'm not so sure about that.

Here's some MAME output:

Code: [Select]

./mame64 -verifyroms 1941
romset 1941 is good
1 romsets found, 1 were OK.
The same in CMP:

Code: [Select]

1941: Counter Attack (World 900227) [folder: 1941 - size: 3mb]
unneeded folder: Z:\Applications\Emulation\MAME\ROMs\1941\1941j [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_01.4a [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_02.5a [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_05.9a [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_06.10a [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_09.4b [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_10.5b [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_13.9b [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_14.10b [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_17.5c [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_18.7c [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_24.5e [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_25.7e [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_32.8f [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_33.9f [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_34.10f [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_35.11f [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_36.12f [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_37.13f [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_38.8h [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_39.9h [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_40.10h [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_41.11h [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_42.12h [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\41_43.13h [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941j\lwio.12e [not fixed]
unneeded folder: Z:\Applications\Emulation\MAME\ROMs\1941\1941r1 [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941r1\41e_30.11f [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941r1\41e_31.12f [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941r1\41e_35.11h [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941r1\41e_36.12h [not fixed]
unneeded folder: Z:\Applications\Emulation\MAME\ROMs\1941\1941u [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941u\41u_30.11f [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941u\41u_31.12f [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941u\41u_35.11h [not fixed]
unneeded file: Z:\Applications\Emulation\MAME\ROMs\1941\1941u\41u_36.12h [not fixed]


Also, the game runs just fine. There's something else going on here.

[Roman]

MAME's verifyroms function is not a real verifyer...it simply tries to collect the files from anywhere (parent/clone relationships, not caring about name or subfolder depth)....so forget about that....


"not fixed" means that something went wrong during the fixing process...so most likely 7z failed to remove a file....(which can be pretty common if your 7z file is nothing standard (like t7z) or not correctly setup 7z options when using solid archives.

You should show/provide the 1941 archive (e.g. a 7z screenshot)...the subfolder structure looks a bit odd.....and some information about the used mame binary (or do you use a datfile?) and used settings.

Keep in mind that if you're switching to full merged sets cmpro have to handle hash collisions (equally named files with different hashes within a parent/clone relationsship).
Generally it's not really worth it to switch to full merged sets and/or 7z..especially in days where "small" HDs are 1TB.

[Carbon]

It's not "fixed" because I replied "No" when CMP prompted me to do so.

Here's the 1941 archive. It decompresses just fine, and, again, the game runs without any problems.


The MAME binary is a self-compiled Mac OS X version of the official 0.174 release without any changes. I tried CMP with that binary and with a .dat file from PD with the same result.

[Roman]

ah...The sets you've downloaded are in "hash collision name" full merge mode....This means someone used the settings option of the same name to organize the full merged sets. It means that ALL clones are in subfolders within the parent set.
Either you
- turn this option on if you like this method, then your scan should simply work...
- or you let cmpro fix the files for your (which may cause some problems since they are t7z files not standard 7z files.....and as we all know 7z fails on some operations on t7z files...)...as I said...it's not worth the trouble to switch from zip to 7z or from split to full merged ;-)

[Carbon]

Ah, I had to turn on "Merged Sets" in "You prefer" in the Scanner module, and "Hash Collision Name" in "Full Merge Mode Mode" in the Settings module.

I don't mind either way, although I prefer not to waste 20 GB of space, but my biggest concern is: will CMP be able to update my set in the future if it is in .t7z format, although I suppose an updated torrent file will also take care of updating pnly the relevant files?

[Roman]

Well yes, you have to specify the prefered merge mode in scanner (rebuilder/merger)....if was still on split cmpro tries to generate sets in split mode.....and moans about every thing clone-like in a parent set.

"hash collision name" mode...well....as mentioned, when using full merged sets you can't simply put everything in one archive file since there are some sets which have identically named files with different content in a parent clone relationship. So merging them would overwrite one of the files. For such sets, cmpro automatically generates subfolders named after the clone.
Some users (and your collection provider seems to be one of them) prefers this full merging storing method (subfolders for clones within the parent) for each and any set...not only for the ones with such hash/name collisions. So by turning this option on, you will follow this method.

Torrent7z ...that's well...a different story. Fact is, t7z files are not fully compatible with the latest official 7z. For example 7z moans about extra data found at the end of the file (since t7z adds some stuff there) and I can't tell you which operations would fail when working on the files. Of course you can select a t7z binary in the compressor settings but keep in mind that a) I don't give any support on it and b) t7z compressing is most likely an overkill for scanning/fixing since the sets need to be reorganized over and over again. So a better way is most likely do a batch t7z recompress after scanning/fixing.


Little update to previous post: If you don't turn on the hash collision mode, cmpro will fix your files if the 7z settings are ok. This means if you have a solid 7z archive, your compression settings need to be adjusted, since the default ones will result in operating failures (like you cannot delete a file from a solid 7z file without turning on solid mode).

So to sum it up: Yes, cmpro will handle 7z/merged/t7z for your.....but the price for it (time you'd better spend somewhere else) is not really worth it.....For rare diskspace solid 7z fully merged sets might be fine (but not really in days of multi-terabyte hds)...but for fixing work it's a real pain in the a**. Solid archives or t7z...each operation will take long since the full archive needs updating/reorganizing..
Really...stick with zip and split sets ;-)

[Carbon]

Thank you for your explanations.

I will postpone my decision what format to use until next release to see how painless updating will be.