User Tools

Site Tools


supported_dats

DATs Supported by DATVault

DATVault is under continuous development and new DAT sources may be added at any time. DATVault currently supports the following DAT sources:

Name Description Source
Archive
Darkwater An early dumping group focused on Sega CD and Sega Saturn in single bin/cue format.
EmulatorArchived DATs for old emulators that are no longer updated. Also includes MADrigal's Handheld Remakes.
Logiqx Very old DATs for a variety of emulators. Site
NonGood Collections of ROMs not found in GoodTools suite.
NonMAME Old arcade dumps that were not supported by MAME at the time.
SMWHacks A huge collection of Super Mario World hacks.
DeDupe
DeDupe DATs that deduplicate large files across datting groups. See FAQ below for details.
Emulators
FBNEO DATs from the FBNeo nightly builds Github
HBMAME DATs exported directly from the HBMAME executable using -listxml Site
MAME DATs exported directly from the MAME executable using -listxml Site
MAMEHash Software List XML files from the current MAME release hash folder. Includes ROMs and CHDs. Site
MAME-SL-CHD-Daily Software List CHDs from the daily MAME binaries. Use instead of MAMEHash to stay up-to-date between MAME releases. Site
MAME-SL-Daily Software List ROMs from the daily MAME binaries. Use instead of MAMEHash to stay up-to-date between MAME releases. Site
RAINE DATs exported directly from the RAINE executable Site
No-Intro
NoIntro DATs that strive for the cleanest version of each game. No hacks or fan translations. Focuses primarily on cartridge based systems. Generally the best set to use for emulator frontends like Launchbox for most consoles. Site
NoIntroPC Parent/Clone DAT variations. Content is almost identical to the standard No-Intro DATs. Site
Others
[T-En]Collection English fan translations for several systems. Includes CD audio hacks, speed hacks, and color enhancements. Updated frequently.
DatsSiteCust Custom DATs for specialty compression formats not used by redump.org (WUX / NKit / nNASOS) Site
Dominater01 Various language translations and hacks for several systems. Updated periodically.
EMMA Arcade dumps that are not associated with a particular emulator Site
FruitMachine Slot machine ROMs
Grubys Gruby's Adventure Pack: a very through collection of point and click adventure games
HTGDB Hardware Target Game Database: A large collection curated specifically for use with flash carts and MiSTer FPGA setups Github
NRS A curated collection of NES ROMs that are supported by NewRisingSun's NES header database Forum
OpenGood DATs for GoodTool contents. Note these are DATs of actual files, not a reverse engineered database from the GoodTools executables. Github
Retrobytes Old PC games from the RetroBytes archival site. Successor to TGOD and very active. Site
TGOD Old PC games from the Good Old Days archival site. Currently fairly inactive. Site
Switch A mirror of a publicly available DAT for Nintendo Switch firmware from user 8BitWonder on the GBATemp forums.
VGM Archive DATs for video game music.
WHDLoad DATs for Commodore Amiga hard disks compatible with the WHDLoad application. Forum
Pinball
FuturePinball DATs for Future Pinball
VisualPinball DATs for various versions of Visual Pinball
Pleasuredome
PD-HBMAME DATs to accompany Pleasuredome HBMAME torrents Github
PD-MAME DATs to accompany Pleasuredome MAME torrents Github
Redump
ReDump DATs that strive for the cleanest version of each game using strict dumping methods. Focuses only on disc-based systems. Site
Scene
DatsSite Custom DATs for console scene releases Site
Snaps
MordorsExtras DATs for MAME artwork and extras. Not as well known as Progetto SNAPs, but an impressive collection.
Snaps DATs for MAME artwork. The PD MAME Extras DAT is based primarily on Progetto SNAPs. Site
TOSEC
TOSEC Main branch for the TOSEC project, which contains a massive amount of ROMs Site
TOSEC-ISO ISO branch, which focuses on disc dumps. Great for Sega Dreamcast, but incomplete for other systems. Site
TOSEC-PIX PIX branch, which contains scans of various magazines and artwork Site
TOSEC-Rollback Rollback DATs which contain ROMs that were removed over time Site

Why are many ROMs duplicated across DATs?

