similar to: specifying 'root' for mboot.c32/syslinux

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

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

Hello syslinux mailing list users, I've initially filed a bug about my problem [1], but people from irc channel suggested to ask for help here. I have a PXE server based on syslinux 4.05 that distributes ReactOS to client machines over network. It has a pretty simple pxelinux.cfg/default, with the following contents (that were suggested by ReactOS wiki [2]): DEFAULT chain.c32 APPEND

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

Two commits available at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/chain_freeldr --- Author: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sun May 1 13:49:43 2011 -0400 chain: Support loading ReactOS' FreeLdr Use something like: LABEL freeldr COM32 chain.c32 APPEND freeldr=freeldr.sys Signed-off-by: Shao

https://bugzilla.samba.org/show_bug.cgi?id=9749 Summary: hardlinkes files are copies instat of make a link Product: rsync Version: 3.0.9 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: dieter.ferdinand at

> On Wed, Jun 15, 2016 at 1:02 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > > > >> On Tue, Jun 14, 2016 at 12:33 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> > > >> >> > kernel.c:new_linux_kernel() to load_linux.c:bios_boot_linux() because > >> >> > there is no convenient way in new_linux_kernel() to

Changes in 4.05: * HDT updated, and now supports uploading data to a TFTP server. * ISOLINUX: remove the .img file support; it has been broken on virtually all systems since the beginning, and has been totally broken since 4.00 at least. Use MEMDISK instead. * chain.c32: Support chaining ReactOS' FreeLdr (Shao Miller) * isohybrid:

On Thu, Jun 16, 2016 at 06:20:31PM +0300, Ady via Syslinux wrote: > the main idea: if the LINUX directive would be capable of using / > parsing "keeppxe", then it might make sense to have the same capability > in linux.c32 (in addition to mboot.c32 and chain.c32). AFAICT, the following modules lead to the syslinux_boot_linux code path: ldlinux.c32 lua.c32 (for boot_linux and

I''m triying to find a memory leak with memprof. I''m using in environmet.rb: Memprof.dump_all(''/tmp/test.json'') after uploading to memprof.com I can see following: * objects with most outbound references 2318 classes and 384 modules * namespace hierarchy * class hierarchy * instances per class * duplicate classes by name 497 source files

Below, attached, and available at the 'ifmemdsk' branch at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=a975c12919bbd48739fede4ebfe099d98b87192e Review welcome! - Shao Miller ----- From a975c12919bbd48739fede4ebfe099d98b87192e Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sat, 6 Aug 2011 05:24:46 -0400 Subject: [PATCH]

The Wine maintenance release 4.0.4 is now available. What's new in this release (see below for details): - Various bug fixes The source is available from the following locations: https://dl.winehq.org/wine/source/4.0/wine-4.0.4.tar.xz http://mirrors.ibiblio.org/wine/source/4.0/wine-4.0.4.tar.xz Binary packages for various distributions will be available from:

When booting windows I currently have to use an extracted boot sector to chain-load the OS, is there any merit to creating a method to execute NTLDR directly using a /reverse engineered/ version of the boot sector?

The Wine development release 4.21 is now available. What's new in this release (see below for details): - HTTP proxy configuration through DHCP. - Parameter block support in D3DX9. - A few more dlls converted to PE. - Various bug fixes. The source is available from the following locations: https://dl.winehq.org/wine/source/4.x/wine-4.21.tar.xz

perhaps the boot-from-cdrom code in Smart Boot Manager? Bernd >>> No, since booting from CD-ROM requires that the El Torito part of the BIOS is activated, which it won't be if it didn't boot from CD-ROM in the first place. ---------------------------------------------------------------- Op deze e-mail zijn de volgende voorwaarden van toepassing:

I decided to install Win2K on my "retrogaming/htpc" system to take advantage of the dual processors in the thing when I'm multitasking a lot, but, it's kind of annoying having to use first one bootloader to chainload my Windows 98 partition, then, via NTLDR, selection Windows 2000 to get to Win2k. I tried using the recovery console to try to force it to write a boot sector to

> On Tue, Jun 14, 2016 at 12:33 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > > > >> > kernel.c:new_linux_kernel() to load_linux.c:bios_boot_linux() because > >> > there is no convenient way in new_linux_kernel() to control the boot > >> > flags value. > >> > >> This is the part that has me questioning things and trying