search for: mkdosfs

...for floppies to know if the geometry that MEMDISK >guesses is the one that you actually intended. This will be in the >information that was snipped out. 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 of MB. And MEMDISK auto-determines those exact same numbers. But if I manually call mkdosfs there's a lot more out...

Greetings one and all. I'm a unix newbe....so deal with me here. I have a .iso copy of syslinux 1.67 (which actually might be ISOlinux??) that I boot from CD (ramdisk version...no HD needed)... but my version doesnt have the mkdosfs utility on it. I was looking for an executable that would work with this version... can someone point me toward such an animal??? :Pat

...d with syslinux? Basically given an existing floppy image, it creates a larger image and copies its contents over and sets up the bootsector of the newimage appropriately. ---- SCRIPT STARTS ----- #!/bin/bash NEWIMAGE=dosimage.img OLDIMAGE=oldimage.img # Name of an existing dos image SIZEMB=8 MKDOSFS=mkdosfs # binary for mkdosfs SIZEKB=`echo "$SIZEMB 1024 * p" | dc` NUMSECT=`echo "$SIZEKB 2 * p" | dc` MNTNEW=`mktemp -d /tmp/mntptnew.XXXXXX` # Create a mountpoint MNTOLD=`mktemp -d /tmp/mntptold.XXXXXX` # Name of an existing mountpoint # Create the filesystem OUTLINE=`$MKDOS...

...----- Original Message ----- From: "Gene Cumm" <gene.cumm at gmail.com> > To: <pat at patotoole.net> > Cc: "For discussion of Syslinux and tftp-hpa" <syslinux at zytor.com> > Sent: Friday, July 24, 2015 7:54 PM > Subject: Re: [syslinux] Looking for mkdosfs for Syslinux 1.67 > > >> On Fri, Jul 24, 2015 at 3:18 PM, pat via Syslinux <syslinux at zytor.com> >> wrote: >> >>> I guess...what I need is a 'mini unix'..that will boot from cd >>> and run in ramdisk..without installing anything on the HD......

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 of MB. And MEMDISK auto-determines those exact > same numbers. But if I manually call mkdosfs there'...

....44MB FreeDOS fdboot or fdoem to a 10MB version thereof, but trying to boot the result with MEMDISK led to an infinite loop of MEMDISK banners. That's where the discussion started, and turns out I titled the thread poorly: it really has nothing 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 differ...

...a few small scripts to do what I need over the years. I guess...what I need is a 'mini unix'..that will boot from cd and run in ramdisk..without installing anything on the HD... (I first found this via a link on an old minds at work webpage) that also has dostools..that include, of course, mkdosfs. True--this version must be really old....so a newer one would work just as good...just didnt know what to look for. Most newer versions seemed to be packages to install...maybe what I'm looking for is a unix recovery type disc?? Thankx all :) ~Pat

Hi On 23/07/2015 19:14, pat via Syslinux wrote: > I'm a unix newbe....so deal with me here. Don't worry. We are her to help. > I have a .iso copy of syslinux 1.67 (which actually might be ISOlinux??) I don't know how you got that but syslinux 1.67 was released more than 13 years ago and AFAIK never distributed as an ISO, at least by the project. I suggest that you tell us what

PS (addendum to my previous answer) I found the message announcing it in the archives: http://www.syslinux.org/archives/2002-February/000103.html However it is not available from the repository: https://www.kernel.org/pub/linux/utils/boot/syslinux/1.xx/ Didier

Thank you all very much!! ~Pat

...doem to a 10MB version > thereof, but trying to boot the result with MEMDISK led to an infinite > loop of MEMDISK banners. That's where the discussion started, and turns > out I titled the thread poorly: it really has nothing 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 diffe...

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

