Entrance | Main Index | Search | New user | Login | Who's Online | FAQ | Rules

MAMEWorld >> EmuChat
Previous thread Previous  View all threads Index   Next thread Next   Threaded Mode Threaded  

Pages: 1

Vuader
MAME Fan
Reged: 08/12/14
Posts: 2
Send PM


Solved: -listroms differ between linux and Windows
#329777 - 08/12/14 08:49 AM
Reply to this post Reply


I am trying to play a rom on a windows machine, but get


Quote:

the selected rom is missing one or more required rom or chd images




On Linux, this rom works fine.

The strange thing is the difference between the output of -listroms and -verifyroms when run on linux vs when run on windows.

On linux:


Quote:

mame xmcota -verifyroms
romset xmcota is good
1 romsets found, 1 were OK.




but on windows:


Quote:

mame64.exe xmcota -verifyroms
xmcota : xmne.03f (524288 bytes) - NOT FOUND
xmcota : xmne.04f (524288 bytes) - NOT FOUND
xmcota : xmne.05b (524288 bytes) - NOT FOUND
xmcota : xmne.10b (524288 bytes) - NOT FOUND
xmcota : qsound.bin (8192 bytes) - NOT FOUND (qsound)
romset xmcota is bad
1 romsets found, 0 were OK.




Those roms obviously does not exist in the .zip romfile. But they also do not show up when running -listroms on linux:


Quote:

mame xmcota -listroms
ROMs required for driver "xmcota".
Name Size Checksum
xmne.03e 524288 CRC(a9a09b09) SHA1(e316f443d393139894592dbb1b676f3a2385ed14)
xmne.04e 524288 CRC(52fa2106) SHA1(6904eef0fb11e44046e160a1c0ff6ea48337f630)
xmn.05a 524288 CRC(ac0d7759) SHA1(650d4474b13f16af7910a0f721fcda2ddb2414fd)
xmn.06a 524288 CRC(1b86a328) SHA1(2469cd705139ee9f1142e6e379e68d0c9675b37e)
xmn.07a 524288 CRC(2c142a44) SHA1(7624875f9c39b361fc83e52e87e0fd5e96279713)
xmn.08a 524288 CRC(f712d44f) SHA1(0d18d4a4eacad94a66beca6ec509ac7f690c6882)
xmn.09a 524288 CRC(9241cae8) SHA1(bb6980abf25aaf3eb14e230ca6942f3e2ab2c660)
xmn.10a 524288 CRC(53c0eab9) SHA1(e3b1ec1fd517735f7801cfebb257c43185c6d3fb)
xmn.13m 4194304 CRC(bf4df073) SHA1(4d2740c3a827f0ec2cf75ad99c65e393c6a11c23)
xmn.15m 4194304 CRC(4d7e4cef) SHA1(50b8797b8099a8d76ad063ba1201a13dbb88ae3a)
xmn.17m 4194304 CRC(513eea17) SHA1(a497477ad9ac13180911d8745ef6ee1955c0b877)
xmn.19m 4194304 CRC(d23897fc) SHA1(1e31627999736652252164d32662779a1ac6ca29)
xmn.14m 4194304 CRC(778237b7) SHA1(89a759ec383518ec52f5059d10ec342f2247aa20)
xmn.16m 4194304 CRC(67b36948) SHA1(692fb6e4096b880aa22996d554b160f664bbd907)
xmn.18m 4194304 CRC(015a7c4c) SHA1(cccc95dafd076a1a9fa004710006149c42d058ba)
xmn.20m 4194304 CRC(9dde2758) SHA1(17ba259cad03c7b5d56c0a5eda9ab53521665729)
xmn.01a 131072 CRC(40f479ea) SHA1(f29e15f537675305264ae2138a0a537fb9e2008b)
xmn.02a 131072 CRC(39d9b5ad) SHA1(af502debfd36100d4fc971ed25fdf9d7121d6f18)
xmn.11m 2097152 CRC(c848a6bc) SHA1(ac8ac564d3c43225822f8bc330eba9f35b24b0a4)
xmn.12m 2097152 CRC(729c188f) SHA1(3279774ad8aebbcf0fc779cdfcbe21044dd192ad)




On windows, these differ:


Quote:

