similar to: memdisk operations FAIL to boot with Syslinux-4.02

Hello, Is "Dos installer from Win98" REMOVED from Syslinux-5.00/syslinux-5.01-pre1? Prof S W Damle

The Windows recovery console doesn't work with chain.c32 3.85 or 3.86-pre1. COM32 chain.c32 APPEND cmldr=/cmldr Initially reported by cdob at: http://www.boot-land.net/forums/index.php?showtopic=10487#entry94001 It did work fine with the: "chain.c32: Handle nonlinear logical partitions" patch. The following patch broke the recovery console hack: chain.c32: add option to set hidden

[1} Gert Hulselmans wrote: > > ...Thanks. > > I still think chain.c32 should be able to do a reverse partition > lookup, to determine from which partition it was booted. This would be > useful to boot ntldr, setupldr.bin, bootmgr, grldr, ... when you want > to boot it from the same partition as from which SYSLINUX is booted, > without specifying the partition explicitly

This patch introduces extra functionality to chain.c, mainly with reference to BPB adjustments, but not only that. It expects 3 small patches I sent earlier (they are included for easy reference, patches 1-3/4). The changes introduced are: 1) file and boot sector use separate options to control load address and jump address (if applicable). Options are as described below: *

$ git log -p commit d8c5e94803fa01f0d52475a50b69681ad3135700 Author: Gert Hulselmans <kimmik999999 at yahoo.co.uk> Date: Sat Jan 9 15:30:49 2010 +0100 chain.c32: Add grldr= command for Grub4dos grldr of Grub4dos wants the partition number in DH: 0xff: whole drive 0-3: primary partitions 4-*: logical partitions diff --git a/com32/modules/chain.c

I have decided to promote SYSLINUX 3.31-pre4 to release candidate status. If it tests out OK, it will become 3.31 some time next week, probably. -hpa

The attached config works, but gives 2 error messages that get covered up by the GUI screen so fast I cannot read them. I think they are probably about having 'LABEL' with nothing after it. I was trying to follow the example in menu.doc but somehow I'm doing it wrong. Please consider helping me figure out how to get the same resulting GUI menu without any error messages. I am using

I have just released SYSLINUX 3.31. It is functionally identical to SYSLINUX 3.31-pre4. Changes in 3.31: * The simple menu system (menu.c32 and vesamenu.c32) now support loading more than one configuration file at a time, using MENU INCLUDE or by specifying multiple filenames. * The MENU COLOR statement can now control the shadowing mode. Changes in

Hi all, I would really appreciate feedback on the graphical menu system and its infrastructure. It's not really clear to me that it's what people want; it seems to me that it makes more sense than gfxboot, for example (C rather than pseudo-Forth), but I can understand people would disagree. Anyway, the more feedback I get the easier it will be to pick a direction and a priority for

Hello Sir, on Friday, August 20, 2010 11:32 AM Gert Hulselmans wrote > loading the boot file ... > Boting ... > "-" cursor keeps on blincking Are you quite sure that booting the Windows Recovery Console under syslinux can work and that "cursor keeps blinking" is only a problem of your special menu? YES I am 100% sure that booting the Windows Recovery Console

Hello Sir, Copid cmdcons and cmldr to O:(my usb drive) as follows (1) Microsoft(R) Windows 98 (C)Copyright Microsoft Corp 1981-1999. C:\WINDOWS>format o: /s C:\WINDOWS>format o: /s WARNING, ALL DATA ON DISK DRIVE O: WILL BE LOST! Proceed with Format (Y/N)?y Checking existing disk format. Formatting 967.98M Format complete. System transferred Volume label (11 characters,

The following patch for chain.c32 adds support to boot the Recovery Console of Windows NT/2K/XP. Normally when you want to boot the recovery console, you need to patch "cmdcons\0" into the bootsectorof the partition (8 bytes starting at 0x3 (4th byte)). We can do this patching in memory: strcpy((char *) 0x7c03, "cmdcons"); To boot the recovery console with chain.c32:

Hello, when I try to boot from my computer extlinux needs about one minute before the boot menu is shown. Here's my system configuration -Two IDE drives on one controller -Second hdd is boot hdd -I'm using Arch Linux (i686) Is there an official bug tracker which I can use? I only found the debian bug tracker and I can't find any information about bugs on the homepage. Here is my

On Thu, Jul 7, 2016 at 8:00 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > >> > We would need at least: > > A_ the partitions and directory structure in which the following items > are _located_ : /dev/sda1: # tree . . ??? extlinux ? ??? ldlinux.c32 ? ??? ldlinux.sys ? ??? libcom32.c32 ? ??? libmenu.c32 ? ??? libutil.c32 ? ??? menu.c32 ? ???

isoconfig.sys file below - Only change from past is adding stuff after the bz28.7 kernel. DEFAULT vesamenu.c32 Prompt 0 menu color screen 37;40 #80ffffff #00000000 menu color border 30;44 #40000000 #00000000 menu color title 1;33;44 #c0fdd017 #00000000 menu color unsel 37;44 #90ffffff #00000000 menu color hotkey 1;37;44 #ffffffff #00000000 menu color sel 7;37;40

I have updated syslinux in Parted Magic's test version to the 5.10 release. With 4.06 I booted plop like this: LINUX /boot/plpbt/plpbt.bin Now it says /boot/plpbt/plpbt.bin... ok Booting kernel failed: Invalid argument Other "extras" like IPXE, HDT, memtest86+, chntpw, Super Grub Disk, etc... all work with 5.10. Revert to 4.06 and plop works again. Is this a problem with syslinux

Hi, I'm trying to setup a flash drive with Syslinux 4.0.2, ifplop.c32, and plpbt.bin (5.0.10) as shown in the thread here: http://forum.plop.at/index.php/topic,165.0.html Unfortunately, the system reboots as soon as I load plpbt.bin from Syslinux. I don't think it's a problem with plpbt.bin because it works if I boot Grub4DOS and load it. : ( It will also work if I boot

I have syslinux 5.10 on a 32bit gentoo system. It boots fine. Now I installed another linux system in other partitions of the same drive (a 64 bit system), updated syslinux.cfg, setup the new system as default, and the new entry appears in the menu. Problem is: it doesn't boot. On timeout, it starts counting down again, and that's it. No error message whatsoever. Selecting the old system

We are running Solaris 10 11/06 on a Sun V240 with 2 CPUS and 8 GB of memory. This V240 is attached to a 3510 FC that has 12 x 300 GB disks. The 3510 is configured as HW RAID 5 with 10 disks and 2 spares and it''s exported to the V240 as a single LUN. We create iso images of our product in the following way (high-level): # mkfile 3g /isoimages/myiso # lofiadm -a /isoimages/myiso

chain.c32 of SYSLINUX 3.82 does set the boot drive passed to the DL register to 0x80 and not to the boot drive (CD-drive). This can be a problem if you want to chainload grldr (grub4dos bootloader) from a CD and if you want to let grldr search for its menu.lst file on the CD. For more info: http://www.boot-land.net/forums/index.php?showtopic=8457 This 1 line patch fixes the issue (Thanks to