search for: pathbased

>From the current pathbased branch, linux/syslinux.c, line 421, open() yields an error on a FAT floppy image, 2.88M standard size. At first, this was a floppy that did have a previous version of SYSLINUX installed. I saved that floppy image and tried deleting ldlinux.sys with the same results. I'm still trying to dril...

Just a slight poke regarding the MEMDISK and MDISKCHK.COM possibilities available here[1]. Review by non-hpas is welcome, too. Thanks! - Shao [1] http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/ mdiskchk_enh2

Hi, I am using syslinux-4.00-pre24, -pre27 and -pre31. chain.c32 fails for pre27 and pre31 for particular configs ... shown below. 1) works on pre24, fails with error message "Chainboot failed!" for pre27 and pre31 LABEL local MENU DEFAULT MENU LABEL Local Boot ... (skip PXE boot) KERNEL chain.c32 APPEND hd0 0 2) works on all three. LABEL local

Hey guys, I can't seem to figure out how to debug a COM32 app with GDB under qemu. I start "qemu -s" and then "gdb hello.elf ; target remote:1234" but can't set any breakpoints that work. I"m using syslinux4 (pathbased from the repo). Can anyone verify that they can use qemu+com32+gdb with something as simple as com32/samples/hello.c32 ? Also, is it possible to use com32/gdbstub with qemu? (How would you connect to qemu's serial port)? Thanks a lot for your time. don

Just a status update on my progress with ROSH: I now have it able to compile as a COM32 and Linux ELF on the pathbased branch. The main reason I am using the Linux ELF is to test and compile a little easier and faster. At this point, it's approaching a stable, usable state. However, it depends on some changes to libutil, the main COM32 library, and the Syslinux core. I think I have the libutil changes done...

Hi all, I have pushed out Syslinux 4.00-pre20, which includes support for running out of a new working directory: if a directory is given on the append line to a "config" statement, that will now be considered the new working directory. The "pathbased" branch is now the active development branch for Syslinux 4. With this checkin, I now expect that the major restructuring work in the Syslinux 4 is mostly done. There are, of course, still be little bits we'd like to fix here and there, but I don't expect any more major rewrites on t...

Sorry for all the noise, but I can't seem to find the location of the Syslinux 4 git codebase. The wiki give this for 3.x: http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=summary but I haven't been able to find the 4.x branch. Thank you. don

...INUX are fully merged as a single entity. The program extlinux(8) remains as an online nstaller for the SYSLINUX bootloader (ldlinux.sys), since the syslinux program (on Unix) is an offline installer. -> These may get merged in the future, but not without care. b) The former "pathbased" branch is now the "master" branch. Legacy 3.8x development, to the extent there will be any, will be on the "syslinux-3.8x" branch. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

From: Matt Fleming <matt.fleming at linux.intel.com> This series fixes some bugs and switches the elflink branch to be entirely ELF modules. It applies on top of, http://syslinux.zytor.com/archives/2011-April/016369.html The deletions in the diff stat below are mainly from deleting com32/elflink/modules (finally!). Now there should be no duplicate code because we don't need COM32 and