similar to: SYSLINUX 1.75-pre2 released: ISOLINUX workarounds

I have released SYSLINUX 1.75 -- this one is identical to 1.75-pre9 except the version number. I have gotten enough testing done that I feel it's time to release... Changes in 1.75: * ALL: NASM 0.98.32 or later is now required to build SYSLINUX from sources. * SYSLINUX: put back in the workaround for the BIOS floppy table. This seems to be a

http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ Here is the list of changes in 1.75 so far: Changes in 1.75: * ALL: NASM 0.98.32 or later is now required to build SYSLINUX from sources. * SYSLINUX: put back in the workaround for the BIOS floppy table. This seems to be a requirement for "extended" floppy formats to work

I have released SYSLINUX 2.10-pre2. I *really* would like testing reports for this one, especially ISOLINUX, since I've included Knut Petersen's fix for Award BIOSes... Changes in 2.10: * MEMDISK: Handle images compressed with zip as well as with gzip. Some Windows-based image tools apparently generate these kinds of images by default. Patch by Patrick

> -----Original Message----- > From: Michael K Ter Louw [mailto:mterlouw at gmx.net] > Sent: woensdag 4 september 2002 1:24 > To: Lagerweij B ; syslinux at zytor.com > Subject: Re: [syslinux] isolinux.asm - improving spec_query_failed > routine... > > > > Hi Peter, Bart, and everyone else, > > I also write software that boots from the CD drive, so 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

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

On 12/13/2013 02:20 PM, Gene Cumm wrote: > On Dec 13, 2013 4:55 PM, "H. Peter Anvin" <hpa at zytor.com > <mailto:hpa at zytor.com>> wrote: >> >> On 12/12/2013 04:21 AM, Gene Cumm wrote: >> > On Wed, Dec 11, 2013 at 9:22 PM, ?? <kun.he at cs2c.com.cn > <mailto:kun.he at cs2c.com.cn>> wrote: >> >> When we meet UEFI or EFI

Hi all, I just pushed out SYSLINUX 3.72-pre2. It has a rather cool new feature: a hack to ISOLINUX to create a single image which can be booted either from CD-ROM or from what BIOS considers a hard disk medium (USB keys, etc.) -hpa

Hi, Ady wrote: > So, someone could assert the following reasoning steps: > 1_ We can workaround the Sector Count limitation of 32MiB for > no-emulation methods. If the EFI firmware programmers obey version 2.4, yes. > 2_ The ESP is considered a no-emulation method. >From the view of UEFI 2.4 it is a partition. Partitions may be marked by MBR partition table or by GPT on hard

Hi, i did not succeed to get my test computer (Asus A7V8X-X of 2004) to boot from an isohybrid image. I tried http://www.tux.org/pub/people/kent-robotti/looplinux/rip/RIPLinux-7.0-non-X.iso which is obviously isohybrid enabled. The system has a "Promise Ultra 133 TX2" IDE controller which supercedes the mainboard BIOS. To make the system react on the USB stick i set boot option

Hi Peter, I noticed in your isolinux.asm code, when loading spec packet fails you are trying to wing it, in other word, loop the drive numbers from 0xff through 0x80 until the booted drive number is found... I write software that also "wings it". Recently I had to create some "wird" workarounds because of bad bios in some Dell and Compaq PC's. Below is my function for

I have just released SYSLINUX 2.06-pre2. This, I hope, fixes the ISOLINUX directory length bug, a.k.a. the "SRPMS bug." ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ I haven't done anything to the lss tools yet; I was hoping to actually get some sleep tonight. Please, if you have had problems with either SYSLINUX or ISOLINUX lately, please test these out...

[cross-posted to nntp://comp.os.linux.setup, sorry] Dear Everyone, I'm writing this message merely to publish this information somewhere visible, so that others can find it when debugging a linux-based bootable CD compilation setup... For many months now, I've been using cdrtools 2.0 with isolinux 2.04 to create bootable Linux CD's. I know there are newer versions of both

On 10/11/2014 10:46, Thomas Schmitt wrote: > 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 >

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

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

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

This release is identical to 1.67-pre1. Unfortunately the people who reported problems with 1.66 never got back to me to indicate if it solved their problem or not, but since it fixes a real bug, regardless, I decided to release it as 1.67. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/ -hpa 1.67 is a trivial bug fix release affecting a fairly small number of systems. 1.66 is an

Changes in 3.61: * EXTLINUX: fix crash when accessing an empty file. * elf.c32: If a PHDR segment is present, load it. * Fix SHA-1 and MD5 passwords. * ISOLINUX: fix booting when mastered without mkisofs -boot-info-table (broken since 3.50, sigh...) * Handle BIOSes which emit multiple contiguous valid memory regions in the e820 map. Begin3 Title: syslinux Version: 3.61 Entered-date: