similar to: MBRCheck issues

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

Hi, I am trying to track down a ISOLINUX boot problem on my workhorse computer. Booting slax-6.0.0-rc5.iso from www.slax.org (a live distro) from CD gives the following messages: Loading /boot/vmlinuz ........... Loading /boot/initrd.gz ............ Ready. _ Silence. The next message should be, but does not appear: Uncompressing Linux ........... This message appears with the same CD on an old

Hello, you guys have helped me before. I am setting up a multiboot system on my usb stick. At one point, with syslinux, i had the two of the three systems working. However in a sucessful attempt to get the third working, i used that os'es instructions for usb installition, which included syslinux. After which, that system worked, with its syslinux.cfg being located in a non-root folder

On Tue, 2019-12-17 at 22:46 +0100, David Bala?ic via Syslinux wrote: > Hi! > I have bootable (USB flash) disk, that _appears_ to be using syslinux. > (the word syslinux is in the PBR, in the hexdump). > How can I chainload it? The payload seems to be a file that I tried > load with COMBOOT, COM32 etc, but nothing works (they report that the > file is not in proper format, wrong

Yes, I tried to dd the mbr.bin and use both --install and --stupid parameters. The FAT32 partition is bootable. Here is what I did: $ sudo fdisk /dev/sda -l Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal):

Hi, I've been working on making a USB key which is bootable via EFI and BIOS, and so far I've succeeded but only by using GRUB on the MBR. Syslinux installs correctly, but because the USB key can only have one partition and its type is EFI protective, it isn't set to bootable on the MBR partition table and so syslinux (mbr.bin) doesn't boot. I've also tried gptmbr.bin

--- mbr/Makefile | 6 +- mbr/mbr-diag.S | 371 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 376 insertions(+), 1 deletions(-) create mode 100644 mbr/mbr-diag.S diff --git a/mbr/Makefile b/mbr/Makefile index 0bdf7e3..b9d743d 100644 --- a/mbr/Makefile +++ b/mbr/Makefile @@ -17,7 +17,7 @@ topdir = .. include $(topdir)/MCONFIG.embedded -all: mbr.bin gptmbr.bin

> > > Ady, before responding to you further, I'll ask you now to take onje > more (fresh) look at this thread that I started over in the GParted > forums: > > http://gparted-forum.surf4.info/viewtopic.php?pid=31834 > > Please note that I have now followed-up on myself and that I have added > quite a lot of new & additional information. > > It now

--- mbr/Makefile | 6 +- mbr/mbr-diag.S | 377 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 382 insertions(+), 1 deletions(-) create mode 100644 mbr/mbr-diag.S diff --git a/mbr/Makefile b/mbr/Makefile index 0bdf7e3..b9d743d 100644 --- a/mbr/Makefile +++ b/mbr/Makefile @@ -17,7 +17,7 @@ topdir = .. include $(topdir)/MCONFIG.embedded -all: mbr.bin gptmbr.bin

Hi all. I am new to the list. I am trying to make a SD flash bootable. I have a MSI Wind netbook running Fedora 9 with a built-in card reader that detects the SD flash properly. However, when I run syslinux, it does not update the boot block. I also tried using a SD -> USB adapter, but I get the same behavior. Fedora 9 uses an older syslinux 3.61, but I also tried the latest 3.72 with

On Tue, Oct 20, 2015 at 04:40:09PM +0100, slim tabka wrote: > Hi everyone, > > I'm working with libguestfs 1.30.3 on Centos 7 host. > I encountered a problem when I wanted to install extlinux with guestfish as > a bootloader for my guests and I always get this error: > > SYSLINUX 4.05 EDD 0x54f93f16 Copyright (C) 1994-2010 H. Peter Anvin et al > ERROR: No

I have syslinux booting slax off of a usb stick but in the process I think I may have found a bug in syslinux im using version syslinux-3.31 my syslinux.cfg use to look as follows <== beginning display boot/splash.cfg default slax autoexec=startx prompt 1 timeout 40 F1 boot/splash.txt F2 boot/splash2.txt F3 boot/splash.cfg label slax kernel boot/vmlinuz append vga=769 changes=slaxsave.dat

> Yes, I tried to dd the mbr.bin and use both --install and --stupid parameters. > > The FAT32 partition is bootable. > > > Here is what I did: > > $ sudo fdisk /dev/sda -l > > Disk /dev/sda: 500.1 GB, 500107862016 bytes > 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size

Op 2013-12-15 om 17:39 schreef Ferenc Wagner: > Ruben Kerkhof <ruben at rubenkerkhof.com> writes: > > > /* 80 00 00 00 ee 00 00 00 > > - - bootable partition, type EFI (EE), no CHS information */ > > + - bootable partition, type EFI (ED), no CHS information */ > > Please fix the previous comment line as well. As I understand that, so in _my words_:

Just achieved success using syslinux to multi-OS boot, including a WinXP System (boot) partition that's been encrypted with TrueCrypt (TC). You'll need syslinux version 3.81-pre13 or newer to get a working altmbr.bin file. I used: http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/syslinux-3.81-pre13.zip Background: I started with a 'normal' multi-OS boot setup as

The handover protocol uses ED as partition type but the comment above it still mentions EE Signed-off-by: Ruben Kerkhof <ruben at rubenkerkhof.com> --- mbr/gptmbr.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mbr/gptmbr.S b/mbr/gptmbr.S index 7f450d3..8ab6b50 100644 --- a/mbr/gptmbr.S +++ b/mbr/gptmbr.S @@ -194,7 +194,7 @@ found_part: pushw %di /* 80 00 00 00

--- mbr/Makefile | 6 +- mbr/mbr-diag.S | 372 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 377 insertions(+), 1 deletions(-) create mode 100644 mbr/mbr-diag.S diff --git a/mbr/Makefile b/mbr/Makefile index 0bdf7e3..b9d743d 100644 --- a/mbr/Makefile +++ b/mbr/Makefile @@ -17,7 +17,7 @@ topdir = .. include $(topdir)/MCONFIG.embedded -all: mbr.bin gptmbr.bin

On 6/19/20 9:48 AM, Nicolas Kovacs wrote: > Hi, > > In my daily work I'm mainly using USB keys for work : one with CentOS 7, one > with OpenSUSE Leap 15.1, one with Slax Live for data recovery purposes, one > with Ghost4Linux and one with FreeDOS which I use for flashing the odd BIOS. > > Last week I bought a set of three flashy colored USB keys in a local shop. To >

> Op 2013-12-15 om 17:39 schreef Ferenc Wagner: > > Ruben Kerkhof <ruben at rubenkerkhof.com> writes: > > > > > /* 80 00 00 00 ee 00 00 00 > > > - - bootable partition, type EFI (EE), no CHS information */ > > > + - bootable partition, type EFI (ED), no CHS information */ > > > > Please fix the previous comment line as well.

Dear all, I'm working on a shell script which is producing a bootable image file. It contains a populated MBR and a single file system (ext4) which again contains a debootstrabed debian stable distribution. Unfortunately, I'm experiencing problems with the bootability of the produced image. When selecting the installed system at the boot prompt, Syslinux responds with something like