Scan Range Counts

3 March 2002

Scan range counts are now fully implemented and support for undefined scan ranges for data and sync values. This allowed us to fully re-enable gap support. As previously stated, this was temporarily removed due to missing functions.

Because of this, a gap track descriptor was added, and the block descriptors that implement gap scanning were modified.

The scan range based descriptors do not normally take a noticeable amount of time. However, each gap track takes about 9 seconds to fully check. One particular game that contains about 130 gap tracks takes the analysation time up to about 20 minutes!

This time can be improved, however it may be pointless since usually only very old games contain gap tracks and it is way too much effort to implement for just this.

To get the remaining dumps fully described we need:

• Noise (unformatted) track support through normal data types
• Viewer for unmapped data after analysation
• SAVE

Not too much compared to what has already been done.