similar to: ISOLINUX -- how many BIOSs don't support this?

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

isolinux: Extremely broken BIOS detected Yoper 2.1 --------- ISOLINUX 2.11 2004-08-16 isolinux: Loading spec packet failed, trying to wing it... isolinux: Extremely broken BIOS detected, last ditch attempt with drive = 9F isolinux: Disk error 01, AX = 4209, drive 9F Boot failed: press a key to retry... Helix 1.5 --------- ISOLINUX 2.04 (Debian, 2003-06-06) isolinux: Loading spec packet failed,

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

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'm creating a Linux "live" CD that boots just fine on our newer machines... but isolinux is not working on some of our older ones. The older boxes work fine with boot floppy image systems like Knoppix... so I'm wondering if there's something more I can do to make them happier with isolinux? By "older", I mean a generic P-120 motherboard with an Award v4.50PG

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)

I am experiencing a problem booting a machine with ISOLINUX on a machine that has no hard drive (CD-ROM only). I've tried two different machines, a Dell Poweredge 2600 and a Dell Poweredge 1300, both exhibit identical symptoms. When I boot the exact same cd on a system with a hard drive, the boot is just fine. I had been using ISOLINUX 1.66, but I just upgraded to 2.02 and I am having the

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

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 (

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

H. Peter, I came across the first system where isolinux failed to load: ======================================================= Isolinux 1.63 2001-8-6 Copyright ... isolinux: Starting up, DL = F0 isolinux: Loaded spec packet OK, drive = F0 isolinux: Sector size appears to be 0800 isolinux: Loading main image from LBA, 0003F25D isolinux: Sectors to load = 0004

Improving chain.c32 help message Impact: Error message is more detailed In case of syntax error, the message is far more detailed and provides the same content as the documentation integrated in the source code. You can get this patch from Erwan's git repo: http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=3fc3126d0c7df5701680e043c34f200166f24564 Add 'isolinux=' option to

> 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

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

Hallo, I'm just trying to boot a Clonezilla *.iso (live-20100521-lucid) via PXE; Label clonezilla kernel memdisk append iso raw initrd iso/clonezilla.iso The first step is ok - I see the boot menu of the *.iso. When I choose "Clonezilla live" the system fails with Isolinux: Disk error 02, AX = 4224, drive E0 when I choose "freedos" it fails with

forgive me.. i have no idea what im asking or if its possible... i have 2 partitions as follows and am using the std windows xp bootloader to boot xp - ntfs (windows xp) - fat16 stupid question is... can i use syslinux, isolinux, memdisk or some combo there of to place a bootable cdrom iso image on the fat16 partition and then have a boot menu with something to the effect of : 1) winxp as

> Hi, > > Ady wrote: > > Is this "32MiB" a limitation related to the UEFI specs in any way? Or > > is it relevant for BIOS (non-EFI) too? > > It comes from El Torito specs which are referred to by UEFI 2.4 > specs. In EL Torito 1.0, Figures 3 and 5, "Sector Count" is a 2-byte > "Word". So it can count up to 65535. > Sector count

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