similar to: Installing syslinux on a purely virtual disk

Gene, thanks for doing "Reply-All". I only get digest, so this keeps me in the loop. Appreciated. > which appears to be included in diskstart.inc. I will have to dig in and > see > > how this all gets compiled (pointers always appreciated :-) ). > > Yes. > Is the build process documented? Or am I just going to have to plod through the makefiles? > As Ady said,

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

> > > Is the build process documented? Or am I just going to have to plod > through > > the makefiles? > > I don't think so. > Oh well... > > 1. Run installer > > 2. Installer loads ldlinux.sys onto the filesystem (and copies > ldlinux.c32, > > but irrelevant for now). > > 3. Installer calculates which blocks in the filesystem contain

Hello, We are experiencing a strange behaviour on an embedded system (i386 PC board). The structure of our disk is the following one : - A 2GB fat16 partition with DOS and syslinux - A 100GB Ext4 partition with Extlinux an several linux images to boot on ram - A swap partition The system boot on syslinux to choose among Dos and Linux boot using chain. When Linux is chosen, syslinux chains to

git://git.zytor.com/users/genec/syslinux.git Branch core-diskstart-boot-for-hpa. I found that INT 13h AH 08h in BOCHS used ES, DI, at least when using a partitionless HDD, causing "Boot error" from the magic check as it was loaded to the wrong location. HPA suggested wrapping INT 13h with the push/pop for ES's safety. This then lead to checking over for all int 13h calls in

On Tue, Oct 20, 2015 at 1:08 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> Hello, >> >> We are experiencing a strange behaviour on an embedded system (i386 PC board). >> >> The structure of our disk is the following one : >> - A 2GB fat16 partition with DOS and syslinux >> - A 100GB Ext4 partition with Extlinux an several linux images

Hi Syslinuxers, I am trying to understand the basic load chain in fat32 and ext4. I dug into the assembly for MBR, which is pretty straightforward: 1. Find boot partition (or use the pre-defined one at byte 440 for altmbr.bin) 2. Load the first 512-byte sector of the partition (VBR for fat32, Block Group 0 padding for ext). 3. Execute that code The code that is loaded, however, has to be too

> 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 Wed, Jan 3, 2018 at 2:38 AM, Avi Deitcher <avi at deitcher.net> wrote: > Gene, thanks for doing "Reply-All". I only get digest, so this keeps me in > the loop. Appreciated. > >> > which appears to be included in diskstart.inc. I will have to dig in and >> > see >> > how this all gets compiled (pointers always appreciated :-) ). >>

Here's some reminders for various branches that are pending. All branches are at my public repo at git://git.zytor.com/users/genec/syslinux.git ( http://git.zytor.com/?p=users/genec/syslinux.git;a=summary ) HPA, I'd appreciate a response in the direction of a status like on hold, under review, denied or to be completed soon. Branch win64-mingw32-ubuntu-for-hpa adds more prefixes in

On Sat, Jan 6, 2018 at 12:34 PM, Avi Deitcher <avi at deitcher.net> wrote: >> > Is the build process documented? Or am I just going to have to plod >> > through >> > the makefiles? >> >> I don't think so. > Oh well... >> > 1. Run installer >> > 2. Installer loads ldlinux.sys onto the filesystem (and copies >> >

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

Hi all, I was using grub2 for booting Archlinux x86_64 in my GPT Internal HDD (/dev/sda) then I switched to syslinux/extlinux. It was working fine but suddenly it staring showing "Boot Error" message on screen. I googled for a solution and tried all syslinux versions from 4.04-pre4 down to 4.03-stable but non of them worked. I don't know what suddenly changed caused this

> Hello, > > We are experiencing a strange behaviour on an embedded system (i386 PC board). > > The structure of our disk is the following one : > - A 2GB fat16 partition with DOS and syslinux > - A 100GB Ext4 partition with Extlinux an several linux images to boot on ram > - A swap partition > > The system boot on syslinux to choose among Dos and Linux boot using

On 01.07.2015 12:10, Gene Cumm wrote: > On Wed, Jul 1, 2015 at 4:35 AM, poma <pomidorabelisima at gmail.com> wrote: >> >> To remind you once again. >> ISOLINUX >= 6.00 built with GCC >= 5.0.0 causes a broken boot. >> This relates specifically to the use of the vesamenu.c32, >> menu.c32 works without problemos. > > isolinux-debug.bin is not for

At this point in my lab, the only solid servers I have are Win2000. So I xcopy the distro CDs into a directory that I make available for install via ftp. Well I have had problems copying files from this distro. I had to use the /c option in xcopy to get past the problem files.. A few examples are: The following files in the image directory of disk 1 has 'File creation error - The

With the decreasing price of USB Flash Memory Drives, I was wondering how I would go about creating a USB Flash Drive that could be used the same as CD 1 to install CentOS on my servers. Has anyone done this, and if so, can you tell me the procedure to make this work? Thanks!

Well, we wanted to put an install on a USB key. Neither I nor the other admin was amused by the singing and dancing that the wiki offers - and just *why* is it that syslinux is broken? At any rate, I did some googling, and found <http://www.pendrivelinux.com/>, and I ran this installer. Ok, it has some bugs: a) I had several .isos, and it *insisted* on grabbing the first one,

I have a Laptop with 6G HD, there are FD and CD-ROM port to external devices. But I only have a external floppy drive, no cd-rom. Now I boot from 1fd linux and make HD as partition, next I want to install FC4 on this laptop. But FC4 CD only support CD-ROM or USB memory, I tried to write diskboot.img to /dev/hda1 with dd command, I found all files in image bootdisk.img in /dev/hda1, but when I

I have found something called: diskboot.img at: http://www.gtlib.gatech.edu/pub/centos/4/os/i386/images/ But it is 6Mb large (6411Kb) instead of 1411Kb And the rawreadwrirewin program gets an error on it when run on NT. On Win2000, it makes a diskette that fails to boot.. So really, HELP!!!! I 'just' discovered that my old bootable diskette is for Centos 3.0, and my other CDs are