We have been able to consistently reproduce everytime cmpro 4.08b deletes or loses some roms/sets for unknown reason when scanning + fix a 147 complete romset with a self compiled 147u2 or 147u3 MAME binary.
FYI since we are working with merge sets here at the Datfile problem prompt we answer Yes To All about removing parent/clone relationship.
This happens when working with a complete 147 merged/zip set and also same result happens with merged/7-zip
strange thing is there is a different amount of roms that cmpro moves to backup path depending if your doing merged/zip or merged/7-zip
Here are some quotes from a friend testing along with me.
I was able to reproduce the problem.
While updating my 0.147 7z/merged set to 0.147u2, I ended up missing 20 ROMs.
These were not part of the 0.147 to 0.147u3 update torrent.
They were not part of my CMP backup folder either.
However, they were part of the 0.147 7z/merged set I started with (I made a backup of that)!
The ROMs must have been deleted from my set while scanning/fixing the 0.147 set with the 0.147u2 datfile.
That leaves us with the following questions:
It's a CMP problem, but is it 7-zip related?
Is it a problem CMP deleting ROMs while editing 7-zip files instead of moving them to the backup folder?
If it is, does CMP use an internal 7z routine to scan/fix or does it use the 7-zip version installed on the system and assigned in the CMP settings?
If it's external, which 7-zip version can be used to avoid this problem (9.22 used)?
Unlikely option: is it perhaps the t7zip file CMP (7z) has problems with?
To be continued...
Interesting.
This strikes a few questions.
The same happens with a merged/zip set.
CMP deleted ROMs when scanning/fixing the 0.147 set with the 0.147u2 datfile.
This time more ROMs ended up in the backup folder, 10 ROMs were deleted.
All 10 missing ROMs were part of the original 0.147 ROMs set I started with.
To be continued...
Will try to get more information as we figure things out. Hopefully Roman or Oxy can understand what is taking place here.