directory_settings
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
directory_settings [2024/07/13 18:37] – johnsanc | directory_settings [2024/07/13 18:55] (current) – [Don't Auto Add DAT Directories] johnsanc | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== DAT Rules ====== | ====== DAT Rules ====== | ||
- | 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. | + | DAT rules allow you to configure |
- | + | ||
- | <WRAP alert> | + | |
- | + | ||
- | <WRAP important> | + | |
The directory settings can be accessed in two ways: | The directory settings can be accessed in two ways: | ||
- | * From the top menu: **Settings > Directory | + | * From the top menu: **Settings > Directory |
- | {{: | + | {{: |
\\ | \\ | ||
- | * 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. |
{{: | {{: | ||
\\ | \\ | ||
----- | ----- | ||
- | ===== Rule Path and Directory Location | + | ===== Rule Path ===== |
\\ | \\ | ||
- | {{: | ||
- | \\ | ||
- | \\ | ||
- | ==== Rule Path ==== | ||
This field is for reference and is not editable. The root of your entire setup is always called " | This field is for reference and is not editable. The root of your entire setup is always called " | ||
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 '' | 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 '' | ||
- | |||
- | |||
- | ==== 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: | ||
- | * '' | ||
- | * '' | ||
- | * '' | ||
- | * '' | ||
----- | ----- | ||
===== Directory / Merge Rules ===== | ===== Directory / Merge Rules ===== | ||
\\ | \\ | ||
- | {{: | + | {{: |
\\ | \\ | ||
\\ | \\ | ||
- | ==== Don' | + | ==== Don' |
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 " | 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 " | ||
- | <WRAP info> | + | <WRAP info> |
directory_settings.1720921024.txt.gz · Last modified: 2024/07/13 18:37 by johnsanc