similar to: Memdisk/floppy image question

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

Sorry for the delay, I should not send email on an holiday week-end. I'll try to answer all the questions by explaining what does work for me right now, and what I'd like to do. I have a script to create the a USB stick or an ISO image. The boot media contains many DOS images, and I use versamenu to select one of them. If my DOS image is smaller than 8megs, everything is working fine as

Hi All, Okay. Now I am confused. I have a bunch of virtual machines running under Virtual Box 3.2.12. I want to run them under KVM and drop Virtual Box from these systems. Supposedly "qemu-img convert" now supports direct conversion from vdi to whatever KVM uses. So I fired up the man page and got really confused. Then I fired up Google and got worse confused. Might I impose on

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

Latest syslinux 2.00 stable version from freshmeat. Are the programs that will just copy boot sectors or create boot sectors for /dev/hda1, /dev/hda2 etc.. that I can simply copy with a dd command? Mohan -----Original Message----- From: leaf-user-admin at lists.sourceforge.net [mailto:leaf-user-admin at lists.sourceforge.net]On Behalf Of Luis.F.Correia Sent: 05 November 2002 15:01 To: leaf-user

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.

I am trying to build a distribution without having to be root. The SYSLINUX installer 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

On Sat, Jul 25, 2015 at 3:58 PM, Pat O'Toole <pat at patotoole.net> wrote: > thank you very much!! You're welcome. Sometimes the hardest part is asking the right question. > ----- 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

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

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

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

since a few of you asked what I use it for...since I'm not a unix person.. I started using it back in 2002...to update hard drives that used a 'superfloppy format' (if anyone remembers the old DigitalWallet from Minds at work!) I fixed several of them after the company went belly up for photographer friends of mine. I mostly use it to do HD maintance...fixing fats...restoring backup

> 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

Greetings, I have a problem that is baffling me. My host machine is an older Dual Xeon machine that does not support HVM - PAE is supported. I have 2008.11 b98 installed as Dom0. I''m trying to install the same as a DomU. In the DomU, I''m starting the ssh service, logging in with X forwarding and starting the gui with: (dom1) jack$ pfexec gui-install The gui displays on my

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 :

I'm trying to make my own boot+root linux on a floppy disk this is what i am trying: dd if=/dev/zero of=disk bs=1k count=900 mkdosfs -F 12 disk mount disk mnt -o loop cp bzImage mnt/linux umount mnt syslinux -s disk dd if=disk of=/dev/fd0 but when i tray to boot with the disk i get "boot filed"

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