MAMEWorld Forums - News - Re: [Annc] MAMEUI64 .221 and icons/snaps released.

> Hi!
>
> Thanks for the release, although there is a small bug in MAMEUI:
> The sets HP86b_001 and HP86b_004 require ROMs that official mame doesn't.
> these are:
>
> hp86b_001 : romsys1.bin (8192 bytes) - NOT FOUND
> hp86b_001 : romsys2.bin (8192 bytes) - NOT FOUND
> hp86b_001 : romsys3.bin (8192 bytes) - NOT FOUND
> hp86b_001 : rom000.bin (8192 bytes) - NOT FOUND
> hp86b_001 : rom001.bin (8192 bytes) - NOT FOUND
> hp86b_001 : rom320.bin (8192 bytes) - NOT FOUND
> hp86b_001 : rom321.bin (8192 bytes) - NOT FOUND
>
> hp86b_004 : romsys1.bin (8192 bytes) - NOT FOUND
> hp86b_004 : romsys2.bin (8192 bytes) - NOT FOUND
> hp86b_004 : romsys3.bin (8192 bytes) - NOT FOUND
> hp86b_004 : rom000.bin (8192 bytes) - NOT FOUND
> hp86b_004 : rom001.bin (8192 bytes) - NOT FOUND
> hp86b_004 : rom320.bin (8192 bytes) - NOT FOUND
> hp86b_004 : rom321.bin (8192 bytes) - NOT FOUND
>
> These sets work just fine in official mame without those ROMs.
>
> Sets HP86b_001 and HP86b_004 are CLONES of HP86b on official MAME, but for some
> reason, they're not on MAMEUI, that's why MAMEUI fails to find the required ROMs
> (they're in the parent set, but MAMEUI doesn't look there because they're incorrectly
> treated as independent sets)
>
> check: https://i28.servimg.com/u/f28/20/10/75/21/mameui10.png

There was a hotfix just before release of 0.221 which changed these 2 mentioned machines to clones of machine HP86B.

https://github.com/mamedev/mame/commit/180d2a582224f97ba84e4c4516558ea351d920f5

That means that MAMEUI was built on source before this hotfix and showing the different "requirements" compared to mainline release. All that would mean that in instances where you have a SPLIT romset setup (each parent/clone only holds what isn't shared), MAMEUI would likely not see the missing because it has no reference to the newly added parent.

The next release should be unified between both baseline MAME and MAMEUI in this instance.