[x] WIP release (MPF.Check (.NET 6.0, Debug, Windows x64))
Build
What runtime version are you using?
[x] .NET Framework 4.8 running on (Windows 10)
[x] .NET 6.0 running on (Windows 10)
[ ] .NET 7.0 running on (Operating System)
Describe the issue
When using MPF.Check on a UMD dumped with UIC, in the generated submission info text file, the CRC32 hash does not appear to be correct. It does not match other tools, or existing dumps' CRC32, however the MD5 and SHA1 hashes do match.
To Reproduce
Run MPF.Check against an .iso (tested with files and parameters for UIC-dumped PSP UMD)
Check the CRC32 checksum in the generated submission info text file
Calculate the CRC32 checksum of the file with another tool, and it is different
Expected behavior
The CRC32 checksum matches the result of other tools.
Screenshots
In order: submission info generated from an older version of MPF.Check, the current release version, and the WIP debug release.
Additional context
I tested with this two UIC dumps of different discs, with both the current release and latest WIP build, and it had the same issue occur.
I have a submission info text file on the first dump that was generated using an older version of MPF.Check (sorry, I am not sure which one, but I think it was from around June/July), and this one had the expected CRC32 hash that matches other tools.
Version What version are you using?
Build What runtime version are you using?
Describe the issue When using MPF.Check on a UMD dumped with UIC, in the generated submission info text file, the CRC32 hash does not appear to be correct. It does not match other tools, or existing dumps' CRC32, however the MD5 and SHA1 hashes do match.
To Reproduce
Expected behavior The CRC32 checksum matches the result of other tools.
Screenshots
In order: submission info generated from an older version of MPF.Check, the current release version, and the WIP debug release.
Additional context I tested with this two UIC dumps of different discs, with both the current release and latest WIP build, and it had the same issue occur.
I have a submission info text file on the first dump that was generated using an older version of MPF.Check (sorry, I am not sure which one, but I think it was from around June/July), and this one had the expected CRC32 hash that matches other tools.