John IV |
|
IV/Play, MAME, MAMEUI
|
|
|
|
|
Reged: 09/22/03
|
|
Posts: 1970
|
|
Loc: Washington, USA
|
|
|
|
Send PM
|
|
|
[Annc] MAMEUI64 .221 and icons/snaps released.
#386323 - 05/19/20 08:31 AM
|
|
|
|
|
|
Re: [Annc] MAMEUI64 .221 released.
[Re: John IV]
#386358 - 05/20/20 04:25 AM
|
|
|
> Thanks to Robbbert for the .exe.
>
> http://www.mameui.info/
Changes:
- MAMEUI - Multipart software items will be loaded correctly via "SW Items".
- MAMEUI - Stability adjustments
- NewUI - If a multipart item had been loaded through MAMEUI, you can choose to load the other parts as needed
- NewUI - If a software-list item is loaded, you can view the usage (loading instructions), step by step as you work through the procedure.
*NewUI is only visible if you enable the "menu".
|
|
|
|
Re: [Annc] MAMEUI64 .221 and icons/snaps released.
[Re: John IV]
#386432 - 05/24/20 11:41 PM
|
|
|
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
Edited by Jorge (05/24/20 11:52 PM)
|
|
|
Tafoid |
|
I keep on testing.. testing.. testing... into the future!
|
|
|
|
|
Reged: 04/19/06
|
|
Posts: 3135
|
|
Loc: USA
|
|
|
|
Send PM
|
|
|
Re: [Annc] MAMEUI64 .221 and icons/snaps released.
[Re: Jorge]
#386433 - 05/25/20 12:08 AM
|
|
|
> 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.
|
|
|
|
Re: [Annc] MAMEUI64 .221 and icons/snaps released.
[Re: Tafoid]
#386438 - 05/25/20 06:51 AM
|
|
|
Thanks for the answer.
Now, since we are on the "wrong clones" subject, there's a VERY OLD bug in MAMEUI(64). When you type a name in the search box (to find a set quicker), you'll notice that a lot of systems appear listed as clones of other machines, but in reality, they have nothing to do with them. When you erase the text in the search box, then those sets return to their correct location in the list. This is most noticeable when using the "grouped view".
I don't know if something can be done about that...
Edited by Jorge (05/25/20 06:52 AM)
|
|
|
|
Re: [Annc] MAMEUI64 .221 and icons/snaps released.
[Re: Jorge]
#386675 - 06/09/20 07:33 AM
|
|
|
|
|
| John IV |
|
IV/Play, MAME, MAMEUI
|
|
|
|
|
|
Reged: 09/22/03
|
|
Posts: 1970
|
|
Loc: Washington, USA
|
|
|
|
Send PM
|
|
|
Re: [Annc] MAMEUI64 .221 and icons/snaps released.
[Re: Jorge]
#386677 - 06/09/20 08:05 AM
|
|
|
The search picks up text in the set name, description, manufacturer, and driver.cpp so atari will produce the results you're seeing. Some of the parents are not 'caught' so the indented clone children remain indented.
|
john iv
http://www.mameui.info/
|
|
Previous 
Index 
Next 
Threaded 
[Annc] MAMEUI64 .221 and icons/snaps released.
Reply
[Re: 
