similar to: Is a directory

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]

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

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

On 02/26/16 09:54, Gene Cumm via Syslinux wrote: >> >> I'm not exactly sure how that would work (how would you mark those clusters >> as wasted when my understanding is that the FAT's can't provide any >> knowledge about them in the first place?) and unless it is automatically >> integrated and ran during the Syslinux installation, it sounds quite >>

On Tue, Jan 21, 2014 at 2:41 PM, mike setzer <qualityana at sbcglobal.net> wrote: > hello Gene, > > good to get your message > > I have not seen a link to reply to a particular thread, > so I am replying to you right now > hopefully the thread can be made to look right, also I double posted since my connection was lost > right during the first posting. Sorry, I

Hi! I was looking to download EXTLINUX in the following page : http://www.syslinux.org/wiki/index.php/Download But I do not see that it can be done. It is said that "The SYSLINUX download includes PXELINUX, ISOLINUX and MEMDISK as well." But, there is no word about EXTLINUX Please, advise Thanks Mau

Hi, I'm trying to install debian-6.0.5-amd64-CD-1.iso from USB memory-stick. The problem is, that Debian-Installer is not able to "Detect and mount CD-ROM" during the installation process. The USB memory-stick is a 2GB model containing MBR and FAT32 file system: # fdisk -lu /dev/sdb Disk /dev/sdb: 2013 MB, 2013265920 bytes 62 heads, 62 sectors/track, 1022 cylinders, total 3932160

Hello everyone, It''s a particularly slow Friday afternoon here, so time to try stuff out... I''ve just installed Instant Rails on a USB key, thinking it would be a great way of showing off Rails in general, giving a progress update to customers, trying out ideas, and generally all the other benefits that come from having a completely portable environment. However, the 168Mb of

Hi Gene, On 2016.02.26 11:49, Gene Cumm wrote: > I think there may be another answer to this: > > 1) a tool to fix the broken FSs by "wasting" the high clusters of the > file system, a non-destructive correction. As it stands they're > effectively wasted already and might risk a user thinking the file > system isn't full when in fact the FAT itself is.

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

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

I recommend someone verify that tar.gz and tar.xz files ( at https://www.kernel.org/pub/linux/utils/boot/syslinux/ ) unpack without errors. (I assume use of compression is in hope of saving download bandwidth) Regards

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

> Hello, > > Ady via Syslinux said on Mon, Apr 06, 2015 at 09:57:02PM +0300: > >Can 'syslinux.efi' v.6.03 boot some media formatted with ISO9660? > > Not at this time, no. > > It took me quite some time to find that :-( Google didn't really help. > > I'd like to get a bit more details on this issue: > > 1/ Using syslinux.efi for PXE

> > I need to create one bootable UEFI disk partition that contains all the > space on the disk. The steps must work in a shell script. Ideally with > syslinux/extlinux but if not possible then grub. > > > > echo format file system > sudo mkfs.ext4 -F /dev/${DISK_DEVICE_NAME_CURRENT_OS}1 > EFI requires a FAT filesystem. Ideally FAT32 but that might be encumbered

As I said before, booting is bigger than one bootloader. I am replying to what I think was asked. I might have misunderstood the questions. Whichever the case, this email is less about Syslinux itself. If this is considered too far off-topic in the Syslinux Mailing List, please receive my apologies. > > I still have the factory-set contents of my three USB sticks. A small

git://gnx.ath.cx/syslinux.git On branch for_hpa, I've got several groups of changes (listed bottom up) -chain.c32: the beginning of a DRMK loader; I still need to test this further and document/code what ones can possibly work -mtools/syslinux.c: Check to be sure fs is not NULL in case libfat_open() failed, like it can on a bad filesystem. Try to present a useful error rather than a seg

Hi All, Setup :- NAS device is running with 2.6.13 kernel and samba 3.0.32.I have connected a 4GB USB flash drive having FAT32.USB drive is available from the windows machine as connected shared drive. >From my windows machine when I am trying to copy the file (>1Gb) to shared USB drive(FAT32).it is giving error as shared USB drive is not reachable. File copy is working fine with small

On Thu, Oct 22, 2015 at 1:56 PM, Bruno Cornec via Syslinux <syslinux at zytor.com> wrote: > 3/ Using syslinux.efi in a FAT32 image (similar to the previous 2 > confs) stored on a iso9660 media by genisoimage and its > -eltorito-alt-boot -efi-boot $imagefile -no-emul-boot option doesn't > work. I get a red screen with debug info (attached). However, I'm not >