Re: [VCDImager Bugs/Devel] vcd_assert (_root->size == ISO_BLOCKSIZE* _root->secsize);

I wrote: 

> The assertion as I understand it is a the check is that the size
> recorded for a directory entry on the CD be a multiple of the 2048,
> the ISO 9660 blocksize unit (as I understand it).  Certainly, blocks
> are *written* to a CD as written in whole "sector" units. In your
> case, the blocksizes recorded in the directory entries are short. It
> may very well be that's the amount *used*. And whether that is
> permissible or not, I don't know.  If you look at say Unix directory
> sizes you'll they often are a multiple of blocksizes like 512.

To which WD reports:

OK, got it.   I found some information:
http://www.alumni.caltech.edu/~pje/iso9660.html

Near the end, there is a section called 10. Directories In this
document, it mentions that a directory entry *must* be an exact
multiple of the sector size to be ISO9660 compliant.

Now, from what I've read, the White Book standard for VCD requires
that the disc must be ISO 9660 compliant.

So logically, the Pinnacle Studio VCD that I have created is not a
totally VCD compliant disc.  (And vcddebug/vcddump Assert because of
this violation)

The Pinnacle Studio VCD that I have plays fine in my DVD player, and
I've given out a couple copies to others and they haven't reported any
problems either.


I'll notify Pinnacle of my findings, but I'm not going to hold my
breath for a fix on their end....  They've got notoriously poor
support.  (I'm still waiting on a fix for a bug that was reported over
a year ago, among others!)

Thanks for the help.


-WD