User Tools

Site Tools

Trace:
directory_settings

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
directory_settings [2023/06/17 16:10] – johnsancdirectory_settings [2024/04/10 18:27] (current) – 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 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.
  
-<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 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>+<WRAP 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: The directory settings can be accessed in two ways:
Line 34: Line 34:
   * ''%%\\%%Server\Share\''   * ''%%\\%%Server\Share\''
   * ''\\?\UNC\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> 
  
 ----- -----
Line 44: Line 42:
 \\ \\
 ==== 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.</WRAP>
  
  
Line 83: Line 81:
   * **Headerless** - Only ROMs without headers will be included.   * **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 ==== ==== Single Archive ====
Line 98: Line 96:
  
 ==== Use description (instead of name) for auto added paths ==== ==== 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   * The value of the ''<name>'' tag in the DAT header
   * If no ''<name>'' tag is present, then the DAT filename will be used   * If no ''<name>'' tag is present, then the DAT filename will be used
Line 132: Line 130:
 |Exact|''_readme_.txt''|Ignores the file named exactly ''_readme_.txt''| |Exact|''_readme_.txt''|Ignores the file named exactly ''_readme_.txt''|
 |Wildcard|''*.sbi''|Ignores all .sbi files which are sometimes packaged with PS1 dumps| |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:''</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>
  
 ----- -----
 \\ \\
-====== Cascading Directory Rules ======+===== Cascading Directory Rules =====
 Settings for a directory will cascade to all of that directory's descendants until overwritten by a higher priority rule. Rules for descendant directories are always a higher priority than the rules for ancestor directories. Settings for a directory will cascade to all of that directory's descendants until overwritten by a higher priority rule. Rules for descendant directories are always a higher priority than the rules for ancestor directories.
  
directory_settings.1687043442.txt.gz · Last modified: 2023/06/17 16:10 by johnsanc