mame64.exe xmcota -listroms
ROMs required for driver "xmcota".
Name Size Checksum
xmne.03f 524288 CRC(5a726d13) SHA1(046d068f1f3c3d2a0b73df5b1f69a6afdde8d030)
xmne.04f 524288 CRC(06a83f3a) SHA1(2f30de88fccb104bfd038310483a63de7bee4b94)
xmne.05b 524288 CRC(87b0ed0f) SHA1(f4d78fdd9fcf864e909d9a2bb351b49a5f8ec7a0)
snip
qsound.bin 8192 BAD CRC(059c847d) SHA1(229cead1be2f86733dd80573d4983ba482355ece) BAD_DUMP




Any idea why this is and what I should do to play the rom on windows?

10 of the 12 roms that I have works on the windows PC. And not sure if it's related, but this error pops up when mame starts: "Error playing: 80070057"

Edited by Vuader (08/12/14 11:43 AM)



Dullaron
Diablo III - Dunard #1884
Reged: 07/22/05
Posts: 6125
Loc: Fort Worth, Tx
Send PM


Linux version having reading issue on some games loading. new [Re: Vuader]
#329778 - 08/12/14 09:22 AM Attachment: firefox.png 1052 KB (0 downloads)
Reply to this post Reply


For example. Fire Fox have a missing message on the SDLMAME. Top snapshot. Under that snapshot is the working MAME64 version. Weird huh?

A little different on Cube Quest. Crashes on the Linux version. But it loaded on the MAME64 without a problem.

0.154

Been this way for a while now.

Gotta be the SDL can't read the videos in the CHD files. Probably not compatible.

Anyway just because something works on the MAME/MAME64 doesn't mean it will work on Linux version.

I'm not bashing any DEV on this. Just pointing out to others.

[ATTACHED IMAGE - CLICK FOR FULL SIZE]

Attachment


W11 Home 64-bit + Nobara OS / AMD Radeon RX 5700 XT / AMD Ryzen 7 3700X 8-Core 3.59 GHz / RAM 64 GB


Roman
Regular
Reged: 09/21/03
Posts: 1584
Send PM


Re: -listroms differ between linux and Windows new [Re: Vuader]
#329780 - 08/12/14 09:29 AM
Reply to this post Reply


Generally speaking, if MAME complains about a missing file, you do miss it.
The reason can be:

- wrong configuration of rompaths
- outdated sets (incl. missing parent sets, missing device and bios sets)
- you simply use different MAME versions on your linux machine than on your windows machine....looking at the output it's more that..

e.g. xmn.05a sha1 650d4474b13f16af7910a0f721fcda2ddb2414fd which is listed in your linux output is not a parent xmcota rom in .154...it's part of its clones.

...so you should double check the versions first...and after that, you can double check the sets...(and availability of qsound device archive).



Vuader
MAME Fan
Reged: 08/12/14
Posts: 2
Send PM


Re: -listroms differ between linux and Windows new [Re: Roman]
#329781 - 08/12/14 11:42 AM
Reply to this post Reply


Thanks for the advice Roman, you are a legend.

It turns out I was running .145 on linux. Put that same version on windows, now the rom plays fine.

A am a bit of a mame noob, so I do not understand how to check for parent/device/bios sets, or how to see if something is a clone or a parent rom.

Are there any good literature that you can refer me to? (man mame talks about parents/clones as if one is familiar)



R. Belmont
Cuckoo for IGAvania
Reged: 09/21/03
Posts: 9716
Loc: ECV-197 The Orville
Send PM


Re: -listroms differ between linux and Windows new [Re: Vuader]
#329793 - 08/12/14 05:28 PM
Reply to this post Reply


> Thanks for the advice Roman, you are a legend.
>
> It turns out I was running .145 on linux. Put that same version on windows, now the
> rom plays fine.
>
> A am a bit of a mame noob, so I do not understand how to check for parent/device/bios
> sets, or how to see if something is a clone or a parent rom.
>
> Are there any good literature that you can refer me to? (man mame talks about
> parents/clones as if one is familiar)

The text at the very top of this forum is very relevant to your questions

Google "ClrMAME" and "Pleasuredome Tracker" and you'll be able to run everything forever.


Pages: 1

MAMEWorld >> EmuChat
Previous thread Previous  View all threads Index   Next thread Next   Threaded Mode Threaded  

Extra information Permissions
Moderator:  Robbbert, Tafoid 
0 registered and 526 anonymous users are browsing this forum. 		You cannot start new topics
You cannot reply to topics
HTML is enabled
UBBCode is enabled
Thread views: 4841

Browser Test | Delete Cookies atom-guru atom-guru *
UBB.threads™ 6.3.2