ps2exe currently assumes that every disc image has 2048 bytes of user data all the time. This isn't the case and there are times when there can be more than 2048 bytes of user data, specifically mode 2 form 2 sectors. As a result, ps2exe is truncating these sectors to 2048 bytes and using them as the basis for computing sums. We need ps2exe to know user data sizes depending on reported information in the sync.
This change will affect all old data sets used in versions before this commit. All sets generated after this change will not be guaranteed to be comparable.
Should we change ps2exe's version number to reflect when this change occurs? It's a substantial change that will affect previous data sets. This way we can denote old sets with a "version 0.0.1" and an old set using the version number that generated the data.
ps2exe currently assumes that every disc image has 2048 bytes of user data all the time. This isn't the case and there are times when there can be more than 2048 bytes of user data, specifically mode 2 form 2 sectors. As a result, ps2exe is truncating these sectors to 2048 bytes and using them as the basis for computing sums. We need ps2exe to know user data sizes depending on reported information in the sync.
This change will affect all old data sets used in versions before this commit. All sets generated after this change will not be guaranteed to be comparable.
Should we change ps2exe's version number to reflect when this change occurs? It's a substantial change that will affect previous data sets. This way we can denote old sets with a "version 0.0.1" and an old set using the version number that generated the data.