DATVault provides many collecting and storage options depending on your preferences. Because there are many options, there's also overlap in the ROMs present across DATs. For example:

  • MAME and HBMAME DATs are available in different variations for merged, split, and non-merged archive preferences
  • MAME and HBMAME DATs are available from both the official executables as well as provided as custom DATs that can be used to match Pleasuredome torrents
  • MAME Software Lists are available as separate DATs or as a single combined DAT
  • No-Intro DATs are available in standard format and parent/clone format
  • Many ROMs are simply datted by multiple groups. In this case, you can try using DatVault's dedupe DATs to save space.

What are the dedupe DATs?

Some datting projects cover the same systems, which means the same files may be duplicated across multiple DATs with different naming conventions. This is generally not a concern for older systems because the files are very small. However, for disc based systems the duplicated files can add up to a significant amount of space. Redump and TOSEC-ISO for example both DAT Philips CD-i discs, but you may only care about collecting one copy of each disc regardless of the datting group. In this case, DatVault provides you the option to use “Dedupe DATs” that filter out the overlap allowing you to collect a single copy of the disc without any fancy filesystem level deduping.

The dedupe DATs work by taking a primary DAT and comparing it to a set of secondary DATs. Any files that are present in the secondary DATs that are also included in the primary DAT are marked with a status of “deduped” in the secondary DATs. This status in RomVault basically means “Do not collect this file here because I only want it collected with my primary DAT”. These deduped files are shown with a gray ROM status.

DatVault provides multiple variations of dedupe DATs for you to use depending on your preferences. For example, if you prefer to have Redump primary and TOSEC-ISO secondary for a particular system, you would use the normal Redump DAT plus the dedupe TOSEC-ISO DAT with “Redump removed” for that system.

What are the rollback DATs?

Occasionally ROMs are removed because they are found to be bad, or are replaced with better dumps. This happens often between each MAME and TOSEC release. DATVault provides rollback DATs that include these removed ROMs for MAME and TOSEC specifically. The MAME rollback DATs are part of the PD group, and the TOSEC rollback DATs are custom made and available exclusively through DATVault.


What DATs should I use?

There are several options available for some of the most popular DATs. Most people would not want to use every DAT available. Its best to choose the DAT for a given set that best fits your needs and preferred way of storing your ROMs. The tables below outline the DATs that have multiple options and when you might want to choose a particular DAT variation over another:

