| Both sides previous revision Previous revision | |
| directory_dir2dat_guide [2025/02/05 20:29] – hiccup | directory_dir2dat_guide [2025/02/05 20:31] (current) – hiccup |
|---|
| todo: document how to use RomVault for this, as that is a much better option - it represents directories using special <dir> tags. It lets you create dats by scanning the contents of the ROMRoot, and then right clicking the ROM root and choosing "Save full dat". You can also do the same using ToSort, but to do that you need to have a blank .dat in the DATRoot. | todo: document how to use RomVault for this, as that is a much better option - it represents directories using special <dir> tags. It lets you create dats by scanning the contents of the ROMRoot, and then right clicking the ROM root and choosing "Save full dat". You can also do the same using ToSort, but to do that you need to have a blank .dat in the DATRoot. |
| |
| **Warning: there currently is no supported dir2dat tool that properly distinguishes between empty files and folders. As a workaround, you should use store the output of | |
| `dir /s` (if you are using Windows) or `ls -R` (if you are using Linux) alongside the datfile.** | ---- |
| | **Old guide** |
| | |
| | //This method should no longer be used, as it does not properly distinguish between empty files and folders.// |
| |
| If the "ROM" consists of of multiple directories, you will want to use the "dir2dat" function of [[https://mamedev.emulab.it/clrmamepro/|clrmamepro]] with the following settings in the "Options" section. | If the "ROM" consists of of multiple directories, you will want to use the "dir2dat" function of [[https://mamedev.emulab.it/clrmamepro/|clrmamepro]] with the following settings in the "Options" section. |