A method which needs exceptions correction to give proper results is not what we want. Our method don't comprehend exceptions. It works with all discs and handle them all the same way with proper results. I don't want to dump a disc first and THEN have to check if it falls in the exceptions category or not. I'll dump with IsoBuster+EAC directly and all will be fine.
Well, it hasn't been proven yet that CDRWIN definitely cuts of data from the last audio track. That could easily be checked by one of you guys, taking one of the example Sega CDs (e.g. Winning Post) where you say that they contain audio data until the very last byte.
If you do that, and compare the raw audio data from the Isobuster+EAC dump and the CDRWIN dump using the method I outlined in my Inn post, and then get a difference, then it is proven that CDRWIN behaves faulty and cuts of data. If it is still the same checksum, then it is proof that you do not lose data with CDRWIN.
Finally, with each dump you can take note of the drive read offset, detect the sample offset and from that calculate the factory write offset using one single tool analyzing the dumped CDRWIN image. Together with the cue sheet, you can also calculate checksums for all tracks, even choosing different methods (with or without offset correction, with or without pre- or postgap zeros).
Also, I'm still waiting for a sufficiently good statement about CDRWIN's and EAC's pregap detection. Is there any particularily "difficult" CD with which that can be tested and see if both tools come up with different results?