similar to: Does syslinux support FAT32? If so, which version? eg., 3.11 and above

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

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,

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

Hi Ady, Your insightful post prompted me to to a little bit more digging as to how the Ridgecrop algorithm computed its FAT size, with the result of my investigations presented below. NB: For those who don't want to go through this whole part, there's a TL;DR near the end. For reference, the computation of the FAT size all done in the GetFATSizeSectors(), the code of which is at [1]

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

Hi Ady, On 2016.02.25 02:08, Ady via Syslinux wrote: > There is an "extra" sector, in comparison to... what exactly? Sorry if I wasn't clear. I think I implied that the Large FAT32 fat size had an extra sector compared to minfatsize, when of course I meant the opposite (the Large FAT32 has one less sector than the minfatsize computed by the unpatched code, hence the check

forgive me.. i have no idea what im asking or if its possible... i have 2 partitions as follows and am using the std windows xp bootloader to boot xp - ntfs (windows xp) - fat16 stupid question is... can i use syslinux, isolinux, memdisk or some combo there of to place a bootable cdrom iso image on the fat16 partition and then have a boot menu with something to the effect of : 1) winxp as

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"

On 2016.02.26 15:32, Ady via Syslinux wrote: > Regarding the "+1", when talking about the math (not the computer code > to achieve a result as accurate as it can be) Well, sorry, but I will not dissociate the context of application from the formula itself. I thought this was implied into what I wrote, which was in the context of fixing a computation algorithm bug. The sole

On Tue, 08 Jul 2014 15:54, H. Peter Anvin wrote: > >On 07/08/2014 11:26 AM, Ady wrote: >> >> It's interesting that you ask this, because every document related to >> newmkfloppyimg.sh specifically recommends adding: >> floppy c=$CYLINDERS s=$SECTORS h=$HEADS >> to the MEMDISK arguments. >> > >It would be important for floppies to know

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

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

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

When trying to installing Syslinux on a FAT32 drive formatted using Ridgecrop's Large FAT32 formatting tool [1], the installer will bail due to the minfatsize check, as there is an extra sector being used. This fix addresses that. [1] http://www.ridgecrop.demon.co.uk/index.htm?fat32format.htm -------------- next part --------------

Hi, "Mircea Popescu" <nufarul.alb at go.ro> schrieb am 29.01.02: > I have this problem: > I've partitioned my hard drive with PQMagic 7 in the following way: > hda1 - fat32 > hda2 - ext2 > hda3 - fat16 > hda4 - extended > hda5 - Linux Swap > hda6 - fat32 > hda7 - ext2 > hda8 - fat32 > > I've put syslinux on

Windows uses several sectors in the _partition_ for booting. Windows only uses sector 0 of the Disk (the MBR), and does not use any other sectors. Other boot managers and copy protection software (the stuff that comes with TurboTax this year uses track 0, evil...) For FAT16 filesystems, only the first sector is used. For FAT32, there are 32 sectors that are reserved by the FS, and I've come

Hello, I found a bug in Latest wine releases. I found it in the wine-20040914,wine-20040813 rpms for the RedHat Distributions.I had tested it in RedHat-9.0,7.3 systems. The bug is that, when we try to open(file->open) from any windows applications, the application hangs. For eg., even in Notepad, when I click File-> Open, wine shows the following error. --------- wine: Unhandled

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

Hi! I have a question about filesystems. I'm running a fairly recent version of WINE from CVS on RH7.1 (Kernel 2.4.6). I have Win98 installed for on a partition. I user WINE to run Quicken2001 and Word97. When I'm running Word, I click on the 'open file' button, a get a message: err:dosfs:DRIVE_ReadSuperblock The filesystem is not FAT !! (device=/dev/hda1)