EMULAB Forum

clrmamepro [English] => clrmame Discussion => Topic started by: Dullaron on 29 December 2012, 04:19

Title: I have a question on this.
Post by: Dullaron on 29 December 2012, 04:19
Set: King Derby (bootleg set 2)
Name: kingdrbb2 ROM: sg1_b.e1
Issue: Possible wrong nodump definition found A valid checksum for it within its parent/clone relationship was found though.
Insert found checksum instead of using the 'nodump'?

What do I put? No?
Title: Re: I have a question on this.
Post by: Roman on 29 December 2012, 08:28
it does not harm if you select 'yes'.
Title: Re: I have a question on this.
Post by: Dullaron on 29 December 2012, 10:07
Oh OK. Making sure it doesn't do anything to the ROM. :)
Title: Re: I have a question on this.
Post by: Roman on 29 December 2012, 12:18
it only replaces the not existing checksum in the datfile with one from the parent/clones
Title: Re: I have a question on this.
Post by: Dullaron on 29 December 2012, 21:18
OK I found a real problem.

mess64 -listxml >mess64.xml

clrmamepro wasn't able to read it. Ton of 0 popping up saying it is not read able.

But get this. clrmamepro can read the mess64.exe just fine. No errors on this end.

/Edit.

No problem with the mame64.exe and mame64.xml loading.
Title: Re: I have a question on this.
Post by: Roman on 30 December 2012, 08:03
mess' xml is different from mame's elementwise. so of course you need other profiler parser settings than DATFILE when reading in the file.
Title: Re: I have a question on this.
Post by: Dullaron on 30 December 2012, 13:24
Using the one from the UME. I switch to this. It have MAME and MESS together. I didn't find any issues at all. =)
Title: Re: I have a question on this.
Post by: Roman on 30 December 2012, 16:16
there are no issues with the others either if you tell the profiler how to read them in correctly. but anyway a direct exe import is always the easier choice