similar to: 6.02 won't boot XP. 6.01 works slowly, but successfuly.

Due to a strange reason, my patch broke chainloading on 6.02. Working hard on it to find the root of the problem. I'm currently working on the MultiFS support, and hopefully the booting process will be faster for XP as an example. -- Raphael S. Carvalho

It would be good to clean it up so out can be used for both. Just teach it that ) ends the parse. On June 4, 2014 2:06:22 PM PDT, Raphael S Carvalho <raphael.scarv at gmail.com> wrote: >On Wed, Jun 4, 2014 at 5:36 PM, Raphael S Carvalho ><raphael.scarv at gmail.com> wrote: >> On Wed, Jun 4, 2014 at 5:21 PM, H. Peter Anvin <hpa at zytor.com> wrote: >>> On

From: Raphael S. Carvalho <raphael.scarv at gmail.com> MULTIFS SYNTAX: (hd[disk number]:[partition number])/path/to/file The meaning of this_fs was changed to improve the flexibility of the support. Now, this_fs means the file system being currently used. root_fs was created to save the context of the main file system (where ldlinux.sys lives in). get_fs_info is a function pointer that

On Wed, Jun 4, 2014 at 6:17 PM, H. Peter Anvin <hpa at zytor.com> wrote: > It would be good to clean it up so out can be used for both. Just teach it that ) ends the parse. Sounds reasonable, I will do that! > > On June 4, 2014 2:06:22 PM PDT, Raphael S Carvalho <raphael.scarv at gmail.com> wrote: >>On Wed, Jun 4, 2014 at 5:36 PM, Raphael S Carvalho

From: Raphael S. Carvalho <raphael.scarv at gmail.com> This patch finishes the MultiFS support. init_multifs gets called in the main (startup) function of ldlinux.c32, so MultiFS will be initialized automatically. init_multifs calls enable_multifs (lives in the core) to hook get_fs_info. Subsequent accesses will callback the get_fs_info living in ldlinux.c32. Signed-off-by: Raphael S.

Raphael, Except for the : instead of the , this looks like the grub hard disk nomenclature that's been around for a thousand years. Certainly since early GRUB1. Example: (hd0,0)/grub/splash.xpm.gz Why did you chose : instead of grub's , ? I'm guessing (like grub) that disks & partitions are 0-based? (Were the original grub authors European?) Spike #Date: Wed, 4 Jun 2014

On Wed, Jun 4, 2014 at 5:36 PM, Raphael S Carvalho <raphael.scarv at gmail.com> wrote: > On Wed, Jun 4, 2014 at 5:21 PM, H. Peter Anvin <hpa at zytor.com> wrote: >> On 06/04/2014 11:09 AM, Raphael S Carvalho wrote: >>> Before proceeding with the MultiFS patchset, let's discuss the MultiFS syntax. >>> >>> It's currently as follows:

From: Raphael S. Carvalho <raphael.scarv at gmail.com> My commit 09f4ac33 broke 'com32/lib/syslinux/disk.c' __lowmem doesn't work for declarations outside the core. Using __lowmem outside the core wouldn't have the desired effect, then lmalloc must be used instead to store dapa into the correct section (".lowmem"). Reported-by: Dark Raven <drdarkraven at

On Wed, Jun 4, 2014 at 5:21 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 06/04/2014 11:09 AM, Raphael S Carvalho wrote: >> Before proceeding with the MultiFS patchset, let's discuss the MultiFS syntax. >> >> It's currently as follows: >> (hd[disk number]:[partition number])/path/to/file >> >> Any objections? >> > > As others

C:\syslinux>type syslinux.cfg prompt 1 timeout 1 default hello label xp com32 chain.c32 append hd0 1 ntldr=/ntldr label memtest linux memtest86+.bin label hello com32 hello.c32 C:\syslinux> syslinux command was: syslinux.exe -a -d /syslinux -f -i -m c: 1. The syslinux copyright

From: Raphael S. Carvalho <raphael.scarv at gmail.com> v2: Extract ADV_SIZE automatically from libinstaller/setadv.h. 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 can be at most: 65536 - 2 * ADV_SIZE - 512 (limit). Certain file systems

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 files changed, 34 insertions(+), 2 deletions(-) create mode 100644 core/ldlinux_limit.pl diff --git a/core/Makefile b/core/Makefile index f795a5c..00de331 100644 ---

Peter, does this look OK to you? Raphael, I can't work out why ADV_SIZE is a constant in this file? On Sat, 31 Aug, at 05:01:20PM, Raphael S.Carvalho wrote: > 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:

On Mon, 30 Sep, at 02:14:34AM, Raphael S.Carvalho wrote: > From: Raphael S. Carvalho <raphael.scarv at gmail.com> > > v2: Extract ADV_SIZE automatically from libinstaller/setadv.h. > > 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

While going throug old posts found: Op 2013-08-31 om 17:01 schreef Raphael S.Carvalho: > 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

This patch adds support for serial output functions. It may be useful for debugging purposes since you can separate ordinary outputs from debugging dumps. Just add "serial.h", and use either serial_print or serial_puts as you would use printf and puts respectivelly. For QEMU, you only need to specify the option -serial stdio. If you use another VM, find how you can redirect the serial

[PATCH 001/001 v2] core/serial: Add support for serial output functions. Second version fixes an initialization issue. ----- This patch adds support for serial output functions. It may be useful for debugging purposes since you can separate ordinary outputs from debugging dumps. Just add "serial.h", and use either serial_print or serial_puts as you would use printf and puts

From: Raphael S. Carvalho <raphael.scarv at gmail.com> Most of file system drivers initialize the cache themselves. The problem is that the same cache could be again initialized later, then invalidating the previous one. This patch fixes this. Problem found while auditing the code. Signed-off-by: Raphael S. Carvalho <raphael.scarv at gmail.com> --- core/fs/cache.c | 2 ++

Ady, Peter, et al. On Fri, July 24, 2015 5:28 pm, Ady via Syslinux wrote: > >> On 07/23/2015 02:09 PM, Raphael S Carvalho via Syslinux wrote: >> >> >> > My sincere opinion is to apply this patchset as-is, and incrementally >> > improve multifs. Lack of alternatives (additional features) *should >> not* be >> > a reason to block this patchset.

Before proceeding with the MultiFS patchset, let's discuss the MultiFS syntax. It's currently as follows: (hd[disk number]:[partition number])/path/to/file Any objections? Regards, Raphael S. Carvalho