Please login or register.

Login with username, password and session length
Advanced search  


The new forum is online, hope you enjoy it!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Roman

Pages: 1 2 3 4 5 [6] 7 8 9 10 11 ... 166
Your problem is not related to cmpro. It's a question of old chds which can't be converted via chdman to match the current ones. You need to find the old chds or the new chds depending on which MAME version you want to check.

I think there was a time where chds were simply redumped / reencoded with chdman instead of just being updated to a newer chdman version. For example to include some more metadata.....but hey...that was years ago...can't really remember.

If I'm not mistaken a current MAME chdman has no update function anymore and I doubt that all old chdfiles can be simply updated.
Since all chds are 'available' for the current MAME version (which is .257) you shouldn't have a problem finding them.

Yep placeholder files which are shared thousands of times are a killer. They are one of the reasons why fix missing options (and deeper look for fix missing etc) should be turned off. If you then also use solid 7z archives you can go on vacation while fixing 😁

Maybe a full rebuild is faster in such cases or a manual zip after working with decompressed sets….

As mentioned, maybe the not too far future brings you something faster 😁 however progetto snaps are not in the focus yet at all but I guess I will have a look at it too

I‘d go with decompressed sets and anything fixmissing related turned off. Use the rebuilder to add the update sets to the existing collection.

Future might bring something faster…..cough

"not working" is no term which is used in any way when it comes to audit sets. MAME has tons of sets which are non working simply because the emulation is not yet fully working, e.g. due to encryption/protection issues etc.

So differ between playing sets and auditing sets. cmpro is only for auditing sets and it audits what's listed in the datfile. Yes, there are 1GB CHDs which are non working...there are CHDs which are 30GB...so if you're into MAME, you should look out for larger HDs. However these days 2TB Disks are like 50EUR which is enough for plain MAME (roms/chds). When it comes to software lists you might look out for some more TB.

"ddr3ma", assuming you keep your sets split and using MAME .256, then you only need:


Why? Because the set has a 1 chd on its own, 1 nodump rom file (hd6473644h.18e, yes, the icon with the question mark....you can't find it, it's not dumped, ignore it), some shared files with its parent (ddr3mk) and 2 roms shared from devices and bios roms.... So no "own" rom files are needed, so you don't have a ddr3ma.zip

Keep in mind: A set is a collection of roms and/or chds and/or samples. There are chd-only sets, there are sample-only sets.
If you miss a chd from a chd only set you're missing the full set, if you miss a chd from a set with roms and chds and you got the roms, cmpro will still show the set as partially bad with the missing chd

To use ddr3ma in MAME (when storing the sets split), you of course need the chd, the parent romset, the needed devices and the needed bios rom....

"Where possible i have add the correct 'romset' but not add the CHD file."
There is no romset. The CHD is the only needed file...easy as that :)

It's not really recommended to disable sets in set information. You have to understand what that means if you do so.
There are options for example which mark unselected sets as unneeded (Scanner-> Advanced). Other problematic cases are if you e.g. enable clones while disabling parents and so on. Disabling sets is nothing you usually need to do.

So....Problem 1: You have incomplete sets due to missing chds. Well....either you're the "gonna get them all" guy, then find them and add them. Or you're the "I don't want them" guy, then either don't scan for chds or disable the set (and its parent/all its clones) or find/edit a datfile which suits your needs better.

Problem 2: ddr3ma ...well...can't really tell you since I can't see if it's enabled or not. If cmpro wants to rename it, then it has a good reason for it. If it's disabled then surely ddr3ma is not known and then it tries to find a set which matches best for the data inside the zip.

So...keep all sets enabled and decide yourself "I need the chds" or "I don't need the chds". You can - as you already found out -  temporarily close your eyes on the chd errors by toggling the checkbox.

If you remove incomplete sets and run another scan and you got "fix missing" enabled, it's pretty likely that the messages reappear, simply because it found one of the missing entries in a different set.
If you want to ignore some sets due whatever reason, you can either modify the datfile or go to set information and enable just the ones you're interested in

Yes, if you toggle the checkboxes after a scan, the results tree is updated.

"If i put this files on 'Roms' folder.... it's be removed by scanner..... because ?"  ???? which files? if you have valid chds on a rompath root, they can get moved to their correct subfolder. If you're talking about other files, they are unneeded and get removed (-> backup folder).

