Print

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

[john iv]

Hi Roman, I've outgrown my NVME 2TB SSD which I was keeping a full set of MAME on w/ CHDs.  So I've moved the CHDs to a second SATA SSD.  I'm trying to do this for rompath:
c:\o\games\mame\roms
d:\chds

CHDs are stored in d:\chds\setname\*.chd structure.

I've added those to clrmame in settings rom-path (and mame.ini of course).
Mame plays fine and can find the CHDs, no problem there.

When I audit with clrmame I am getting a bunch of wrong name messages that I never did before, here's a sample:
wrong name: D:\CHDs\area51mx [wrong: D:\CHDs\area51mx] [right: a51mxr3k] [not fixed]
wrong name: D:\CHDs\area51ta [wrong: D:\CHDs\area51ta] [right: area51t] [not fixed]
wrong name: D:\CHDs\blitz [wrong: D:\CHDs\blitz] [right: blitz11] [not fixed]
wrong name: D:\CHDs\bm2ndmix [wrong: D:\CHDs\bm2ndmix] [right: bm2ndmxa] [not fixed]
wrong name: D:\CHDs\bmcompmx [wrong: D:\CHDs\bmcompmx] [right: hmcompmx] [not fixed]

Then I get the following messages referencing a wrong SysDefPath and clrmame wanting to put the CHDs back to their prior location it seems:
2 Spicy [folder: 2spicy]
wrong SysDefPath: 2spicy [wrong: D:\CHDs\] [right: C:\O\Games\MAME\ROMs\]
Area 51: Site 4 (HD Rev 2.01, September 7, 1998) [folder: a51site4]
wrong SysDefPath: a51site4 [wrong: D:\CHDs\] [right: C:\O\Games\MAME\ROMs\]

So where in clrmame can I re-set the sysdefpath for the CHDs to go to the new d:\CHDs location and what is happening w/ the renaming requests for about these 30 CHDs?  Thanks!

[Roman]

Using sysdefpaths is only possible if you split your sets by (bios/software lists) systems (e.g. neogeo, naomi, etc).
Having a chd folder means that you have a rompath setup which uses the chd folder ("one folder") for multiple systems, so sysdefpaths won't work.
But of course your idea of keeping chds in one folder is fully valid.
So actually (as long as you don't use software lists), you should turn off the sysdefpath usage. This can be done by accessing the sysdefpaths (via "systems") and remove (unbind) all.

After that you should run a full scan again to see if this already resolves your rename issues, too. If not, you should send me your cmpro.ini, the *.cmp file from the cmpro settings folder so I can try to rebuild your scenario.

[john iv]

Thanks Roman, that worked.  I unbound the systems and re-ran the full scan.  Did not get the renaming options prompt this time around, so things look good to go.
What were those names that it was suggesting? They weren't the setname and they weren't the chd names, something internal?

[Roman]

you mean for example a51mxr3k for area51mx? a51mxr3k is a clone of area51mx which uses the same chd (but different roms).