#Fba 0.2.97.43 romset archive

as I said, I will double check this.maybe I think about a stricter merge element mode which would mean that only files with a merge element are considered being a clone.time will tell. Guess it is merged because of some very old routines for bios files which don't care about names but only look for identical hashes. Keeping this in mind, the 2 bios files in your example should actually not be removed from the clone since they don't have a merge element and the names differ. Then you got the profiler->parse rom/disk merge tags', when enabled, cmpro uses the given merge name for the name + checksum check (so it's a bit less strict then) Meaning that different names but equal hashes within a parent/clone relationships mean 'different files, do not merge'. Normally cmpro detects clone and bios files by name + checksum compare. yes, I will rethink the 'merge' element rules since at least in this example there is a break in logic regarding the bios ones. Weekend time.and not much time to read through / answer everything now. Oh and I always think of the Sentinel now when I visit! Have a great weekend! I know there's a reason here I am sure but when you disable separate BIOS sets it still complains they are missing when you actually check it as an option, how come?ДЄnyway thank you for all you do and I often sing your praises on other forums. I know I build fix DATs of missing ROMs frequently and that works great.ДЄre files flagged as 'no dump' or 'bad dump' processed the same as regular ROMs at default settings? Can you pull a parent and all clones (possibly the BIOS) in ClrMamePro. I suppose the program needs a way to know the parent/clone/bios relationships. I tried building some ROM sets out of zips with DatUtil and it works great for 'flat' sets but I was trying to figure out a way to use it to build a DAT with merge information but had no luck. Kind off topic but I was wondering is it possible to tell which merge files belong to the parent and which ones to the BIOS or do you need to check each 'ROM' entry to really know? I always look at the Clone/Parent/BIOS unless there is none. I did look at 0.198 of the same games and none of these examples are valid and it looks much cleaner in there now. Here's the with the DATs I used based off FBA 0.2.97.43. I don't know if you heard of RetroPie (using a Raspberry Pi) and the emulator is called lr-fbalpha (Libretro core) using Retroarch as the frontend. I do have another example but it's also from the same parent/BIOS set just a different clone. Just to clarify has the processing changed between versions and it's not a setting I am missing correct?

#Fba 0.2.97.43 romset archive

I went back to the old version for testing and it does indeed leave them in the archive in non-merged mode and removes them in current ClrMamePro in non-merged mode. I completely became aware when I had upgraded from a really old version and extra files where being removed between the two versions. Maybe there's no answer here but just an awareness. They didn't bother to view the DAT and see what's happening and just tell people to manually add the 'missing' files. These 'errors' (as they call them) have been in several versions of the lr-fbalpha DAT now so the posts are far and wide. I've seen people giving out wrong information on what's happening on other forums. I spent a few hours yesterday going through the DAT and testing it to understand what was happening. Yes I see your points and they make perfect sense in how they may be interpreted in more than one way and also end up with duplicate files possibly.

The Gladiator - Road Of The Sword / Shen Jian (V101) I spent quite a while trying to figure out if there's an option I was missing to get the current version working the same. I don't know if I set something differently in that version or if it just worked differently back then. When running 4.023 32-bit it does keep the equal hash files in Non-Merged mode. I have a few ROMs from the current FBA (lr-fbalpha) that are doing the same thing. Their is no merge information so it seems like it should work. When I run this DAT through ClrMamePro (Non-Merged Sets) it discards the ROM's in thegladpcb that have an equal hash but a different name from the BIOS ROM files.

I was wondering if you could take a look at the example below.