Collection Option Description
MAME ROMs and CHDs
MAME ROMs ListXML Best if you want to store ROMs and CHDs in the same parent directory. You can choose how you want your ROM sets merged using directory settings. If you use this option you can collect both ROMs and CHDs with a single DAT.
Merged The sets are forced into merged archives. The Official and PD versions should be identical.
Non-Merged The sets are forced into non-merged archives. The Official and PD versions should be identical.
Split The sets are forced into split archives. The Official and PD versions should be identical.
BIOS Devices This is special DAT just for BIOS ROMs. These ROMs are included in ListXML, merged, non-merged, and split sets as well.
MAME CHDs ListXML Best if you want to store ROMs and CHDs in the same parent directory. You can choose how you want your ROM sets merged using directory settings. If you use this option you can collect both ROMs and CHDs with a single DAT. The DAT contains internal hashes for CHDs which means verification is done on the CHD contents, not the CHD file itself.
Merged The sets are forced into merged directories. The DAT contains internal hashes for CHDs. The Official and PD versions should be identical.
Merged dir2dat The sets are forced into merged directories. This is a custom DAT from Pleasuredome and contains the external hashes for the CHD files. This dir2dat option is particularly useful for Rollback CHDs where you want to ensure the correct CHD version for the rollback is collected.
MAME Software List ROMs Daily The separate “MAME-SL-Daily” DAT group contains software list information from daily MAME builds. These DATs are best used if you want to stay up-to-date between MAME releases. Contains info about ROMs only.
Hash Folder The separate “MAMEHash” DAT group contains a copy of all XML files in the hash folder of a MAME install. These DATs contain both ROMs and CHDs. This option is useful if you want precise control over where and how the ROMs and CHDs for each supported system are stored. This option is also useful if you would like to see exactly what supported systems are updated with each MAME release.
Merged The sets are forced into merged archives. All Software List XMLs are combined into a single DAT. Best if you like to keep MAME software lists in the exact default structure MAME expects. The Official and PD versions should be identical.
Split The sets are forced into split archives. All Software List XMLs are combined into a single DAT. Best if you like to keep MAME software lists in the exact default structure MAME expects. The Official and PD versions should be identical.
BIOS Devices This is special DAT just for BIOS ROMs. These ROMs are included in “MAMEHash” group, merged, and split sets as well.
MAME Software List CHDs Daily The separate “MAME-SL-CHD-Daily” DAT group contains software list information from daily MAME builds. These DATs are best used if you want to stay up-to-date between MAME releases. Contains info about CHDs only.
Hash Folder The separate “MAMEHash” DAT group contains a copy of all XML files in the hash folder of a MAME install. These DATs contain both ROMs and CHDs. This option is useful if you want precise control over where and how the ROMs and CHDs for each supported system are stored. This option is also useful if you would like to see exactly what supported systems are updated with each MAME release.
Merged The sets are forced into merged directories. All CHDs from Software List XMLs are combined into a single DAT. The DAT contains internal hashes for CHDs. The Official and PD versions should be identical.
Merged dir2dat The sets are forced into merged directories. All CHDs from Software List XMLs are combined into a single DAT. This is a custom DAT from Pleasuredome and contains the external hashes for the CHD files. This dir2dat option is particularly useful for Rollback CHDs where you want to ensure the correct CHD version for the rollback is collected.
MAME Artwork and Extras
MAME Artwork and Extras PD Extras Contains most content found in the Progetto SNAPs DATs plus a few non-artwork MAME extras such as samples.
PD Multimedia Supplemental content to go along with the MAME Extras. Most content is also in Progetto SNAPs.
Progetto SNAPs Source for most MAME extras and multimedia. If you collect the Extras and Multimedia DATs you may not find much value in this set, and vice versa.
HBMAME ROMs and CHDs
HBMAME ROMs ListXML Best if you want to store ROMs and CHDs in the same parent directory. You can choose how you want your ROM sets merged using directory settings. If you use this option you can collect both ROMs and CHDs with a single DAT.
Merged The sets are forced into merged archives. The Official and PD versions should be identical.
BIOS Devices This is special DAT just for BIOS ROMs. These ROMs are included in ListXML and merged sets as well.
HBMAME CHDs ListXML Best if you want to store ROMs and CHDs in the same parent directory. You can choose how you want your ROM sets merged using directory settings. If you use this option you can collect both ROMs and CHDs with a single DAT. The DAT contains internal hashes for CHDs which means verification is done on the CHD contents, not the CHD file itself.
Merged The sets are forced into merged directories. The DAT contains internal hashes for CHDs. The Official and PD versions should be identical.
Merged dir2dat The sets are forced into merged directories. This is a custom DAT from Pleasuredome and contains the external hashes for the CHD files. This dir2dat option is particularly useful for Rollback CHDs where you want to ensure the correct CHD version for the rollback is collected.
No-Intro
No-Intro (All) Standard Standard DATs used by most people. All ROMs are included as separate sets.
Parent/Clone The DATs include parent/clone information which is used mainly for merging ROMs across regions. For more information refer to No-Intro's instructions about parent/clone DATs.
No-Intro (7800/LNX/NES/FDS) Headers Skipped The standard No-Intro DATs for 7800, Lynx, Famicom Disk System, and NES contain header skippers. These DATs can be used if you do not have a preference for ROMs with headers vs no headers.
Headerless The DATs are customized and have the header skipper reference removed. These DATs can be used if you want to ensure you are only matching on headerless ROMs for these systems.
RetroBytes
RetroBytes Merged Official DAT available on the RetroBytes site. Many games have .raw files merged for disks, which is arguably incorrect.
Games Custom DAT maintained and supplied by a ROMVault user. Maintains the correct split .raw format of the original disks that can be downloaded from the site.
Removed Custom DAT maintained and supplied by a ROMVault user. Games that have been removed from the site.
Extras Custom DAT maintained and supplied by a ROMVault user. DAT for game manuals and other extras available on the site.
supported_dats.txt · Last modified: 2022/05/26 17:12 by johnsanc