similar to: Patch to port isohybrid.pl to isohybrid.c

Hi, Miller, Shao: > I am enjoying this discussion Me not. I feel quite misunderstood. hpa: > Actually, I would prefer if you removed this in its current form. Ok. Will do. If any viable solution emerges, please let me know. Have a nice day :) Thomas

Hi, Just checking, if there are any updates about testing of the isohybrid.c patch at -> http://pjp.dgplug.org/tools/syslinux-3.86-isohybrid.patch.10 Is there anything I can do to help test it? Thank you. --- Regards -P J P PS: Please don't send me html/attachment/Fwd mails

Hi together, this is the second version of my cross-compilation patch serie. I'm sending it in the hope to get an honest review, and possibly see the patches integrated upstream. Those patches allow to build syslinux using a toolchain different from the host one by explicitely using the host toolchain for the utilities that are required at build-time / on the build machine. I am using the

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

Dear list, I have been trying to debug a build failure for a while in the utils directory on isohybrid which seems to be distro specific. On Fedora 17 64bit the build completes without problems, but under both Ubuntu 32/64bit 11.10 and 12.04 I get the following: tim at oxygen:/usr/src/git/syslinux/utils$ make gcc -O2 -luuid -o isohybrid isohybrid.o isohdpfx.o isohybrid.o: In function

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

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, 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, 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, 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, > The ISO will boot successfully (when chainloaded from grub) on 2 and > 3, but not on 5 and 6. Did you try with a boot loader other than GRUB ? Afaik, the MBRs of newly bought USB sticks often contain code which hops on the MBR code of the partition that is marked by the boot flag. At least one could exclude that your problem is in a GRUB peculiarity. Have a nice day :) Thomas

> Hi, > > > All the "isohybrid.exe" I know of are based on the Perl variant. > > I just got one from > http://www.filewatcher.com/m/isohybrid.exe.39568-0.html > > Its strings seem not to stem from isohybrid.pl. > > Digging in slitaz source brought a shell script (that would be > variant #5 then): >

Hello, The recent discussion about the size of the image produced by isohybrid not being a multiple of 2048 when people use -h 255 -s 63, made me wonder of whom should be worried by this more than 1024 cylinders warning. Are there any technicals details available on this "not all BIOSes will be able to boot this device"? After all, any hard drive now a days cannot be represented under

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

> 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

Could someone help me get the syntax for `genisoimage' and/or `xorriso' correct? Apparently it is not in many linux distros so below my little HOWTO shows how to compile it. ( which adds tons of crap that can go wrong) mkdir -p ISO_root/isolinux cp /usr/lib/syslinux/[i,m,v]* ISO_root/isolinux cat > ISO_root/isolinux/isolinux.cfg << EOF UI menu.c32 label isolinuxtests EOF # Most

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

On Sun, Feb 2, 2014 at 6:27 AM, Mattias Schlenker <ms at mattiasschlenker.de>wrote: [...] > Build a recent xorriso - this can be run from the build directory without > installing (thanks, Thomas!): > > ./configure --enable-static > > Thank you for pointing this out, I tried desperately to statically compile `mkisofs' yesterday, to no avail. To hear that xorriso is

Hi, me: > > Please enable editing. Gene Cumm: > Done. Thanks. I have now edited http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#USB-Miscellaneous ------------------------------------------------------------ Next i'll try to develop a user oriented hint for SYSLINUX#Creating_a_Bootable_Disk which takes into respect the opinions of Ady, Mattias, me, and of any

I posted this on the bugzilla page but I figured that on the mailing list it would get more attention. Please see http://bugzilla.syslinux.org/show_bug.cgi?id=49 for a description of my current issue. -- Thank you, Fernando Reyes GPG BDD75DD7 Mission Accomplish, Inc. http://missionaccomplish.com Email:design at missionaccomplish.com Tel: 7187100008 Cell: 3479275477