similar to: Creating a bootable FS thats larger than 2880?

Hi, I am trying to create an image that is larger than 1.44MB to be used with PXE boot (Ghost 8 requires 2 floppys). My current attempts result in the boot hanging at : Loading boot sector... booting... Starting... My config just says the following: default memdisk append initrd=smalldos.img I created the image following http://syslinux.zytor.com/archives/2005-August/005573.html (I am unsure

Hello, I'd be very grateful if someone can help me with the process of creating bootable floppy images to be used with isolinux/memdisk. I usually do the following: label image kernel memdisk append initrd=/bootdisk/image.img floppy (lines in isolinux.cfg file) Sometimes I pass memdisk the c/h/s parameters, depending on the image size. I have learned from this mailing list how to

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.

I just installed CentRC1 on a Dell gx150 as a test. I'm running into the same problem I had with Fc3. I get a partition table error when trying to use ghost8 to create an image. I was considering putting Cent4 on a ProliantDL380, FC3 installed on that machine but wouldn't boot up, stuck on Grub. I had FC2 on the Proliant but when FC2 went to the 2.6 kernel, it hung up on the Nash prompt.

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"

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 am trying to use symantic 8.X and ghost a disk. I get "Apllication Error 29004. Read sector failure, result = 1, drive = 0, sectors 2071692247 to 2071692255" when trying to ghost the disk. anyone done this successfully? symantic supports ext3. Thanks, jerry

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

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

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"

>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

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

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

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

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