similar to: [PATCH] chain.c32: comments fix and usage output corrected

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:

$ 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

[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

Allow the grub loader to (optionally) support using a GRUB menu file. For example chain fs grub=stage2,grub.conf will load GRUB's stage2 and pass the (absolute) path to the file "grub.conf" in the Syslinux filesystem to GRUB's stage2. The path is passed to stage2 in GRUB's device/partition syntax (eg, "(hd0,1)/foo"). Note that we don't check whether the

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

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

Syslinux 3.85 is a bug fix and minor new feature release. The biggest change is undoubtedly that gPXELINUX is now considered feature complete, and should be able to be a drop-in for PXELINUX for all uses. Special thanks to Intel Corporation, my current employer, for their support for my Syslinux work. Changes in 3.85: * gPXELINUX: updated to gPXE 1.0.0. gPXELINUX can now do NBP

Hello everyone, I have just released SYSLINUX 3.70, which is the first version which includes gPXE for support of non-TFTP network scripts, as well as a large number of other enhancments. gPXE support is still somewhat experimental - in particular it still doesn't support chaining other NBPs. Very special thanks to: - rPath, Inc, my employer, for the uncountable hours I've spent

Hi, I'm trying to boot Debian-Installer image from extlinux with chain.c32; i.e.: - I'm doing this from a loopback device (loop0) which later will be dumped to an USB stick. - GPT disklabel. - Partition 15 (loop0p15) contains extlinux info, and partition 12 contains Debian multi-arch installer image *dumped*[1], and its corresponding menu entry for extlinux is something like: LABEL

I got the following message with chain.c32 ===================== Loader file too largeBoot: ===================== Like you can see, there should be a new line after 'large'. I guess that some other error messages, will result in the same behavior. Gert Hulselmans $ diff -u com32/modules/chain.c.old com32/modules/chain.c.new --- com32/modules/chain.c.old 2009-08-17

From: Kim Mik <kimmik999999 at yahoo.co.uk> To: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com> Sent: Tuesday, 29 September, 2009 22:21:39 Subject: Re: [syslinux] Chainc.32 missing some \n one error messages > From: Kim Mik <kimmik999999 at yahoo.co.uk> > To: syslinux at zytor.com > Sent: Monday, 17 August, 2009 1:30:04 > Subject: [syslinux] Chainc.32

Is there a practical reason that the NTLDR clause of the CHAIN module isn't operable under ISOLINUX ? The reason for my question is that I like the SYSLINUX suite over the alternatives, that is GRUB and BCDW, however these pkgs all can chainload (just about anything) from an ISO. That is, they can handle .BSS files and the various NT/XP boot files, like SETUPLDR.BIN, etc. I make/update

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,

>From 1db8a8919482dbed4cc15509d8078b2f16a289bb Mon Sep 17 00:00:00 2001 From: Gert Hulselmans <gerth at zytor.com> Date: Wed, 30 Jun 2010 14:10:23 +0200 Subject: [PATCH] chain.c32: add grubcfg= for passing an alternative config filename to GRUB Legacy GRUB Legacy reserves 89 bytes for storing the filename of the configfile from memory address 0x8217 to 0x826f. We allow overwriting the

Hello I'm working on my RIS server; I got a problem when I use pxelinux.0 to load setupldr.exe from windows XP 32bits (both home and corporate) Here is how I configure a working server, then how to modify it to reproduce the bug: ========================= I suppose you got -a dhcp server configured to load pxelinux.0 to client computer. -a working tftp server (mine is tftpd-hpa, with a rule

Have a look at the 911cd forums. I wrote the initial thread on RAM booting WinPE. To answer to question... memdisk won't work with Windows. Windows uses 32bit access (direct HW access) and memdisk relies on the BIOS. Any programs that don't use the BIOS disk interfaces will not work. The other problem is the allocation of memory. Windows doesn't respect the memdisk allocation.

Hello all I have installed "syslinux" as follows: 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, ENTER for none)?

I and some other people have problems with running the freedos image included in Ultimate Boot CD (UBCD), when using memdisk for floppy emulation. Memdisk starts booting the image and freedos shows the following menu: 0 Boot Clean 1 Boot UMBPCI (silent) 2 Boot UMBPCI (optimal) 3 Boot UMBPCI (semi-defensive) 4 Boot EMM386 (optimal) 5 Boot EMM386 (semi-defensive) 6 Boot no UMB (defensive) 7 Boot

So I've been playing with this for hours and still unable to get everything working properly. In short I'm trying to boot an ISO image created by BartPE over pxelinux. When I attempt to do this it goes directly to a blank screen that just has a blinking cursor. Here's what my setup looks like: pebuilder.iso - the ISO file created from BartPE using WinXP SP2 CD as source but with