similar to: Bug-report: Booting DOS images from USB

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

Helle, I'm facing a strange issue with memdisk The context : syslinux 3.75 gpxelinux.0 the gpxe stript called from a menu executed through menu.c32 : #!gpxe kernel /modules/memdisk initrd=/freedos initrd /freedos The output before the freeze : /boot.gpxe. ok /modules/memdisk. ok /freedos...... ok MEMDISK 3.75 3.75 Copyright 2001-2009 H. Peter Anvin et al e820: 0000000000000000

Hey, Firstly i like to say good work on your project, I love the ability to use PXE to ghost all my machines without the use of floppy disks. Now i managed to setup PXE correctly using a copy of Barts Boot Disk's with ModBOOT and modified it to meet our company needs. This works perfect and i can ghost not a problem using the standard loader prompt boot: and inserting text depending on

Franga . wrote: > > Now i moved to my next step of trying to get Simple Menu's working. My > problem occurs after selecting a menu option. The image loads and > gives me this output: > > command line: initrd=images/c201.img BOOT_IMAGE=memdisk Disk is > floppy, 1440 K, C/H/S = 80/2/18 Total size needed = 1491 bytes, > allocating 2K Old dos memory at 0x9f000 (map

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

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:

On 11/20/2014 03:21 PM, Konrad Rzeszutek Wilk wrote: > On Thu, Nov 20, 2014 at 03:48:47PM +0000, Ian Campbell wrote: >> The libxc xc_dom_* infrastructure uses a very simple malloc memory pool which >> is freed by xc_dom_release. However the various xc_try_*_decode routines (other >> than the gzip one) just use plain malloc/realloc and therefore the buffer ends >> up

On Thu, 2014-11-20 at 22:13 -0500, Gedalya wrote: > On 11/20/2014 03:21 PM, Konrad Rzeszutek Wilk wrote: > > On Thu, Nov 20, 2014 at 03:48:47PM +0000, Ian Campbell wrote: > >> The libxc xc_dom_* infrastructure uses a very simple malloc memory pool which > >> is freed by xc_dom_release. However the various xc_try_*_decode routines (other > >> than the gzip one)

- mkdiskimage -d image.dsk 2 64 32 - load it in dosemu and make it bootable with sys - isolinux: label 999 kernel memdisk append initrd=image.dsk harddisk c=2 h=63 s=32 results: memdisk 2.11 -> boots memdisk > 2.11 (up to 3.07) -> hangs The following message is printed in the boot messages > 2.11: MEMDISK: image has a fractional end sector The complete error message

Hi friends, I am new to this list and have some questions about PXE Booting, because its not working well. My Situation: I was preparing my Server like described on http://unattended.sourceforge.net And everything was working well, this means I was able to install Windows XP via PXE onto my clients. But now, I thought, It would be really a great Idea to make my clients able to

syslinux-3.0.7 Cannot boot memdisk+harddisk image. 1) mkdiskimage -d image.dsk 10 64 32 (I get a 10485888 bytes file) 2) start dosemu+freedos with image.dsk loaded as d: and do sys d: then copy some files to d: 3) reboot dosemu using image.dsk as c: to verify it's bootable, and it is C:\>ver FreeCom version 0.82 pl 3 XMS_Swap [Mar 06 2004 10:49:37] C:\> 4) isolinux.cfg: label 999

Im trying to boot memtest86 via pxelinux, memdisk, I found this advice on http://forum.x86-secret.com/viewtopic.php?t=2906 folks are making the image match a floppy size by one of the following: dd if=memtest86+-1.xx.bin of=memtest.img bs=360k count=1 conv=sync or dd bs=360k count=1 conv=sync if=memtest86+-1.xx.bin|gzip > memtest.gz I did the former, it did suppress the warning/errors I saw

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 power cycled. Updating the firmware didn't help. There didn't appear to be any similar issues on the mailing list unless I missed them. Wondering if

Package: xen-utils-4.4 Version: 4.4.1-3 When booting domU's running amd64 jessie, I notice some memory problems with xl. root at xen:~# pmap -x 4121 4121: /usr/lib/xen-4.4/bin/xl create --quiet --defconfig /etc/xen/auto/mail_deb80.cfg Address Kbytes RSS Dirty Mode Mapping 0000000000400000 144 128 0 r-x-- xl 0000000000623000 4 4 4 r---- xl

> -----Original Message----- > From: xen-staging-bounces@lists.xensource.com > [mailto:xen-staging-bounces@lists.xensource.com] On Behalf Of > Xen staging patchbot-unstable > Sent: 24 April 2007 12:16 > To: xen-staging@lists.xensource.com > Subject: [Xen-staging] [xen-unstable] hvm rombios: Fix int15, > func 0x86 (udelay). > > # HG changeset patch > # User

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

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

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