similar to: Boot another *.efi from SYSLinux?

> -----Original Message----- > Hi! > I am currently trying upgrade my bios pxe server with additional uefi support. > My current using memtest86+ doesn't seem to support uefi, so I would have to > use memtest86, as it supports this. > But the memtest86 file itself is an *.efi file. When booting this one directly > without syslinux, its working. > > But I want to

I've just spent at least half an hour swapping files, downloading things and stuffing around with memtest86 and memtest86+. I can't get either to start from pxelinux. Currently I have "memtest86" as the filename, and i'm trying to load it direct (not trying to use memdisk or anything). This just results in a near instant reboot. Am I doing something wrong? I can't

Hi there, ----- Original Message ----- From: koxudaxi at gmail.com To: syslinux at zytor.com Date: 01.04.2013 10:00:27 Subject: Re: [syslinux] Problem with pxelinux 5.0 and memtest > On 04/01/2013 09:28 AM, H. Peter Anvin wrote: >> On 03/31/2013 05:26 PM, Koudai Aono wrote: >>> I ran the test on a x86 emulator is called Oracle VirtualBox. >>> I think it might not be

Hello list, any try the new memtest86 v3.2 with isolinux 3.11 cd and pxeboot? How is the proper way to chainload memtest86 I was tried: label memtest kernel memtest.bin but, nothing happens just a weird hang (my older versions of memtest hangs too). Anyway chainloading in a floppy image with memdisk on CD or pxeboot was fine but if I use memory to emulate a floppy I was not using this memory

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

On 2014/3/7 ?? 05:23, Gene Cumm wrote: > On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: >> Sorry for the confusion, I am actually using 6.02. It turns out that I was >> trying to use the 32-bit efi binary to load 64-bit kernels. I switched to >> using "syslinux64.efi" but it hangs during boot, just before loading the >>

Hello all, At the end of README.menu there is : "... It is also possible to load a secondary configuration file, to get to another menu. To do that, invoke menu.c32 with the name of the secondary configuration file. LABEL othermenu MENU LABEL Another Menu KERNEL menu.c32 APPEND othermenu.conf" I'm unable to have such a conf. working. tftp logs shows

Deal developers, I'd like to follow the thread http://www.zytor.com/pipermail/syslinux/2013-April/019761.html but change the subject to 'pxelinux 5.10 and memtest86+ 4.20' and provide more test cases. The pxelinux before version 5, e.g. version 4.06, worked very well with memtest86+ 4.20, all my PXE client machines, including VMWare workstation 9, VirtualBox 4.2, and all the real

Hi! At first thanks for your great work! I started to make multiboot CDs 1,5 years ago, with Bart Lagerweij 's utils. I have a problem with the memtest86 floppy image, made by the authors in the .zip file, downloadable from it's homepage, when I use diskemu. Some days ago I found on Bart's page a new method to select boot images on CD with syslinux/isolinux/memdisk. I thought this is

Hi guys! I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and i have issues to boot it with pxelinux 5.x and greater.Pxelinux 4.06 works fine both memtest 4.1 and 4.2. With version 6.00 no error message caught, only writes out dots. Any keypress does a reboot.With version 5.01 the error message is the follow:Loading images/memtest/memtest86... okBooting kernel failed: Bad file

On Thu, Sep 12, 2013 at 12:24 AM, Steven Shiau <steven at nchc.org.tw> wrote: > On 2013/9/12 11:55, Steven Shiau wrote: >> >> Deal developers, >> I'd like to follow the thread >> http://www.zytor.com/pipermail/syslinux/2013-April/019761.html >> but change the subject to 'pxelinux 5.10 and memtest86+ 4.20' and >> provide more test cases.

This isn't an esp urgent issue, but I'd like to use a certain RAM diagnostic (Doc Mem) which I've already posted a note about a couple of months ago. Simply won't work booting the floppy disk image via MEMDISK. In the interim, I've tried to resolve this by changing things on my side. I'm pretty sure it's a XMS incompatibility, as it fails differently depending on

On Fri, Jun 28, 2013 at 10:13 AM, Ady <ady-sf at hotmail.com> wrote: > But, in Syslinux 4.06, there is linux.c32, which is a sort of > introduction to Syslinux 5.xx (please allow me to be not strictly > accurate in this sentence in this context). > > Booting with any variant of Syslinux 4.06, but using linux.c32, > memtest would fail, which indicated some kind of problem

On 06/28/2013 04:07 PM, Gene Cumm wrote: > On Fri, Jun 28, 2013 at 12:53 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Fri, Jun 28, 2013 at 10:13 AM, Ady <ady-sf at hotmail.com> wrote: >> >>> But, in Syslinux 4.06, there is linux.c32, which is a sort of >>> introduction to Syslinux 5.xx (please allow me to be not strictly >>> accurate in

Hello, I'm investigating ways to boot a DOS floppy image stored on the FAT32 EFI System Partition using Syslinux and Memdisk. The system will be running Win8 using UEFI mode (GPT disks) and secure boot off. Change the Windows efi boot loader is the easy part... With the current syslinux's alpha version (6.0), is it possible to boot the syslinux's efi module from the FAT32 EFI

Dear Colleagues, memtest86 does not work any more after upgrading PXELINUX to 6.01. When trying to boot, I get the following message: PXELINUX 6.01 2013-07-04 Copyright (C) 1994-2013 H. Peter Anvin et al Loading memtest86... ok Booting kernel failed: invalid argument boot: The config is simple: DEFAULT memtest label memtest kernel memtest86 Any ideas? What additional information can I

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

Hi, I am trying the simple menu passswd in syslinux 3.11, and it seems that if I set the timeout option, the menu passwd is ignored. For example: ----------- default menu.c32 timeout 70 prompt 0 noescape 1 MENU MARGIN 5 MENU MASTER PASSWD $4$x$03NXHMe7QS0Ukxlkyh684LkWdqY$ label local MENU DEFAULT # MENU HIDE MENU LABEL Local operating system (if available) MENU PASSWD localboot 0 label

I've very new to this... what I want to achieve, is to have my clients network boot - and then be presented with a menu, allowing them *well, me* to choose what to do. Maybe, boot from the main hard disk, or boot a disk image from a samba share, or maybe even boot a CD image, instead of having the actual CD in the drive. Also, I would want to be able to change this menu, without actually

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