Hi Roman.

My scan of mame 0.100 produced the following log:

no problems with currently set options

----------
Missing Sets: 0 of 5778
Wrong SetName Case: 0 [0 fixed]
Wrong Named Sets: 0 [0 fixed]

Missing Roms: 128 (128 are 'nodumps') of 83941
Missing Bytes: 52mb of 41gb
Wrong Named Roms: 0 [0 fixed]
Wrong RomName Case: 0 [0 fixed]
Wrong Sized Roms: 0 [0 fixed]
Wrong Date/Time Roms: 0 [0 fixed]
Wrong CRC32s: 0
Wrong MD5s:
Wrong SHA1s: 0

Missing Samples: 0 of 2452
Wrong SampleName Case: 0 [0 fixed]

Missing DiskImages:
Wrong DiskImageName Case:
Wrong Named DiskImages:
Wrong CHD_MD5/SHA1s:

Unneeded Files/Folders: 0 [0 fixed]

Number Of Sets: 5778
Number Of BIOS sets: 25
Number Of Parents: 1296
Number Of Clones: 2612
Number Of Others: 1870
Number Of Roms: 83941
Number Of Samples: 2452
Number Of 'nodump' ROMs: 221
Number Of 'baddump' ROMs: 303

I couldn't find the explanation for 'missing bytes' in the docs. Does this mean I have an incomplete set somehow?
I don't recall this happening before.

Many thanks!

> Missing Roms: 128 (128 are 'nodumps') of 83941
> Missing Bytes: 52mb of 41gb

> I couldn't find the explanation for 'missing bytes' in the docs. Does this mean
> I have an incomplete set somehow?
> I don't recall this happening before.



Missing bytes is in since hmm...don't remember..one or two versions. It's simply the unpacked size of the missing roms. And as you see you're missing 128 nodump files which of course got a size...and if you sum the size up you got 52MB 8) If you want to see your missing nodump files, enable scanner->nodump handling->show missing and rescan.


Roman Scherzer

And to clarify:

"nodumps" means no good dump known, and hence are supposed to be missing? Or are there placeholders/ 'best available' roms that I am missing?

Thanks again.

> And to clarify:
>
> "nodumps" means no good dump known, and hence are supposed to be missing? Or are
> there placeholders/ 'best available' roms that I am missing?
>
> Thanks again.
>


A rom flagges as nodump is a known not-dumped-rom (while on the other hand a baddump is a known existing bad dumped rom). The size of it IS known though. Checksums aren't available. "Missing bytes" does count the sizes of the nodumps and missing nodumps are listed in the statistics window as well.
By default clrmamepro hides missing no dumps. Scanner->nodump handling->show missing will show them. You can optionally create dummy placeholders for the missing ones.

Still wonder why people care so much about the statistics window. The only important thing is that the scanresults tree shows nothing. Numbers in the stats window are just..well...numbers.




Roman Scherzer

> Still wonder why people care so much about the statistics window. The only
> important thing is that the scanresults tree shows nothing. Numbers in the stats
> window are just..well...numbers.

I know what you mean, but I'm not afraid to say that I find CMP a complicated program to use, and am wary of new features!

Thanks for clearing up anyway!

> I know what you mean, but I'm not afraid to say that I find CMP a complicated
> program to use, and am wary of new features!

complicated?

load a datfile, setup a rompath, click scan...done

that's enough for the common user and most people find that easy ;)


Roman Scherzer