Mame2003 game runs on 4.3 but not 4.7

mahoneyt944

Just pulled up the driver for guardian. This is what it's looking for.

ROM_START( guardian )
	ROM_REGION( 0x80004, REGION_CPU1, 0 )	/* 8*64k for 68000 code */
	ROM_LOAD16_BYTE( "2021.8e",  0x00000, 0x20000, CRC(efea1e02) SHA1(f0f1ef300f36953aff73b68ffe6d9950ac575f7d) )
	ROM_LOAD16_BYTE( "2020.8cd", 0x00001, 0x20000, CRC(a8f655ba) SHA1(2defe4d138613e248718a617d103794e051746f7) )
	ROM_LOAD16_BYTE( "2023.9e",  0x40000, 0x20000, CRC(cfa29316) SHA1(4e0e76304e29ee59bc2ce9a704e3f651dc9d473c) )
	ROM_LOAD16_BYTE( "2022.9cd", 0x40001, 0x20000, CRC(ed2abc91) SHA1(81531040d5663f6ab82e924210056e3737e17a8d) )

	ROM_REGION( 0x14000, REGION_CPU2, 0 )	/* 64k for 6502 code */
	ROM_LOAD( "0080-snd.12c", 0x10000, 0x4000, CRC(0388f805) SHA1(49c11313bc4192dbe294cf68b652cb19047889fd) )
	ROM_CONTINUE(             0x04000, 0xc000 )

	ROM_REGION( 0x180000, REGION_GFX1, ROMREGION_DISPOSE )
	ROM_LOAD( "0037a.23e",  0x000000, 0x80000, CRC(ca10b63e) SHA1(243a2a440e1bc9135d3dbe6553d39c54b9bdcd13) ) /* playfield, planes 0-1 */
	ROM_LOAD( "0038a.22e",  0x080000, 0x80000, CRC(cb1431a1) SHA1(d7b8f49a1e794ca2083e4bf0fa3870ce08caa53a) ) /* playfield, planes 2-3 */
	ROM_LOAD( "0039a.20e",  0x100000, 0x80000, CRC(2eee7188) SHA1(d3adbd7b20bc898fee35b6ba781e7775f82acd19) ) /* playfield, planes 4-5 */

	ROM_REGION( 0x020000, REGION_GFX2, ROMREGION_DISPOSE )
	ROM_LOAD( "0030.23k",   0x000000, 0x20000, CRC(0fd7baa1) SHA1(7802d732e5173291628ed498ad0fab71aeef4688) ) /* alphanumerics */

	ROM_REGION16_BE( 0x600000, REGION_GFX3, 0 )
	ROM_LOAD16_BYTE( "0041.2s",  0x000000, 0x80000, CRC(a2a5ae08) SHA1(d99f925bbc9a72432e13328ee8422fde615db90f) )
	ROM_LOAD16_BYTE( "0040.2p",  0x000001, 0x80000, CRC(ef95132e) SHA1(288de1d15956a612b7d19ceb2cf853490bf42b05) )
	ROM_LOAD16_BYTE( "0043.3s",  0x100000, 0x80000, CRC(6438b8e4) SHA1(ee1446209fbcab8b17c88c53b65e754a85f279d1) )
	ROM_LOAD16_BYTE( "0042.3p",  0x100001, 0x80000, CRC(46bf7c0d) SHA1(12414de2698178b158ec4ca0fbb176943c944cec) )
	ROM_LOAD16_BYTE( "0045.4s",  0x200000, 0x80000, CRC(4f4f2bee) SHA1(8276cdcd252d2d8fa41ab28e76a6bd72613c14ec) )
	ROM_LOAD16_BYTE( "0044.4p",  0x200001, 0x80000, CRC(20a4250b) SHA1(6a2e2596a9eef2792f7cdab648dd455b8e420a74) )
	ROM_LOAD16_BYTE( "0063a.6s", 0x300000, 0x80000, CRC(93933bcf) SHA1(a67d4839ffdb0eafbc2d68a60fb3bf1507c793cf) )
	ROM_LOAD16_BYTE( "0062a.6p", 0x300001, 0x80000, CRC(613e6f1d) SHA1(fd2ea18d245d0895e0bac6c5caa6d35fdd6a199f) )
	ROM_LOAD16_BYTE( "0065a.7s", 0x400000, 0x80000, CRC(6bcd1205) SHA1(c883c55f88d274ba8aa48c962406b253e1f8001e) )
	ROM_LOAD16_BYTE( "0064a.7p", 0x400001, 0x80000, CRC(7b4dce05) SHA1(36545917388e704f73a9b4d85189ec978d655b63) )
	ROM_LOAD16_BYTE( "0067a.9s", 0x500000, 0x80000, CRC(15845fba) SHA1(f7b670a8d48a5e9c261150914a06ef9a938a84e7) )
	ROM_LOAD16_BYTE( "0066a.9p", 0x500001, 0x80000, CRC(7130c575) SHA1(b3ea109981a1e5c631705b23dfad4a3a3daf7734) )

	ROM_REGION( 0x100000, REGION_SOUND1, 0 )	/* 1MB for ADPCM samples */
	ROM_LOAD( "0010-snd",  0x80000, 0x80000, CRC(bca27f40) SHA1(91a41eac116eb7d9a790abc590eb06328726d1c2) )

	ROM_REGION( 0x0600, REGION_PROMS, ROMREGION_DISPOSE )	/* microcode for growth renderer */
	ROM_LOAD( "092-1001.bin",  0x0000, 0x0200, CRC(b3251eeb) SHA1(5e83baa70aaa28f07f32657bf974fd87719972d3) )
	ROM_LOAD( "092-1002.bin",  0x0200, 0x0200, CRC(0c5314da) SHA1(a9c7ee3ab015c7f3ada4200acd2854eb9a5c74b0) )
	ROM_LOAD( "092-1003.bin",  0x0400, 0x0200, CRC(344b406a) SHA1(f4422f8c0d7004d0277a4fc77718d555f80fcf69) )
