Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Tafoid

Pages: [1]

clrmame Discussion / Re: clrmamepro 4.03a released

« on: 21 February 2012, 16:22 »

Quote from: Roman on 20 February 2012, 20:41

clrmamepro 4.03a

fixed: 7z crash for archives which don't use date/time stamps (t7z)
fixed: incorrect removal of sampleof assignements starting with .145u1

Regarding this, are they (parent sets which have samples named after them) supposed to still come up with a warning, even though they scan after an "OK to ALL" click? All games that use samples now have this "sampleof=" tags, even the parent samples. I think this is a permanent change in behavior.

clrmame Discussion / Re: clrmamepro 4.03a issue

« on: 21 February 2012, 16:18 »

Quote from: Roman on 21 February 2012, 14:58

Please answer my question regarding the allow-chds-on-rompath-root option.

It's also possible he's using the old command-line syntax for updating CHD's (v4 vs. v5), in which case it would likely appear that nothing is happening since clrmame didn't get the validation text from CHDMAN to continue? Just a guess...

clrmame Discussion / Re: datfile problem - double rom?

« on: 30 December 2009, 17:52 »

Quote from: gwent on 29 December 2009, 18:01

I'm using the latest version of clrmamepro, and used it to scan the 135u4 version of MAMEUI32. It then popped up a box with the following info:

Set:   Trivia ? Whiz (Edition 3 - Horizontal) (set 1)
Name:   trvwz3h
ROM:   gen-002_02

Issue:   Double ROM with different hashvalues found

Keep ROM but rename it?
Otherwise it'll be removed from the set definition.

So what is the appropriate thing to do here? Should I click yes to rename it or no to remove from the set definition? Does anybody know why this would happen?

This is already corrected in MAME's SVN (for release in 0.136). Accepting YES will not hurt your collection - CLRMAMEPRO will only rename those particular files to something different so they can co-exist in the same ZIP file. MAME itself does not care what a filename inside a ZIP is, only that they match the expected crc/hash values. When you run 0.136 against the changed sets - CMP will simply rename them to MAME defaults, which are now not-conflicting.