View Full Version : Mame - i can't get roms to work

January 20th, 2006, 10:10
i'm trying to play my roms but the thing is that they won't work. they appear on the 'available' option. everytime i click on them nothing happens. i right click and choose the "play [insert rom] option". can anybody help me on this please

January 20th, 2006, 15:40
What error message do you get?

And what game are you trying to play?

And have you even noticed that you sig has been removed?

January 20th, 2006, 17:21
i noticed the sig... but there is no message... my roms are recognized from my directory but they won't play... i haven't played the roms in 5 months... and just so happened i felt like playing now

January 20th, 2006, 18:32
I'm just curious: are you using the latest MAME build, regardless of whether it's Plus!/FX/whatever?

January 20th, 2006, 22:16

January 20th, 2006, 22:17
mame32fx 099u6 to be exact

January 21st, 2006, 01:30
1. First, update to the latest MAME build, if only just for kicks.
2. So you're saying that the rom audit finds the games, but nothing shows up when you run any of them?
3. For the sake of just entertaining me, please name at least one of these games, so I can test it myself.

January 21st, 2006, 03:49
i did audit the games. this is what came up...

avsp : avpe.03d 524288 bytes NOT FOUND
CRC(774334a9) SHA1(f60b0e39139ea40e0b0ba97ed01d4a757ed 65e1a)
avsp : avpe.04d 524288 bytes NOT FOUND
CRC(7fa83769) SHA1(930f02e4d35686e80fbdd673380c4b2bd78 4a9e5)
avsp : avpex.03d 524288 bytes NOT FOUND
CRC(73dd740e) SHA1(c577928eb42616c87439fa30299daa59865 14c37)
avsp : avpex.04d 524288 bytes NOT FOUND
CRC(185f8c43) SHA1(6802787918a794c8c44aec887c7f17eeeee 1885d)
avspa : avpax.03d 524288 bytes NOT FOUND
CRC(efbe8b5f) SHA1(a49a8ce4bb74c7630c0e84137a0c027516c b9994)
avspa : avpax.04d 524288 bytes NOT FOUND
CRC(3b1aa217) SHA1(b6ba1929fba00091b94e1e3fc7fcb82c4ac b0271)
xmcota : xmne.03e 524288 bytes NOT FOUND
CRC(a9a09b09) SHA1(e316f443d393139894592dbb1b676f3a238 5ed14)
xmcota : xmne.04e 524288 bytes NOT FOUND
CRC(52fa2106) SHA1(6904eef0fb11e44046e160a1c0ff6ea4833 7f630)
xmcota : xmn.06a 524288 bytes NOT FOUND
CRC(1b86a328) SHA1(2469cd705139ee9f1142e6e379e68d0c967 5b37e)
xmcota : xmn.09a 524288 bytes NOT FOUND
CRC(9241cae8) SHA1(bb6980abf25aaf3eb14e230ca6942f3e2ab 2c660)
xmcota : xmnex.03e 524288 bytes NOT FOUND
CRC(2f5daa9f) SHA1(16a25c45ab2a267b402539c5b9b6dbaf8bc c56ba)
xmcota : xmnex.04e 524288 bytes NOT FOUND
CRC(f0e24605) SHA1(c72105491d9c1d97286eea09c9ac506fa23 4a776)
xmcotau : xmn.06a 524288 bytes NOT FOUND (shared with parent)
CRC(1b86a328) SHA1(2469cd705139ee9f1142e6e379e68d0c967 5b37e)
xmcotau : xmn.09a 524288 bytes NOT FOUND (shared with parent)
CRC(9241cae8) SHA1(bb6980abf25aaf3eb14e230ca6942f3e2ab 2c660)
xmcotau : xmnux.03e 524288 bytes NOT FOUND
CRC(27636ac7) SHA1(b1aee9afbc1feebc7bf810411175771cac1 addfb)
xmcotau : xmnux.04e 524288 bytes NOT FOUND
CRC(0aed300c) SHA1(9f1b69ebb4c31cbf3ff195e9297da0742c4 87482)
xmcotaj1: xmnj.03a 524288 bytes NOT FOUND
CRC(00761611) SHA1(e780dbe1d21a0d5b6981f0395942c9fa596 88113)
xmcotaj1: xmnj.04a 524288 bytes NOT FOUND
CRC(614d3f60) SHA1(2272ae243557562a0bc85d2cd2b37dd876f 6902c)
xmcotaj1: xmnjx.03a 524288 bytes NOT FOUND
CRC(515b9bf9) SHA1(57e4604e7e013d95629546988db2448896d c95f2)
xmcotaj1: xmnjx.04a 524288 bytes NOT FOUND
CRC(5419572b) SHA1(7f25cd7aaa30569b4e3889d9b6066bb6b63 8e91e)
xmcotaa : xmna.03a 524288 bytes NOT FOUND
CRC(7df8b27e) SHA1(2f0ce6b10857e04ddaf7a76edf126282c53 511b3)
xmcotaa : xmna.04a 524288 bytes NOT FOUND
CRC(b44e30a7) SHA1(27b0a8b06aa11673dd145717c6286eb2718 6cf79)
xmcotaa : xmnax.03a 524288 bytes NOT FOUND
CRC(978a0de4) SHA1(cdf3542f03cbf373efc8596ac886566b345 8647d)
xmcotaa : xmnax.04a 524288 bytes NOT FOUND
CRC(07cb0839) SHA1(1aaf5ba8e256107ce8ef7dbd961b15149dc 6d11b)
xmvsf : xvse.03d 524288 bytes NOT FOUND
CRC(5ae5bd3b) SHA1(f687f018008cef24f86f53373c3f5547741 a4c5b)
xmvsf : xvse.04d 524288 bytes NOT FOUND
CRC(5eb9c02e) SHA1(25a392913213b98ce1bbd463bf5e5e10729 bde0c)
xmvsf : xvsex.03d 524288 bytes NOT FOUND
CRC(3b3e7836) SHA1(fca470d98a04f4391dee3dd3bb1cb9fa479 99341)
xmvsf : xvsex.04d 524288 bytes NOT FOUND
CRC(108863ce) SHA1(5ffa4af1afa4ea3530927fabfc49bf95ba8 7c5c6)
mshvsf : mvse.03f 524288 bytes NOT FOUND
CRC(b72dc199) SHA1(61bd581ea4b969298f8a39fe03023b5456c ac750)
mshvsf : mvse.04f 524288 bytes NOT FOUND
CRC(6ef799f9) SHA1(2d45dbf7bc277b84c6bcd9615ab3b80c42a f7781)
mshvsf : mvs.05a 524288 bytes NOT FOUND
CRC(1a5de0cb) SHA1(738a27f83704c208d36d73bf766d861ef2d 51a89)
mshvsfb : mvsb.03g 524288 bytes NOT FOUND
CRC(143895ef) SHA1(0664fad64996118df86e9887bd6e301d04d 84978)
mshvsfb : mvsb.04g 524288 bytes NOT FOUND
CRC(dd8a886c) SHA1(a16f262fd14e726c7837980d0556a9c3bdc 7fb11)
batmanfr: epr19730.ic8 524288 bytes NOT FOUND (BIOS)
CRC(d0e0889d) SHA1(fae53107c894e0c41c49e191dbe706c9cd6 e50bd)
batmanfr: mp17951a.s 524288 bytes NOT FOUND (BIOS)
CRC(2672f9d8) SHA1(63cf4a6432f6c87952f9cf3ab0f977aed23 67303)
batmanfr: mp17952a.s 524288 bytes NOT FOUND (BIOS)
CRC(d1be2adf) SHA1(eaf1c3e5d602e1139d2090a78d7e19f04f9 16794)
batmanfr: 20091.bin 524288 bytes NOT FOUND (BIOS)
CRC(59ed40f4) SHA1(eff0f54c70bce05ff3a289bf30b1027e1c8 cd117)
batmanfr: mp17953a.ic8 524288 bytes NOT FOUND (BIOS)
CRC(a4c47570) SHA1(9efc73717ec8a13417e65c54344ded9fc25 bf5ef)
batmanfr: mp17954a.s 524288 bytes NOT FOUND (BIOS)
CRC(f7722da3) SHA1(af79cff317e5b57d49e463af16a9f616ed1 eee08)
batmanfr: stv110.bin 524288 bytes NOT FOUND (BIOS)
CRC(3dfeda92) SHA1(8eb33192a57df5f3a1dfb57263054867c6b 2db6d)
fatfury1: sfix.sfx 131072 bytes NOT FOUND (BIOS)
CRC(354029fc) SHA1(4ae4bf23b4c2acff875775d4cbff5583893 ce2a1)
fatfury1: sp-s2.sp1 131072 bytes NOT FOUND (BIOS)
CRC(9036d879) SHA1(4f5ed7105b7128794654ce82b51723e16e3 89543)
fatfury1: sp-s.sp1 131072 bytes NOT FOUND (BIOS)
CRC(c7f2fa45) SHA1(09576ff20b4d6b365e78e6a5698ea450262 697cd)
fatfury1: usa_2slt.bin 131072 bytes NOT FOUND (BIOS)
CRC(e72943de) SHA1(5c6bba07d2ec8ac95776aa3511109f5e1e2 e92eb)
fatfury1: sp-e.sp1 131072 bytes NOT FOUND (BIOS)
CRC(2723a5b5) SHA1(5dbff7531cf04886cde3ef022fb5ca68757 3dcb8)
fatfury1: asia-s3.rom 131072 bytes NOT FOUND (BIOS)
CRC(91b64be3) SHA1(720a3e20d26818632aedf2c2fd16c54f213 543e1)
fatfury1: vs-bios.rom 131072 bytes NOT FOUND (BIOS)
CRC(f0e8f27d) SHA1(ecf01eda815909f1facec62abf3594eaa8d 11075)
fatfury1: sp-j2.rom 131072 bytes NOT FOUND (BIOS)
CRC(acede59c) SHA1(b6f97acd282fd7e94d9426078a90f059b5e 9dd91)
fatfury1: sp1.jipan.1024 131072 bytes NOT FOUND (BIOS)
CRC(9fb0abe4) SHA1(18a987ce2229df79a8cf6a84f968f0e42ce 4e59d)
fatfury1: sm1.sm1 131072 bytes NOT FOUND (BIOS)
CRC(97cf998b) SHA1(977387a7c76ef9b21d0b01fa69830e949a9 a9626)
fatfury1: 000-lo.lo 65536 bytes NOT FOUND (BIOS)
CRC(e09e253c) SHA1(2b1c719531dac9bb503f22644e6e4236b91 e7cfc)
kinst2 : kinst2 NOT FOUND
SHA1(ab0242233d2eaf9d907abe246a54e09a8a2 561a5) MD5(2563b089b316f2c8636d78af661ac656)
Audit complete.

