search for: fat12

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

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

...) newmkfloppyimg.sh calls mkdosfs to create an enlarged floppy image > and then copies over the existing boot sector --- but the enlarged > floppy image might have a *different* underlying file system, in which > case that copied boot sector won't work. > > 2) That is to say, FAT12, FAT16, and FAT32 are different, and require > different boot sectors. (And in the case of FreeDOS, also require > different versions of kernel.sys.) > > 3) newmkfloppyimg.sh doesn't show the output from mkdosfs, so you won't > know whether the file system changed. >...

Hi, I'm getting a "Boot error" message when the BIOS tries to boot a SPI flash disk. I installed the syslinux on SPI flash disk mounted as a block device. The flash was formatted as FAT12. The BIOS emulates the flash as floppy. I also tried to install the bootloader using a DOS version of syslinux running on FreeDOS. If I use this way so the BIOS boots correctly. Why am I getting that error message?

...stem using equivalent UEFI boot methods (optical media, network boot). I am not saying that Syslinux is not at fault (probably lacking some feature), but rather that the results, at this time, might be suggesting that the firmware in this system could be a factor (too). I am attaching a zipped FAT12 image for you to test (hopefully it passes the mailing list filters). I would recommend using xorriso for testing, and no isohybrid (nor equivalent xorriso options either). A second (different, separated) test could perhaps use only UEFI boot -- not having BIOS boot would be uncommon, but I'...

...ng to do with MEMDISK! 1) newmkfloppyimg.sh calls mkdosfs to create an enlarged floppy image and then copies over the existing boot sector --- but the enlarged floppy image might have a *different* underlying file system, in which case that copied boot sector won't work. 2) That is to say, FAT12, FAT16, and FAT32 are different, and require different boot sectors. (And in the case of FreeDOS, also require different versions of kernel.sys.) 3) newmkfloppyimg.sh doesn't show the output from mkdosfs, so you won't know whether the file system changed. 4) After-the-fact, you can det...

...of how some of these > structures work and how they've changed over time. > That was what I was afraid of... > extlinux lets the Linux kernel do all of the heavy lifting of > installing the file then finding its blocks then performs the same > modifications as syslinux does on FAT12/FAT16/FAT32. extlinux has > less knowledge about ext2/ext3/ext4 and FAT12/FAT16/FAT32 file systems > (basically 0 outside the FAT32 VBR format) than syslinux does about > FAT12/FAT16/FAT32. > "kernel do all of the heavy lifting", i.e. it doesn't actually try to modify se...

> Hello, > > Gene Cumm said on Thu, Oct 22, 2015 at 06:39:44PM -0400: > >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

> 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 07/08/2014 05:55 PM, H. Peter Anvin wrote: > On 07/08/2014 03:05 PM, Alexander Perlis wrote: >> >> Question: what's special about the transition from 8203KiB to 8204KiB? >> Both have CHS=8/64/32 and both involve a fractional end cylinder. > > Fractional cylinders with floppy disks is almost certainly a very bad thing. > Agreed, but that doesn't appear to

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,

...ot leaf off the HDD(/dev/hda1) and backup to the flash (/dev/hdc1). I then disable the hard disk in the bios and check if I can boot off the flash. So far so good. I got a IDE CF adaptor recently. The CF card is a 32MB card. It gets formatted to FAT16 when formatted using DOS. I think DOS6.22 uses FAT12. I checked syslinux site and it says we can boot off FAT12 or FAT16 partitions. Problems occur only when cylinder count > 1024 or cluster size > 16kb. I remember Guitarlynn's oft repeated comment in the mailing list that syslinux gives a problem if partition is > 24MB. I also tried Ra...

Hi, I need a little information from you all. Kindly update me about the file systems that are supported by SYSLINUX for ramdisk image... Thanks in advance and regards, Pankaj Agarwal

