This field is currently being treated as the high byte of the sector size, when it's apparently actually log2(bps)-7, the direct value out of the DPB. I don't know why this wasn't caught before, although the result is the same for standard 512-byte sectors, and any unusual images that still worked may have incorrectly filled this field.
Have also seen an instance (Red Sunset) where the logbps in TIB[0] is 0, but 2 in all the associated SIBs.
This field is currently being treated as the high byte of the sector size, when it's apparently actually log2(bps)-7, the direct value out of the DPB. I don't know why this wasn't caught before, although the result is the same for standard 512-byte sectors, and any unusual images that still worked may have incorrectly filled this field.
Have also seen an instance (Red Sunset) where the logbps in TIB[0] is 0, but 2 in all the associated SIBs.