Differences

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

--- directory_settings [2023/06/17 16:11] – johnsanc
+++ directory_settings [2024/07/13 18:55] (current) – [Don't Auto Add DAT Directories] johnsanc
@@ Line 1: / Line 1: @@
-====== Directory Rules ======
+====== DAT Rules ======
-Directory rules allow you to define locations for your ROMs and settings for how you want those ROMs stored. These settings offer a lot of flexibility and control over your collection. To get the most value out of RomVault its best to spend time understanding exactly what options are available and how they work.
+DAT rules allow you to configure how you want your ROMs stored. These settings offer a lot of flexibility and control over your collection. To get the most value out of RomVault its best to spend time understanding exactly what options are available and how they work.
-<WRAP round alert>The RomVault UI will allow you map multiple DATs to a single directory. Do NOT map multiple DATs to the same ROM directory. Doing so may result in unintentional file deletions during a fix operation if the "[[global_settings#double_check_delete|Double Check Delete]]" global setting is disabled.</WRAP>
-<WRAP round important>Directory rules can only be applied to standard directories, not auto-created virtual directories in the DatRoot. If you place multiple DATs into a single directory, you cannot apply a rule to an individual DAT within that directory. If you need to apply a directory rule to a specific DAT, then the DAT should reside in its own directory in the DatRoot.</WRAP>
 The directory settings can be accessed in two ways:
-  * From the top menu: **Settings > Directory Settings**. \\ This view displays all of your directory rules in a single place.
+  * From the top menu: **Settings > Directory Dat Rules**. \\ This view displays all of your directory rules in a single place.
-{{:settings:directory-settings.png?nolink&600|}}
+{{:settings:dat-rules.png?nolink&600|}}
 \\
-  * Right-clicking a directory in the tree and selecting **Set Dir Settings**. \\ This view displays only the directory rule for the directory selected.
+  * Right-clicking a directory in the tree and selecting **Set Dir Dat Settings**. \\ This view displays only the directory rule for the directory selected.
-{{:settings:directory-rule.png?nolink&600 |}}
+{{:settings:dat-rule.png?nolink&600 |}}
 \\
 -----
-===== Rule Path and Directory Location =====
+===== Rule Path =====
 \\
-{{:settings:directory-paths.png?nolink&600 |}}
-\\
-\\
-==== Rule Path ====
 This field is for reference and is not editable. The root of your entire setup is always called "RomVault". "RomVault" is mapped to where ever you keep all of your ROMs.
 This may not seem intuitive at first, but this mapping ensures that the path references to your ROMs are stored in a relative fashion in the cache. For example, lets say you start by storing all your ROMs at ''C:\ROMs\''. At some point in the future you may run out of space on ''C:\'' and you need to move your ROMs to a NAS accessed with a mapped network drive of ''Y:\''. You can make this change to the RomRoot location without needing to rescan all of your ROMs.
-==== Dir Location ====
-The Dir Location is the path to your ROMs. The folder icon allows you to choose the location by browsing.
-The ROM locations can be modified directly in the RomVault config XML. This should not be required unless you want to use the long path syntax or reference a remote server. Examples:
-  * ''Y:\ROMs\''
-  * ''\\?\Y:\ROMs\''
-  * ''%%\\%%Server\Share\''
-  * ''\\?\UNC\Server\Share\''
-<WRAP round important>It's recommended to use regular UNC paths or drive letters to ensure support with chdman.exe for CHD verification. chdman.exe does not support long path syntax.</WRAP>
 -----
 ===== Directory / Merge Rules =====
 \\
-{{:settings:directory-rule-main.png?nolink&600 |}}
+{{:settings:directory-rules.png?nolink&600 |}}
 \\
 \\
-==== Don't Auto Add DAT Directories ====
+==== Don't auto add DAT directories ====
-If two or more DATs share a directory then RomVault will automatically create a subdirectory for each DAT so that they do not conflict with each other. If the "Don't Auto Add DAT Directories" option is __enabled__ then these directories will not be automatically created and the contents of the DATs will be effectively merged together. The result is that all of your ROMs from these DATs will be placed in the same directory.
+If two or more DATs share a directory in the DATRoot then RomVault will automatically create a virtual subdirectory for each DAT so they don't conflict with each other. If the "Don't Auto Add DAT Directories" option is __enabled__ then these directories will not be automatically created and the contents of the DATs will be effectively merged together. The result is that all of your ROMs from these DATs will be placed in the same directory.
-<WRAP round info>Because this option causes DATs to be merged its likely you may encounter a DAT merge conflict if used haphazardly. This option is only useful under very specific circumstances.</WRAP>
+<WRAP info>Because this option causes DATs to be merged its likely you may encounter a DAT merge conflict if used haphazardly. This option is only useful under very specific circumstances, such as merging No-Intro regular and private DATs, or MAME extras.</WRAP>
@@ Line 83: / Line 63: @@
   * **Headerless** - Only ROMs without headers will be included.
-<WRAP round info>The "Headered" setting applies to all files in the DAT, even files where a header would not apply such as BIOS files. This means you may have missing ROMs if the DAT includes both types of files. This is normal and currently by design.</WRAP>
+<WRAP info>The "Headered" setting applies to all files in the DAT, even files where a header would not apply such as BIOS files. This means you may have missing ROMs if the DAT includes both types of files. This is normal and currently by design.</WRAP>
 ==== Single Archive ====
@@ Line 98: / Line 78: @@
 ==== Use description (instead of name) for auto added paths ====
-If two or more DATs share a directory then RomVault will automatically create a subdirectory for each DAT so that they do not conflict with each other. If the "Use description (instead of name) for auto added paths" option is __disabled__ then these subdirectories will be named as follows:
+If two or more DATs share a directory in the DATRoot then RomVault will automatically create a virtual subdirectory for each DAT so they don't conflict with each other. If the "Use description (instead of name) for auto added paths" option is __disabled__ then these subdirectories will be named as follows:
   * The value of the ''<name>'' tag in the DAT header
   * If no ''<name>'' tag is present, then the DAT filename will be used
@@ Line 132: / Line 112: @@
 |Exact|''_readme_.txt''|Ignores the file named exactly ''_readme_.txt''|
 |Wildcard|''*.sbi''|Ignores all .sbi files which are sometimes packaged with PS1 dumps|
-|Regex|''regex:(/.stignore|/.stfolder)''|Ignores .stfolder and .stignore files which may be present if you sync a directory with syncthing to another location|
+|Regex|''regex:(\.stignore|\.stfolder)''|Ignores .stfolder and .stignore files which may be present if you sync a directory with syncthing to another location|
-<WRAP round info>Each ignore rule must be on its own line. Wildcard rules support ''?'' to match a single character and ''*'' to match any number of characters. Regex rules must be prefixed with ''regex:''</WRAP>
+<WRAP info>Each ignore rule must be on its own line. Wildcard rules support ''?'' to match a single character and ''*'' to match any number of characters. Regex rules must be prefixed with ''regex:''. The ''ignore:'' prefix is not supported with DAT rules. Global scanning engine ignore rules must be defined in [[global_settings#filenames_not_to_remove|Global Settings]].</WRAP>
-<WRAP round tip>For assistance with regex, try [[https://regex101.com/|regex101.com]]</WRAP>
+<WRAP tip>For assistance with regex, try [[https://regex101.com/|regex101.com]]</WRAP>
 -----