similar to: Patch: Fix isohybrid.c tool under Windows platforms

> 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, 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 proposal. If one wants the same behavior of

Hi, i wrote: > > Not only MBR writing but also reading of the Primary Volume Descriptor > > and of the El Torito catalog by isohybrid.c are currently prone to > > unwanted CR-insertion. Miscalculations can be caused by this. I have to correct myself: Carriage Return characters (byte value 13 = 0x0d) are not at risk to be inserted, but rather to be removed if they happen to be

Am 17.04.2017 um 15:44 schrieb Thomas Schmitt via Syslinux: >> So, is there any reason not to apply the suggested patch? Any potential >> compatibility issues? Backward compatibility between different versions >> of isohybrid and isolinux.bin? Anything? > > No. It's just a bug fix. So, is anything more going to happen now? My patch is apparently accepted, yet nobody

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, 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, On 29/07/2014 21:34, Thomas Schmitt wrote: > Nevertheless i advise Didier to simply try with 0xef rather than Mac. At least the ISO will then have MBR, GPT and APM entries for the file macboot.img. I did that, and also tried the xorriso command you posted. I uploaded both ISO images on http://slint.fr/misc/MacBoot resp. renamed: slint64-14.1-Thomas_mkisofs.iso

I'm going to get the hang of this mailing list eventually. Apologies for any duplicate emails.. >Ian Bannerman: >> While I did know the .exe variant was not official / untrusted, >Is there a special reason for this ? (Except the known bugs which affect Linux binaries, too.) Not really. I had never found a convincing source for it and had seen previous list entries like this

hello every body, I'm trying to build an isohybrid image based on syslinux able to boot on bios and uefi with optical disk or usb key. I've build a 16Mb hard disk image (core.img) with necessary parts for bios (legacy bootable partition, protective mbr, gptmbr.bin & syslinux installation) and for uefi (gpt, esp, /efi/boot/bootx64.efi & syslinux files). my hard disk image is ok -

Hi, Didier Spaier: > I uploaded both ISO images on http://slint.fr/misc/MacBoot A good opportunity to brag with xorriso's boot inspection features (since xorriso-1.3.8): xorriso -indev slint64-14.1-Thomas_mkisofs.iso \ -report_el_torito plain \ -report_system_area plain yields (block size is 2048): El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz

Hello, I installed IE6 with both WineTools and IEs4Linux (under different user accounts). Most of the features work, but IE often hangs. Then I can only kill the process. Has someone got IE6 stable under WINE? If so, which WINE version do I have to use and how shall I configure it? Thanks in advance, Colin Finck

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

> > I am still interested in improving the isohybrid wiki > and will watch for pointers to descriptions of the FAT > production process (with GRUB/GRUB2 if not with SYSLINUX). > > If no such descriptions appear within the next weeks, > then i plan to state in > http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI > > "The SYSLINUX project cannot yet provide

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, > > Ady wrote: > > cdrtools.sourceforge.net/private/man/cdrtools-3.01axx/mkisofs.8.html > > Mac Boot entries for the Apple Mac platform. > > Interesting feature. But the El Torito specs of Phoenix and > IBM of 1994 state that "Mac" would be Platform Id 2. > http://download.intel.com/support/motherboards/desktop/sb/specscdrom.pdf > Page

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

Hello everyone, I am maintaining a distribution loosely based on LFS and am now trying to add UEFI support. Integrating a FAT formatted partition image containing, preloader, gummiboot, kernel and initramfs correctly results in a ISO image that is bootable on BIOS and UEFI systems if booted from the optical drive. However, when I run isohybrid --uefi name-of.iso the resulting GPT entry for

when you say """ Unfortunately, syslinux.efi v.6.03 is not capable of booting optical """, you talk about isolinux.bin ? because my iso image with a "good" alternate eltorito boot image (eg. "uefi ready") is booting with qemu (qemu -cdrom core.iso -bios uefi.fd) and is also booting in hard disk mode (qemu -hda core.iso -bios uefi.fd). Le mercredi

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