similar to: isohybrid fails with: seek error - 3

On 01/11/2013 05:36, Ady wrote: > >> That is with syslinux 4.05 on Slackware-14.0: >> >> bash-4.2# isohybrid -v /tmp/slint64-13.3720131030-dvd.iso >> catalogue offset: 561 >> ve[0]: 1, cs: 1 >> ve[1]: 0, cs: 1 >> ve[2]: 0, cs: 1 >> ve[3]: 0, cs: 1 >> ve[4]: 0, cs: 1 >> ve[5]: 0, cs: 1 >> ve[6]: 0, cs: 1 >> ve[7]: 0, cs: 1

> That is with syslinux 4.05 on Slackware-14.0: > > bash-4.2# isohybrid -v /tmp/slint64-13.3720131030-dvd.iso > catalogue offset: 561 > ve[0]: 1, cs: 1 > ve[1]: 0, cs: 1 > ve[2]: 0, cs: 1 > ve[3]: 0, cs: 1 > ve[4]: 0, cs: 1 > ve[5]: 0, cs: 1 > ve[6]: 0, cs: 1 > ve[7]: 0, cs: 1 > ve[8]: 0, cs: 1 > ve[9]: 0, cs: 1 > ve[10]: 0, cs: 1 > ve[11]: 0, cs:

On 01/11/2013 18:40, Didier Spaier wrote: > On 01/11/2013 05:36, Ady wrote: >> >>> That is with syslinux 4.05 on Slackware-14.0: >>> >>> bash-4.2# isohybrid -v /tmp/slint64-13.3720131030-dvd.iso >>> catalogue offset: 561 >>> ve[0]: 1, cs: 1 >>> ve[1]: 0, cs: 1 >>> ve[2]: 0, cs: 1 >>> ve[3]: 0, cs: 1 >>>

Op 2014-06-20 om 15:56 schreef Ady: > > The Perl variant, isohybrid.in, seems to be getting left behind > regarding several patches. I don't recall whether there is at least > some mention in the isohybrid docs about the existence of 2 variants > included in Syslinux (and that is in addition to other isohybrid > methods outside Syslinux). Is there any reference? >

EFI systems typically don't support booting off ISO 9660 filesystems, even if written to USB sticks. This patch adds support for generating a GPT that covers the stick as well, with an additional partition entry pointing purely at the secondary El Torito image. When burned to CD the secondary El Torito will be used as an EFI boot image, and when written to a USB stick the GPT partition

Hello Recently while playing with bigger iso images (>2G) looks like isohybrid from syslinux-4.02 fails. Sometimes tunning heads/sectors (-h/-s) works, because no padding is needed depending of size of the image. Some debug info provided, if more info is needed please just ask. # isohybrid -v pandereta-2010.09.13-i686.iso catalogue offset: 326 ve[0]: 1, cs: 1 ve[1]: 0, cs: 1 ve[2]: 25927,

> Hi, > > Pascal wrote: > > mkisofs -o core.iso -b boot/core.img -c boot/boot.cat -hard-disk-boot core/ > > my iso image is ok with qemu on bios and uefi, > > Astounding. As CD-ROM this is not supposed to work with UEFI unless the > firmware emulates BIOS. What particular UEFI firmware did you use ? > > > and with qemu as hard disk on uefi but not on

Hi, Ady wrote: > I very much doubt that there is any ISO image, publicly > available or not, that can boot optical media in UEFI mode by means of > Syslinux for EFI as of today. I hope this status will change at some > point. > [...] > I doubt that syslinux.efi (renamed as "EFI/BOOT/BOOT<arch>.EFI") > is capable of booting optical media in UEFI mode at

Hi, following will be 6 patch proposals for isohybrid.c 1: Encode GPT partition names as UTF-16LE 2: Correct blocking factor in APM partition block counts 3: Correct end block address of first GPT partition 4: Write GPT backup to the very end of the image 5: Change all fseek(3) to fseeko(3) 6: Introduce option --mbr and make isohybrid.c compilable standalone If the form needs adjustments,

Hi, i downloaded http://slint.fr/misc/testing/slint64-14.1_syslinux.6.03.iso Inspection by xorriso-1.3.8: xorriso -indev slint64-14.1_syslinux.6.03.iso \ -report_el_torito plain \ -report_system_area plain yields El Torito catalog : 46 1 El Torito cat path : /isolinux/isolinux.boot El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA El

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, Didier Spaier wrote: > http://slint.fr/testing/slint64-14.1_syslinux.6.03/slint64-14.1_syslinux.6.03.img This looks like the content of an EFI system partition. Exactly what i need for experiments. Thanks a lot. (slint64-current-goofiboot.iso and slint64-current-efi-stub.iso were already in my collection.) It boots to "Slint installer for Slackware64-14.1" by:

Various EFI systems insist that there be no active flag in the pMBR in order to parse the GPT. The only way around this is to also generate a valid MBR - the firmware will then pick that up and use the system partition provided there. In order to deal with other EFI "sanity" checks, the partition type for the non-EFI partitions is set to 0 to skip the firmware bailing because of

Hi there, I failed to boot an installer in a VMware player (Version6.0.3 build-1895310) using syslinux 6.03, be it off an hybrid ISO image and an USB stick. Booting succeeds if the VM is set to use a BIOS firmware with both media, but fails using an efi firmware. Trying to boot off the ISO image I get an error message "The firmware encountered an unexpected exception" Trying to

Hi, > Unfortunately I get the error message: > isohybrid: slint64-14.1.iso: unable to find mac efi image This is probably due to El Torito Platform id "Mac" in -eltorito-alt-boot -no-emul-boot -eltorito-platform Mac \ -eltorito-boot isolinux/macboot.img \ This caused in the image http://slint.fr/misc/MacBoot/slint64-14.1.iso platform id 1 with the third image. (I would

Hi, > I don't understand why you say "*But* the El Torito...". I don't see > a difference with what the mkisofs manual says. The manual announces "Mac" for Apple Mac. The program obviously writes Platform Id 1 in this case. The El Torito specs say "Platform ID 0 = 80x86 1=Power PC 2=Mac". In the sum this does not match. A bug in mkisofs would be the

Hi, i wrote: > > Not only MBR writing but also reading of the Primary Volume Descriptor > > and of the El Torito catalog by isohybrid.c are currently prone to > > unwanted CR-insertion. Miscalculations can be caused by this. I have to correct myself: Carriage Return characters (byte value 13 = 0x0d) are not at risk to be inserted, but rather to be removed if they happen to be

Hi, Ady wrote: > http://www.syslinux.org/archives/2015-October/024526.html I still have it in my mailbox: ADY4UEFI.IMG in ADY4UEFI.ZIP. The test results are the same as with Didier's partition image. Wrapped in an ISO and presented as -cdrom it reboots in cycles. Presented as -hda it boots as naked disk image and as part of a GPT enhanced ISO 9660. > the wiki page needs

It seems unwise to offer future programmers fseek(3) calls for copy+paste. They are simply insufficient for large image files. This change switches all calls of fseek(3) to fseeko(3) and takes care that the offset value if of type off_t. --- utils/isohybrid.c | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/utils/isohybrid.c b/utils/isohybrid.c index

I have addressed all the issues that I know about (including, hopefully, the isohybrid version dependence...). I would like to release this this week so please let me know as soon as possible if this version is "go". -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.