Corrupt CHDs marked as good after L1 then L2 scan

RV 3.6.2

Scanning
j

johnsanc

last year

If a corrupt CHD is first scanned with a header-only scan it is recorded as good in the cache. If a regular scan is conducted afterwards, the scanning window will identify the CHD as corrupt, however the status will remain as good instead of corrupt.

Steps to reproduce:

  1. Purposely create a corrupt CHD by modifying a few bytes somewhere in the middle of it with a hex editor

  2. Scan the CHD with a header-only scan and notice it is not detected as corrupt (expected)

  3. Rescan the CHD with a regular scan, and during the verification process the scanning window will show the CHD is corrupt (expected)

  4. After the scanning is complete, the corrupt CHD is not flagged with the appropriate corrupt status in the game list / rom details grids.