similar to: what I'm doing wrong?

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

Hello, when testing FreeBSD-7.1-BETA i discovered that the floppy disk controller doesn't work correctly. Trying to format a floppy (perhaps with bad blocks) i get: Processing fdformat: ioctl(FD_FORM): Device not configured instead of the normal E letter. I then checked the same problem is present on FreeBSD-6.3 and it has been reported by Beech Rintoul (*) in 2006! Of course the floppy disk

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

Hello, I'm trying to boot a dos floppy stored on a disk image which is initially loaded over pxe using memdisk. I've created the disk image as follows: dd if=/dev/zero of=$IMGLOCATION/$IMGNAME bs=$(( 1024 * 1024 )) count=20 LOOPDEV=$(losetup --show -f $IMGLOCATION/$IMGNAME) MAJOR_MINOR=$(ls -l $LOOPDEV|awk '{print $5$6}'|sed 's/,/:/') DMSIZE=$(( $(ls -l

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: >* *>* syslinux: this

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

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

At: http://www.serverelements.com/naslite.php the following command is supplied near the bottom: **fdformat /dev/fd0u1722 ** I have plugged in my USB floppy drive and have a /media/floppy I get no such file or directory with this command. And what is this with a 1722 formatted floppy. What I do a man fdformat, 1722 is not listed....

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

I have a computer that dual boots between Windows and CentOS. Each has it's own hard drive. I suddenly have a problem with Windows, and may need to reinstall. I need it for applications like After Effects, Premiere, and other things that I am currently in the middle of a project with. It seems the system has become usnstable, it's preventing me from continuing to work, and I

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

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

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]

I experimented with floppy sizes. Eg. I used FDFORMAT v1.8 to format a Disk fdformat a: t82 s21 D10 (I even have a modified version of FDFORMAT that creates only 1 FAT to save space, but I'm not using that.) All the information is written nicely to the Boot-Record http://home.freeuk.com/foxy2k/disk/disk3.htm But SYSLINUX seems to ignore the information. While DOS boots fine from these

Hi, One of my clients has a mixed Linux/Mac OS/Windows environment in his office. He just purchased a 4 TB external hard disk, which he intends to use on his various workstations. Up until recently, I've been using plain old MBR/FAT for hard disks in mixed environments. Fire up fdisk, make one big 0b type partition, and then format it using mkdosfs. Unfortunately, there's a 2 TB limit

Hello, I'm working on the oscar-1.3 release with my Linux Itanium's cluster to test cloning process via systemimager. After having succeeded to boot my client node via the network, when running the following script : /var/lib/systemimager/scripts/ced1.sh rsync is able to get small files (e.g : mkdosfs). However, when the script tries to rsync the whole oscar image in the following way :

Quick summary: Syslinux stops at "Boot failed". Which, from a quick look at the raw disk image, seems to indicate that the boot sector loads but it fails to load the .sys loader. The details: I've been trying to load Linux (or etherboot...or anything at all that is not NT embedded) into a set of Compaq Evo T20 48/64 for a while now. What I finally managed to do is using the