similar to: Any errors in the process for creating bootable DOS image

It is now possible to build a bootable floppy image which contains HDT, with my patch applied to Erwans HDT branch: http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=16b37fe2266c920087f88cdec94243b71218d871 Unpack the Syslinux archive and build whole Syslinux first, then cd to ./com32/hdt/ and make hdt.img $ make $ cd ./com32/hdt/ $ make hdt.img Now you have a 2.88 MB floppy image which

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'm running into some issues with regard to isolinux and memdisk, and am not sure where to ask/look in the best way possible. These are DOS-related issues. So here goes: * Can MEMDISK map a imagefile (compressed? harddisk?) to more than (and/or beyond) 4GB of memory? Say you'd have 8/16GBGB and want 4GB available to the user so might as well use the other 4/12GB for MEMDISK. Or max

I am trying to acheve pxe booting of a image of barts boot disk (www.nu2.nu). I have managed to get LTSP booting via pxelinux, so I know my dhcp/tftp servers are ok. However when I try to boot memdisk with either a stock suselinux boot image file (taken from SuSE 9.1) or my dos disk (created by dd if=/dev/fd0 of=/imagefile) I get output like MEMDISK 2.08 command line : BOOT_IMAGE=memdisk

Trying to be not long, on x86 I have 3 floppies images boot, root-1, root-2 Booting from boot image with no problem, I try reading root-1 and root-2 image in raw format. Reading root-1 and root-2 is made from boot init script, using klibc-1.5.9 or klibc-1.5.10 with debian insmod patch, and a vanilia linux-2.6.24.7 root-1 and 2 images are smaller than 1440 kB and are made the same way with cd

I can't get fd.c32 to load a DOS 6.22 boot floppy it says: boot: fd.c32 . >>>! Non-System disk or disk error Replace and press any key when ready "chain.c32 fd0" doesn't work either. This floppy boots fine from the bios. fd.c32 does work with a Win98 boot floppy. Thanks for any help -Aaron

Hi! I've got a USB key with several tools (small linux, memtest86+) booting via syslinux. But now I have to add powermax.exe (a MSDOS tool to test Maxtor disks) on this key. As I've always been on Unix/Linux system, I don't know what to do to run powermax.exe from syslinux. I've made a boot floppy disk and tried to copy everything on my usb key and put the command.com in kernel

Hello, I'm trying to create and boot a Win98SE-DOS OS through Hard Disk emulation. My src files are from a Win98SE 1440K floppy image file, with a x86 boot sector (dl'd from the net - I have no floppy drive and a slow net link 3.2KB). I don't know what to put into the partition boot record of my image and how to load dos.bss properly (the docs explain for floppy images not for HD

Hello syslinuxers I'm stuck with a scientific problem which gives me headaches: I have a laptop (Gateway MX3410) which has a SD memory card reader. Recently an interesting thought crossed my mind: why don't I setup a 2GB SD card as a harddrive and put some rescue tools on it. So I dug on the net and I came across the idea of using memdisk to boot floppy images without the need of a

Hi all, I try to boot an msdos system using pxelinux and memdisk on my PC engines Wrap-2.c card and I have problems with it This is what I see: PXELINUX 3.11 Debian-2006-03-16 Copyright (C) 1994-2005 H. Peter A boot: msdos Loading memdisk.... Loading images/msdos/msd622bd.dosim......................... Ready. dp83815: Setting full-duplex based on negotiated link capability. MEMDISK 3.11

hello guys. i've been digging through the mail list archive for a few days, to no avail. i hope you can help me : i want to create a bootable DOS image, approximately 25MB , to boot a system from the network, using PXELINUX . now, i've followed some instructions on this list, but the image always fails to boot. the only thing which succeeds, is to take a bootable DOS disk, put it in

Hi, I looked at the web http://clic.mandrakesoft.com/documentation/pxe/ch06.html, and create a floppy boot image by : dd if=/dev/fd0 of=boot.img. I copied the boot.img to /tftpboot, and my /tftpboot/pxelinux.cfg/default is : default freedos display boot.msg label freedos KERNEL memdisk APPEND initrd=/boot.img When I boot up my client, it shows : could not find kernel image: memdisk What

hi, i want to load a small linux system with memdisk and when the linux system is started i want to mount the memdisk-image. is this possible? if yes: how can i mount it? when i try to mount /dev/fd0 it accesses to my floppy drive. bye, johannes (jaf) _____________________________________ Varium et mutabile femina semper est!

I would like to be able to create a 2.88MB bootable floppy image to hold the kernel and initrd -- will be used for automated install. In various newsgroups there have been many posting attempting to describe how to achieve this, but none of them is complete. Can syslinux be used to achieve this? What about memdisk? Thank you in advance. Fet

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

I have the same problem. I can not boot a floppy disk. Once I did it but no longer I can do this. I think there is some problem in the new versions of PXELinux. -----Original Message----- From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] On Behalf Of Quinn Plattel Sent: Thursday, September 28, 2006 7:04 PM To: syslinux at zytor.com Subject: Re: [syslinux] problem booting

Hi - daft one for Friday morning coffee break: I have been trying to mount floppies on a couple of CentOS5 servers - the usual "mount /dev/fd0 /mnt/floppy" (yes, /mnt/floppy exists!). On both servers, the mount command just doesn't come back and I have to hit CTRL-C. I have tried different media and also changed the floppy drive on one server, /dev/fd0 is seen as present on both

hi there. I'm trying to boot several OSes floppy images from a cdrom via memdisk. Actually, Linux and FreeBSD boots fine, but, while i'm using the same method, I couldn't get into booting netbsd nor openbsd. The boot process seems to hang up, in those two cases, when the second stage native bootloader try to load the kernel (i'm not absolutely sure about this). The native first

>+ booting floppy34.fs image from the CD works correctly (no ISOLinux, in >built BIOS emulates the floppy) Hi, have you tried the following (Isolinux direct emulation): KERNEL 34FS.IMG should function the same as if direct 1.44MB eltorito emulation was used. but using MEMDISK it fails? KERNEL MEMDISK APPEND INITRD=34FS.IMG that's all I can come up with .