Hello guys!

All my mame roms are in a single rom called 'roms' folder and each CHDīs are in the 'roms/setname' folder. Iīm using split sets.

So, I would like to separate all roms by systems, like neogeo, decocasset, etc. Is the rebuilder option able to scan all my roms and put them on the respective system folder? Will CLRMAME create all new directories for each system automatically or I need to create each one and add them to the roms-folder?

Please somebody help me.

The solution: sys-default-paths.

Add a folder on your disk for each system you like to have separated. Now assign these paths as sys-default-paths. Click on 'Systems' (e.g. in the rebuilder). Assign the newly created paths there (doubleclick the right column entries). Autodetect won't help you since it would assign all to systems to your current rompath.

Currently there's no automatic move to sys-default-paths (although that's a fine idea for the future), so you have to rebuild your sets to these new folders.
Enable the "use sysdefpaths" option in the rebuilder and rebuild your sets (source points to your old collection). Be sure you keep 'recompress' disabled (otherwise it'll take much too long).

After that you got your sets separated in the sysdefpaths.


For future Scanning you have to change some things:

Remove your old rompathsettings and add the newly created folders as rompaths. (Here you can see that sysdefault paths don't necessarily be rompaths....for scanning they have to!)

When using sysdefaultpaths you should enable at least one scanner advanced option: "use sys-default-paths for fix missing". This is needed if you add new sets via fix-missing. There's also an option there which lists sets which aren't in the correct sys-default-path (detect sets in wrong sysdefault path), usually people keep that enabled when they work with sysdefaultpaths.


Sounds complicated? Nah...it's easy 8)



So again:

- add new folders, set them up as sysdefpaths and rompaths
- rebuilder: keep 'use sysdefpaths' enabled
- scanner advanced: enabled 'use sysdefpaths for fix missing'

That's it 8)



...and I guess I will add an automatic "move to sysdefpaths" option somewhere and maybe some automatic generation of them. Time will tell.




Roman Scherzer

In addition to what Roman has advised. When you set up these multiple ROM paths in MAME/MAME32 use a relative path instead of the full rom path.

Instead of:

C:\games\arcade\Multiple Arcade Machine Emulator\ROMs\NeoGEO

Use just 'ROMs\NeoGEO'

In MAME32, you can edit the ROM paths from the GUI, by single clicking (may have to do the single click twice) on the path that you want to edit. Then remove everything before ROMs.

Also, MAME32 is limited to 20 directory entries, and there are at least 23 systems. To fix this, you would need to edit the src/ui/directories.c file to change MAX_DIRS.

NOTE: This only fixes the number of directories problem in the MAME32 sources. You also need to increase the allocated rom_path size in the MAME sources. If you use relative paths, then the problem with rom_path alocation size shouldn't affect you.

So, the best thing to do is to add an recursive algorithm to the rom directory, allright?

> In addition to what Roman has advised. When you set up these multiple ROM paths
> in MAME/MAME32 use a relative path instead of the full rom path.
>
> Instead of:
>
> C:\games\arcade\Multiple Arcade Machine Emulator\ROMs\NeoGEO
>
> Use just 'ROMs\NeoGEO'
>
> In MAME32, you can edit the ROM paths from the GUI, by single clicking (may have
> to do the single click twice) on the path that you want to edit. Then remove
> everything before ROMs.
>
> Also, MAME32 is limited to 20 directory entries, and there are at least 23
> systems. To fix this, you would need to edit the src/ui/directories.c file to
> change MAX_DIRS.
>
> NOTE: This only fixes the number of directories problem in the MAME32 sources.
> You also need to increase the allocated rom_path size in the MAME sources. If
> you use relative paths, then the problem with rom_path alocation size shouldn't
> affect you.
>

> So, the best thing to do is to add an recursive algorithm to the rom directory,
> allright?

Nope. This won't fit with cmpro's set-subfolder support ;)

btw...I just added a 'move sets' option in the System window which scans all assigned sysdefpaths and moves found misplaced sets to the correct sysdefpath. So no rebuild will be needed now....

...don't ask me when I release that version....but I doubt it will take long ;)


Roman Scherzer

Sorry Roman, but i was talking about mame32 rom directory support!

I downloaded the newer clrmame version and used the new feature. Itīs great. The CHD files are moved to the correct system directory too! Very good!

So, after doing by my hands (first try!), I lost these roms:

Cosmic Avenger [folder: cavenger - size: 36kb]
missing rom: 1 [size: 4096] [CRC32: 9e0cc781] [SHA1: f23bd6b9f427c26ac996a5c8ba29f356cf45c78a]

Defence Command [folder: defence - parent: defender - size: 28kb]
missing rom: 1 [size: 4096] [CRC32: ebc93622] [SHA1: bd1c098e91b24409925d01aa25de013451dba8e6]

Dragon Blaze [folder: dragnblz - size: 43mb]
missing rom: 10h.u59 [size: 2097152] [CRC32: 30e304c4] [SHA1: 1d866276bfe7f7524306a880d225aaf11ac2e5dd]
missing rom: 10l.u58 [size: 2097152] [CRC32: a3f5c7f8] [SHA1: d17478ca3e7ef46270f350ffa35d43acb05b1185]
missing rom: 1h.u12 [size: 2097152] [CRC32: 23cb46b7] [SHA1: 005b7cc40eea103688a64a72c219c7535970dbfb]
missing rom: 1l.u4 [size: 2097152] [CRC32: c2eb565c] [SHA1: 07e41b36cc03a87f28d091754fdb0d1a7316a532]
missing rom: 2h.u13 [size: 2097152] [CRC32: b75f59ec] [SHA1: a6cde94bc972e46e54c962fde49fc2174b312882]
missing rom: 2l.u5 [size: 2097152] [CRC32: bc256aea] [SHA1: 1f1d678e8a63513a95f296b8a07d2ea485d1e53f]
missing rom: 3h.u14 [size: 2097152] [CRC32: abe5cbbf] [SHA1: c2fb1d8ea8772572c08b36496cf9fc5b91cf848b]
missing rom: 3l.u6 [size: 2097152] [CRC32: 4284f008] [SHA1: 610b13304043411b3088fd4299b3cb0a4d8b0cc2]
missing rom: 4h.u15 [size: 2097152] [CRC32: 0ab0a12a] [SHA1: 1b29b6dc79e69edb56634517365d0ee8e6ea78ae]
missing rom: 4l.u7 [size: 2097152] [CRC32: c9fcf2e5] [SHA1: 7cecdf3406da11289b54aaf58d12883ddfdc5e6b]
missing rom: 5h.u16 [size: 2097152] [CRC32: 5450fbca] [SHA1: 7a804263549cea951782a67855e69cb8cb417e98]
missing rom: 5l.u8 [size: 2097152] [CRC32: 68d03ccf] [SHA1: d2bf6da5fa6e346b05872ed9616ffe51c3768f50]
missing rom: 6h.u2 [size: 2097152] [CRC32: 7362f929] [SHA1: 9ced06202e3f104d30377aeef489021d26e87f73]
missing rom: 6l.u1 [size: 2097152] [CRC32: 8b52c90b] [SHA1: e1067ef252870787e46c62015e5778b4e641e68d]
missing rom: 7h.u20 [size: 2097152] [CRC32: 44b7b9cc] [SHA1: 3f8122b62ea1183d9fb3aad32d0e47bd32244f87]
missing rom: 7l.u19 [size: 2097152] [CRC32: b4f4d86e] [SHA1: 2ad786c5626c98e6943ae05688a1b66307ceac84]
missing rom: 8h.u29 [size: 2097152] [CRC32: 3edb508a] [SHA1: 72b07fb34a94cc127de02070604b1ff31f3d46c7]
missing rom: 8l.u28 [size: 2097152] [CRC32: cd079f89] [SHA1: 49c46eb36bc0458428a7fad3fe622f5ed974073b]
missing rom: 9h.u42 [size: 2097152] [CRC32: bc61998a] [SHA1: 75dbefe712104c64576196c27c25dbed59ae3923]
missing rom: 9l.u41 [size: 2097152] [CRC32: 0b53cd78] [SHA1: e2071d9fe6c7be4e289b491587ab431c164e59da]
missing rom: snd0.u52 [size: 2097152] [CRC32: 7fd1b225] [SHA1: 6aa61021ada51393bbb34fd1aea00b8feccc8197]

Eggor [folder: eggor - size: 25kb]
missing rom: 4.bin [size: 2048] [CRC32: dc805be4] [SHA1: 18604b221cd8af23ff8a05c954a42c3aa9e1948a]

I donīt know why I lost these roms! For me itīs very strange because before separate the roms, I had them.

I would like to suggest another simple thing. Please add the correct system for each rom at the report screen example in uppercase):

Eggor [SYSTEM: STANDARD - folder: eggor - size: 25kb]
missing rom: 4.bin [size: 2048] [CRC32: dc805be4] [SHA1: 18604b221cd8af23ff8a05c954a42c3aa9e1948a]

I think thatīs all. So, Iīll download the lost roms...

Thanks for reply! You are very attentive.



> > So, the best thing to do is to add an recursive algorithm to the rom
> directory,
> > allright?
>
> Nope. This won't fit with cmpro's set-subfolder support ;)
>
> btw...I just added a 'move sets' option in the System window which scans all
> assigned sysdefpaths and moves found misplaced sets to the correct sysdefpath.
> So no rebuild will be needed now....
>
> ...don't ask me when I release that version....but I doubt it will take long ;)
>
>
> Roman Scherzer
>

> So, after doing by my hands (first try!), I lost these roms:

Don't manage roms manually 8)


Roman Scherzer