similar to: CD-ROM hybrid mode

Hi, I would like to ask if there are any known issues with booting an ISOLINUX hybrid iso image from a USB Flash Drive on older Dell PC's (i.e. P4 2.2GHz). I've tried several that one should just be able to write to UFD and boot, but they all fail on my hardware. I get "isolinux.bin missing or corrupt" message on screen. This function would be very convenient for me, so

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

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

I have been using syslinux-6.x along with isohybrid --mac and --efi option to create a usb hybrid iso with EFI support. The thing with EFI is that you'll need to use grub as your bootloader for EFI but isohybrid does setup the proper partition schema for EFI. You'll need to use the following to generate an iso that works. xorriso -as mkisofs -J -R -l -V some-vol-label \ -o ../image.iso

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

On 14.07.2015 01:31, Gene Cumm wrote: > On Mon, Jul 13, 2015 at 3:24 PM, poma <pomidorabelisima at gmail.com> wrote: >> On 13.07.2015 18:48, Gene Cumm wrote: > >>> It stops after printing the access type "ETCD" and before printing the >>> remainder of the banner. I presume this is not a hybridized image? >>> >> >> >> I

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

> Hi, > > Ady wrote: > > This could be misinterpreted by some users as: "if > > you want to build an isohybrid image, then you cannot use > > 'syslinux.efi'". This would be incorrect. > > I don't know whether syslinux.efi can be used for booting > from ISO 9660 via UEFI. Currently there is no example > around which would succeed

On 13.07.2015 18:48, Gene Cumm wrote: > On Mon, Jul 13, 2015 at 10:20 AM, poma <pomidorabelisima at gmail.com> wrote: >> On 13.07.2015 15:19, Gene Cumm wrote: >>> On Mon, Jul 13, 2015 at 9:03 AM, poma <pomidorabelisima at gmail.com> wrote: >>>> On 13.07.2015 14:53, Gene Cumm wrote: >>>>> On Mon, Jul 13, 2015 at 6:42 AM, poma

Hi, On 11/11/2014 02:55, Ady wrote: > Again, dd'ing your isohybrid image onto your (virtual or real) drive > will fail to boot in EFI mode. Your "syslinux.efi-based" > "/isolinux/efiboot.img" will not be capable of booting. This is one > of the steps that corresponds to grub2, not to whichever other EFI > bootloader you use (e.g. syslinux.efi). So,

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:

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

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

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.)

Hi all, As part of a bigger effort to port the ISOLINUX hybrid mode to ReactOS, I've encountered a bug in isohybrid under Windows platforms. Attached comes a patch to fix it. Precisely, if isohybrid currently finds a 0x0A (LF) byte in the MBR code (which exists in the strings), it adds a 0x0D (CR) before, thereby shifting the MBR bytes to the right and making it invalid. This can be fixed by

Hi, i wrote: > > http://mjg59.dreamwidth.org/11285.html piranna at gmail.com wrote: > There it says about creating a third El Torito image only for Macs, > since old ones could fail and this could be the problem I'm having. The third boot image is HFS+, not FAT. I understand this is for pre-EFI Macs. Try a Debian amd64 ISO, e.g.:

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

Precis: I?m trying to debug a problem with CentOS7 failing to install from an ISO written to a USB pendrive ? anyone got suggestions? What works ? installing on a modern, ?standard PC?; the pendrive image boots and installs as I expect What does not work ? same pendrive booting in an ATCA blade. What I?ve tried is? 1. Boot the standard CentOS7 minimal image. This seems to start but then

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