similar to: isolinux pathnames

SYSLINUX is certainly useful. I currently start Debian from their standard boot floppy, which uses SYSLINUX. I found it very easy to edit syslinux.cfg for ide-scsi setup. Surely the future lies with bootable CDs and floppy images specifically designed for them. Maybe there should be a combined SYSLINUX / ISOLINUX package which allows you to specify Floppy Emulation or not. But if you invent a

Due to limitations of equipment, I have need of using the isolinux boot loader with .iso files generated by roxio. After trying (and of course failing) with an off the shelf version of isolinux, I grabbed the source for isolinux (syslinux 2.11 package) and started looking. It took a few hours to orient myself, but I ended up doing the modification below to isolinux.asm. I then had to write

> Hi, > > Ady wrote: > > I wonder if isolinux.bin should be limited to max. 16 sectors (of > > 2KiB each), as that's the default limit in mkisofs "-G > > <generic_boot_image>" option. > > Option -G is not related to the El Torito boot image isolinux.bin. > It inserts its data into the System Area of the ISO, which is > indeed limited

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 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 Mr Anvin, after downloading the Freedos bootable cd, which now uses your projects (ISOLINUX & MEMDISK) instead of Bart Lagerweij's DISKEMU (www.nu2.nu), I contacted the creator of the freedos cdrom. I was interested in how he did make that cd bootable. Now I understand it a bit. As I'm a MS Windows user, I had to figure some things out. However, upon booting I get a beautiful

Hello List, I have used isolinux for years without problems. Recently I decided to upgrade from 3.09 to 3.11. Every CD I create can be read on my Vectra (Pentium 3) and all other Pentium 3 boxes, but all my Pentium 4 boxes will not boot (they ignore the CD and boot from hard disk). The bochs VM will boot the CDs fine just like the Pentium 3 machines. I have tried 3.09 (which worked

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

Hi, Ady wrote: > This is a quote from Wonko/Jaclaz, who has also been investigation this > issue and deserves credit for it: > Ok, not that I understand the code, but what *somehow* happens is that > the "embedded" checksum in Isolinux.bin (starting from 4.00) is the > checksum of the WHOLE file (i.e. starting from offset 0 instead of 64) > at a time when: > 1)

Hello, i'm just curious, why the -boot-load-size 4 for mkisofs with isolinux.bin is needed. I searched the list archive and found nothing and found nothing anywhere else. Since the isolinux.bin is much bigger than 4 * 512 byte, I'd suspect, it wont get completely loaded. With -boot-load-size 4, mkisofs reports: Size of boot image is 4 sectors -> No emulation Without it, mkisofs

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 have a non-bug related question, which has been giving me fits for a while. Can ISOLINUX.CFG be updated on a multi-session disc ? It seems not, as I make m/s CDs all the time and can change every other file on the disc, exc ISOLINUX.CFG. My best guess at this point is that ISOLINUX.BIN can't access secondary sessions on the disc, pos related to the boot-info-table patch. Whether

Hi folks, I'm new to the list so forgive me if this topic has already been explained in great detail. I'm trying to understand how an image gets booted from an EL-TORITO compabatible CD-ROM, so I have some general questions: 1) Is there a limit of how big the boot image can be? In the Initial/Default entry I see a "Sector Count" which is only a word long in length. Does

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.

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

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

Thomas Schmitt via Syslinux said on Sat, Oct 24, 2015 at 12:56:49AM +0200: >Needed is a EFI FAT image > 32 MiB and a new xorriso (available >on demand). My test script on RHEL 7.1 creates that even if I could make it smaller as the kernel + initrd fits in less than 32 MB. So let me make that try first ! o I changed myline in the script to dd a 30 MB image file, burt the ISO with it, and

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

Hi all, I am using sys/isolinux for a mini-distro I am developing (movix.sf.net) and I have a few questions based on the feedback I got from users. As it is well known, there are some BIOS on which isolinux does not work, so I had to create a boot floppy image for those unfortunate users that have that kind of BIOS. The floppy boots, looks for the CD and, if succesful, mounts the CD initrd.gz