Database files are used to ensure a rom collection is named accurately and only contains rom for the applicable system. In some instances, those database files will also contain information about each of the roms in that collection e.g. Release Date, Publisher, Developer, etc. The database file will use one or more file hash value (CRC32, MD5, SHA-1, etc) to determine if the rom needs to be renamed, deleted, or merged with another rom in a compressed archive. Also, EO is only able to handle database operations for one console at a time.
The supported database formats are outlined below:
Name |
Import |
Export |
Separate |
No-Intro (*.dat) |
YES |
YES |
NO |
NesCartDB (*.xml) |
YES |
NO |
NO |
Clrmamepro (*.dat) |
YES |
NO |
NO |
Csv system ini (*.ini) |
YES |
YES |
YES |
SMS (*.txt) |
YES |
YES |
YES |
WHDLoad (*.map) |
YES |
YES |
NO |
Cateveren (*.ini) |
YES |
NO |
NO |
Mame dat (*.dat) |
YES |
NO |
NO |
Hyperlist (*.dat) |
YES |
NO |
NO |
Hyperlist (*.xml) |
YES |
NO |
NO |
See also:
How
to use a database file to rename roms, delete unknown roms, and fill in related
details about each game such as the year or developer
How to
create a database file based on the contents a console