cache_structure
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
cache_structure [2022/11/08 19:36] – [Table] johnsanc | cache_structure [2022/11/19 17:41] – [Cache Structure] johnsanc | ||
---|---|---|---|
Line 2: | Line 2: | ||
RomVault stores all information about scanned and datted files in the RomVault Cache. This cache file is essentially a highly optimized database that includes filenames, sizes, hashes, modified timestamps, and pertinent flags to track various ROM statuses. | RomVault stores all information about scanned and datted files in the RomVault Cache. This cache file is essentially a highly optimized database that includes filenames, sizes, hashes, modified timestamps, and pertinent flags to track various ROM statuses. | ||
- | |**ⓘ NOTE:** \\ This page is under construction and should not be considered comprehensive | + | |**ⓘ NOTE:** \\ This page is for low level debugging reference only. You should never need to look at the cache contents in a hex editor, but if you do the tables below help to explain the cache structure. |
===== RomVault 3.5.x Cache ===== | ===== RomVault 3.5.x Cache ===== |
cache_structure.txt · Last modified: 2022/11/24 14:30 by johnsanc