similar to: isolinux from floppy

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

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

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

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

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

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

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

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,

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 Peter, I tried isolinux-1.73, its great! Because of some problems making a universal boot-CD I tried to use bocs-1.4 (a PC emulator, very good). This emulator is able to boot a win98-installation-CD but fails on self made isolinux-1.73-CDs. I can coot the isolinux-CD by a real PC without problems. Also a SuSE-Linux CD or an image of it which claims to use solinux-1.62 is bootable in bochs, but

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

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