similar to: Dir_FstClusHi being used for FAT16/12 fs types

Hello, I noticed after upgrading from 3.20, I haven't been able to get syslinux to boot properly with menu.c32 or mboot.c32 from a USB key. I get an error saying invalid kernel when its trying to load menu.c32 or mboot.c32 (or any other kernel for that matter). I tried 3.35 and 3.36-pre5. Same exact behaviour. I'm using the following to compile: gcc version 3.2.3 20030502 (Red Hat Linux

Hello, I noticed after upgrading from 3.20, I haven't been able to get syslinux to boot properly with menu.c32 or mboot.c32 from a USB key. I get an error saying invalid kernel when its trying to load menu.c32 or mboot.c32 (or any other kernel for that matter). I tried 3.35 and 3.36-pre5. Same exact behaviour. I'm using the following to compile: gcc version 3.2.3 20030502 (Red Hat Linux

On 07/09/2014 04:00 PM, H. Peter Anvin wrote: > > So this would seem consistent that this is the FAT12/FAT16 boundary that > breaks stuff. Perhaps FreeDOS has a problem with FAT16 on floppies? If I understand things correctly, a bootable floppy has two key pieces of executable code: the 512-byte boot sector, and the kernel loaded by that boot sector. The kernel can be large, and thus

> On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao > Miller, Kenneth Davis, wrote: > > [...] > > Thank you all for your responses. You helped me solve my problem. For > anyone else that runs into similar trouble and finds this thread, here > follow summaries of what I've learned. > > To recap, our PXE server holds Dell BIOS updates 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 >> >

> > > 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

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 :-) ). >>

On 07/09/2014 01:54 PM, Alexander Perlis wrote: > > Ah, this might explain things although I don't know what is meant by > "intended". First, to clarify, newmkfloppyimg calls mkdosfs 3.0.12, and > grabs H/S from the output and then computes C. For all the sizes I've > tried, newmkfloppyimg always tells me H=64 S=32 and then C is the > approximately the number

In the following text, I am about to use terms such as "inaccurate". I don't mean to question what some code does, but rather to compare the expressions against what I think is a more accurate one, in theory. I mean no disrespect, and I am not saying that developers are doing the wrong thing. In addition, of course I could be wrong (or type in incorrectly, or some formatting

I downloaded DOS6.22 image from putergeek.com. Used fdisk from that floppy and format from that floppy. Still no luck. If I execute fdisk under leaf (monkeynoodle.org) as fdisk/dev/hdc, and give p for print partition table, I get the following: Disk /dev/hdc: 16 heads, 32 sectors, 123 cylinders. Units = cylinders of 512 * 512 bytes Device Boot Start End Blocks Id System /dev/hdc1

> Hi All, > First post and hopefully someone can steer me in > the right direction for this problem. I did a bit > of googling and found some hints but nothing concrete. > > We are using Syslinux and a FAT32 USB thumb drive > (single partition) to boot a customized Debian OS > which works very well with newer motherboards. > However we have a few older Dell

Latest syslinux 2.00 stable version from freshmeat. Are the programs that will just copy boot sectors or create boot sectors for /dev/hda1, /dev/hda2 etc.. that I can simply copy with a dd command? Mohan -----Original Message----- From: leaf-user-admin at lists.sourceforge.net [mailto:leaf-user-admin at lists.sourceforge.net]On Behalf Of Luis.F.Correia Sent: 05 November 2002 15:01 To: leaf-user

-----Original Message----- From: S Mohan [mailto:smohan at vsnl.com] Sent: 05 November 2002 16:13 To: Luis.F.Correia; leaf-user at lists.sourceforge.net Subject: RE: [leaf-user] (no subject) I know that is the proper way. Unfortunately, I'm stuck and am mad at myself for that. Error message: ERROR 440D: Unable to lock drive for exclusive access - when I use syslinux 2.00 from freshmeat.

Hi All, First post and hopefully someone can steer me in the right direction for this problem. I did a bit of googling and found some hints but nothing concrete. We are using Syslinux and a FAT32 USB thumb drive (single partition) to boot a customized Debian OS which works very well with newer motherboards. However we have a few older Dell machines that simply hangs when trying to boot

I'm home at last. I did a mixture of things. I downloaded DOS6.22 floppy from putergeeks.com, extracted my old syslinux 1.75 (dos version) into the same boot floppy and made my CF /dev/hda1 as suggested by Luis (Hail O King - my saviour). Lo and behold it went thro' like a hot knife thro' butter. syslinux did not complain at all. I did an xcopy /s of my D: (hard disk) to my C:(CF) and

Hi, I had the same problem last week. I got it work when I used an old syslinux (the one from Daschtein Utils). I think that the problem is with newest version of syslinux, but could get confirmation from the syslinux group. Nick "S Mohan" wrote: > > I'm home at last. I did a mixture of things. I > downloaded DOS6.22 floppy > from putergeeks.com, extracted my old

Hello, I use Tim's mboot.c32 to load multiboot kernels over pxelinux. However, some kernels require the symbol table and other information in the ELF section header table to be able to load properly. This functionality is not present in mboot.c now, so I added support for it. The patch is attached. It would be great if you can push this into the next release of syslinux so ELF multiboot

On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao Miller, Kenneth Davis, wrote: > [...] Thank you all for your responses. You helped me solve my problem. For anyone else that runs into similar trouble and finds this thread, here follow summaries of what I've learned. To recap, our PXE server holds Dell BIOS updates in FreeDOS floppy images booted via MEMDISK.

Recently (and for ages, I'm sure) folks have suffered partition destruction and had to try and recover. In the recent thread, the victim eventually had to resort to Google and fond some package that I can not remember now. Well, I was perusing my YumInfo.lst.05, for general info, and I discovered this (potential) little gem. Thought I would pass it on and make it "more googleable"

This is a resend since I didn't hear back from anyone. Hey guys, I noticed the appended ipappend options end up in the beginning of the cmdline argv[] when mboot is entered. mboot then tries to parse the first argument as the name of the kernel module and promptly fails cuz it can't find "ip=.." or "bootif=...". I'm attaching a patch which basically looks for any