Differences

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

--- bugs_known_issues [2021/09/06 10:02] – gordonj
+++ bugs_known_issues [2021/10/25 17:12] – johnsanc
@@ Line 1: / Line 1: @@
 ====== Known Issues ======
-  * (1) If you run out of disk space during a fix that uses the 7z cache, RomVault with throw a friendly error. Upon dismissing this message a hard crash will occur with an error and the cache will become corrupted. RomVault will not start again until the corrupt cache file is removed. (Kind of fixed in next release, running out of disk space is always a bad thing, but RV should no longer hard crash or corrupt the cache, but the cache will be out of date, as there is no space left to write out the latest cache, and a rescan will be required, once space has been made on the drive.)
+  * (1) If a file is in use by another process during a fix operation on that file, RomVault will crash and throw an error. At this point the cache will be out of sync with the files on disk and a rescan will be needed.
-  * (2) If a file is in use by another process during a fix operation on that file, RomVault will crash and throw an error. At this point the cache will be out of sync with the files on disk and a rescan will be needed.
+  * (2) A fix operation on a 7z file can leave orphaned files in the 7z cache directory. This can be reproduced by starting with a 7z file that has some files that match an existing complete set in a DAT and other files that do not match. Upon fixing, the matched files are removed from the archive and the archive is recompressed, however the unmatched files are also left in the 7z cache.
-  * (3) A fix operation on a 7z file can leave orphaned files in the 7z cache directory. It appears these orphaned files are then completely ignored  by RomVault, even if they match a file in a DAT.
+  * (3) Single Archive settings do not work properly unless the DATs are each in their own folder.
-  * (4) Single Archive settings do not work properly unless the DATs are each in their own folder.
-  * (5) If the Single Archive + No SubDirs settings are used when a DAT is NOT in its own subfolder in the DATRoot, then subdirectories are still created. If the DAT is in its own subfolder, then the settings work as expected. This issue has been reported by people who are also using "File" as the Archive Type.
+  * (4) If the Single Archive + No SubDirs settings are used when a DAT is NOT in its own subfolder in the DATRoot, then subdirectories are still created. If the DAT is in its own subfolder, then the settings work as expected. This issue has been reported by people who are also using "File" as the Archive Type.
-  * (6) If you generate fixDats on directories that are using the Single Archive setting with "Add SubDirs if multiple roms" then RomVault will crash with an error. The text reports will not cause a crash, but the reports will not include any information from the directories using Single Archive. This may also occur under other directory setting scenarios but this is unconfirmed.
-  * (7) DATs with zero entries are automatically selected in the tree after a DAT Update, even if the DATs did not change.
-  * (8) The side icons are not visible when RomVault is used on Linux. This is likely a PNG transparency issue.
-  * (9) Corrupt archive icons are only displayed at levels above the directory where the corrupt archive resides. E.g. an archive sitting in the base directory of your ToSort will not appear as corrupt when clicking on ToSort in the tree.
-  * (10) Files can be deleted in certain scenarios with unrecommended directory settings. For example, if you map a directory in your RomRoot to a ToSort directory then a fix operation will delete files that RomVault thinks are not needed because they reside elsewhere. In this case the directory deleted from and the location of the undeeded roms are the same. An extra check is needed to prevent unwanted deletions. (Extra checks have been added to the next release to make this less likely to delete files in this incorrect user case.)
-  * (11) Files without read permissions are completely skipped by RomVault with no indicators. Ideally these files should be flagged with a blue status.
+  * (5) If you generate fixDats on directories that are using the Single Archive setting with "Add SubDirs if multiple roms" then RomVault will crash with an error. The text reports will not cause a crash, but the reports will not include any information from the directories using Single Archive. This may also occur under other directory setting scenarios but this is unconfirmed.
-  * (12) RomVault throws a "Rescan needed" error during a fix operation if the fix is to correct the character case of the ROM. If you close this error and attempt the fix again, RomVault proceeds past this error. A rescan is not required.
+  * (6) DATs with zero entries are automatically selected and expanded in the tree after a DAT Update, even if the DATs did not change.
-  * (13) Missing counts in the tree and summary panes include ROMs that are in blue locked status. For example, an unneeded locked file will count as missing even if you have all other ROMs marked as "Have."
+  * (7) The side icons are not visible when RomVault is used on Linux. This is likely a PNG transparency issue.
-  * (14) If RomVault does not have proper access to a directory, scanning an uncompressed file in that directory will throw a "ZipErrorOpeningFile" error. This is unrelated to opening a zip file.
+  * (8) Corrupt archive icons are only displayed at levels above the directory where the corrupt archive resides. E.g. an archive sitting in the base directory of your ToSort will not appear as corrupt when clicking on ToSort in the tree.
-  * (15) The Dat Info pane can display information that does not reflect what is selected in the tree. This can be reproduced by navigating with right and left clicks in the right pane. (Fixed, in next release.
+  * (9) Files without read permissions are completely skipped by RomVault with no indicators. Ideally these files should be flagged with a blue status.
+  * (10) RomVault throws a "Rescan needed" error during a fix operation if the fix is to correct the character case of the ROM. If you close this error and attempt the fix again, RomVault proceeds past this error. A rescan is not required.
-,10,15  This are fixed (Improved) ready for next release.
+  * (11) Missing counts in the tree and summary panes include ROMs that are in blue locked status. For example, an unneeded locked file will count as missing even if you have all other ROMs marked as "Have."
-Would like to know if this is still a problem?
+  * (12) If RomVault does not have proper access to a directory, scanning an uncompressed file in that directory will throw a "ZipErrorOpeningFile" error. This is unrelated to opening a zip file.
-,5  Don't know if this is really broken? (or just not a well understood feature.)
-,7   Yep, Bugs that need fixed
+,4  Don't know if this is really broken? (or just not a well understood feature.)
+,6  Yep, Bugs that need fixed