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

Displaying 20 results from an estimated 100 matches similar to: "Bug-report: Booting DOS images from USB"

2007 Dec 11
1
memdisk boot failure
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:
2017 Feb 02
3
memdisk load failure on HP DL360g9
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
2006 Feb 09
1
menu.c32 error "Windows is bypassing your startup files"
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
2006 Feb 09
3
menu.c32 error "Windows is bypassing your startupfiles"
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
2017 Feb 06
1
memdisk load failure on HP DL360g9
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
2014 Nov 21
4
Bug#767295: [PATCH for-4.5 v2] libxc: don't leak buffer containing the uncompressed PV kernel
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
2014 Nov 21
1
Bug#767295: [PATCH for-4.5 v2] libxc: don't leak buffer containing the uncompressed PV kernel
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
2009 Apr 26
3
memdisk issue with gpxelinux.0
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
2014 Oct 29
4
Bug#767295: xl: apparent memory leak
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
2017 Feb 02
0
memdisk load failure on HP DL360g9
> 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
2007 Apr 30
3
disk image creation, step by step
Hi, I am aware that it is impossible to netboot ISO files through pxelinux/memdisk and that there are multiple reasons for not even attempting it (like the operating system which will try to access a physical optical drive through its own drivers anyway, BIOS issues etc.). When people ask questions regarding ISO support in pxelinux/memdisk, they're mostly told to convert the ISO
2005 Nov 05
1
Cant PXE boot DOS image
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
2004 Apr 05
4
memdisk : booting OpenBSD and NetBSD
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
2005 May 17
1
chain / memdisk / mboot of memtest86, SBM loader.bin, ISO image
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
2009 Apr 14
5
"keeppxe" broken in 3.74 - short-cycle 3.75
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
2010 Dec 07
6
MEMDISK issue with OptiPlex GX280,620
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
2013 Dec 03
1
Boot iPXE from syslinux/isolinux
Christian Hesse <list at eworm.de> on Mon, 2013/11/11 18:41: > "H. Peter Anvin" <hpa at zytor.com> on Mon, 2013/11/11 08:09: > > On 11/11/2013 04:09 AM, Christian Hesse wrote: > > >> > > >> Let be know if you need any more info. > > > > > > Is anybody working on this? Is there a bug tracker I should
2011 Jan 25
2
MEMDISK issue with OptiPlex GX280,620
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:
2013 Nov 11
2
Boot iPXE from syslinux/isolinux
On 11/11/2013 04:09 AM, Christian Hesse wrote: >> >> Let be know if you need any more info. > > Is anybody working on this? Is there a bug tracker I should report > this to so it does not get forgotten? Could not find one for > syslinux. > Hm... it is odd that 03dda0f1 etc. didn't fix this. Since this is extremely likely to be dependent on the memory
2005 Feb 21
2
memdisk: regression: 2.11 -> 2.12 (up to 3.07)
- 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