Print

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

[danielocdh]

So I have complete roms but some missing chds, split sets, roms on zips, chds on subfolders, scanning for all (sets, roms, samples and chds), fix checkboxes enabled.

DrumMania 8th Mix (G*C07 VER. JAA) [system: System 573 BIOS - folder: drmn8m - size: 2mb]
missing rom: gcc38jaa.u1 [size: 4116] [CRC32: 0xaaa03630] [SHA1: 0x4976b0c2e1b4458840a165bd889861d62289ad89]
missing rom: gcc38jaa.u6 [size: 8] [CRC32: 0xce84419e] [SHA1: 0x839e8ee080ecfc79021a06417d930e8b32dfc6a1]
missing chd: c38jaa02.chd [chd-sha1: 9115252e6cc13ff90e73cd1a864e0d99e3c8b5ea]
missing chd: c38jba02.chd [chd-sha1: 2a31335277929b2231b12ad950ab69e35b37d973]

Also for roms listed as missing, the rom is present and correct inside its zip file, still I get messages like this:

Set:   DrumMania 8th Mix (G*C07 VER. JAA)
Name:   drmn8m
File:   M:\MAME\roms\drmn8m\gcc38jaa.u6

Do you want to add the missing ROM?

Is this normal behaviour? If it is, is there any way to just list what really is incorrect?

[Roman]

you might want to use the latest nightly build

http://mamedev.emulab.it/clrmamepro/binaries/cmp20151002.rar

[oddi]

Hello Roman, with the last nigth build CMP must move chd


 if click fix , next scan result is :



may buggy mame code
Many tnx
--------
forget above

problem is CMP not rename chd , check mame source code on github
before one day Guru change code:

   DISK_REGION("dvd")
-   DISK_IMAGE_READONLY( "wmn1", 0, SHA1(4254e987e71d0d4038a87f11dc1a304396b3dffc) )
+   DISK_IMAGE_READONLY( "wmn1-a", 0, SHA1(4254e987e71d0d4038a87f11dc1a304396b3dffc) )
 ROM_END

when manually rename chd from wmn1.chd --> wmn1-a.chd , cmp report all is fine
tiny tiny bug
Tnx Roman

[Roman]

Nothing wrong here. You have a rompath for CHDs...which is ..well...not the best idea...You separate set components (the roms and the chds). From a set point of view having a chd only rompath is not so clever...

"Fix missing" adds the set where it thinks it would fit best...so it looks for the set and the roms...and finds it in your rompath (not in your chd path). So fix-missing decides to add the file in the same path where the roms are (if it doesn't find any clue, it uses the 1st rompath by the way). So you have to move it manually to your chd path.

[oddi]

When try fix chd --> cmp copy chd with new name (wmn1-a.chd) in my 1st rom path ( my firts path is ROMs folder), and now i have 2 same chds with different names :
/roms/wanganmd/wmn1-a.chd
/chds/wanganmd/wmn.chd
after second scan u see result in second shot from my previous post.
if manually i rename wmn.chd to wmn1-a.chd and remove "/roms/wanganmd/wmn1-a.chd", cmp report - all is fine
Tnx

[Roman]

well..that's exactly what I just explained. Fixmissing tries to put it to the rompath where the rest of the set is (in this case your rompath) and if nothing useful can be found, 1st rompath is used.