similar to: [PATCH] chain.c32: add support for booting the Recovery Console of Windows NT/2K/XP

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

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,

Comments fix and usage output corrected for chain.c32 - Gert Hulselmans Signed-off-by: Gert Hulselmans <kimmik999999 at yahoo.co.uk> $ diff -u syslinux-3.84/com32/modules/chain.c.old syslinux-3.84/com32/modules/chain.c --- syslinux-3.84/com32/modules/chain.c.old 2009-12-29 01:46:34.058793767 +0100 +++ syslinux-3.84/com32/modules/chain.c 2009-12-29 01:53:41.150794351 +0100 @@ -49,7

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

$ 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

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

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

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

Look into the original XP cd and see where NTLDR is located, then place it on your cd in the same directory and it 'should' work. I have created some 2000 XP boot cd's with integrated recent service pack's and they still boot. But I do that with cdrecord+original boot sector, not with any isolinux stuff... But I hope this help! -----Original Message----- From: G. Murali

Correct the "seg=" value(s) corresponding to the "reactos=" option for chain.c32. The correct segment parameter should be "seg=0x0F80", instead of the incorrect / failing ones "seg=0:0x8000:0x8100". References: https://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/notes.txt?revision=73859&view=markup&pathrev=73859#l24

On Mon, Feb 20, 2017 at 2:17 PM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > Correct the "seg=" value(s) corresponding to the "reactos=" option > for chain.c32. > > The correct segment parameter should be "seg=0x0F80", > instead of the incorrect / failing ones "seg=0:0x8000:0x8100". > > References: >

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

(snip) > > It's a bit more complex. At the time of writing, the data was perfect. > > https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/freeldr/include/arch/pc/x86common.h;hb=28e58e6d01892c1f2f0e1d323745e6463cb9e6c9 > dated 2011-06-14 > >

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.

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

Before I reply on-topic, I'd like to request from people participating in this public mailing list to _avoid_ top-posting whenever possible, and when replying, please quote what's relevant only. Now, back to the topic. > " > Booting... > Error loading operating system_ > " > at the bottom of screen and hangs. I can only reboot using ctrl-alt-del. AFAIR,