similar to: memdisk problem

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

Hi I'm using memdisk as part of CD Shell' isolinux. I've created custom floppy disk image 8440kB size. I've put FreeDOS kernel and bootsector into the floppy. Boot process goes fine with this command: isolinux /boot/memdisk initrd=/ximg/fdos.img c=60 h=8 s=36 floppy The problems begin when I try to run FreeDOS memory manager emm386 from the floppy image. my config.sys: ...

I have many hp laptops that boot msdos with memdisk + pxelinux perfectly. However, I recently have the need to usb boot msdos with syslinux. And memdisk. When the dos Image loads I get "loading bootsector..." and then it halts. Sometimes I can get "starting ms-dos" but freezes as well. I'm trying to boot clean msdos floppy image created with winimage. I'm using

On Thu, Feb 2, 2017 at 1:26 PM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Hi all, > > > > I have observed a problem where, under legacy BIOS booting mode on the > > DL360g9, memdisk fails to execute. The same mechanism works fine on the > > DL360g8. The system displays the below on the console and ceases to > > respond and must be

Hi, As the subject suggests, I am trying to remote boot a Mini-ITX system. I am using PXELinux as the bootloader, and Memdisk (2.11) as the 'kernel'. My ramdisk image is a hard drive image based on PC-DOS. Two things go wrong during the boot process. 1. "INT 13 08: Failure, assuming this is the only drive" message 2. "Loading boot sector... booting..." message,

Hi, It is becoming a bad habit for big OEM vendors to sell computers & servers without floppy drives. Unfortunatly both Windows and Linux (RedHat) need a floppy drive to load storage drivers etc. during installation. This is what I was thinking: Use ISOLINUX and MEMDISK to load a floppy image of a driver disk into memory as a viritual floppy drive "A:"/"/dev/fda" And then

Like a lot of people, I am using SYSLINUX + MEMDISK to make a technician universal boot disk on a USB key (I have done the same with ISOLINUX and MEMDISK for a CD using Bart's method for bootable CDs) I *LOVE* Syslinux and MEMDISK, and what I can do with floppy images! I have a few problems that have cropped up, most notably the DOCMEMORY program (www.simmstester.com) boots fing, but the

Hi, I am trying to load an disk image as Floppy=1, og B: using ISOLINUX. My Config file reads: ------- Begining Of File ------- KERNEL MEMDISK APPEND raw floppy=1 initrd=CERC6.IMG ------- End Of File ------------ --- MEMDISK Output Snip ------ Ramdisk at 0x03b58000, length 0x00168000 command line: initrd=CERC6.IMG raw floppy=1 BOOT_IMAGE=MEMDISK Disk is hard disk, 1440 K, C/H/S =

I'm having trouble getting memdisk 6.03pre18 to boot large floppies and wondering whether I'm doing something incorrectly. 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz 2) gunzip FDOEM.144.gz 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img 5) Use following pxelinux.cfg: LABEL works LINUX syslinux/memdisk INITRD

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

I have been using pxelinux for quite a while to automagically build linux boxes with great success. Thanks to everyone involved! Now, I am trying to download a floppy image and get that to boot. My conf file looks like: default sir4 label sir4 kernel ia32/memdisk append initrd=ia32/sir4/floppy.img Everything starts off fine. pxelinux loads I see it get the conf file. gets memdisk

Hello, I am a *nix newbie I am trying to boot a DOS boot disk using PXE (to Ghost on windows images). We have an existing PXE server which successfully serves out PXElinux and Fedora builds based on that but my floppy disk image with memdisk isn't working I have tried a few different floppy images which people have posted as ones that work for them but I doubt the disk is the problem

Hi, I stumbled on a rather odd problem. A brand new HP Compaq dx2200 computer didn't want to boot up pxelinux+memdisk image. The computer just gave "Disk I/O error" and stopped there. Workaround was rather simple... Just attach regular floppy drive to the motherboard and everything started working fine. I tried with older 2.05 (pxelinux+memdisk) and newer 3.31. Both produced

We are working on a prototype for an installation system, and it would be very useful if we could load two memdisk images, having one pretend to be normal A: drive, and another as B: drive. I have read through the docs as well as done some google searches, and haven't seen such a thing described. We have one person who has asm programming experience, and we were wondering if we could get

Hi, I once again have a problem with memdisk failing to boot a harddisk image to update my Thinkpad X200s firmware. I extracted the harddisk image from the eltorito type 4 ISO using the isobar tool. Then I added memdisk using this image as initrd to my grub, rebooted and it boots into PC DOS and then freezes (ctrl-alt-del still works to reboot the system). Inside Qemu however it works fine

I tried to use memdisk 2.06 to boot a floppy image on my notebook which doesn't have a floppy drive. The boot failed, because the bootstrap code tried to reset the floppy drive (int13, ah=00). Memdisk passes reset calls on to the original int13 handler, which returns failure, because there is no floppy drive to reset (#1). Also i noted that some boot records (notably some created by

I just wanted to pass on some information regarding the behavior of memdisk that I was observing. I have been trying to set up pxelinux/memdisk on a network with a series of machines. I am trying to boot a 2.88MB DOS image. This image worked fine on all but one of our machines. The machine had a usb floppy device. Now the machine would boot the DOS image fine if the usb floppy device was

<..trying again after changing outgoing e-mail options to avoid bad headers...> I'm trying to use syslinux 3.08-pre11 on a Gateway E4000 with the (sample) config file below, and the ramdisk images fail to boot if selected as a menu option, but do boot if I press ESC and type the command line manually. The two options are for the same floppy image, but the first is compressed, the

Hi Peter, I'm using isolinux and memdisk to create a multiboot rescue cd for personal use as described on Bart's page (www.nu2.nu). One boot item is to boot DOS 7.1 from Win98SE with a lot of other staff for emergencies. This DOS bootimage puts all necessary stuff into it's own ramdisk (XMSDSK). Some progs on the ramdisk needs access to floppy drive A: and unfortunately I've no

Memdisk 2.08 cannot boot an XP boot floppy image (XP appears to use WinME boot files for its bootable floppy). For example: http://members.iinet.net.au/~bdriver/bootdisk/download.htm This disk will not boot with Memdisk (Memdisk starts to load the image and then hangs). I'm using Bart's tools to build a boot CD: http://www.nu2.nu/corpmodboot/ Which uses Isolinux and Memdisk.