Differences

This shows you the differences between two versions of the page.

--- directory_dir2dat_guide [2021/12/31 18:52] – hiccup
+++ directory_dir2dat_guide [2023/11/17 12:33] (current) – hiccup
@@ Line 1: / Line 1: @@
 ====== Directory Dir2Dat Guide ======
+todo: document how to use RomVault for this, as that is a much better option
+**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.**
 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.
@@ Line 20: / Line 24: @@
 {{:general:directory_dir2_dat_folder_structure.png?400|}}
- You can test this setup is working correctly by hashing the contents of {{ :test_dir_structure.zip |this zip}} and comparing the datfile that clrmamepro creates with {{ :test_dir_structure.dat.zip |this pre-made datfile}} . Currently there is no solid solution for "directory hashing" that supports SHA256, so you can leave that hash type out.
+You can test this setup is working correctly by hashing the contents of {{ :test_dir_structure.zip |this zip}} and comparing the datfile that clrmamepro creates with {{ :test_dir_structure.dat.zip |this pre-made datfile}} . Currently there is no solid solution for "directory hashing" that supports SHA256, so you can leave that hash type out.
+There will also be a top-level entry called "Default" with a single empty folder, which should be ignored/deleted.