similar to: Issues Booting Hybrid ISO from UFD on Dell PC

Hi, if I inspect an hybrid ISO with tools like fdisk and gdisk, then looks like hybrid ISO has both the MBR and GPT in order to support both the BIOS and UEFI: # gdisk -l /dev/sdb GPT fdisk (gdisk) version 0.8.10 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: present Found valid MBR and GPT. Which do you want to use? 1 - MBR 2 - GPT 3 - Create blank GPT

Hi, we are the developers of an alternative to mkisofs: program xorriso from libburnia-project.org . The current development cycle is about support for creating bootable CDs, DVDs, BDs. So we look for testers and for advise about ISOLINUX specifics. The example from the ISOLINUX wiki is supposed to work if you replace "mkisofs" by "xorriso -as mkisofs". I.e: xorriso -as

Hi, it would be interesting to know for what solution TAILS decides and whether any problems arise with it. ------------------------------------------------------- On with the fundamental discussion of MBR cylinders: Ady wrote: > 1_ The resulting ISO9660 file system size shall be a multiple of 2048 > (bytes_per_sector). The known ISO production programs comply to this condition.

I?ve been creating slightly modified CentOS netinstall ISO images using the following steps: Copy contents of CentOS netinstall ISO image to a temporary directory Edit isolunux/isolinux.cfg file Create new ISO image using the following command: mkisofs -o new.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -R -J -v -T /tmp/iso I?ve been using

Hi, Ady wrote: > Let's not forget that the goal usually is to select CHS values so that > the resulting (optical and/or other) media would boot correctly in as > many systems as possible Agreed. But we now have a report about failure of 255x63 on a popular pseudo-hardware, when the ISO is presented as DVD-ROM. (Probably there is no complaint when it gets presented as hard disk.)

> I proposed -h 252 -s 63 because it yields the largest > possible cylinder size which is divisible by 4 (i.e. > the byte count is divisible by 512*4 = 2048). > -h 240 -s 63 would fulfill this constraint, too. > Size limits are 252*63*1024*512 = 8,323,596,288 > resp. 240*63*1024*512 = 7,927,234,560 bytes. > > > The workaround cannot be temporal, because the

Thomas Schmitt wrote: > I still don't get the "backwards" aspect. (Probably not enough background > knowledge.) Sigh. inst x, y gas use x and possibly y, operates according to inst and puts the result in y. Intel lives with the misconception this should mean use y and possibly x, operate according to inst and put the result in x. If you come from gas background the first

Hi, at [Tails] we're in the process of shipping hybrid ISO images by default again. We're using `isohybrid -h 255 -s 63' to do that (thanks to the advice we got on this mailing-list a few months ago!). And then, we've discovered that sometimes, isohybrid produces ISO images whose size is not a multiple of 2048 bytes. Who cares? ... may you ask. Well, apparently, VirtualBox does:

[I was dropped from cc in the initial response but I'd appreciate if you could keep it this time around since I'm not subscribed to this list. Thanks!] Ady wrote: > I do not know the exact complete procedure that the TAILS team is using > to build the original ISO image, and how it is transformed into an > isohybrid image (there are multiple tools for each, sometimes >

> > I ponder whether it would be possible to create a diagnostic MBR > which does not necessarily have to boot but rather tells what the > isohybrid MBR would perceive: Presence of partition table, > EBIOS or CBIOS, block address used with INT 13, content of the block > read by the first INT 13, ... > > One could preserve the isohybrid MBR of an ISO and replace it by >

Hi, On 29/07/2014 21:34, Thomas Schmitt wrote: > Nevertheless i advise Didier to simply try with 0xef rather than Mac. At least the ISO will then have MBR, GPT and APM entries for the file macboot.img. I did that, and also tried the xorriso command you posted. I uploaded both ISO images on http://slint.fr/misc/MacBoot resp. renamed: slint64-14.1-Thomas_mkisofs.iso

Hi, Didier Spaier: > I uploaded both ISO images on http://slint.fr/misc/MacBoot A good opportunity to brag with xorriso's boot inspection features (since xorriso-1.3.8): xorriso -indev slint64-14.1-Thomas_mkisofs.iso \ -report_el_torito plain \ -report_system_area plain yields (block size is 2048): El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz

Hi, Gene Cumm wrote: > it seems the stack format got > set, changed, then mostly reverted back, with this code being the last > piece missing from 2009. The commit to isohdpfx.S of 2009-05-31 looks incomplete. The sequence of the stack pointers was swapped, but the sequence of stack pushes was not.

Just tried the latest release and found a minor bug. Have a UFD w/ SYSLINUX, which boots a simple .BSS image no problem. Launching exactly the same image on a ISOLINUX disc fails w/ the following error msg: Invalid image type for this media That's it for this msg. Later....Jet -- Powered by Outblaze

Hi, I am trying to create a hybrid ISO image for FreeBSD 9.2 using syslinux 6.01 and isohybrid.pl I found at http://www.overclockix.com/sources/isohybrid.pl (I know there is a C version in syslinux but I haven't been able to build it yet due to the UUID library being different to the one in FreeBSD). According to the wiki mboot.c32 can boot FreeBSD, however I haven't been able to get it

> Hi, > > Ady wrote: > > http://repo.or.cz/syslinux.git/tree/HEAD:/diag > > "handoff.bin > > This does not look like it would tell much of the properties in question. > Nevertheless its print functions might be of interest for an isohybrid > diagnostic MBR. > > > > and at least 2 geodsp*.{bin,img(gz)} > > I am now reading >

HI, In http://slint.fr/misc/MacBoot/ you'll find all context information. All files referenced here are stored there. Long story short: once dd-ed on an USB stick the ISO image can boot on a BIOS or EFI machine, but I want it to be able to boot on most x86_64 Macs with an EFI firmware. Unfortunately I get the error message: isohybrid: slint64-14.1.iso: unable to find mac efi image The

Hi, Ady wrote: > so, why the original isohybrid image from Debian and many other > isohybrid images have mostly (but not all) "00s" in place of the "90s"? That's a fake Block0 of an Apple Partition Map. Part of mjg's layout. Caused by isohybrid option --mac or xorrisofs option -isohybrid-apm-hfsplus. * Fedora has it with EFI FAT filesystem in one partition

Thomas Schmitt wrote: > I ponder whether it would be possible to create a diagnostic MBR > which does not necessarily have to boot but rather tells what the > isohybrid MBR would perceive: Presence of partition table, > EBIOS or CBIOS, block address used with INT 13, content of the block > read by the first INT 13, ... ... > The diagnostic MBR should only use 432 bytes because at

Hi, On 29/07/2014 23:19, Thomas Schmitt wrote: > A good opportunity to brag with xorriso's boot inspection > features (since xorriso-1.3.8): Yes! I've upgraded libburn, libisofs and libisoburn so now I can play with it too ;) > I forgot to advise (or misadvise) -isohybrid-apm-hfsplus with > the image /isolinux/efiboot.img . So we only got one APM > partition here. A