Displaying 3 results from an estimated 3 matches for "isohybrid_test_mockup".
2015 Feb 20
0
isohybrid and ISO images whose size is not a multiple of 2048 bytes vs. VirtualBox
>
> I wrapped the essential code into a standalone program for
> playing with a few numbers:
What about '-h 255 -s 63 , ISO size 1085736960' ?
> I expect the average waste to be a bit less than 16 MB.
Yes, but slightly misleading. For example, the "16MB average" is
relevant for 255/63.
Some user reading the code might not know the whole reasoning for:
>
2015 Feb 20
3
isohybrid and ISO images whose size is not a multiple of 2048 bytes vs. VirtualBox
Hi,
> What about '-h 255 -s 63 , ISO size 1085736960' ?
-h 255 -s 63 , ISO size 1085736960 :
align_factor= 4 , padding= 0 , image size= 132.000000 cylinders
-----------------------------------------------------------------
Code of isohybrid_test_mockup.c :
-----------------------------------------------------------------
#include <stdlib.h>
#include <stdio.h>
int main(int argc, char **argv)
{
int cylsize = 0, frac = 0, align_factor, align_cylsize;
int padding;
unsigned long img_size;
int head, sector;
sscanf(argv[1], "%d&...
2015 Feb 20
4
isohybrid and ISO images whose size is not a multiple of 2048 bytes vs. VirtualBox
Hi,
> Now, I have a question: what about the "offset" parameter? How it
> modifies our assumptions and calculations if the "offset" parameter is
> not zero?
The offset influences only the start address of the
partition. The alignment goal is about the end address.
So these concepts are nearly independent.
Of course, partition start must be smaller than partition