| Previous | Next |
| E_IMAPI_RAW_IMAGE_TRACK_INDEX_NOT_FOUND | E_IMAPI_RAW_IMAGE_TRACK_INDEX_TOO_CLOSE_TO_OTHER_INDEX |
E_IMAPI_RAW_IMAGE_TRACK_INDEX_OFFSET_ZERO_CANNOT_BE_CLEARED
E_IMAPI_RAW_IMAGE_TRACK_INDEX_OFFSET_ZERO_CANNOT_BE_CLEARED protects the mandatory first index boundary of a track. IMAPI documents the zero-offset entry as index 1 and does not allow it to be cleared from the track layout.
Do not treat the first track boundary as an optional cue marker
- Inspect code that converts user chapter markers or cue entries into raw track indexes.
- Keep the zero-offset index and remove only optional later indexes when editing the layout.
- When the intended first audible/data position is different, review pregap and track-stream construction rather than deleting index 1.
This is a structural rule, so recreating the same image and issuing the same clear operation will fail again. It also differs from TRACK_INDEX_NOT_FOUND: offset zero exists, but IMAPI refuses its removal. Diagnostics should record the requested clear offset and track number so the application can distinguish an attempt to remove the protected first index from an attempt to remove an index that is not present at all.
Track information · Track indexes · IMAPI return values
Looking for a different code? Search another status or error code.