similar to: How is a isohybrid --partok image to be used ?

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, 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, 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, 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

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

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

Thanks for all the input everyone. I can understand the problem more clearly now. Didier Spaier wrote: > Sorry if this is a silly question: why not use a GUID partition > table instead of using logical partitions? Not a silly question, I had the same idea and had tried it out but it didn't work (same error msg). Ady Ady wrote: > The typical (modern) "MBR" supports 4

> 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

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, > > Ady: > > _ Wiki should use more user-friendly language and "less deep" > > technical information. > > I tried to stay at the surface of isohybrid. > (Didier already asked for more depth about expert options.) My interpretation of Didier's questions is less depth and more user-friendly practical commands for end-users. Our points of view

Hi, i'm possibly not the best source of general SYSLINUX knowledge, as my interest in it is only with my xorriso hat on. (As you can see in the SYSLINUX wiki, xorriso can do the isohybridization without the need for the isohybrid program.) Fulalas Caos wrote: > I tried this: > mkisofs -o "$ISONAME" -v -l -J -joliet-long -R -D -A "$CDLABEL" \ > -V

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? >

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

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: *

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

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, > > Ady: > > Since both included variants are currently different, and both > > variants have problems > > I am not aware of problems of the perl version. It is just lacking > the newer features which support EFI/GPT and Mac/APM. > The known bugs of isohybrid.c are with those newer features. > http://www.syslinux.org/archives/2012-May/017843.html >

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, i have implemented in xorriso the equivalents of isohybrid.c options --mac and --uefi. There remains the question how to ensure that the submitted MBR is prepared for the 32 byte mock-up of an APM Block0. I see in git of may 2012 that all mbr/isohdp[fp]x*.bin begin by 33 ed 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90