...at the time) Version 2.00 has just come out, give it a try and test it! What is the exact error given by syslinux? -----Original Message----- From: S Mohan [mailto:smohan at vsnl.com] To: leaf-user at lists.sourceforge.net Subject: CF Preparation Addendum to my post. I downloaded syslinux.lrp and mkdosfs.lrp from monkeynoodle.org. I copied them to my hard disk (/dev/hda1), did lrpkg -i syslinux and lrpkg -i mkdosfs. Both got installed into memory. I then gave syslinux /dev/hdc. Syslinux aborted saying sector sizes should be 512 and fs does not seem to be FAT. I executed mkdosfs /dev/hdc and mkdosf...

Hello Marc I am having the same issue mentioned below. I ran the mkdosfs, and received the following: /dev/sdb contains a mounted filesystem Can you help? On Tuesday 10 July 2007 11:16, Visar Zejnullahu wrote: >* hi I'm new to this, and already havin some trouble :( *>* *>* I tried to make my usb pen drive bootable with sysliux, but I got this *message: &g...

...typically needs root to do loopback mounting, but if you have MTOOLS, you can use that instead. This seems to work so far: #!/bin/sh # A minimal replacement for /usr/bin/syslinux; assumes that ldlinux.sys # and ldlinux.bss are available in the current directory. You must # specify locations of mkdosfs and mcopy. You need not be root. The # image will be overwritten if it exists, and an empty boot disk image # will be created. To avoid overwriting existing files, just omit # the two steps marked "Create fresh image" below. # General configuation IMAGE=`pwd`/lnx.img TEMP=bootsector.t...

Hi, i think this message should be removed ;) paradigm:~# umount /mnt2 paradigm:~# mkdosfs /dev/fd0 mkdosfs 2.5 (07 Jan 2000) paradigm:~# /tmp/syslinux /dev/fd0 paradigm:~# sync paradigm:~# mount /dev/fd0 /mnt2 VFS: Can't find an ext3 filesystem on dev fd(2,0). Flo -- Florian Lohoff flo@rfc822.org +49-5201-669912 Why is it called "common sens...

.... This is, in fact, required anyway for some specific reasons. That being said, if Windows accepts such a filesystem then Syslinux really should, too; perhaps with a warning. libfat is sometimes overly paranoid, on purpose, in order to avoid problems. It is also worth noting that someone ported mkdosfs to Windows; perhaps the best thing would be if this could be folded into the stock dosfstools upstream (if it hasn't been already): http://www1.mager.org/mkdosfs/ --- TL;DR: Ridgecrop's tool has a bug that needs to be fixed. They can either extend the FAT size to cover the entire volu...

...9;ve been attempting to create a bootable image thats double the size of the 2880 floppy disk. I can do the following to create a image that will boot with memdisk but i cant seam to get it to work with a larger size. What works... dd if=/dev/zero of=floppy288.img bs=1024 count=2880 mkdosfs floppy288.img ms-sys -1 -f floppy288.img mount -o loop floppy288.img /mnt cp msdos.sys /mnt/ cp io.sys /mnt/ cp command.com /mnt/ I then boot that using PXE and it works fine. The problem comes when i try to grow the image dd if=/dev/zero of=floppy288.img bs...

...artition) 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 using the same drive. Someone suggested that we try FAT16 filesystem which I created using Ubuntu disk utility and as well as mkdosfs command line utility. I reduced the partition size to 1 GB for FAT16. Neither worked. However a colleague created a FAT16 drive on a Windows machine and that booted just fine on the Dell. So my question is there some specific drive parameters I should be selecting when creating a FAT16 USB t...

Hi, I'm trying to build a bootable MSDOS disk and put it on a ISO with floppy and hard disk emulation. I want to use commonly available Linux tools like dd, losetup, mkdosfs, memdisk etc. I have done the following: 1. dd if=/dev/zero of=myImage bs=1M count=50 [ Builds a 52MB image ] 2. losetup /dev/loop0 myImage [Links /dev/loop0 to myImage file ] 3. vi /grub/stage1; %!xxd; [ NULL the partion tablei within stage1 ]; %!xxd -r; 4. cat /grub/stage1 /grub/fat_stage1_5...