January 21st, 2006, 04:52
NOT FOUND would be your first clue. Maintaining a set of arcade roms is far different from the consoles. You have bios to worry about, parent/clone relationships, and the fact that sets often change as MAME is updated, which means downloading new roms.

Looking at your audit I suspect you have some clone sets without the parents.

January 21st, 2006, 07:54
so does that mean i have to redownload the roms again

January 21st, 2006, 08:00
"bios"... (how do i install this/these) "parent/clone relationships,"... (do roms create copies of itself when emulated?) "the fact that sets often change as MAME is updated"... (does that mean that the roms i got the from the site are invalid b/c their roms never change or are updated?)

January 21st, 2006, 15:44
I'd suggest running them through ClrMamePro and rebuilding with the latest mame dat and see if/what files are missing, and getting the latest MAME32FX.

January 21st, 2006, 15:55
Think of the parent set as the "main" rom for a particular game. It contains all the files necessary to run the game. The clones only contain the files which distinguish them from the parent (usually region differences, jap/us/europe etc.). If you right-click the game entry in the gui and bring up the properties, it'll show you the name of the parent set (assuming you have a clone).

MAWS (http://www.mameworld.net/maws/) is a great resource for roms. Type in a name (or set name) and it'll show you what you need, and give you an idea of what you may be missing.

January 21st, 2006, 22:24
what model is the latest model of mame after mame32fx 099u6

January 21st, 2006, 22:35
I am using also Mame32 0.102

January 22nd, 2006, 02:06
how do i work clmame pro

January 22nd, 2006, 02:16
Don't do anything they say, not that its not relevant, in fact it is, but i will give you a special build of MamePlus which support the games you want to play & i'll give you the Latest NeoGeo bios, cheats & commands(list of moves/buttons).

Unzip the emulator & run the exe, chose a folder for the extraction(where you want your emulator's main directory to be)

For the Neogeo, its the bios for neogeo games, just put it in your roms folder(as it is, don't unzip it).

For the cheat.dat, unzip in your mameplus main directory(where the exe of the game is).

For the command.dat, same as for the cheat.dat, unzip in your mameplus main directory(where the exe of the game is). A command.dat give you a list of movement combo that your player can do & tells you which button do what. To acces the list, while in game, press "TAB", then "Game Documents", & last press "Show Command List".

For the txt, it explain a cheating altenative for all the NeoGeo games, with the using of the unibios, which i've merge into the neogeo bios. Its quit helpful, cause some NeoGeo games don't have cheats in the cheat.dat(not yet supported)

Good Luck & Have Fun!

If you still need help, PM me :D

January 22nd, 2006, 04:25
furio... you are the sh*t. i appreciate this. if ya need anything, roms, etc. email me.

January 22nd, 2006, 15:17
Sorry furio, but the neo-geo bios is copyrighted material, same as a rom. That's a ban.

furio... you are the sh*t. i appreciate this. if ya need anything, roms, etc. email me.
I could ban you for that (offering roms), but I'll let you slide with a warning.