|
CLRmamePro Reports Wrong !! (Or is it mame which is wrong ?)
#291560 - 07/12/12 02:26 AM
|
|
|
Anyone has the same problem with me ? I'm using MameUI64(146u2) and clrmamepro v4.06 !
It reports the rom "epr-14105.ic18" in in the romset "radr" Rad Rally(World) as missing and the rom "epr-14105.ic16" has to be replaced to the games clone "radru". But actually these are the same file with identicall crc's.It doesnt ask to rename the file. What is wrong ?
Likewise , it reports the rom "epr-13523.ic22" in in the romset "radm" Rad Mobile(World) as "missing but fixable" but it is there in the romset.Mame doesnt give any error loading the game.Just the name is different.ClrMame doesnt ask to rename it. What is wrong ?
Moreover , in the romset "manxtt" it reports the roms "epr-18924a.30" and "mpr-18763.31" as unneeded files.These two was just added in previous versions. WTF is going on ?
Edited by Hibo (07/12/12 02:27 AM)
|
|
|
| B2K24 |
|
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
|
|
Reged: 10/25/10
|
|
Posts: 2663
|
|
|
|
|
|
Send PM
|
|
|
Re: CLRmamePro Reports Wrong !! (Or is it mame which is wrong ?)
[Re: Hibo]
#291564 - 07/12/12 02:55 AM
|
|
|
You are not supposed to audit with MameUI. It's not even officially supported anymore for running games.
Audit with the official mame binary from mamedev.org OR properly created XMLs from http://www.emulab.it/rommanager/
|
|
|
| redk9258 |
|
Regular
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 3968
|
|
Loc: Troy, Illinois USA
|
|
|
|
Send PM
|
|
|
Re: CLRmamePro Reports Wrong !! (Or is it mame which is wrong ?)
[Re: B2K24]
#291569 - 07/12/12 03:43 AM
|
|
|
> You are not supposed to audit with MameUI. It's not even officially supported anymore
> for running games.
>
> Audit with the official mame binary from mamedev.org OR properly created XMLs from
> http://www.emulab.it/rommanager/
Instead of bashing MAMEUI, let's look at the source. The way CLRMAMEPRO gets it's dat file will result in the same results if made from MAME or MAMEUI.
Code:
ROMs required for driver "radr".
Name Size Checksum
epr-14241.ic21 131072 CRC(59a5f63d) SHA1(325a26a09475ddc828de71e71a1d3043f3959cec)
epr-14106.ic37 524288 CRC(e73c63bf) SHA1(30fb68eaa7d02a232c873bd7751cac7d0fa08e44)
epr-14107.ic38 524288 CRC(832f797a) SHA1(b0c16ef7bd8d37f592975052ba9da3da70a2fc79)
epr-14108.ic9 131072 CRC(38a99b4d) SHA1(b6455e6b29bfef41c5e0ebe3a8064889b7e5f5fd)
epr-14109.ic14 524288 CRC(b42e5833) SHA1(da94ce7c1d7a581a1aa6b79b323c67a919918808)
epr-14110.ic20 524288 CRC(b495e7dc) SHA1(b4143fcee10e0649378fdb1e3f5a0a2c585414ec)
epr-14237.ic22 524288 CRC(0a4b4b29) SHA1(98447a587f903ba03e17d6a145b7c8bfddf25c4d)
epr-14102.ic3 262144 CRC(5626e80f) SHA1(9844817295a8cd8a9b09da6681b0c1fbfe82618e)
epr-14103.ic7 262144 CRC(08c7e804) SHA1(cf45b1934edc43cb3a0ed72159949cb0dd00d701)
epr-14104.ic12 262144 CRC(b0173646) SHA1(1ba4edc033e0e4f5a1e02987e9f6b8b1650b46d7)
epr-14105.ic18 262144 CRC(614843b6) SHA1(d4f2cd3b024f7152d6e89237f0da06adea2efe57)
mpr-13511.ic1 1048576 CRC(f8f15b11) SHA1(da6c2b8c3a94c4c263583f046823eaea818aff7c)
mpr-13512.ic5 1048576 CRC(d0be34a6) SHA1(b42a63e30f0f7a94de8a825ca93cf8efdb7a7648)
mpr-13513.ic10 1048576 CRC(feef1982) SHA1(bdf906317079a12c48ef4fca5bef0d437e9bf050)
mpr-13514.ic16 1048576 CRC(d0f9ebd1) SHA1(510ebd3d7a52bcab2debea61591770d1dff172a1)
mpr-13515.ic2 1048576 CRC(77bf2387) SHA1(7215dde5618e238edbe16b3007ede790785fe25f)
mpr-13516.ic6 1048576 CRC(8c4bc62d) SHA1(3206f623ec0b7558413d063404103b183f26b488)
mpr-13517.ic11 1048576 CRC(1d7d84a7) SHA1(954cfccfc7250a5bead2eeba42e655d5ac82955f)
mpr-13518.ic17 1048576 CRC(9ea4b15d) SHA1(7dcfd6d42bb945beca8344cf92e7bd53903a824b)
epr-14084.17 32768 CRC(f14ed074) SHA1(e1bb23eac85e3236046527c5c7688f6f23d43aef)
eeprom-radr.bin 128 CRC(602032c6) SHA1(fecf14017e537fe870457d2a8d4f86ec6d442b90)
ROMs required for driver "radru".
Name Size Checksum
epr-14240.ic21 131072 CRC(8473e7ab) SHA1(fbd883dc804d7de6ce239b68c6e6ae3a54e9e03c)
epr-14106.ic37 524288 CRC(e73c63bf) SHA1(30fb68eaa7d02a232c873bd7751cac7d0fa08e44)
epr-14107.ic38 524288 CRC(832f797a) SHA1(b0c16ef7bd8d37f592975052ba9da3da70a2fc79)
epr-14108.ic9 131072 CRC(38a99b4d) SHA1(b6455e6b29bfef41c5e0ebe3a8064889b7e5f5fd)
epr-14109.ic14 524288 CRC(b42e5833) SHA1(da94ce7c1d7a581a1aa6b79b323c67a919918808)
epr-14110.ic20 524288 CRC(b495e7dc) SHA1(b4143fcee10e0649378fdb1e3f5a0a2c585414ec)
epr-14237.ic22 524288 CRC(0a4b4b29) SHA1(98447a587f903ba03e17d6a145b7c8bfddf25c4d)
epr-14102.ic3 262144 CRC(5626e80f) SHA1(9844817295a8cd8a9b09da6681b0c1fbfe82618e)
epr-14103.ic7 262144 CRC(08c7e804) SHA1(cf45b1934edc43cb3a0ed72159949cb0dd00d701)
epr-14104.ic12 262144 CRC(b0173646) SHA1(1ba4edc033e0e4f5a1e02987e9f6b8b1650b46d7)
epr-14105.ic16 262144 CRC(614843b6) SHA1(d4f2cd3b024f7152d6e89237f0da06adea2efe57)
mpr-13511.ic1 1048576 CRC(f8f15b11) SHA1(da6c2b8c3a94c4c263583f046823eaea818aff7c)
mpr-13512.ic5 1048576 CRC(d0be34a6) SHA1(b42a63e30f0f7a94de8a825ca93cf8efdb7a7648)
mpr-13513.ic10 1048576 CRC(feef1982) SHA1(bdf906317079a12c48ef4fca5bef0d437e9bf050)
mpr-13514.ic16 1048576 CRC(d0f9ebd1) SHA1(510ebd3d7a52bcab2debea61591770d1dff172a1)
mpr-13515.ic2 1048576 CRC(77bf2387) SHA1(7215dde5618e238edbe16b3007ede790785fe25f)
mpr-13516.ic6 1048576 CRC(8c4bc62d) SHA1(3206f623ec0b7558413d063404103b183f26b488)
mpr-13517.ic11 1048576 CRC(1d7d84a7) SHA1(954cfccfc7250a5bead2eeba42e655d5ac82955f)
mpr-13518.ic17 1048576 CRC(9ea4b15d) SHA1(7dcfd6d42bb945beca8344cf92e7bd53903a824b)
epr-14084.17 32768 CRC(f14ed074) SHA1(e1bb23eac85e3236046527c5c7688f6f23d43aef)
eeprom-radr.bin 128 CRC(602032c6) SHA1(fecf14017e537fe870457d2a8d4f86ec6d442b90)
Looking closely you will see these as being different...
Code:
ROMs required for driver "radr".
Name Size Checksum
epr-14241.ic21 131072 CRC(59a5f63d) SHA1(325a26a09475ddc828de71e71a1d3043f3959cec)
epr-14105.ic18 262144 CRC(614843b6) SHA1(d4f2cd3b024f7152d6e89237f0da06adea2efe57)
ROMs required for driver "radru".
Name Size Checksum
epr-14240.ic21 131072 CRC(8473e7ab) SHA1(fbd883dc804d7de6ce239b68c6e6ae3a54e9e03c)
epr-14105.ic16 262144 CRC(614843b6) SHA1(d4f2cd3b024f7152d6e89237f0da06adea2efe57)
I use split sets and CLRMAMEPRO 4.06 put those two different ROMs in radru.7z
|
|
|
| redk9258 |
|
Regular
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 3968
|
|
Loc: Troy, Illinois USA
|
|
|
|
Send PM
|
|
|
Re: CLRmamePro Reports Wrong !! (Or is it mame which is wrong ?)
[Re: redk9258]
#291573 - 07/12/12 04:27 AM
|
|
|
I just did a test. I compiled MAME64 0.142u2 and MAMEUI64 0.142u2 in the same folder. I ran the -lx command on both. The resulting files were identical. Both had the same CRC value too.
|
|
|
|
Re: CLRmamePro Reports Wrong !! (Or is it mame which is wrong ?)
[Re: Hibo]
#291595 - 07/12/12 10:51 AM
|
|
|
> Likewise , it reports the rom "epr-13523.ic22" in in the romset "radm" Rad
> Mobile(World) as "missing but fixable" but it is there in the romset.Mame doesnt give
> any error loading the game.Just the name is different.ClrMame doesnt ask to rename
> it. What is wrong ?
what settings do you have in clrmame? split sets? merged sets? the answer could be there
|
|
|
|
Re: CLRmamePro Reports Wrong !! (Or is it mame which is wrong ?)
[Re: redk9258]
#291596 - 07/12/12 10:52 AM
|
|
|
> ROMs required for driver "radr".
> Name Size Checksum
> epr-14241.ic21 131072 CRC(59a5f63d) SHA1(325a26a09475ddc828de71e71a1d3043f3959cec)
> epr-14105.ic18 262144 CRC(614843b6) SHA1(d4f2cd3b024f7152d6e89237f0da06adea2efe57)
>
> ROMs required for driver "radru".
> Name Size Checksum
> epr-14240.ic21 131072 CRC(8473e7ab) SHA1(fbd883dc804d7de6ce239b68c6e6ae3a54e9e03c)
> epr-14105.ic16 262144 CRC(614843b6) SHA1(d4f2cd3b024f7152d6e89237f0da06adea2efe57)
>
> I use split sets and CLRMAMEPRO 4.06 put those two different ROMs in radru.7z
for the record, there is nothing wrong in MAME. the two games had the epr-14105 rom in different locations (IC18 in the former case, IC16 in the latter), so they get different names
simple as that
|
|
|
|
Re: CLRmamePro Reports Wrong !! (Or is it mame which is wrong ?)
[Re: Hibo]
#291601 - 07/12/12 11:33 AM
|
|
|
Welcome to the wonderful world of strict naming. Different names for identical files within a parent clone relation ship are common. Unless you use cmpro's profiler->parse rom merge tags, you need the files correctly named and even doubled in some cases.
So..nothing's wrong and btw...MAME loads files by hash compare and doesn't give a s**t about naming or where it finds the files...that's the difference of auditing and playing 
|
|
|
| R. Belmont |
|
Cuckoo for IGAvania
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 9716
|
|
Loc: ECV-197 The Orville
|
|
|
|
Send PM
|
|
|
Re: CLRmamePro Reports Wrong !! (Or is it mame which is wrong ?)
[Re: redk9258]
#291619 - 07/12/12 05:22 PM
|
|
|
Doesn't matter. MAMEUI in its current form is the AIDS. Stop trying to fight MAMEdev, you can't win.
|
|
|
|
Re: CLRmamePro Reports Wrong !! (Or is it mame which is wrong ?)
[Re: R. Belmont]
#291647 - 07/12/12 11:22 PM
|
|
|
> Doesn't matter. MAMEUI in its current form is the AIDS. Stop trying to fight MAMEdev,
> you can't win.
I have a soft spot for mameui as when I started compiling MAME I was running NT4, so while the official tools were DJGPP I was using Visual Studio.
|
|
|
| redk9258 |
|
Regular
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 3968
|
|
Loc: Troy, Illinois USA
|
|
|
|
Send PM
|
|
|
Re: CLRmamePro Reports Wrong !! (Or is it mame which is wrong ?)
[Re: R. Belmont]
#291649 - 07/12/12 11:34 PM
|
|
|
I'm not fighting MAMEDev. MAMEUI is not perfect, but it still works pretty good for most people. It's bullshit that someone says it's broken and doesn't work with CLRMAMEPRO the same as MAME. It does. The XML files matched byte for byte. That is all.
|
|
|
| R. Belmont |
|
Cuckoo for IGAvania
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 9716
|
|
Loc: ECV-197 The Orville
|
|
|
|
Send PM
|
|
|
Re: CLRmamePro Reports Wrong !! (Or is it mame which is wrong ?)
[Re: redk9258]
#291671 - 07/13/12 04:14 AM
|
|
|
> I'm not fighting MAMEDev. MAMEUI is not perfect, but it still works pretty good for
> most people. It's bullshit that someone says it's broken and doesn't work with
> CLRMAMEPRO the same as MAME. It does. The XML files matched byte for byte. That is
> all.
You don't understand. It's *not supported*. Doesn't matter if you can prove today's version works for that, past ones produced mismatches and future ones will again. It should not ever be used to audit ROMs or anything of that sort where you could lose valuable data.
|
|
|
Index 
Threaded 
CLRmamePro Reports Wrong !! (Or is it mame which is wrong ?)
Reply
[Re: 
