similar to: Syslinux Bootsector

Hello Peter, The attached patch contains three small (although 2 of them are fundamental :) fixes for pxelinux 1. Alignment error when more than one initramfs are loaded using initrd - the alignment of the last disk is discarded in calculations but is ALWAYS present when the loading procedure is called. As a result - the second image (cpio) is not recognized. 2. On some platforms

Hi all! I'm trying to install a suse-linux via network on a machine with a asus p4te-mainboard (BIOS-rev 1005). There is a known problem with some screwed up bios call that locks up the fdc which got "worked around" in recent kernel versions. I'm depending on the floppy because there is a file on it which is read during installation.

HPA, is it possible to add a parameter/argument to syslinux.com/syslinux.exe to specify a file? currently it's something like SYSLINUX A: I'd like the following also to be possible: SYSLINUX A: A:\SYSLINUX.BIN It still copies LDLINUX.BIN to A:, but writes the generated bootsector intended for drive A: to a 512byte user-specified file Perhaps to allow both at the same time even SYSLINUX

Mr Anvin, is there a specific loading address used with the Syslinux bootsector (to load ldlinux.sys)? like msdos 0x70, freedos 0x60 we're trying to have a SYS program that can create bootsector for other OS's than FreeDOS only. not much luck though :( this way I'm trying to avoid the use of syslinux.exe/com (need the diskspace that it would save by not including this program) I

HPA, a longterm reminder. See below. Can you also make a LABEL ignore other labels if no KERNEL statement is found in between? That way you could define multiple aliasses for an entry. label foo label bar label memtest kernel memtestp foo ignores 'label bar' , 'label memtest' and executes 'kernel memtest' bar ignores 'label memtest' and executes 'kernel

I have a Centos 3.x server install that has been working for months now but is now going the error "resource temparary unavailable" any idea what normally causes this error ? Thanks Denis

I have occasional problems booting kernel boot floppies made with syslinux-2.04/2.05. The symptom is that syslinux loads an initial part of the kernel image and then halts with Boot failed: please change disks and press a key to continue. Observations: 1. It's not a media problem. I've switched floppies and reformatted them, but the failure persists. 2. It's not a BIOS problem.

HPA, I believe that support to boot windows CD bootsectors was broken in 3.05. I have tested 2.13, 3.00, 3.02, 3.05, 3.06, 3.08, 3.11, and 3.20pre6. All versions >= 3.05 are broken. All versions <= 3.02 work fine with the same config. The error message I get is: ================================================================ IOSLINUX 3.20 3.20-pre6 Copyright (C) 1994-2005 H. Peter Anvin

Hello Recently I've been happily experimenting with syslinux, replacing grub and my old bootmanager. All works beautifully, but I have one question - in case of .bss bootsectors - what exactly and under what circumstances is patched in ? With syslinux used as main bootmanager - bootsectors from xp64, xp32 and [pre-syslinux] msdos 7.1 (98se) work perfectly fine when chainloaded natively as

Hi, I've coded loading NT cdrom bootsector into isolinux 1.68 myself (http://www.nu2.nu/bootcd/#multimemdisk) and I now see you have included it in isolinux 1.73 and higher. Great!!! I tried it using isolinux 1.74 and 1.75pre2, but I cannot get it to work. It says: -- Loading Invalid or corrupt kernel image. -- I use the file extension ".bin" as I see in the isolinux.asm source,

ÎÒ¹«Ë¾ÏµÍâóÆóÒµ£¬ÓÐÒâÀ©´ó¾­Óª¹æÄ££¬ÏëÔÚ¹óµØÑ°ÕÒºÏ×÷»ï°é£¬Ìؽ«´Ë¼ÛÄ¿±íÌṩ¸øÄú·½²Î¿¼£¬ÎÒ¹«Ë¾±£Ö¤²úƷΪȫÐÂÔ­×°Èý¸öÔ°ü»»Ò»Äê°üÐÞÈý°ü£¬±£Ö¤ÐÅÓþ£¬»õµ½¸¶¿î £¬²»ÏêÊÂÒËÄú¿ÉÀ´ÈËÀ´µç´¹Ñ¯£¡ÈçÓдòÈÅ£¬Çë¶à°üº­£¡£¡£¡ ÁªÏµÈË£º¹ù½õºê ÁªÏµµç»°£º(0)13859713911 ¹«Ë¾£ºÌ¨Íą̊±±ºè´óÆóÒµÉÌó¹«Ë¾ Ò»¡¢µçÄÔÅä¼þ (ÈËÃñ±Ò) 1.cpu InteI p4 2G/1.8G/1.7G(Socket478) £¤ 500/420/390Ôª InteI p4 1.6G/1.5G/1.4G(Socket478) £¤

On Tue, Jan 21, 2014 at 2:41 PM, mike setzer <qualityana at sbcglobal.net> wrote: > hello Gene, > > good to get your message > > I have not seen a link to reply to a particular thread, > so I am replying to you right now > hopefully the thread can be made to look right, also I double posted since my connection was lost > right during the first posting. Sorry, I

(I *really* need to learn this list is configured for replying to sender instead of the list itself..) Dinesh P. schreef: > Hi there, > I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... > what is the problem can anybody tell me.. > please read Syslinux and Memdisk

Hello, We are experiencing a strange behaviour on an embedded system (i386 PC board). The structure of our disk is the following one : - A 2GB fat16 partition with DOS and syslinux - A 100GB Ext4 partition with Extlinux an several linux images to boot on ram - A swap partition The system boot on syslinux to choose among Dos and Linux boot using chain. When Linux is chosen, syslinux chains to

On 07/26/2013 01:36 PM, Raphael S Carvalho wrote: > > Bootsector is installed into the 0-512 range, whereas 2 copies of ADV > into (65536 - 2 * ADV_SIZE). > Then basically ldlinux.sys must fit between the bootsector and two > copies of ADV whose size may vary. > > The range 0-64k is laid out something like this, right?! > [0](bootsector)[512](ldlinux.sys)[65536 - 2 *

On 07/26/2013 08:10 AM, Matt Fleming wrote: > On Wed, 24 Jul, at 08:05:16AM, Raphael S.Carvalho wrote: >> Check if ldlinux.sys is larger than 64k at build time. >> >> Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> >> --- >> core/Makefile | 5 +++-- >> core/ldlinux_limit.pl | 31 +++++++++++++++++++++++++++++++ >> 2

Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. Thus, the size of ldlinux.sys (limit) can be at most: 65536 - 2 * ADV_SIZE - 512. Certain file systems (such as BTRFS and UFS2) will rely on ldlinux.sys being installed on the 0-64k range, thus it can't exceed the limit,

On Tue, Oct 20, 2015 at 1:08 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> Hello, >> >> We are experiencing a strange behaviour on an embedded system (i386 PC board). >> >> The structure of our disk is the following one : >> - A 2GB fat16 partition with DOS and syslinux >> - A 100GB Ext4 partition with Extlinux an several linux images

Apparently there's a semi-new feature in SYSLINUX that will allow you to, from what I've heard, boot DOS. I've got a portable USB flash drive and I've managed to make it multi-boot with disk images, but that takes quite a bit of memory. I think bootsector booting is the best way to go, but I have no idea how to do it. Tell me if I've got this right: So, I want to get a flash

Okay, spending the time to dot t's and cross i's (or something like that), I think I have something now that can be called 3.00-worthy, so let's call it a release candidate. Changes over the earlier 3.00 prereleases: - -m and -a options now supported by the DOS installer. - PXELINUX now allows IP addresses, FQDNs, and truncated hostnames when specifying an alternate TFTP server