similar to: pathbased: linux/syslinux.c:421:open() yields error

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

_ Vbox 4.2.18 VM booted with FreeDOS floppy, kernel 2041, no config.sys, no autoexec.bat, no TSR's, no memory managers. _ The booting floppy includes syslinux.com 6.02. _ Two HDD images attached to the VM, MBR + 1 FAT16 formatted partition each. Executing syslinux.com -i c: (or "d:") results in the following error: "Invalid Opcode at AD04 5080 0206 5080 2021 3666 FFFD 0083

After formatting a floppy to MSDOS format and using syslinux /dev/fd0, I successfully installed ldlinux.sys to the root directory of the floppy. Then I created a syslinux.cfg under the root directtory of this floppy to load the linux kernel in my first hard disk, 3rd partition, boot folder. The file system of this partition is ext3. The floppy has a FAT file system. This config file is listed

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I have problems booting linux 2.4.21 with syslinux 2.04 from floppy. Booting with this combination I get the following error: Loading kernel................ Boot failed: please change disks and press a key to continue. (Note: there are exactly 16 dots ".", it this is relevant) The floppy was DOS formatted with mformat and contains

I'm trying to add boot support to https://github.com/libguestfs/nbdkit/tree/master/plugins/floppy This NBD server plugin generates a completely virtual FAT filesystem and partition table. Nothing is ever written to a file, and it must run without anything needing to be root, loop mounting etc. Running "syslinux --install <something>" is a non-starter. So I've looked at

As you know, the Linux version of syslinux supports mount points. But for the Win32 version, it only supports drive letters as in: syslinux ?ma e: However, drive letters are not always available, such as drives mounted to NTFS folders. In order to install syslinux to these drives, future release of syslinux should support using mount points as the drive spec; or alternatively, support disk

Hello, I have to load a syslinux floppy image from grub using memdisk, it works like: grub - memdisk -> linux floppy image. the linux floppy image is using syslinux as linux bootloader. before syslinux 3.02, it works fine. However if syslinux >=3.05 it doesn't works. After vmlinuz and initrd loaded , before boot linux kernel, system hangs. Or, is it possible to run

I am trying to use syslinux on a floppy image to create a bootable CD. When I boot (on a number of computers) I only get "Boot error", using the image file on a floppy works. I realize the correct way to do this is using isolinux with no emulation but but I need to do this with syslinux :( I've looked into it and older versions of syslinux dont have this problem. From my research

If a syslinux floppy does not contain a config file (syslinux.cfg) modules are not being found unless specified with a directory prefix (e.g. /pcitest.c32). The reason is that CurrentDir is only set if there is a config file present. This is a possible regression since commit 68eefb79e2cbb590ebf958dd0c50ce00b941abd2. Before this change RootDir was used in searchdir and now it's CurrentDir

Hardware with issue is a Lenovo T410 (circa 2007?): SysLinux PXE boot (pxelinux.0) version 2009 - PXE boot works, select Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking is working for Ghostcast/peer to peer. SysLinux PXE boot (pxelinux.0) version 2014 - PXE boot works, select Ghost from PXE menu, PC-DOS loads, Ghost.exe runs and networking is NOT working for Ghostcast/peer to

Hi All, I was testing syslinux floppy on a Mazza MotherBoard, his chipset is VIA MVP3 (VT82C598MVP, VT82C586B), and Winbond W83877F/TF. After reading the floppy, I see 'boot failed', I have to ide disk in the system, only flash device. I used the -s option to build the floppy. Does Somebody know if the chipset is supported? I tested the floppy on toshiba laptop and it works very fine.

My ?default? was just a sample to prevent further tl;dr :) Right, by 2014 I meant 6.03. I didn?t notice in the docs this was a known issue. If keeppxe is a bug with 6.03, that?s likely my issue. Do I drop back to 6.02 or X? Which version? Thanks, David Sent from my iPhone > On Feb 1, 2018, at 6:53 PM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > >> Hardware

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

core and the simple menu do not interpret the IPAPPEND/SYSAPPEND directives in the same way. Which is the proper way? Either way, this should be clarified in the documentation. com32/elflink/ldlinux/readconfig.c: } else if ((ep = looking_at(p, "ipappend")) || (ep = looking_at(p, "sysappend"))) { uint32_t s = strtoul(skipspace(ep), NULL,

I am currently unable to get Syslinux v6.03 to load kernel + ramdisk when booting from a PXE server in EFI mode. Is this a feature that is currently supported? If not, is there a known time frame for which support will be added? Thanks. -Bryan

After so much time and improvements, I'm glad to see and publicize a pre-release, 6.04-pre1 in https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.04/ Personally, I've already been working testing the pre-release as-is and my tests have been positive so far. I appreciate feedback like that from Gabriele Balducci and testing "make bios installer". Yes, there are a

On Fri, Oct 11, 2019 at 10:27 AM James Pearson via Syslinux <syslinux at syslinux.org> wrote: > > James Pearson via Syslinux wrote: > > > > However, I have just tested the exact same boot procedure using a Dell > > laptop (Latitude 7480) - and it all worked without a problem - that is, > > syslinux.efi and ldlinux.e64 were downloaded without a problem - and >

Is there a method to reboot a memdisk (floppy) image? I'm working on a DOS-based installation floppy that needs to repartition the hard disk prior to proceeding. DOS will only recognize the updated partition table after a reboot, but I'd like to be able to save information to the currently loaded memdisk floppy disk and simply reboot the image. Possible? I haven't had any luck with

On May 13, 2014 4:04 PM, "Ady" <ady-sf at hotmail.com> wrote: > > On Tue, May 13, 2014 at 7:51 PM, Ady <ady-sf at hotmail.com> wrote: > > > I wonder why the already built-in binaries are not enough / adequate. > > I don't believe it can be used as is: > > bash# file syslinux > > syslinux: ELF 32-bit LSB executable, Intel 80386, version

On Sat, Sep 14, 2013 at 04:51:52PM -0400, Gene Cumm wrote: > On Sat, Sep 14, 2013 at 3:20 PM, Regid Ichira <regid23 at nt1.in> wrote: > > > label xp > > com32 chain.c32 > > append hd0 1 ntldr=/ntldr > > > 2. Installed by > > From xp cmd prompt: > > c:\downloadedPrograms\syslinux\syslinux.exe --active \ > >