Differences

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

--- error_messages [2022/02/03 01:13] – johnsanc
+++ error_messages [2023/07/04 15:31] (current) – johnsanc
@@ Line 2: / Line 2: @@
 ====== Error Messages ======
-|**ⓘ NOTE:** \\ This page is under construction and should not be considered comprehensive. This page aims to document all "friendly" errors you may encounter along with guidance how to resolve those errors. All Stack Trace errors should be considered bugs and reported on the [[https://discord.gg/fVJQPA8|RomVault Discord]].|
+<WRAP info>This page is under construction and should not be considered comprehensive. This page aims to document all "friendly" errors you may encounter along with guidance how to resolve those errors. All Stack Trace errors should be considered bugs and reported on the [[https://discord.gg/fVJQPA8|RomVault Discord]].</WRAP>
 \\
@@ Line 137: / Line 137: @@
 ==== Double Name Found ====
-  * Two or more DATs in a directory share the same value in their header "name" tag
+  * There are sets that share the same name with different character case
-  * Remediation: Move each of the conflicting DATs into their own subdirectory or modify the name tags in the DATs so they are unique. You can also try adjusting your Directory Rules to use the DAT Description value instead of Name.
+  * Remediation: Double check your filesystem case sensitivity settings and if you have multiple files/directories that have the same name but different character case. Remove any duplicates and try again.
 ==== Error is Set Missing Status in DatUpdate ====
@@ Line 226: / Line 226: @@
 ==== Rescan needed, File Changed : [X] ====
-  * The file RomVault was attempting to use for a fix was found, but the timestamp did not match what is record in the cache. Your cache is out of sync with your filesystem.
+  * The file RomVault was attempting to use for a fix was found, but the timestamp did not match what is recorded in the cache. Your cache is out of sync with your filesystem.
   * Remediation: Rescan your files to ensure your cache is up-to-date. If you continue to run into issues, check your timestamp configuration settings for any remote shares. Its possible that the timestamp granularity conflicts could cause RomVault to flag a file as modified when it was not.