 No.02227
Fujix Administrator
Aug 26, 2008, 18:38
edited on: Aug 26, 2008, 18:41
|
In fact this issue used to be listed as romcrc0109ora:List of ROMs of the same name with different CRC: It's not found here now tho. I'd like Dev team's policy on this. |
|---|---|
 No.02228
etabeta Developer
Aug 26, 2008, 19:47
|
I think MAME should use the name used on labels in the pcb, so if they're the same on the board they must be the same in MAME the merged sets handling could be done by the rommanagers, which could append something at the end of the filename to distinguish between each of them the renamed roms should work with no problems since MAME can load by crc |
 No.02229
Tafoid Administrator
Aug 26, 2008, 19:53
|
Agreed. I was about to post pretty much the same thing as etabeta... This to me is more of a FEATURE request than a core problem - the documentation aspect of MAME presupposes that the filename, when possible, will match that of the chip label or actual part number of the rom. Since MAME loads by CRC, filenames don't matter and are an issue for the rom managers (which clrmame handles seemingly fine). |
 No.02232
john_iv Senior Tester
Aug 26, 2008, 20:08
edited on: Aug 26, 2008, 20:10
|
I understand the arguments, but on the flip side it is not possible to reconcile this with one of Mame's built in storage techniques. So either that needs to be altered by dropping fully merged support and going to a forced full split mode or perhaps allowing nested folders w/in the parent zip w/ the files stored that way so they don't collide. Clrmame does complain about them though these days and forces a decouple of the parent/clone relationship so you end up w/ the clone existing separately, defeating the purpose of full merge mode. |
|
No.02233
etabeta Developer
Aug 26, 2008, 20:14
edited on: Aug 26, 2008, 20:14
|
Well, you can reconcile them: you manually rename those files to something different and you put them in the merged sets. At that point MAME shall be able to load the correct files from the crc, no matter the filename (iirc the priorities at loading) |
 No.02234
aaron Developer
Aug 26, 2008, 20:55
|
There is no "MAME Full Merge Mode". We happen to support looking in the parent for a match if not present. It so happens that mostly this allows you to merge all clones into the parent, but it is a side-effect, not a special mode. If the names clash then sorry, the side-effect is that a full merge is not possible for the set in question. If the proper solution is to stop looking in the parent, I can do that, but I doubt that's what anyone really wants. |
|
No.02236
john_iv Senior Tester
Aug 27, 2008, 01:02
edited on: Aug 27, 2008, 04:33
|
Hmm, I'm torn. If a full merge across all games is no longer possible I would contend that the feature/implementation falls short of the bar even if it's a side effect and we should go to only supporting split-merge in clrmame parlance [parent.zip exists w/ its common roms and its clones exist as zips w/ their separate roms] or full-split [every rom duplicated in separate. [Update: Well, went split merged so it's academic now. :-)] |
 No.02237
Robbbert Senior Tester
Aug 27, 2008, 05:56
|
I have used fully-merged sets for some years now, mainly to save space and directory entries. The rom manager that I use (a homebrew that I made), renames all roms to their CRC (the CRC is the filename), thus avoiding clashes. There's nothing to say that you have to use the filename specified in MAME, it's just that ClrMamePro insists on it, rather than being flexible. Personally, I don't believe it's the dev's responsibility to look out for clashes; the user has to sort that out for themselves. |
|
No.02238
Firewave Senior Tester
Aug 27, 2008, 08:13
|
It's a clrmamepro option and not a MAME feature. It just tries to utilize MAME's abilities to the biggest extent. It also detects such clashes and still gives you the best possible fully-merged sets, so you don't even have to concern about those. Maybe you find something, that's more convenient for you and convince Roman to implement it after his vacation ;) And keep in mind ...not long ago a convenience feature has been removed from clrmamepro, because it caused issues (nodump fillers). |
|
No.02239
Robbbert Senior Tester
Aug 27, 2008, 08:43
|
I'm happy with what I have, and ClrMamePro isn't the only rom manager around. What happens with it doesn't concern me. However, I agree with the removal of the nodump fillers, it was only ever there to keep the rom kiddies happy. |