similar to: Location and name of configuration files

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

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

> > 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, ... > > One could preserve the isohybrid MBR of an ISO and replace it by >

> Hi, > > Colin Finck wrote: > > 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 opening the file in binary mode with the "b" flag. > > This is a very reasonable

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

> 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

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, > > 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. > > The reference to "above mkisofs command" anticipates the final > position of this text at the end

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, On 29/07/2014 23:19, Thomas Schmitt wrote: > A good opportunity to brag with xorriso's boot inspection > features (since xorriso-1.3.8): Yes! I've upgraded libburn, libisofs and libisoburn so now I can play with it too ;) > I forgot to advise (or misadvise) -isohybrid-apm-hfsplus with > the image /isolinux/efiboot.img . So we only got one APM > partition here. A

> 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: > 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 UEFI implementation is that it probably cannot serve as realistic test bed for the first stage of UEFI booting. It seems far too

Hallo, I use "isohybrid <myimage>.iso" for creating an *.iso which can boot from CD or from USB stick. Booting from CD works fine (since years). Booting from USB stick leads to ISOLINUX 4.04 ... EDD: Error 0400 reading sector ... No DEFAULT or UI configuration directive found! What goes wrong? Searching with google showed many such messages but (at least at the

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

> I'm the developer of manjaroiso, the tool we use to build our install > medias for Manjaro Linux. > During our testings we found out, that syslinux6 won't work on older > hardware. I've a new Lenovo i7 notebook which booted up our images > just fine. Even with syslinux6. On my other PCs I got similar error > messages as Carl got. (snip) > > In

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.

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, > > Ady wrote: > > http://repo.or.cz/syslinux.git/tree/HEAD:/diag > > "handoff.bin > > This does not look like it would tell much of the properties in question. > Nevertheless its print functions might be of interest for an isohybrid > diagnostic MBR. > > > > and at least 2 geodsp*.{bin,img(gz)} > > I am now reading >

Hello everyone, Since I have some some adventures in UEFI PXE booting ahead I tried to go with the latest syslinux development snapshot in this case 5.10pre1. But I already fail when booting from CD with Failed to load COM32 file .c32 I am a bit perplex since no name of COM32 files is given. I am trying to trace down the issue as good as I can. COM32 files present are: