similar to: Can't get COM32 + GDB to work

Hello, Pardon the newbee question but I'd like to be able to log to disk from within syslinux (extlinux actually, as it's a ext2 fs). fopen("w") does not appear to be implemented (returns EINVAL). Has anyone written the filesystem write support, and if not, any suggested routes? Should I just implement the lower level BIOS disk write support, add the FS layer, and go from

Here is the initial release: git://github.com/donhiatt/Syslinux-EXT2FS-Library-port.git I am very new to git so I hope I managed to get the repo setup properly. The repo is branched from 'disklib' as I plan to use it for all disk read/write access (I'm currently using modified gpllib/disk/* -- see README). Cheers, don ----- README for ext2fs module. * Description -----------

Hi list, I ran a syslinux drive on a QEMU machine with a gdbstub opened. I tried the simplest modules: the hello.c in com32/samples/ directory, which is compiled into hello.c32 in bios/com32/samples/. I already compiled the module with debug info attached via -g option added to CFLAGS in the Makefile. However, the problem is that the generated module is a shared dynamic module, which only

Hi, I am trying to create a bootable linux usb drive using syslinux command as given below but I am getting error as given below syslinux4.exe -maf G: Return code : 1 Output : Error : Could not write the whole boot sector I have tried to do this with syslinux4, syslinux5, syslinux6 with the same error message. The usb drive is formatted to FAT32 drive system and has a capacity of 4GB. The OS

Hey guys, I've searched the archives but couldn't find any instructions on setting breakpoints in com32 apps. I'm trying to debug my app under Qemu. BTW, is there any limits on the amount of malloc space you can do? I'm trying to track down a reboot after a lot of mallocs. Thanks a lot.

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

Is there a known problem with fopen and/or fwrite in Syslinux? I'm trying to open a file to write data to but fopen( file_name, "w+" ) fails everytime. fopen( file_name, "r" ) works just fine.

>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 drill away and find more about its status and understand what is

On Thu, Oct 5, 2017 at 11:48 AM, Tu Do via Syslinux <syslinux at zytor.com> wrote: > Hi list, > > I ran a syslinux drive on a QEMU machine with a gdbstub opened. I tried the simplest modules: the hello.c in com32/samples/ directory, which is compiled into hello.c32 in bios/com32/samples/. I already compiled the module with debug info attached via -g option added to CFLAGS in the

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

> > syslinux4.exe -maf G: > Return code : 1 > Output : > Error : Could not write the whole boot sector > In addition to my comments in my prior email in this same email thread, (FWIW and for other readers) I should add that for latest version 4.xx and onwards, a more-adequate command should had been: syslinux[64].exe -mai <drive_letter>: and reflecting the original

On 11/24/2013 09:56 AM, Ady wrote: >> The very early code that emits this message is *identical* between >> Syslinux 4 and Syslinux 6. The biggest difference is the size of >> isolinux.bin, so it is possible that that might be the source of the >> problem. >> >> -hpa > > I wonder if isolinux.bin should be limited to max. 16 sectors (of > 2KiB

This patch fixes a crash in disk.c32 owing to the change in get_error()'s signature. Instead of calling get_error() I just dump the error code. don diff --git a/com32/modules/disk.c b/com32/modules/disk.c index e94a36b..2966173 100644 --- a/com32/modules/disk.c +++ b/com32/modules/disk.c @@ -37,11 +37,8 @@ int main(int argc __attribute__ (( unused )), continue;

Hello, Would com32 modules be considered the same as an ordinary Linux executable with respect to LGPL? That is, as long as you released any changes to syslinux/com32 libs would you also have to release the source to the com32 module? Thanks for your time.

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

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2 +- hw/msix.c | 423 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/msix.h | 35 +++++ hw/pci.h | 20 +++ 4

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2 +- hw/msix.c | 423 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/msix.h | 35 +++++ hw/pci.h | 20 +++ 4

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

Amardeep Verma via Syslinux <syslinux at zytor.com> writes: > syslinux4.exe -maf G: > Return code : 1 > Output : > Error : Could not write the whole boot sector > > I have tried to do this with syslinux4, syslinux5, syslinux6 with the > same error message. The usb drive is formatted to FAT32 drive system > and has a capacity of 4GB. The OS that I am using is Windows

Hi all, I'm new here so bear with me. I am working on a project at work where we are replacing 1000+ Dell servers. When a new Dell server is delivered to one of our remote offices it will PXE boot off of the existing Dell server and install openSuse and then configure itself. We also PXE boot windows PCs in the remote offices so we needed a way to assign a large range of MAC addresses to a