bugs_known_issues
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
bugs_known_issues [2021/09/05 18:34] – gordonj | bugs_known_issues [2021/10/25 17:14] – johnsanc | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Known Issues ====== | ====== Known Issues ====== | ||
- | * If you run out of disk space during a fix that uses the 7z cache, RomVault | + | * (1) If a file is in use by another process |
- | * If a file is in use by another process during | + | * (2) A fix operation on a 7z file can leave orphaned files in the 7z cache directory. This can be reproduced |
- | * 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 | + | * (3) Single Archive settings do not work properly unless the DATs are each in their own folder. |
- | + | ||
- | * Single Archive settings do not work properly unless the DATs are each in their own folder. | + | |
- | * 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 " | + | * (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 " |
+ | |||
+ | * (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. | ||
+ | |||
+ | * (6) DATs with zero entries are automatically selected and expanded in the tree after a DAT Update, even if the DATs did not change. | ||
- | * If you generate fixDats on directories that are using the Single Archive setting with "Add SubDirs if multiple roms" then RomVault | + | * (7) The side icons are not visible when RomVault |
- | * DATs with zero entries | + | * (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. |
- | * The side icons are not visible when RomVault | + | * (9) Files without read permissions |
- | * 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) RomVault throws a " |
- | * Files can be deleted | + | * (11) Missing counts |
- | * Files without read permissions are completely skipped by RomVault | + | * (12) If RomVault |
- | * RomVault | + | * (13) RomVault |
- | * 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 " | ||
- | * If RomVault does not have proper access to a directory, scanning an uncompressed file in that directory will throw a " | + | 3,4 Don't know if this is really broken? (or just not a well understood feature.) |
- | * 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.) | + | 5,6 Yep, Bugs that need fixed |
bugs_known_issues.txt · Last modified: 2024/05/04 08:58 by johnsanc