EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

The new forum is online, hope you enjoy it!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - elsanto

Pages: [1]
1
clrmame Discussion / Re: clrmamepro generates duplicated files
« on: 17 September 2018, 19:54 »
Ok. I will try to explain myself a bit better.

I have a MAME 0.106 dat file that I use to prepare games for advmame/raspberrypi.

I did a rebuild using as Add Paths some folders that I have with roms. I chosed split roms.

The problem is that clrmamepro did not create a jdreddb.zip file because the 3 roms that should be inside that zip file were already in jdredd.zip file.

If I run the scanner over the just rebuilded collection, clrmamepro says that jdreddb is a missing romset. To get a "no missing rom" result from clrmamepro scanner i can either:
- create a empty folder named jdreddb in rom path or....
- ... make a copy of jdredd.zip named jdreddb.zip (In this case the scanner shows a warning telling that the 3 roms inside jdreddb should be move to parent)

It's not a big problem for me. I just described it trying to find some differences between this case and natodef one. With natodef this problem does not happen.

Thank you and regards.

2
clrmame Discussion / Re: clrmamepro generates duplicated files
« on: 16 September 2018, 20:11 »
Ooops, sorry. I was talking about two different sets.

The first set, the one I was talking about in the first three messages, was a "repository" romset that i decided to store fully merged.

In my last message I was talking about another set I have for recalbox (MAME 0.106 DAT). This one is using splitted roms and is the one who have the problem with jdredd and jdreddb.

I've noticed that ClrMamePro doesn't show any warning if there is a empty folder called jdreddb.

Again, sorry for the confussion, my bad... O:-)


3
clrmame Discussion / Re: clrmamepro generates duplicated files
« on: 14 September 2018, 23:07 »
as an example for identical sets (however it is a parent/clone, not a clone/clone), there is natodef and natodefa, which only differ in the order of levels...which is defined by how mame loads the roms....both machines do exist in reality....and so you have 2 identical sets :-)

I think I found another case: jdredd and jdreddb (at least with 0.78 DAT). But, in this case, the Scanner shows 3 warnings (on for each file inside the rom) regarding to jdreddb: "wrong placed file" and suggest to move to parents. With natodef and natodefa it doesn't show any error/warning.

I attached the relevant parts of dat file. I don't understand why the different behavior. Maybe is because jdredd/jdreddb requieres a CHD?

Thank you and regards.

4
clrmame Discussion / Re: clrmamepro generates duplicated files
« on: 13 September 2018, 20:47 »
as an example for identical sets (however it is a parent/clone, not a clone/clone), there is natodef and natodefa, which only differ in the order of levels...which is defined by how mame loads the roms....both machines do exist in reality....and so you have 2 identical sets :-)

Amazing!

Finally, I decided to store the roms collection as a merged set. The space saving is small, about 1,5% but I found that clrmamepro is much faster when rebuilding, scanning, etc... with merged sets.

Thank you and regards!

5
clrmame Discussion / Re: clrmamepro generates duplicated files
« on: 12 September 2018, 18:29 »
OK, Roman. Thank you very much for the explanation.

I didn't know that some clones share roms between them but not with the parent. That explains the "kovlsjba/kovlsjb" case.

After reading your post, I realized that there is many shared files between romsets without a parent/clone relationship. Now, I'm rebuilding a merged set. I suppose that doing it this way, the collection will take much less space.

Maybe, the MAME team could develop a new "rom to game" assignations to store the sets more efficiently, as they did, many years ago, when they introduced the merged or split romset, to make collections smaller.

What I still don't understand is why are there is "identical clones". Would not be a smarter choice if two (or more) drivers could use the same romset instead of require "identical clones"?

Thank you again and regards.

6
clrmame Discussion / clrmamepro generates duplicated files
« on: 11 September 2018, 21:49 »
Hi all!

First of all, I wanted to thank you for such a great piece of software.

I have used clrmamepro with much success for several years, mainly for mame romset maintenance.

But now I found a problem. I want to rebuild a split romset for mame 191. I built mame and launched it with -listxml to generate a dat file. I loaded such file in profile window and set an empty folder as ROM path and some other folders with roms as ADD paths. Then i clicked on the rebuilder button and make sure that "Use Add-Paths" was checked, Destination folder was the empty folder and "Split Sets" was checked too. After rebuilding I found than the clrmamepro make many identical files in the ROM path. For example: kovlsjba.zip, kovlsjb.zip, kovlsqh.zip and kovqhsgs.zip. Those four files have all the same sha1sum (75e40d829b04b20028008d287bf11875458e77df). It's like if it was using some merged setting, despite I the checked "Split" option.

Is this normal? Am I missing something?. Can you help me, please?

I'm running cmp4035-32bits portable with wine under debian linux.

Thank you and regards.

Pages: [1]

Page created in 0.122 seconds with 20 queries.

anything
anything