similar to: Win32 syslinux needs to support mount points, disk numbers or volume names in addition to drive letters

This set of patches add some support for sector size >512. Currently it fixes extlinux, MBR for GPT and ext partitions. Other code is unaffected. This set of patches has been tested on a read Dell machine running a beta firmware.

On Fri, Nov 13, 2015 at 06:14:36AM +0100, Geert Stappers via Syslinux wrote: > On Fri, Nov 13, 2015 at 05:05:26AM +0200, Ady via Syslinux wrote: > > diff U3 syslinux-6.03/extlinux/main.c syslinux-6.03_typo/extlinux/main.c > > --- syslinux-6.03/extlinux/main.c Mon Oct 06 16:27:44 2014 > > +++ syslinux-6.03_typo/extlinux/main.c Fri Nov 13 02:29:56 2015 > > patch seen >

I've recently got a new flash drive (Kingston DT Micro 3.1 64GB) and found my existing SYSLINUX 6.02 fails to load on it, it just shows the version info and hangs forever. I've tried 6.03 as well as the latest git revision (currently 5483860), they both give me "Failed to load ldlinux.c32" The same builds and config work on my Kingston DT 101 G3 32GB. Both are formatted as NTFS

Hi Community - I would like to request that SYSLINUX be extended to install on a filesystem image file on the Windows platform. This feature is available on Linux (option -t); however, on Windows SYSLINUX only installs with a raw device path. This feature would be use by another open source project. As an small incentive, I'll offer a small, token bounty ($50) for the developer that

Hello syslinux list, I have installed Arch over a btrfs-formatted dos/MBR primary partition* (no btrfs subvolumes, just installing everything including /boot in the root of the btrfs). I have been unsuccessful for several days trying to get it to boot with syslinux (6.02-8 package from Arch, also tried 4.07-1 Arch package). All I am getting is the copyright header line and a blinking cursor

On May 25, 2014 3:39 AM, "Geert Stappers" <stappers at stappers.nl> wrote: > > > 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. >

I made several attepmts using the tree of 5.01 2013. My syslinux.cfg file has display /path_to/syslinux.cfg directive. 1. The installation, with a --directory option, was successful. After boot I got syslinux boot prompt. The syslinux.cfg was not displayed. I guess that means the MBR was there, but not the partition boot sector. Then I noticed the thread at

Hi.... >From within Windows 7 NTFS I would like if possible to be able to do either of the following: * Force Windows 7 to reboot into a PXE boot from a TFTP server using a specific PXE/TFTP config file OR * Force Windows 7 to reboot and load a linux kernel from the NTFS partition. This kernel would then use an NFS root filesystem. All of my testing is being done on a Windows 7 NTFS

On Sun, Nov 15, 2015 at 12:30:35PM +0100, Ady SF via Syslinux wrote: > [PATCH] extlinux/main.c: typo fixes > > Some typo fixes in extlinux/main.c. > None of them effects code execution. > --- > extlinux/main.c | 10 +++++----- > 1 file changed, 5 insertions(+), 5 deletions(-) > FWIW working on a new version that is `git am` ready, it will have a "sign-off".

So last week I was wondering if XFS was still working -- even with its last on-disk structure changes -- and it _suprisingly_ worked as expected. Right, now I can finally get rid of GRUB and use Syslinux to boot my Linux on EFI from a rootfs with xfs. Shit, I have two partitions (the first one being the required ESP) so there is no way to access the other partitions since because Syslinux does not

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

Hello Gene, thanks for your reply. Yes BIOS mode. The config wants a menu, which loads fine under ext4 and not under btrfs. Under btrfs I have also tried to remove the syslinux.cfg file altogether (which should trigger the boot: prompt if I am not mistaken) and the result is the same: only the copyright line appears and no prompt. The three letter sequence is EDD. The disk is 160GB, here is the

On 2019-4-5 11:28, Ady Ady via Syslinux wrote: >> >> #This item fails >> label normal >> menu default >> menu label Boot from ^hard disk >> com32 chain.c32 hd1 > > >>From the Syslinux boot menu, press [Esc] in order to get to the boot prompt. At > the boot prompt, type in: > > normal > > and press [Enter]. > > Is there

> > All of my testing is being done on a Windows 7 NTFS virtual machine ins > ESXi 5.5 and I am using syslinux 6.02. I have tried the following on my > Win7 NTFS C: drive: > > * mkdir c:\syslinux > * run 'syslinux.exe --force --mbr --active --directory /syslinux/ --install > C:' This works and I can see 2 hidden files ldlinux.sys and ldlinux.c32 in >

I have some concerns about the Syslinux boot process, which I'm now investigating in connection with my work on booting Live-CD images from USB flashdrives. Some of these are related to what seems to be inadequate documentation, but I think that there are also aspects of Syslinux operation which could be fairly easily improved. quoting from the official documentation: Since version 5.00,

> > In message <BLU0-SMTP2805E16A0E7A33B925EDF458BB80 at phx.gbl>, > Ady <ady-sf at hotmail.com> wrote: > > >Now, to move forward with Clonezilla in your USB drive, we need to > >proceed with some steps that are not as simple as dd'ing an image. > > Apologies for my impertinence, but I have one question: Why? > > I was under the impression

For reasons I won't get into, I need to use grub (not grub4dos, super grub, or any other variant) as multiboot loader on a USB thumb drive, but I also need some of the partitions to contain bootable content from syslinux-based ISOs. All of these syslinux partitions must be logical rather than primary partitions and they will not be the first partition on the drive. Porting the syslinux

I'm trying to install SysLinux on a disk image as part of NodeOS automated build process, but seems SysLinux requires administrative priviledges. I suposse this is needed because `syslinux` command try to mount the disk image / device to store the needed files, that otherwise would be have been written before and this step omitted. The other half would be to write the MBR bootloader, that

> You might want to read Wikipedia's articles about "FAT32" and "Design of the FAT file system", Good pointer. I spent far far too long on that page figuring out how fat32 is designed. But the reserved sectors, there is the key. > reserved sectors Right! Immediately after the FSIS before the FAT.And it usually is 32 sectors for fat32. Take off the VBR and the FSIS,

On 3/3/2016 07:43, Pete Batard via Syslinux wrote: > [...] as far as I am concerned, 'A "version" such as "6.03" [is not] > enough'. [...] I'd like to help to improve Syslinux with regards to version-related concerns. Having typed that, perhaps we could discuss your (or Rufus') specific needs, in parallel? Do I understand correctly that the primary