similar to: Possible memdisk issue

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.

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

> 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

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

I would like to boot FreeDOS ISO image from USB memory stick using syslinux. I have done following: 1) I created a partition to my 2GB memory stick: root at debian64:~# fdisk -lu /dev/sdb Disk /dev/sdb: 2013 MB, 2013265920 bytes 62 heads, 62 sectors/track, 1022 cylinders, total 3932160 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size

I'm having trouble getting memdisk 6.03pre18 to boot large floppies and wondering whether I'm doing something incorrectly. 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz 2) gunzip FDOEM.144.gz 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img 5) Use following pxelinux.cfg: LABEL works LINUX syslinux/memdisk INITRD

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

2018-06-26 2:10 GMT+08:00 H. Peter Anvin via Syslinux <syslinux at zytor.com>: > On 06/18/18 13:06, R S via Syslinux wrote: >> The narod.ru images are super outdated (FreeDOS kernel 2028) unfortunately. >> >> If you are interested I could provide a 5MB FDD image template based on >> FreeDOS 2041 kernel (the latest available at that time in 2014) where you >>

Dear Syslinux folks, For a firmware update I am following the Gentoo Wiki [1] to create a floppy image of 20 MB, so that the vendor update utility fits. Unfortunately, FreeDOS does not load, and it seems to hang loading the FreeDOS kernel. The original FreeDOS image boots. Do you know if that issue is memdisk related? It?s started from GRUB with the commands below. linux16 /boot/memdisk

In other words: I'm suggesting to use WinImage as it also allows easy injection of new files *and* updating of already existing files. May I ask which vendor is distributing a DOS FW update that is 20MB? I'd like to see the files. Sometimes you just need the .bin/.rom and the actual FW update EXE and it would fit a 5MB FDD image. On Mon, Jun 18, 2018 at 2:03 PM, R S <rene.shuster at

>I tried the commands that you have presented and I running into >problems. I tried the ideology that you presented with both 32 and 16mb >configurations with no luck. Is there something that I'm missing? > >The win98se boot disk boots (just downloaded it from bootdisk today) so >I used that as a based for the boot file. > >Item 8c works fine (1.44 image) but 8b

Hi gang I just did a really stupid thing... I did fdisk and removed the ext3 partition on my 500GB external USB drive, thinking I was working on a usb stick instead. ugh. then I did 'mkdosfs' on it. ugh ugh. Before messing with it any more at all, what good ideas can you all suggest for trying to get my data back? Please don't tell me it's all gone (though I"m afraid it

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

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

On Sat, May 24, 2014 at 11:22 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 05/24/2014 01:58 PM, Ady wrote: > > > > My guess is that if this was a bug in FreeDOS (as in "something" that > > has nothing to do with the syslinux.com command) then it would be > > somehow triggered by other DOS programs trying to write to the MBR. > > Considering

Hello, there is a "fdboot.img" floppy drive image included with FreeDOS ISO file. It's a floppy image file: root at debian64:~# file -s /home/martin/FreeDOS/isolinux/fdboot.img /home/martin/FreeDOS/isolinux/fdboot.img: x86 boot sector, FREE-DOS BEta 0.9 Bootloader KERNEL.SYS, code offset 0x40, OEM-ID "FreeDOS ", sectors/cluster 2, root entries 112, sectors 720 (volumes

>Hello, > > >I am managing 15 separate boot disks with various network disk images. >These disk images are used for network installs of Windows OS's. >Basically the network boot disk contains dos, the network drive in >question and the connection information to the shared server for doing a >ghost install. > >The problem is the 1.44 disk doesn't hold enough

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]

Thanks for Remko for his help to solve the fractional cylinder problem. But there is the second problem, the boot disk failure (see below << [B]) ... command line: initrd=disk.img harddisk c=2 h=256 s=63 BOOT_IMAGE=memdisk Disk is hard disk, 16128K CHS=2/256/63 <<<< [A] ... Loading boot sector... booting... SYSLINUX 2.04 welcome! boot: 1 [single dot]