similar to: Netbooting memtest86

On 2014?03?07? 18:24, Ady wrote: > Hi Steven, > > Perhaps this could be of some basic sample/help, being based on > Debian: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589 > > where: > _ if gpxelinux.0 is needed, it should probably be replaced by ipxe. > _ lpxelinux.0 (from official Syslinux archive) could optionally be > added. > > _ from the

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

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

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

I'm building a custom bootdisk that I would like to boot linux or boot memtest86 (www.memtest86.com). And I'm running into some difficulties with recent versions of syslinux. All I'm doing is making a new label in syslinux.cfg called memtest and giving it kernel memtest.bin. This has worked on and off for several recent versions of memtest. It worked in 1.67, broke in 1.70(loads

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 >On Wed, 24 Jul, at 03:48:14PM, Matt Fleming wrote: >> On Wed, 24 Jul, at 09:04:17PM, Victor Sudakov wrote: >> > 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...

Hi, I've been using pxe-enabled nic's with an lzpxe-etherboot image generated by rom-o-matic.net to boot a ltsp.org kernel, with dhcp 3 to use if statements to determine which filename option he gives to the pxe/etherboot dhcp client.Explained at http://www.ltsp.org/documentation/pxe.howto.html This works perfectly, except for the fact that you can't use 1 etherboot pxe image for

Hello, I'm trying to pass the serial port options to memtest86+ using Syslinux 5.01 but is not working. Debugging the memtest86+, the check at main.cpp function static void parse_command_line(void) if (*OLD_CL_MAGIC_ADDR != OLD_CL_MAGIC) return; Is being evaluated to true. What should I do? There is a way to instruct memtest to use the "old way" to pass

Hi! sorry for the top post. I have had some troubles in the past trying to make equipment to boot a floppy with MS-DOS that also used ms networking to access the network. Particularly the Gateway GSX 500 cannot have the onboard NIC with PXE enabled, as it eats about 92k of highmemory, which in turn makes impossible to start Windows XP setup due to low memory. On that particular machine I had

Hi, I have been trying to boot a PC based terminal using your PXELINUX project and I am having a problem. The Terminal (a Netier NetXpress XL2000) has a m-systems Disk-On-Chip 2000 flash memory module which is normally used to boot a cut-down version of WinNT. I work in a repair department where we often have to open up these terminals and temporarily install a hard-drive to reflash the

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

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

Additional information: I was tried it with 2 virtualbox (version 4.2.14r86644).1rst: debian weezy with isc-dhcp-server, pxelinux5.01, pxelinux 6.00, tftp-hpa2nd: empty virtualbox booting from virtual network card. So memtest 4.1 and 4.2 worked with pxelinux 4.06 Peter > Date: Fri, 28 Jun 2013 09:02:30 +0100 > From: matt at console-pimps.org > To: coolpet80 at hotmail.com > CC:

> Hello, > > FYI. This problem looks similar to the problem I reported in Februari > http://www.syslinux.org/archives/2013-February/019517.html > > Kind regards, > Wim. > > On 06/28/2013 10:02 AM, Matt Fleming wrote: > > On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: > >> Hi guys! > >> I tried to boot memtest86+ v4.2 (renamed memtest.bin to

On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: > 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

Hello, FYI. This problem looks similar to the problem I reported in Februari http://www.syslinux.org/archives/2013-February/019517.html Kind regards, Wim. On 06/28/2013 10:02 AM, Matt Fleming wrote: > On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: >> Hi guys! >> I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and >> i have issues to boot it with

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.

On 09/13/2013 06:36 AM, Gene Cumm wrote: > 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

Hi, I just upgraded syslinux to version 3.0.7 from 2.13, but my pxe client got some warning messages. The pxelinux config file looks like: default memtest timeout 70 prompt 1 #--------------------------------- label local localboot 0 #--------------------------------- label memtest # note! *.bin is specially purpose for syslinux, # do NOT use memtest86.bin, use memtest86 instead of