And actually, what do you expect to see? They are not defined (besides a setname)

size="" crc="" md5="" sha1="" mia="yes"

so...nothing is known about such entries and cmpro will moan about them when importing the datfile....either you click yourself through the prompts or you change cmpro.ini entry
Misc_DisplayLIErrors = 0

clrmame Discussion / Re: Snan ROMs without subfolders
« on: 08 June 2023, 04:47 »
No. The storing method is
Rompath/setname/file1…file n for deompressed sets or
Rompath/setname.zip (.7z/.rar) (where the archive holds file 1…file n) for compressed sets. Where file 1…file n corresponds to rom files of that one set.

You have to follow that.

If you want single-file sets on the same folder level you need to edit the datfile to have one set only holding all sets in one set.

Scanner->Advanced ->Fix Missing Options -> turn off "Deeper check for fixable missing files" and turn off "additionally test sha1/md5 matches.

Progetto Snaps collections use a lot of placeholder pngs where you usually have at least one copy available. So as soon as you miss one of such files, fix misssing (and the upper mentioned ones) look through all your rompaths/backup files...and that takes really long. And when the next missing file is detected it does the same over and over again.

So it's not freezing but it is busy like hell. For progetto snap collections, you should turn off all the fix-missing related stuff. The rebuilder should be used to add the missing parts instead.

You‘ve got fix-missing enabled? If yes, turn it off.

clrmame Discussion / Re: Rebuilder 0.06 released
« on: 07 May 2023, 18:27 »

clrmame Discussion / Re: Rebuilder 0.06 released
« on: 07 May 2023, 17:57 »
Not really a realistic scenario, since I don't know anyone who does a) a full rebuild and having b) compress: rezip and sha1:both enabled. Such options are timekillers (beside the amout of a rebuild).
As an example, if you don't use rezip, sha1 none and hardlinks, your full rebuild is most likely done within an hour (depending a bit from where to where you operate)
I know the argument "but I want to be 100% sure that the archives are fine"...but actually a post run commandline based archive test is faster. Same can apply for "but I want identically compressed archives".
The typical use case for the rebuilder is to update an existing collection with a bunch of sets.

But of course, if you like to spend 4.25 hours to always redo everything, ok...it's of course doable ;-)

clrmame Discussion / Re: Rebuilder 0.06 released
« on: 05 May 2023, 04:41 »
….and now compare it to old cmpro :-)

You have to be careful when comparing results...the diskcache can fool you immensly. So you need to compare either both with or without diskcache...
So the best ist (besides using the same source/destination) a reboot of the machine in between the tests and doing 1 scan.
Or you run multiple ones in a row for one version and take an average.

I'd expect something about 1 to 30% speed gain compared to 0.05...but yes, it also depends on your machine/number of cores

clrmame Discussion / Rebuilder 0.06 released
« on: 04 May 2023, 18:35 »
Rebuilder 0.06 released


Doing source and destination matches now in multiple threads...gives a nice speed boost.

The set merge modes (standalone, new rebuilder tool), full (merged), split (merged), un/not-merged don't play a role here. They only define how the sets are stored on your system. If you want to "cherry pick" several sets, you need to disable the ones you don't want. In old clrmamepro, you can do this in Scanner->Scan Results Tree window, bottom left 'set information' button. In Set Information you have various ways to enable/disable sets either by single-ticking, regular expressions, filter lists and so on. Only enabled ones will be rebuilt.
In the new rebuilder tool you can set a regular expression via the -f --filter parameter.

clrmame Discussion / Re: -listxml VS hash/*.xml
« on: 22 April 2023, 20:14 »
Ask the devs 😁

clrmame Discussion / Re: -listxml VS hash/*.xml
« on: 22 April 2023, 18:59 »
Especially the rompath setup is really really annoying which I have to admit....but as I said, this might change drastically.
Actually I don't know the reason why -listsoftware does not include all software lists of the hash folder. Well, at least in the past, several were not included in the extract. And since normally only a handful of lists change from MAME version to version, it makes more sense to have a profiler per software lists. Rompath generation and assignement can be here done via the batcher...

Pages: 1 2 3 4 5 [6] 7 8 9 10 11 ... 166

Page created in 0.472 seconds with 19 queries.