Show Posts

41

clrmame Discussion / Re: Possible bug with WinX

« on: 11 August 2015, 17:52 »

OK, thank you very much.
I'll move clrmame to a different directory.

42

clrmame Discussion / Possible bug with WinX

« on: 11 August 2015, 14:02 »

Hi,
I just upgraded one of my PCs from Win7 to WinX and I get a small quirk:
Dragging files onto "rebuilt" window or onto "scan results" window does nothing. The rebuild process doesn't start.
Am I the only one experiencing this?
Thanks in advance for your help.

43

clrmame Discussion / Re: UME support request

« on: 03 February 2015, 09:52 »

Yes, I regularly use UME builds on my spare machine, and it works perfectly with clrmame.

44

clrmame Discussion / Re: DAT (depreciated) -> XML

« on: 17 January 2015, 14:49 »

Does it work also in the other way round?
Transforming a new XMLdatfile to al old format one?

45

clrmame Discussion / Re: Status

« on: 27 November 2014, 20:46 »

IMHO the funkyfiga problem should be addressed by MAMEDevs and not by cmpro.

46

clrmame Discussion / Re: Status

« on: 25 November 2014, 22:28 »

It looks GREAT!

47

clrmame Discussion / Re: Status

« on: 25 November 2014, 11:18 »

The idea of using variables in .ini is wonderfull.
Maybe it could be that you split the .ini in 2 files: gui.ini and engine.ini
In this way, people could share engine.ini and be sure to create the exact same set of roms, leaving them free to have different gui settings on their respective PCs.

48

clrmame Discussion / Re: command prompt / scripting with .bat

« on: 10 October 2014, 08:32 »

time to go public with the source?

just a suggestion...

49

clrmame Discussion / Re: command prompt / scripting with .bat

« on: 09 October 2014, 16:56 »

OK, thank you any way.

50

clrmame Discussion / Re: command prompt / scripting with .bat

« on: 09 October 2014, 13:12 »

Yes, thank you very much for your answer.

I'm using the batcher on a regular base, but it still requires the user to perform the task.

I was looking into a way to automate a number of repetitive tasks:
1-update the svn
2-compile last build
3-create a diffdatfile from latest official to newly compiled build
4-feed it to clrmame
5-rebuild from "unsorted" rom directory
6-scan&fix the "mame-upcaming" rom directory

I'm done with my .bat file up to item 4
I was looking for a way to complete it with 5 and 6

51

clrmame Discussion / command prompt / scripting with .bat

« on: 08 October 2014, 18:58 »

Hi Roman,
is it possible to use clrmame from the command prompt, calling "cmpro.exe" with a number of different parameters?

Thank you in advance for your help.

52

clrmame Discussion / Re: one more thing...

« on: 11 September 2014, 19:39 »

Quote from: Roman on 11 September 2014, 16:06

...and a general option to use that in any case (not only hash collisions)...

This I like very much!

53

clrmame Discussion / Re: auto rename same-name different-hash roms on merge

« on: 19 August 2014, 08:46 »

I do agree with Roman.
In case of merged sets, it would be logical to have the parent (which is somewhat considered "the perfect set" in MAME) into the root of the zipfile, and the various clones into their subdirectory inside the zip.
IMHO this should be valid for all sets, not only for sets with name collisions. It will have both the advantage of a single zipfile (as it is in merged sets now-a-day) and of a humanly readable structure to separate parent from clones (as it is in split sets now-a-day)
Just my 2 cents. Eurocents, off-course!

54

clrmame Discussion / Re: cmpro 4.09 released

« on: 12 January 2013, 23:19 »

Thank you for the long explanation Roman, very much appreciated.
So basically the general rule should be:
Split set -> ROM merge parsing UNCHECKED
Merge set -> ROM merge parsing CHECKED

Correct?

55