similar to: booting using a specific hard drive configuration

On Fri, Aug 4, 2017 at 12:06 PM, ian_bruce--- via Syslinux <syslinux at zytor.com> 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 >

On Tue, Dec 20, 2016 at 7:14 AM, piranna--- via Syslinux <syslinux at zytor.com> wrote: > 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

Hello, We have been using syslinux to boot machines successfully for quite a while. However, we now have a model of machine that just doesnt seem to work. We are currently using syslinux/pxelinux 2.05 but have tried 2.03 as well Here is the procedure we normally use. This is typically fully unattended. We boot a small linux distro using pxelinux. Then we copy in mbr.bin from the syslinux

hello everybody, apologies if I'm missing something here Just tried to build 6.04-pre1 test version with: make bios installer and found some problems all (seemingly) related to inaccurate paths in various Makefiles. I enclose a complete patch at the end of this email, which details the problems I found and how they got fixed for me. As an example, this is the first error I got:

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,

On 03/19/2017 01:01 AM, Thomas Schmitt via Syslinux wrote: > David Christensen wrote: >> Is there a way I can build live 32-bit Debian GNU/Linux USB images without >> isohdpfx.S and syslinux.bin? > > You could try > https://www.debian.org/releases/jessie/i386/ch04s03.html.en#usb-copy-flexible This is how I prepared an ADATA USB Flash Drive 4 GB: # cat

Hi folks. I'm not very well versed in linux (although I understand the basics, having used unix quite a bit - albeit a long time ago). I've decided to make the break from windows, and I'm trying to learn something along the way. So, I have a Dell Vostro 200, Core 2 Duo, shipped with no OS. I decided to try the Live USB approach to get started. The first step, of course, is to

> Hi there, > > first, thanks a lot for syslinux! > > I'm aware that one can't mix syslinux 4's MBR + ldlinux.sys with > syslinux 6's COM32R modules. Fair enough. Now, I need to know how > strong this "versions *must* match" requirement is when dealing with > different versions of syslinux 6.x. E.g. > > * MBR and ldlinux.sys installed by

Hello, there is a "fdboot.img" floppy drive image included with FreeDOS ISO file. It's a floppy image file: root at debian64:~# file -s /home/martin/FreeDOS/isolinux/fdboot.img /home/martin/FreeDOS/isolinux/fdboot.img: x86 boot sector, FREE-DOS BEta 0.9 Bootloader KERNEL.SYS, code offset 0x40, OEM-ID "FreeDOS ", sectors/cluster 2, root entries 112, sectors 720 (volumes

Just to be clear on the topic, I decided to do some tests from scratch on my MacBook Pro. This are the steps and results: 1. I've pick my USB pendrive and zeroed it, and after that created a new MBR partition scheme with fdisk and a VFAT partition of 32MB. Later I dd'd the file /usr/lib/syslinux/mbr/mbr.bin from SysLinux 6.03 and set the boot flag on the partition, so it could be able to

2015-10-08 12:58 UTC+02:00, Gene Cumm <gene.cumm at gmail.com>: > On Mon, Oct 5, 2015 at 2:15 PM, celelibi--- via Syslinux > <syslinux at zytor.com> wrote: >> 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. >> >>

On Mon, Oct 5, 2015 at 2:15 PM, celelibi--- via Syslinux <syslinux at zytor.com> wrote: > 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

I am trying to build an RPM starting from the TAR archive. The relevant error is: make[1]: Entering directory `/tmp1/Software/rpmbuild/BUILD/syslinux-5.00/libinstaller' perl bin2c.pl syslinux_bootsect < ../core/ldlinux.bss > bootsect_bin.c perl bin2c.pl syslinux_ldlinux 512 < ../core/ldlinux.sys > ldlinux_bin.c perl bin2c.pl syslinux_mbr < ../mbr/mbr.bin > mbr_bin.c perl

Hi, I've spent few long hours on weekend trying to get syslinux as boot loader for my alpine linux. Long story short: Failing to load ldlinux.c32 on ext4, but after changing file system from ext4 to ext3, everything worked (all other things being the same). Details below, my setup is fairly complicated so this is might be a partial reason, ALTHOUGH final and the only change which makes

For the sake of the discussion. Screenshots not included due size limit. ----- Forwarded message from syslinux-owner at zytor.com ----- Date: Sun, 05 Apr 2015 17:09:50 -0700 from: syslinux-owner at zytor.com To: syslinux-owner at zytor.com Subject: Syslinux post from piranna at gmail.com requires approval List: Syslinux at zytor.com From: piranna at gmail.com Subject: Re:

Has anybody tried to boot a dos disk via memdisk with a usb flash device as a primary hard drive? I have a 512MB flash key that when connected becomes my primary hard drive (new bios) - 0x80. If I boot a MS-DOS 7.10 floppy, one gets the command prompt and I can see the contents of my flash key as drive C:. But, if I make a image of the floppy and boot the image via memdisk, then memdisk

Richard W.M. Jones via Syslinux wrote: > 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

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

Hi there, first, thanks a lot for syslinux! I'm aware that one can't mix syslinux 4's MBR + ldlinux.sys with syslinux 6's COM32R modules. Fair enough. Now, I need to know how strong this "versions *must* match" requirement is when dealing with different versions of syslinux 6.x. E.g. * MBR and ldlinux.sys installed by syslinux 6.03-pre1 * all *.c32 modules

I'm building on Debian (Woody) though I don't think that's relevant. Having found no build instructions, no configure script I decided on 'make' It worked, except the ls command showed some files were not built because there are old versions in the tarball. I tried 'make clean all' but still I have old files: ls -ltr kwdhash.gen version.gen ldlinux.bss ldlinux.sys