similar to: SYSLINUX 1.75-pre3 released

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

Please try this version out if you are using floppies to boot, and *especially* if you have observed either of the following two problems: a) "booting with syslinux without -s takes forever" b) "booting with syslinux without -s doesn't work, -s works" Changes in 1.75: * ALL: NASM 0.98.32 or later is now required to build NASM from sources. *

This version adds some workarounds to ISOLINUX for a few broken El Torito BIOSes that have been reported to me. Since I don't have access to these systems myself I don't know if it will help or not (or even if I broke some other workarounds by mistake...) Please try it out. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Good day to all. Since we've adopted Gary Tong's and Bart Lagerweij's ElTorito.sys (now modified by H. Peter Anvin and tiny changes from myself), I'd appreciate if anyone with more El Torito experience might criticize my comments below and advise as to how they might be wrong. Some of it is off-topic GRUB4DOS detail; safe to ignore. A bit of history: FDUBCD ("FreeDOS

I just found a rather embarrassing bug in PXELINUX -- and what's worse -- I wrote an email about it and killed it off accidentally :-/ It appears PXELINUX doesn't free its internal socket buffers (it has 32 of them) when it gets an error reply from the server, including "file not found." This means it will eventually run out of sockets and "go deaf." This

On 7/12/2013 14:22, Michael Szerencsits wrote: > Am 12. Juli 2013 15:06:54 schrieb Matt Fleming <matt at console-pimps.org>: >> Which installer? I would hazard a guess that the installer is also bios >> specific and is going to need to be tailored for EFI boot anyway. > > It's a little be complex. > It's a DVD based installer where I try to change this to be

ldlinux.sys uses a working directory. The documentation seems to improve if that fact is made explicit. So the working directory is added to the documentation (with a bit of vagueness and possibly not entirely correct, to keep it readable). While we're at it, also convert the name ldlinus.sys to lowercase everywhere, even if it's clear its name is used in a DOS context. Signed-off-by:

Hi folks, Syslinux 5.00 is out in time for the holidays. This release includes a lot of changes from 4.06. I've included the NEWS entries below, which highlight the major changes. Lots of assembly code has been rewritten in C, which makes further development much easier (and also really helped for the 'firmware' abstraction that appears in Syslinux-6.00-pre1). So be on the lookout

On Thu, 6 Nov 2014, Geert Stappers wrote: > > The MirBSD bootloader actually took advantage of COMBOOT to > > provide access to SYSLINUX storage and other things. It was > > integrating nicely. > > Please tell more about that COMBOOT use case. Okay. The BSD kernels are normally loaded by their own BSD-specific bootloaders (although some other bootloaders can, with

H. Peter, three simple commits here[1] (for_hpa branch). Gert, sample binaries are here[2]. --- mdiskchk: Add --no-sequential mode It might be useful to suppress MDISKCHK.COM's classic behaviour of probing all BIOS drive numbers in search of MEMDISKs. Some BIOSes might not enjoy being probed. --- memdisk: Correct El Torito termination response Two

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

> Which one, just out of curiosity? They are Sony notbooks > What is the "preload install script"? Is the DVD El-Torito-bootable and > it runs something which reports that the system must be EFI _before_ it > boots any OS? > If you are using PXE, then that's along the same lines as BIOS. If they > want EFI, that's a stronger requirement than CD/DVD. If

Changes in 3.11: * MEMDISK: Fix bug by which accessing the real floppy disk as B: in MS-DOS was broken. * Simple menu system: allow tweaking of the screen layout. * Simple menu system: better command-line editing, correctly handle command lines above 256 characters. * PXELINUX: revert memory allocation change that caused problems

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

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Add get current working directory call to most Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- Adds an API call to obtain the current working directory. EXTLINUX will not return the correct value yet however SYSLINUX, ISOLINUX, and PXELINUX will return the correct value. For the moment, EXTLINUX will ONLY return

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

Hi all, I have released SYSLINUX 1.75-pre4, which is a release candidate for 1.75. Please pretty please test it out: http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ I'm working on some new stuff, basically COMBOOT+an API+32-bit support, which should make doing things like menus and other UI features very easy as separate modules. When that gets finished I'll probably

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