If you want to use clrmamepro with other systems you can write a DatFile for that system, or - if a system has an option to create a filelist- modify the engine.cfg. DatFiles for a lot of systems like emulators can be already found on my homepage.
It's easy to write a datfile for a different systems. Just take a look at so called -listinfo syntax. clrmamepro parses the following tags:
set, name, cloneof, description, rom (name, size, baddump, nodump, crc, crc32, md5, sha1), sample, sampleof, year and manufacturer
The order and the case doesn't matter ! The space between a tagname and its attribute or
a '(' or ')' is important. The description name has to be in quotation marks. If you're using
quotation marks within a name, use '\"'.
description "PuckMan (Japan set 1)"
rom ( name namcopac.6e size 4096 crc fee263b3 md5 3f84d78d59147b9b3c816da72110e55f)
clrmamepro is able to read ROMCenter DatFiles, too. Use them on your very own risk. ROMCenter is (C) by Eric Bole-Feysot.
clrmamepro uses some datfile flags. These are:
rebuilds the files of this set to: rebuilderdestinationpath + "namco/english"
Some profiler specific settings
Normally you shouldn't modify engine.cfg !!! If you want to add a new emulator
or new biosroms, you should contact me. But anyway...here is a short description of the
Each engine starts with this keyword. Be sure to keep spaces between the keyword and the brackets.
Name of the current engine. This name will be displayed in the settings window.
Filename of the cache-file in the <clrmamepro>\cache folder.
For XML datfiles only. This specifies the gamelist tag.
Parameter for the binary to produce a datfile. If no command keyword is given, the engine will be a datfile engine. The enginename isn't a binary and will be handled as a pure datfilename.
Mean that keyword x is ignored while parsing the datfile. E.g. you can forbid the usage of samples by: 'ignore sampleof' and 'ignore samples'. For a list of possible values of x look at 'replace x y'.
Means that special keywords x in the datfile will be replaced by new keywords y. For
example: replace crc32 crc will replace crc32 tags with crc. Of course you can only replace
keywords. Available keywords for y are: