similar to: Syslinux 3.82-pre3 out; short bug fix cycle

Hi everyone, I have pushed out Syslinux 3.82 to the usual places. Again, special thanks to my employer, Intel, for letting me spend time working on this stuff ;) -hpa Syslinux 3.82 is a bug fix release for 3.81. Changes in 3.82: * isohybrid: fix the -partok logic for loading from a partition. * ISOLINUX: deal with systems which return from INT 13h with interrupts

Hi, Ady wrote: > We seem to be suggesting to just dd' the first 432 bytes of their USB > devices with Martin's isohybrid Yes. As long as it is not about the old Macs which the APM of Fedora and some Gentoo ISOs wants to make boot, and not about ISOs made with isohybrid options --partok -ctrlhd0 --forcehd0. > which would be the step-by-step instructions for users of other >

Hello, I have the following scenario: - GPT Partitioned USB disk with syslinux (or extlinux) on the first partition and a menu to boot each partition; all of them are iso9660 images of different linux distros, - Before dumping every iso image into its partition space on the USB disk I need to remaster it changing something on its initrd to be able to coexist with other linux distros on the

Hi, > For instance, if a common user reads a section about a general > concept, then introducing commands of specific tools (even with the > intention of clarity) could make the reader (mis)understand that such > tool or such commands are part of the general concept. The first example with "xorriso ... -isohybrid-mbr" serves the purpose to explain how the isohybrid

I've attempted to understand what the isohybrid tool is doing, specifically with the "--partok" flag. As far as I can see, this essentially trims off the first 3 bytes of the custom isohybrid MBR image before applying it to the ISO. Can anyone explain how this enables the ISO to "be happy" on a partition, rather than whole disk? And does anyone have suggestions for what

Hi everyone, I have pushed out Syslinux 3.81 to the usual places. Again, special thanks to my employer, Intel, for letting me spend time working on this stuff ;) -hpa Syslinux 3.81 is primarily a bug fix release. The main new features are halt-on-idle support and some features to isohybrid, including the ability to boot from an image written to a partition. Changes in 3.81: *

> Hi, > > > For instance, if a common user reads a section about a general > > concept, then introducing commands of specific tools (even with the > > intention of clarity) could make the reader (mis)understand that such > > tool or such commands are part of the general concept. > > The first example with "xorriso ... -isohybrid-mbr" serves the

Thanks for the clarification Thomas. Thomas Schmitt wrote: > (Did you already tell which partitions exist and in which one do you want > to put your ISO ?) I've tried a number of different structures, but the results are consistent (boots fine from primary partitions, not from logical partitions). For example for a disk partitioned like below: Disk /dev/sdc: 3.8 GiB, 4007657472

Hi, I have been attempting to set up a multi-boot USB stick (i.e. multiple bootable ISO images on the one stick) I have had good success by: - processing ISO with isohybrid (with "partok" flag) - dd'ing ISO to primary partitions on the USB stick (e.g /dev/sdc2, /dev/sdc3, /dev/sdc4) - installing grub to USB stick and configuring to chainload to these partitions To remove the limit

Hi, Duncan Elliot wrote: > As far as I can see, this essentially trims off the first 3 bytes of the > custom isohybrid MBR image before applying it to the ISO. You probably mean this line: memcpy(mbr, &isohdpfx[hd0 + 3 * partok], MBRSIZE); The indize do not apply to bytes but to byte arrays of size MBRSIZE. extern unsigned char isohdpfx[][MBRSIZE]; (hd0 + 3 * partok)

Hi, H. Peter Anvin: > It means that the .iso can be booted from a partition using any of the > standard MBRs (not necessarily altmbr), But the --partok MBRs (isohdpp*) stem from altmbr ? If so: don't they need the partition number patched in ? (If not: i have to rethink the link to article "Mbr" at http://www.syslinux.org/wiki/index.php/Isohybrid#MBR_selection ) >

On 06/25/2014 01:16 AM, Thomas Schmitt wrote: > Hi, > > i am trying to document the MBR selection by isohybrid option --partok. > > I assume it is related to "altmbr.bin" as described in > http://www.syslinux.org/wiki/index.php/Mbr > But there i read > "altmbr.bin [...] boots from a partition with fixed number, see below." > > The "see

Hi, i am trying to document the MBR selection by isohybrid option --partok. I assume it is related to "altmbr.bin" as described in http://www.syslinux.org/wiki/index.php/Mbr But there i read "altmbr.bin [...] boots from a partition with fixed number, see below." The "see below" probably refers to "The altmbr.bin (all 3 variants) is only 439 bytes long, -- one

I have just pushed out Syslinux 3.81-pre10. This fixes some pretty serious bugs, including the fact that, apparently, isohybrid didn't work at all in CBIOS mode. Unfortunately it means that the isohybrid handover protocol has changed, and so a new isolinux.bin isn't compatible with an old isohybrid or vice versa (as a result, the magic number has changed.) -hpa

Hi, i think i found the reason for the boot failure in the definition of Extended Boot Records. https://en.wikipedia.org/wiki/Extended_boot_record#Values "Starting sector = relative offset between this EBR sector and the first sector of the logical partition. Note: This is often the same value for each EBR on the same hard disk; usually 63 for Windows XP or older." So if

Thomas Schmitt wrote: > Since we know that the isolinux.bin binary is well ok on other partitions, > i'd say that the MBR code does not load the right blocks from disk when > it wants to get isolinux.bin. Yes, these are my thoughts as well. I think the jump from GRUB to the isohybrid code on the logical partition is working fine, but when the isohybrid code is trying to jump to

Thomas Schmitt wrote: > I have some problems understanding the details of the program's flow. > > - The code inside PARTITION_SUPPORT is supposed to be inactive with > MBR isohdpfx.bin. It belongs to isohybrid --partok which is equivalent > to MBRs isohdppx*.bin. Debian uses isohdpfx.bin. Yes. isohdpfx.bin is generated from isohdpfx.S in which PARTITION_SUPPORT is not

Hi, On 23/06/2014 12:07, Thomas Schmitt wrote:> Hi, > > i have written an introduction to isohybrid and put it on > the discussion page of the ISOLINUX wiki. > > http://www.syslinux.org/wiki/index.php/Talk:ISOLINUX#Proposal_for_description_of_isohybrid > > Review and proposals are appreciated. Caveat emptor: this is a review by an end user (not a developer), who

2016-12-23 9:20 GMT+01:00 Thomas Schmitt via Syslinux <syslinux at zytor.com>: > Hi, > > Ady wrote: > > the UEFI specs do state that the ESP is supposed > > to be set/used as no-emulation mode > > ... > > the UEFI specs should tolerate / accept this situation, rather than > < restricting the ESP to no-emulation mode. > > My criticism towards this

Hi, Duncan Elliot wrote: > What is the thought process of clearing the ISO MBR? It is not necessary in the partok case, because the partition to which you copy the image encloses the ISO, exposes it for mounting, and protects it from partition editors. (Another idea from assembler riddling turned out to be a red herring.) Without understanding the language or the BIOS habits of MBR