ROM_END

And here's getstar

ROM_START( getstar )
	ROM_REGION( 0x18000, REGION_CPU1, 0 )		/* Region 0 - main cpu code */
	ROM_LOAD( "rom0",         0x00000, 0x4000, CRC(6a8bdc6c) SHA1(c923bca539bd2eb9a34cb9c7a67a199e28bc081a) )
	ROM_LOAD( "rom1",         0x04000, 0x4000, CRC(ebe8db3c) SHA1(9046d6e63c33fc9cbd48b90dcbcc0badf1d3b9ba) )
	ROM_LOAD( "rom2",         0x10000, 0x8000, CRC(343e8415) SHA1(00b98055277a0ddfb7d0bda6537df10a4049533e) )

	ROM_REGION( 0x10000, REGION_CPU2, 0 )		/* Region 3 - sound cpu code */
	ROM_LOAD( "a68-03",       0x0000,  0x2000, CRC(18daa44c) SHA1(1a3d22a186c591321d1b836ee30d89fba4771122) )

	ROM_REGION( 0x0800, REGION_CPU3, 0 )	/* 2k for the microcontroller */
	ROM_LOAD( "68705.bin",    0x0000,  0x0800, NO_DUMP )

	ROM_REGION( 0x04000, REGION_GFX1, ROMREGION_DISPOSE )	/* Region 1 - temporary for gfx */
	ROM_LOAD( "a68_05-1",     0x00000, 0x2000, CRC(06f60107) SHA1(c5dcf0c7a5863ea960ee747d2d7ec7ac8bb7d3af) )  /* Chars */
	ROM_LOAD( "a68_04-1",     0x02000, 0x2000, CRC(1fc8f277) SHA1(59dc1a0fad23b1e98abca3d0b1685b9d2939b059) )

	ROM_REGION( 0x20000, REGION_GFX2, ROMREGION_DISPOSE )	/* Region 1 - temporary for gfx */
	ROM_LOAD( "a68_09",       0x00000, 0x8000, CRC(a293cc2e) SHA1(a2c2598e92982d13b51cbb6efb4b963142233433) )  /* Tiles */
	ROM_LOAD( "a68_08",       0x08000, 0x8000, CRC(37662375) SHA1(46ba8a3f0b553d476ecf431d0d20556896b4ca43) )
	ROM_LOAD( "a68_07",       0x10000, 0x8000, CRC(cf1a964c) SHA1(e9223c8d4f3bdafed193a1ded63e377f16f45e17) )
	ROM_LOAD( "a68_06",       0x18000, 0x8000, CRC(05f9eb9a) SHA1(a71640a63b259799086d361ef293aa26cec46a0c) )

	ROM_REGION( 0x20000, REGION_GFX3, ROMREGION_DISPOSE )	/* Region 1 - temporary for gfx */
	ROM_LOAD( "a68-13",       0x00000, 0x8000, CRC(643fb282) SHA1(d904d3c27c2b56341929c5eed4ea97e948c53c34) )  /* Sprites */
	ROM_LOAD( "a68-12",       0x08000, 0x8000, CRC(11f74e32) SHA1(02d8b4cc679f45a02c4989f2b62cde91b7418235) )
	ROM_LOAD( "a68-11",       0x10000, 0x8000, CRC(f24158cf) SHA1(db4c6b68a488b0798ea5f793ac8ced283a8ecab2) )
	ROM_LOAD( "a68-10",       0x18000, 0x8000, CRC(83161ed0) SHA1(a6aa28f22f487dc3a2ec07935e6d42bcdd1eff81) )

	ROM_REGION( 0x0300, REGION_PROMS, 0 )
	ROM_LOAD( "rom21",        0x0000,  0x0100, CRC(d6360b4d) SHA1(3e64548c82a3378fc091e104cdc2b0c7e592fc44) )
	ROM_LOAD( "rom20",        0x0100,  0x0100, CRC(4ca01887) SHA1(2892c89d5e60f1d10593adffff55c1a9654e8209) )
	ROM_LOAD( "rom19",        0x0200,  0x0100, CRC(513224f0) SHA1(15b34612206138f6fc5f7478925b1fff2ed56aa8) )
