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

If you scan you can encounter 2 cases:

1) you got parts of a set (a set is a collection of roms/chds/samples, e.g. "pacman") where some files of the set are 'bad' (wrongly named, missing, bad checksum)

or

2) you don't have any file of the set (pacman is completely missing)

The hide completely missing set option would hide 2) but will show 1).

So in this case you would see only sets which are partly incorrect.


But:
This has nothing to do with playability. If you keep your sets split-merged you have parent sets and clone sets where the clones don't include the needed files from the parent. So if you got a clone you do need the parent, too (sometimes plus device sets plus bios sets). So if your scan result show no problems but you got the hide-fully-missing sets options enabled, you might still miss a parent....and you won't be able to run the game.


Again, there is no real reason to enable the hide-completly-missing sets option.
If you only have 10 sets out of 10000, then yes, you will get 9990 entries saying that you miss a set.
If you want to limit your scan to the sets you have, you go to set information, enable "the four incl. clones,parents,devices,bios" options and hit "avail sets".

"Hide Fully-Missing set" hides -guess what- only fully missing sets. If you miss only one out of 10 roms of a set it's not fully missing and will be displayed.
The option is dangerous since even if you get a clean/empty result tree it means that you might miss sets....if you only have 1% of all sets you get a clean result while in reality you miss 99%. Each set, no matter if parent or clone, is listed separately. Clones will only list their clone files, not the parent ones since they are shared.

So if you got a clone set and it does not appear in the list since you got "all" its roms it only means that the clone is ok. To play the game you do need the parent...which might be completely missing.

To sum it up: There is not really a reason to turn on the "hide fully missing sets". Keep it disabled and scan. If you only collect a small set out of the big MAME collection, it's better to enable/disable sets in the set information dialog, there you can always automatically enable belonging parents/devices/bios sets, too.

Let's see maybe if i have understand how it's works:
If i enable the "Hide Fully-Missing set" and do i scan i obtain an empty scan result but it is possible that mine zip roms collection contains some zip files that in them are missing some files that would be considered "Incomplete" set... right ?

At this point my ideal solution would be to:
- Do a full scan whit "Hide Fully-Missing set" option disabled (and this leads to a series of very long red crosses).
- And only then try to filter the zip files I don't have on my rompath

In this way, in theory, I should get a complete list of all my sets and find out which ones are actually incomplete or have some missing files inside it whether they are parent or original roms.... it's right ? Is it possible to get something like that ?

How i can obtain somethigs similar ? From "Set Information"

"Hide Fully-Missing set" hides -guess what- only fully missing sets. If you miss only one out of 10 roms of a set it's not fully missing and will be displayed.
The option is dangerous since even if you get a clean/empty result tree it means that you might miss sets....if you only have 1% of all sets you get a clean result while in reality you miss 99%. Each set, no matter if parent or clone, is listed separately. Clones will only list their clone files, not the parent ones since they are shared.

So if you got a clone set and it does not appear in the list since you got "all" its roms it only means that the clone is ok. To play the game you do need the parent...which might be completely missing.

To sum it up: There is not really a reason to turn on the "hide fully missing sets". Keep it disabled and scan. If you only collect a small set out of the big MAME collection, it's better to enable/disable sets in the set information dialog, there you can always automatically enable belonging parents/devices/bios sets, too.

Hi... i'm newest italian boys here
I have need some help whit usage of last CLRMamePRO 4.035.
On my PC i have a little collection of roms whit a setup of latest mameui 0.215.
I have use CLRMamePro so many times... i thinks i can use good but now i see i need some help and i have some dubs about the usage.
I try to explain:
I do a full scan... before to start i choose to "Hide Fully-Missing set" for not obtain a red cross.
When scan it's complete i obtain a completely clean SCAN RESULT........... I thought this indicated that my little roms collection it's completely ok whitout any incomplete set or parent missing instead there should be something wrong.
For example:
I take a little look inside my roms folder...... i see inside of this there's present some parents zip files. Little examples like "mk2r91.zip" "mkla1.zip" la2 and la3.zip and many other "Mortal Kombat X" (when x indicates 1 2 3 or 4) parents roms.
All this files apparently it's parents of respective mk mk2 mk3 and mk4.zip right ?

