>This is an email I sent to Jvrg Schilling <[EMAIL PROTECTED]>
>some time ago but neither he nor me have found the explanation.
>I send the email here to know if any of you know the explanation.
>
>I've been comparing images produced with mkisofs and nero.
>
>I've seen that mkisofs writes 4 blank sectors that nero doesn't write at
>the headers.
>
>Are these blank sectors needed to conform to iso9660 ?
>Because images produced with nero work in every system I know about.
The blank sectors are because mkisofs rounds up the number of sectors
for the path tables to an even number of sectors:
/* Now assign addresses on the disc for the path table. */
path_blocks = (path_table_size + (SECTOR_SIZE - 1)) >> 11;
if (path_blocks & 1)
path_blocks++;
jpath_blocks = (jpath_table_size + (SECTOR_SIZE - 1)) >> 11;
if (jpath_blocks & 1)
jpath_blocks++;
However, I have no idea why
It's been in the code since the earliest version I've seen (v0.99).
Comments in the early mkisofs code seem to indicate that the mkisofs code
attempted to create an output compatible with what ever product "Young Minds"
had at the time - may be that's why the number of sectors is rounded up
to an even number ... If Eric is still reading this list, then may be he
knows why ...
James Pearson
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
