similar to: Interaction with Windows bootloader

> On Sat, Jan 5, 2019 at 3:17 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > syslinux[64].exe -i -f c: bootsecfile.bss > > > > > > This should have been the form for your desire as specifying the > > > filename should have told it to create the BSS instead of writing it > > > to the VBR. Being the "fixed" HDD

> syslinux[64].exe -i -f c: bootsecfile.bss > > This should have been the form for your desire as specifying the > filename should have told it to create the BSS instead of writing it > to the VBR. Being the "fixed" HDD instead of a removable drive like a > USB stick, "-f" is necessary. Hmm, instead? Could this syntax be some kind of unintended oversight?

On Sun, Jan 6, 2019 at 12:58 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > On Sat, Jan 5, 2019 at 3:17 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > syslinux[64].exe -i -f c: bootsecfile.bss > > > > > > > > This should have been the form for your desire as specifying the > > > >

On Thu, Jan 3, 2019 at 12:31 PM David Henderson via Syslinux <syslinux at zytor.com> wrote: > > Good afternoon all! I have a project I'm working on that requires > Linux to be installed either to its own partition, or to the partition > of a host OS (Windows or Linux). One way works, the other way does > not... For starters, what version? Official pre-compiled

On Sat, Jan 5, 2019 at 3:17 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > syslinux[64].exe -i -f c: bootsecfile.bss > > > > This should have been the form for your desire as specifying the > > filename should have told it to create the BSS instead of writing it > > to the VBR. Being the "fixed" HDD instead of a removable drive like a

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

Oh somehow I never noticed that "bootsecfile" option. That's probably what I need to use. I was looking at the source to see how the --mbr flag works and thought that there should be a way to do the same thing with the other mbr files. On Thu, Aug 4, 2016 at 2:41 AM poma <pomidorabelisima at gmail.com> wrote: > On 04.08.2016 00:58, Erik Sandberg via Syslinux wrote: >

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,

Hi, I'm working on https://wiki.gnome.org/Projects/OSTree which is a general-purpose update system for Linux-based operating systems. It isn't a package system itself, but operates at the same level. A primary goal of OSTree is fully atomic updates, and the "swapped chroots" model works well for most of userspace and the kernel/initramfs. However, syslinux relies on

Hi, I have two disks in my computer with each one, a bootloader. The first disk (a usb key) boot with syslinux bootloader that launches a tiny kernel. The second disk has grub 2. I need to boot the disk 2 with grub, from the tiny kernel of the disk 1. So i use the bios interruption 0x19 to load the second bootloader, but this solution doesn't works. If i use a my own bootloader, the

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

From: Sylvain Gault <sylvain.gault at gmail.com> These patches basically remove unused linker scripts and port a change that was made to an unused script. Those are to be applied on top of the gcc 5 bug fixes as they would conflict otherwise. Sylvain Gault (4): diag/mbr: fix dependency to linker script Remove unused linker scripts core: Make symbols defined in linker script HIDDEN

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

On 2013.08.10 04:07, H. Peter Anvin wrote: >> My application already its own version of the Syslinux installer [1], >> and simply requires the relevant ldlinux.sys file to be provided. > > But that, too, is version-specific. I think there may be a misunderstanding here. Are you saying that when installing ldlinux.sys + ldlinux.bss v5.01 on a FAT filesystem, the installer needs

On Wed, Apr 23, 2014 at 4:49 PM, Ady <ady-sf at hotmail.com> wrote: > > FWIW and just as one example, ArchLinux has its own script Looks like the canonical source is here: https://projects.archlinux.org/svntogit/packages.git/tree/trunk/syslinux-install_update?h=packages/syslinux Right. Hmm. The painful thing will be transitioning the existing package, as it would obviously break

I've recently purchased an SSD with the goal of having a portable MS-Windows installation, something which Windows 8's "Windows to Go" feature allows (install to, and boot/run from, USB flash device). Housing the SSD in an external Zalman VE300 case allows presenting ISO files as hardware CD/DVD/BD drive with inserted medium. Having the ISO files present, it's tempting

Thanks for the response, Gene. Much appreciated. I didn't get all of it; mind if I follow on below? ldlinux.sys is ldlinux.bin without the VBR (Volume Boot Record) code. > Makes sense. > > 1. Where is the code that goes in the VBR or Block Group 0 padding? > > diskboot.inc. > which appears to be included in diskstart.inc. I will have to dig in and see how this all gets

Hello, I'm trying to create and boot a Win98SE-DOS OS through Hard Disk emulation. My src files are from a Win98SE 1440K floppy image file, with a x86 boot sector (dl'd from the net - I have no floppy drive and a slow net link 3.2KB). I don't know what to put into the partition boot record of my image and how to load dos.bss properly (the docs explain for floppy images not for HD

Hey list, I have an older 2005 Uniwill 259ia3 with a Phoenix bios. Flash booting is limited to keys 512 MB or less! Here's my setup recipe: used the HP utility v. 2.0.6 giving me this geometry ---------------- fdisk -l ----------- Disk /dev/sdb: 493 MB, 493879296 bytes 255 heads, 63 sectors/track, 60 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start

Hello Recently I've been happily experimenting with syslinux, replacing grub and my old bootmanager. All works beautifully, but I have one question - in case of .bss bootsectors - what exactly and under what circumstances is patched in ? With syslinux used as main bootmanager - bootsectors from xp64, xp32 and [pre-syslinux] msdos 7.1 (98se) work perfectly fine when chainloaded natively as