Before to download this 4 files first i have do a scan...... apparently no errors or missing appears on scan result. I open Mame and refresh my "Avaible" files. After scan complete the various MK parents roms not appears on list. To find out that I needed the four mkx.zip i need to manually "Audit" all parent zip files and only after this i have downloaded.... rebuilt it.... made another scan whit clrmp and made another refresh title on mame and only now all Mortal Kombat titles as correctly appears.

At this point the question it's it:
because if the zip files of all parents roms were present on the roms path but they were missing the original roms clrmamepro did not indicate it in the results of the scanner ??
It's a bug or it's need to activate some option on scanner ??

Sorry for my BAD english..... i see this section it's need to use english. If you think I can open a new thread using Italian it's better... let me know it

buongiorno a tutti mi presento sono Gigi e sto finendo di costruire un cabinato fatto tutto da me....ho un piccolo problema non riesco ad emulare circa 10 giochi ...sara perche uso mameui versione 0.184 e le rom appartengono sicuramnete ad un altro emulatore mame un po piu datato....come posso fare?

sounds weird....since cmpro of course only calls windows system library calls to rename files (we're talking about plain files/folders right? not files inside archives!?), so crashing/exisitng to desktop sounds like an internal library call caused an exception/assertion...

at the moment I can only say that it's not related to exFat in general since it works fine on devices formatted that way.
Soo....hard to say what the real problem is...could be a bad USB driver (in the combination with that drive), could be a bad drive (maybe there is a firmware update in the meantime). I guess Samsung has some software coming with the drive which might give a clue.....My laptop at work once had some really weird usb problems till I got updated drivers...

what happens if you (if you can do this without too much effort) format the drive to NTFS and then again to exFat

or what's the cluster size of the exFat formatted drive....so I can try to get a configuration as near as possible to yours

I am using a Samsung Portable T5 external SSD via USB 3.0. I was basically trying to go from MAME 0.185 full set to 0.215 full set. It was not working on the external SSD at all as it Crashed/Closed to Desktop without warning or error message. Essentially on any file that needed its case or name changed. Files were ok as I was able to change case or name by hand. Another weird thing was that it sometimes threw an error that it couldn't backup files (when fixing missing) and therefore would leave those alone.

Only thing that did the trick was to copy to internal SSD NTSF formatted and do the whole operation there. That worked absolutely flawless in all aspects.

I would chuck it right now on the heap of 'my own setup causing issues' especially as there is a simple work-around for me.

Thank you very much for looking into this and staying on it.

Best

Sorry, but i haven't found a solution yet. I've tried today the latest version of the emulator and still having the same issue. Somehow emulator flags some roms as non-working until they are audited/refreshed. I'm runing Win7 32bit, tried installing and moving the files, tried admin rights and got the same results... I'm still using Mame+ XT but kinda bummed 'couse of this bug... Sorry i wasn't more helpfull... :/

empathetic!

hmmm...interesting...

coming from visual pinball....then of course everything in c:\mame\roms which is not shared becomes unneeded, since it simply does not belong to vp....
and vice versa everything unique to vp will become unneeded for mame...

so currently I only see a chance in somehow build a custom datfile......

I wonder what happens when you setup a profile coming from vp and simply adding the mame rompath and keeping unneeded check disabled...but still fixing might become a problem since cmpro can't really decide where to add/fix sets (usually it does it in-place but when it comes to new archives it takes the first rompath).

Hi Roman, I'm getting into Visual Pinball again after 6 years, laugh.  I'm looking at clrmame to help with ROM usage, I wonder if it can keep unique pinmame roms in one location and leave mame roms used in both in another.  To explain:

c:\mame\roms
c:\vp\roms

\mame\roms has a lot of the pinmame roms already, I want that to remain where it is so I get a perfect result w/ a scan of mame.exe.
\vp\roms is missing about half of vpmame.exe's supported roms.

I have rebuilt vpmame.exe's roms from \mame\roms into \vp\roms.  So I now have of course unwanted duplication between the two directories.  I can easily have vpmame use its ROM paths to draw from \mame\roms and \vp\roms.

So the question.  Can I have clrmame somehow create *unique* to pinmame roms in the \vp\roms directory while also recognizing the shared roms in \mame\roms so I can get a 100% scan result for pinmame between the two directories.  Does that make sense?