ROM_END

mahoneyt944

There could be an issue because the name description of getstar matches the rom name zip of guardians in the hood. What commit is your old mame2003 on?

Dochartaigh

lr-mame2003 should be verifying from the CRC32's from the files INSIDE the rom's zip though, correct? Like the error even lists the CRC's. My ClrMamePro-0.78-DAT-verified rom has matching CRC's for Guardians of the Hood like it should (which yes, is also listed under 'guardian' as the name...).

Seems like the older build of lr-mame2003 from the RetroPie 4.3 days (sorry, have another Pi booted up right now and can't switch at the moment or I would tell you the exact built ) got this right as Guardians of the Hood runs on those great (I took a video even if you want!), but something changed with whatever build of lr-mame2003 RetroPie 4.7.1 came with.

How do I get the version number of the 4.3? (if you need that and it'll help you diagnose).

mahoneyt944

Mame2003 is not tied to a retropie version. But as newer retropie builds are released, mame2003 also gets new releases. Likely there was a change made since mame2003 was loaded on the old retropie build you have. So to diagnose this we need a few bits of info:

Old mame2003 commit number (old retropie build)
New mame2003 commit number (new retropie build)

Get a rom to load in the core then enter the retroarch menu, the bottom of the screen should display the core name mame 2003 (.78) with the commit number.

Dochartaigh

@mitu said in Mame2003 game runs on 4.3 but not 4.7:

There may be some changes in the MAME 2003 version that changed the name of the romset or some files within it. Have you verified the ROM with the MAME 2003 .dat file ?

Just wanted to add that I just finished running that .XML file you linked me to in ClrMamePro and it looks to be full of errors, like a more than a few. I could be reading into this incorrectly as I'm NOT an expert whatsoever, but it doesn't seem to be based off the official Mame 2003/0.78 DAT. It found these errors:
https://pastebin.com/gNckDiT7

Now when I run my same set through the official .DAT file provided by Progettosnaps (that's the website with the older .DAT archives who I believe people from the official MameDev team run, and link to from mamedev.org) for my same mame2003/0.78 set it comes back 100% correct to my set:
https://pastebin.com/uAhucPLq

My set and the .DAT file) also matches exactly (like the .DAT files have matching checksums) what's on a certain Archive most of us are familiar with, so I'm totally confident I'm using the correct official verified set. (or I could be messing up ClrMamePro who knows lol ;)

This might not apply to my exact issue as guardian.zip isn't in the error log either way, but it still worries me as my issue is at heart because things aren't matching when they should!

mahoneyt944

@dochartaigh I solved this already. I'll be pushing a patch soon. I'll let you know once it's submitted so you can update.

Dochartaigh

@mahoneyt944 said in Mame2003 game runs on 4.3 but not 4.7:

@dochartaigh I solved this already. I'll be pushing a patch soon. I'll let you know once it's submitted so you can update.

You're the man! Thank you!!!

I was just reporting back that the runcommand options screen didn't say the build number, neither did RetroPie Setup when I go to main packages (closest numbers was Oct 21, 2020 for the 4.7.1 lr-mame2003 build).

mitu

@dochartaigh said in Mame2003 game runs on 4.3 but not 4.7:

I was just reporting back that the runcommand options screen didn't say the build number

That's not where the version/commit number is shown, as @mahoneyt944 said:

Get a rom to load in the core then enter the retroarch menu, the bottom of the screen should display the core name mame 2003 (.78) with the commit number.

mahoneyt944

@dochartaigh ok go into retropie setup, manage packages, main packages, mame2003, then update from source. This will take about 25 minutes or so. From source is important to get the new update. Then retest your guardian.zip rom

mahoneyt944

And to follow up on your xml dat.....the errors you have show that you're missing 7 games. These are mostly hacked games and clones of roms that were already supported.

The clones, like monster maulers, is just an english version of Kyukyoku Sentai Dadandarn (Japan).

The mortal kombat plus games are free to get here.
https://www.mortalkombatplus.com/

No copyright material is included.

Dochartaigh

@mahoneyt944 said in Mame2003 game runs on 4.3 but not 4.7:

@dochartaigh ok go into retropie setup, manage packages, main packages, mame2003, then update from source. This will take about 25 minutes or so. From source is important to get the new update. Then retest your guardian.zip rom

Works! Thank you so much for you help and speedy fix. Now I can bask in the glory of one of the most cheesiest early 90's games lol!

@mahoneyt944 said in Mame2003 game runs on 4.3 but not 4.7:

And to follow up on your xml dat.....the errors you have show that you're missing 7 games. These are mostly hacked games and clones of roms that were already supported.

Thanks for the info. To add to the confusion I'm also finding there's some "U1/2/3/4/5/6" sets (haven't figured out what the "U" actually stands for) but there's like 6 other .DAT files for Mame 0.78 - like incremental updates which I didn't think they did before the mame2004 set came out - so who knows which exact set (subset?) lr-mame2003 is using as it's basis either.

mahoneyt944

@dochartaigh well the beautiful thing about mame 2003 is you can generate your own dat file which will always match the version you're on. Open the mame menu and select "generate xml dat". It will save a xml dat file in your save directory.

Dochartaigh

@mahoneyt944 said in Mame2003 game runs on 4.3 but not 4.7:

@dochartaigh well the beautiful thing about mame 2003 is you can generate your own dat file which will always match the version you're on. Open the mame menu and select "generate xml dat". It will save a xml dat file in your save directory.

Can you tell me more about this please? I loaded up a game in lr-mame2003 and couldn't find any menu item (even after closing the game and just being in retroarch's menu) to "generate xml dat". Google says that mame2003-plus can do this, but didn't find anything about mame2003.

mahoneyt944

@dochartaigh it's accessable from the mame menu. Enter Retroarch menu(select + x) after you load a rom in the core, quick menu -> options -> display mame menu -> on. Then return to the game screen to use the mame menu.

If your default mapping is still present you can press tab on a keyboard to toggle it on.

Dochartaigh

@mahoneyt944 said in Mame2003 game runs on 4.3 but not 4.7:

@dochartaigh it's accessable from the mame menu. Enter Retroarch menu(select + x) after you load a rom in the core, quick menu -> options -> display mame menu -> on. Then return to the game screen to use the mame menu.

Beautiful! Thanks. Actually showed up in Arabian Magic (arabianm.zip) I was playing without having to turn on the mame menu (I was looking for the 4-player option and happened to find it). 19mb - I'll run it against the ROMs I have in ClrMamePro.

While I have you here, since you seem to be the expert with mame2003 (and I assume knowledgeable for mame/arcade stuff overall, especially for Raspberry Pi's), I have a question for you: for years I've been discounting games which say "doesn't work" in the google doc mame/arcade compatibility lists (there's 3 main ones) the official RetroPie Docs on this website link to.

I'm going through a 3-4 player game list I found online with ~40 games, and was cross referencing those lists to see which emulator I should try them out in on my RP4. I'm coming to the realization I maybe shouldn't be trusting even a single one of those lists as I took a chance and tried out those "doesn't work" ones anyway, and I'm not even a third through the list and a TON actually DO work well so far.

My question is: where should I turn to for better info? Is there someplace I'm missing? Every one of the lists in the official docs seem to be WAY outdated, like in numerous ways:

• The one listed on the official RetroPie Docs for FinalBurn Neo is outdated and seems to be the old list for fbalpha, although fbalpha uses 0.2.97.42, and fbneo uses 0.2.97.44. Several of these games so far ALSO worked! No "RP4 Status" column despite that model being out for ~1.5 years so far!

• ~~The mame2003 seems to be the best out of all of them, but still doesn't seem to be accurate as some marked 'not working' are working!~~ EDIT, just saw the RP4 tab here - awesome! Going to go back through.

• And my last resort list, if I strike out in the above (which are the two main emulators I use) is the compatibility list from the overarching RetroPie Doc (the "Arcade" section, which is over top of fbneo and mame2003). That one is going to be where people look first, and that links to a "Retropie Arcade Logbook", which says "MAME .171 FULL" in the header... which unless I missed it there doesn't even seem to be a .171 emulator listed anywhere in the Docs so I don't know where that's even from and from how long ago it was created... or how out of date it really is...

(they all seem to have a lock icon on each tab so I can't edit any of these 3x above lists myself either – to make them more accurate, they're all locked and the link to the Github -where I assume it might say how to update them or ask for access, is broke in each doc as well lol...)

Sorry for writing the above novel but I'm trying to expand my playable mame/arcade library and bad data is kinda throwing a wrench in those efforts and wanted to ask somebody who really knows there stuff if there's something I'm missing.

mahoneyt944

@dochartaigh none of the compatibility charts are very accurate. I would just try them out and see for yourself. Though you can use the xml dat file for general expectations I suppose.

Just open it in a text editor then search for the rom name. At the bottom of each games data you'll see a line:

driver status= "good" color= "good" sound="good"

This is probably the closest you'll get to a "compatibility list". Don't be discouraged to test a game that has "imperfect" tags as the imperfections may not be noticable to the average user.

Mame2003 and Mame2003-plus get updated pretty regularly by a small group of maintainers which is why compatibility charts are often wrong.

dankcushions

@dochartaigh the compatibility lists are so bad BECAUSE they're open to user contributions and google sheets do not have the collaboration tools to lock them down to the extent where they don't get filled with garbage worksheets over time.

for a time we would try to curate them but all it takes is one bot, or a user who uses the wrong romset and thinks that means a game isn't supported, and then they're back to being useless.

so, to that end they have become useless and will be removed from the docs. i'm going to do that today.

Dochartaigh

@mahoneyt944 said in Mame2003 game runs on 4.3 but not 4.7:

Just open it in a text editor then search for the rom name. At the bottom of each games data you'll see a line:

driver status= "good" color= "good" sound="good"

This is probably the closest you'll get to a "compatibility list". Don't be discouraged to test a game that has "imperfect" tags as the imperfections may not be noticable to the average user.

That's a good tip, thanks, was seeing that on a new site I discovered as well, http://adb.arcadeitalia.net/lista_mame.php, where they have status for a bunch fo different aspects of each rom (think that one is solely for the most recent MAME though).

@dankcushions said in Mame2003 game runs on 4.3 but not 4.7:

@dochartaigh the compatibility lists are so bad BECAUSE they're open to user contributions

That's what I feared. I would have also liked to help, but looks like that boat has sailed a while ago.

mahoneyt944

@dankcushions why don't you pull the latest xml dat from the mame cores git page then write the game status to a retropie.org page. That could be a decent compatibility list. Each time the page is loaded it grabs the latest xml dat and populates the list:

dankcushions

@mahoneyt944 aren't those statuses what are used to generate the in-game MAME warning message? if not, they should be IMO. if the core knows about them internally, it shouldn't need a user to go out seeking some external document.

besides, my personal feeling is that trying to being so granular about what games work on what isn't what RetroPie should be trying to track/maintain - it would just be so much work. we should focus on documenting RetroPie :)

however, it's something for emulator authors to consider i suppose. for example: duckstation