similar to: El Torito/ISOLinux questions

Hi, My problem is not uncommun, I have an old machine I'd like to use as a linux internet FW. The Bios is old and does not let me boot from an el torito bootable CD( 1998 PC) The CD's OK on other machines, boots fine Is there any way to get . isolinux on floppy, . when PC read floppy, isolinux tell it to boot from the /dev/hdc device, all bootfiles are in /isolinux on the CD

hello a while ago i posted a question about my troubles remastering isolinux bootable cds. after that Steffen Winterfeldt helped me out a lot and now my problems are gone. i wrote a document about my experiences and i thought i'd share it with you: http://littlesvr.ca/isomaster/eltoritosuppl.php and since i'm in pimping mode, my interest in isolinux is purely because of iso master (

hello i hope this is on topic here... i really need help and i'm guessing one of you will know the answer. i am trying to write software (open source) to work with cd images. the only thing i'm having trouble with is no-emulation 'el torito' boot records. i can't find any place where it sais how big the boot image is. bytes 8-0B of the initial/default entry say where to

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

Hi, i downloaded http://slint.fr/misc/testing/slint64-14.1_syslinux.6.03.iso Inspection by xorriso-1.3.8: xorriso -indev slint64-14.1_syslinux.6.03.iso \ -report_el_torito plain \ -report_system_area plain yields El Torito catalog : 46 1 El Torito cat path : /isolinux/isolinux.boot El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA El

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

Hi all, I am at the end of my wits, after a day and a half of mucking around with this :) My intention was to take a multi-boot DVD - of the style you get with an MSDN subscription - and burn an individual installer to disc. How to do this? My theory was to take the files for the installation CD, add isolinux, add a bootsector, and away I go. Unfortunately it doesn't seem this easy. So I

A very special thanks to H. Peter for finding the time to [at least partially, if not wholly] scrutinize and merge the El Torito emulation code for MEMDISK! I'd like to ask that those who've previously used the stale MEMDISK-ISO switch to this latest[1] MEMDISK proper and report any failures. Gert, I believe this version addresses the PloP .ISO trouble you reported. Could you

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

H, Ady wrote: > A_ The default checksum included in the tested isolinux.bin (offset 20, > 4-bytes-long) is the "correct" one (as oppose to the current situation, > since version 4.00). That's good news. > F_ In the tested isolinux.bin file, there are two additional bytes that > I found to be changed/affected by some ISO-building tools (e.g. > mkisofs), at

I used to use multiple syslinux floppy images to implement what I call CD-ROM-multiboot (EL Torito supports up to 64 bootable images, Award BIOS 8 images, if not wrey old). Now that floppies are getting too small, I find that I must find a workaround for hard coded isolinux directory name in isolinux. Not a big deal, but there might be also others who would like to have multiboot feature. --

I am trying to install Debian Linux on an an old Intel Classic R+ computer that uses an internal Yamaha SCSI CD writer model CRW8424S connected to an Adaptec ISA SCSI card (I think its a 1542CP). The CD writer is is the only device connected to the SCSI card. The computer has one hard drive connected to the on-board IDE interface, a 1.44MB 3 1/2 inch floppy and a 1.2MB 5 1/4 inch floppy. The hard

Hi, When we meet UEFI or EFI firmware, lots of linux os release use GRUB bootloader. But I wanna use isolinux to boot the installation environment and also the linux os installed. Some question puzzled me. Now, I look for your help: 1. I didn't found information about how to use syslinux(isolinux,etc.) in uefi. I wanna know that are there some differences of the isolinux configuration

Hi, i think i found a suspect in lzo/prepcore.c and it would indeed be a wrong range of checksumming (speculative congratulations to Ady). Looking at http://repo.or.cz/syslinux.git/blob/0d82b71304d596d80f3c4520f9dcf90048ca50b7:/lzo/prepcore.c it seems that this change in line 374 could yield correct checksums: unsigned int ptr; - for (ptr = 64; ptr < offset; ptr += 4) +

Hi, I am trying to build a custom installer for a popular linux distro on MacOS. Here is how: makehybrid \ -o isos/muaaa.iso temp/ \ -eltorito-boot temp/isolinux/isolinux.bin \ -no-emul-boot \ -iso -joliet -boot-load-size 4 \ -default-volume-name "Custom Installer" \ -eltorito-platform temp/isolinux/boot.cat This happens when I boot up the new image:

Hi, The reason I ask, is that we (the Debian GNU/Linux CD creation team) are currently contamplating switching to using some form of multi-boot to allow our users the oppotunity to select which kernel to install Debian with.

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

> EFI from CD/DVD/BD has a soft size limit of 32 MB for its > System Partition. > That's due to the format of El Torito Boot Catalog which > counts the 512-bytes blocks by a 16-bit unsigned integer. @Thomas, If you would be so kind, would you please remind me (us)... Is this "32MiB" a limitation related to the UEFI specs in any way? Or is it relevant for BIOS

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