Hi. I'm trying to install the latest version of syslinux on a FAT12 partition on a 16M Flash disk. However, despire reformatting, repartioning, and running both lock c: and fdisk /mbr, I keep receiving an "ERROR 440D: Unable to lock drive for exclusive access" message. Do you have any suggestions on how to bypass this problem? Please respond ASAP. Tha...

...TL;DR: Your work might only install a certain version. Without the history, you might fail other versions. >> extlinux lets the Linux kernel do all of the heavy lifting of >> installing the file then finding its blocks then performs the same >> modifications as syslinux does on FAT12/FAT16/FAT32. extlinux has >> less knowledge about ext2/ext3/ext4 and FAT12/FAT16/FAT32 file systems >> (basically 0 outside the FAT32 VBR format) than syslinux does about >> FAT12/FAT16/FAT32. > "kernel do all of the heavy lifting", i.e. it doesn't actually try...

...s, etc. > > Is that roughly it? I assume extlinux does the same thing, just has some > more knowledge about other filesystems? extlinux lets the Linux kernel do all of the heavy lifting of installing the file then finding its blocks then performs the same modifications as syslinux does on FAT12/FAT16/FAT32. extlinux has less knowledge about ext2/ext3/ext4 and FAT12/FAT16/FAT32 file systems (basically 0 outside the FAT32 VBR format) than syslinux does about FAT12/FAT16/FAT32. -- -Gene

Hi, I did found the problem, a combination of 2 factor. 1- I taught that I did install the latest syslinux, but in fact it was the 3.36 version. 2- Thank to kevin Connelly, he point me to a problem he got with mkdosfs command. The default FAT16 do not work, but the FAT12 do. By adding -F12 to the mkdosfs command fix the problem. The default F16 do seem to work for <8M floppy image. Thank you On 10/9/07, Gaetan linny Lord <email at gaetanlord.ca> wrote: > > Sorry for the delay, I should not send email on an holiday week-end. > > I'll try...

...able" by adding a few keywords at the end of this. Here's the info summary. Name : testdisk Arch : i386 Version: 6.3 Release: 1.el4.kb Size : 480 k Repo : kbs-CentOS-Extras Summary: Tool to check and undelete partition Description: Tool to check and undelete partition. Works with FAT12, FAT16, FAT32, NTFS, EXT2, EXT3, BeFS, CramFS, HFS, JFS, Linux Raid, Linux Swap, LVM, LVM2, NSS, ReiserFS, UFS, XFS I hope it actually "looks for file-system key stuff" instead of just examining the damaged blocks (often just missing the 0x05 (?) valid flag). If so, it looks "Mahvel...

...ot leaf off the HDD(/dev/hda1) and backup to the flash (/dev/hdc1). I then disable the hard disk in the bios and check if I can boot off the flash. So far so good. I got a IDE CF adaptor recently. The CF card is a 32MB card. It gets formatted to FAT16 when formatted using DOS. I think DOS6.22 uses FAT12. I checked syslinux site and it says we can boot off FAT12 or FAT16 partitions. Problems occur only when cylinder count > 1024 or cluster size > 16kb. I remember Guitarlynn's oft repeated comment in the mailing list that syslinux gives a problem if partition is > 24MB. I also tried Ra...

....S +++ b/diag/mbr/handoff.S @@ -43,11 +43,11 @@ * Install instructions (assuming your target is /dev/dev; file or block device): * * MBR: - * dd conv=notrunc bs=440 count=1 if=mbr_ho.bin of=/dev/dev + * dd conv=notrunc bs=440 count=1 if=handoff.bin of=/dev/dev * * VBR/PBR (should work for FAT12/16/32, ext[234]fs, btrfs): * echo -en "\0353\0130\0220" |dd conv=notrunc bs=1 count=3 of=/dev/dev - * dd conv=notrunc bs=2 count=210 seek=45 if=mbr_ho.bin of=/dev/dev + * dd conv=notrunc bs=2 count=210 seek=45 if=handoff.bin of=/dev/dev */ // #define DEBUG_MARKER1 /* Insert markers...