Displaying 3 results from an estimated 3 matches for "partition_size".
2015 Aug 16
0
Questions about the accuracy of the spec
...uch cases that all the audio channels belong to submap #0 in the original order without
examining the array [vorbis_mapping_mux] (which is empty).
2. On page 58 section 8.5., it is unclear as to which of the following implementation is correct:
? A. For each partition, decode a vector the size of [partition_size] * [ch] according to Format 1 and deinterleave. Repeat the process over all partitions. (wrong)
? B. Decode a single vector the size of [blocksize / 2] * [ch] according to Format 1 and deinterleave once. (correct)
3. On page 60 section 8.6.2., taking the greater of [residue_begin] and [actual_size...
2015 Feb 19
0
isohybrid and ISO images whose size is not a multiple of 2048 bytes vs. VirtualBox
...tell for BIOSes, but partition editors have options
> to set heads-per-cyl and sectors-per-head. At least fdisk
> makes guesses from comparing LBA and CHS of the partition ends
> under the assumption that each partition ends at a cylinder end.
Hence, the algorithm should try to achieve:
partition_size = C*H*S*512
which is equivalent to not having partial cylinders.
>
>
> > Additionally, what do you mean with "non-traditional sizes"? Or, in
> > other words, what would constitute a traditional size for the resulting
> > isohybrid image?
>
> I mean non-...
2015 Feb 19
2
isohybrid and ISO images whose size is not a multiple of 2048 bytes vs. VirtualBox
Hi,
Ady wrote:
> I am not so sure that using a different pair of '-h' and '-s' values
> would be better than using 255/63.
But 255 * 63 is not divisible by 4 and thus can cause
trouble with virtual DVD-ROM.
> Most BIOS and most partition editors would assume this geometry.
I cannot tell for BIOSes, but partition editors have options
to set heads-per-cyl and