similar to: PXE booting ISO images with ISOLINUX

Hi, I'm doing a small hobby project writing some tools to put DOS boot images and Linux rescue images on a USB stick. For this I have partitioned my USB stick in 2 partitions, one 192MB partition with a VFAT filesystem (for the normal use) and a second partition with an ext3 filesystem. My aim was to provide a graphical menu (grub) to access the different images using memdisk. Since

It appears that the 3.74 completely broke the "keeppxe" directive -- not due to the command-line parser, but due to mishandling of the flag later. I consider this to be severe enough to do a short-cycle 3.75. As a result, I would like help with: a) are there any other bugs that snuck through? b) once I have a 3.75-pre1, I would really appreciate help testing it. The goal is to have

memdisk fails to boot HD image, if the system does not have an HD. Has any seen this? Is there a solution? memdisk output: Disk is hard disk, 9216 K, C/H/S = 9/64/32 Total size needed = 2063 bytes, allocating 3K Old dos memory at 0x9dc00 (map says 0x9dc00), loading at 0x9d000 INT 13 08: Failure, assuming this is the only driveold: int13 = f000799a int15 = f000f859 new: int13 = 9d000008 int15

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

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

While playing with some less than usual configurations, I've got bitten few times by geometry settings in case of, usually, microsoft[ish] systems. First two examples, then the improvement idea. Example #1 My usb stick has zip-compatible geometry, which should work fine both in hdd and zip modes. It usually does, at least as far as syslinux and normal software is considered - excluding

Hi We have a couple of FSC Computers here which seem to have a very strange bios. I am trying to boot a MS-DOS disk to flash an Scsi Raid controller. Since the computer doesn't have a floppy anymore I tried syslinux from an usb stick. The menu loads fine but I cannot boot disc images with memdisk on this computer. It works fine on others, of course. But now comes the weird part, if I use the

I have set up a RHEL 5.7 PXE server and trying to get a WinPE ISO to work. Currently PXE seems to handle the image properly but the process stops after Loading boot sector... booting... Full list of what is going on. Ramdisk at 0x72b9c00, length 0x0a680000 command line: iso initrd=../images/windows/winpe_x86.iso BOOT_IMAGE=../memdisk Disk is hard disk 0, 170496 K C/H/S = 340992/1/1 Total size

Hi there, while my memdisk setup works perfectly well an an Intel system it fails like this on a Via-C3 based Mini-ITX system (copied manualy, I hope I did not make a mistake): --cut-- Failed to Free base memory, sorry... MEMDISK 2.08 (Debian, 2003-12-22) Copyright 2001-2003 H. Peter Anvin e820: 0000000000000000 000000000009fc00 1 e820: 000000000009fc00 0000000000000400 1 e820: 00000000000f0000

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

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

A kind request for help please. MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below: MEMDISK 3.83: Ramdisk at 0x07eeaa00, length 0x007bc000 command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk MEMDISK: Image seems to have fractional end

I need some help with the following: My system hangs while booting from a CD using?SysLinux?(2.08).? I think that the?driver?hooks into the INT13 and INT15 handlers, writing their new handler hook into the Extended BIOS Data Area (EBDA) used by Phoenix BIOS for BIOS data information.? This area is?used and modified during legacy USB SMI's. I think that the hang happens because the new handler

Hi, just tried memdisk - it works, even with token-ring network cards! I've some problems with dos 6.22 on one machine, though. This one doesn't have a floppy controller (e.g. linux reports that it didn't find any controller). The Dos 6.22 boot disk is loaded, then the boot sector is started and tells me that it can't load the system (German message: 'Kein System oder

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

My system is hanging up when attempting to boot a bootable floppy disk image Does the following info tell any story as to what's happening? Thanks. LABEL dosdiskimage KERNEL memdisk APPEND keeppxe initrd=dos.img floppy Loading dos.img ............. Ready. MEMDISK 3.11 2005-09-02 e820: 0000000000000000 000000000009fc00 1 e820: 000000000009fc00 0000000000000400 2 e820: 00000000000e0000

Hi, I'm trying to boot Feature Tool 2.08 (free download from http://www.hitachigst.com/hdd/support/download.htm) from a pen drive via memdisk. QEMU can boot the pen drive all right, my ThinkPad can't: Loading ftool208.img.........................ready. MEMDISK 3.53 2007-11-17 Copyright 2001-2007 H. Peter Anvin e820: 0000000000000000 000000000009f000 1 e820: 000000000009f000

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

hpa etal, Im trying to get PIRT running on an SBC which has no CD-ROM drive. (an 8 MB ISO which demo's RTAI - RealTime Application Interface, on linux patched with Adeos) (BTW, PIRT uses isolinux) anyway, Im trying to use pxelinux to chainload / memdisk / mboot it, Im having no success. Ive also tried booting memtest86, which I can boot on my laptop using grub, ie title memtest

Good day to you, too. No worries about the delay. I understand how busy everyone is with SYSLINUX. Gladly, the project continues to develop and improve. With that said, thanks for today's flurry of activity regarding my reported problem. Impressively, the debug version of MEMDISK that you had directed me to use appears to have done the trick. Results below. command line: