User Tools

Site Tools


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 [2024/07/13 18:44] johnsancdirectory_settings [2024/07/13 18:55] (current) – [Don't Auto Add DAT Directories] johnsanc
Line 11: Line 11:
  
 ----- -----
-===== 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 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. 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\'' 
  
 ----- -----
 ===== Directory / Merge Rules ===== ===== Directory / Merge Rules =====
 \\ \\
-{{:settings:directory-rule-main.png?nolink&600 |}}+{{:settings:directory-rules.png?nolink&600 |}}
 \\ \\
 \\ \\
-==== Don'Auto Add DAT Directories ====+==== Don'auto add DAT directories ====
 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. 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 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>
  
  
directory_settings.1720921481.txt.gz · Last modified: 2024/07/13 18:44 by johnsanc