similar to: chain / memdisk / mboot of memtest86, SBM loader.bin, ISO image

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

Matt Fleming 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... ok > > Booting kernel failed: invalid argument > > boot: > > What was the previous version

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've been trying to figure out how to netboot memtest86 since terminals don't have local drives and I don't want to have to fish for disks with the memtest program on them for my machines that do. I'm in an etherboot environment where I can't figure out how to create a network tagged image of memtest86. Evidently I can use pxe somehow to allow me to start the memtest.bin file

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

On Wed, 24 Jul, at 09:04:17PM, Victor Sudakov wrote: > 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: What was the previous

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...

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

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

On Wed, 24 Jul, at 10:20:03PM, Victor Sudakov wrote: > Well, it's odd, PXELINUX 6.01 + memtest86 still works on VirtualBOX, > but not on any "real" NICs I have tried. The bug is entirely dependent upon the memory map layout of a machine. The layouts vary widely, even between machines from the same vendor. -- Matt Fleming, Intel Open Source Technology Center

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 All, I'm experiencing a problem with some mails in deliver. Here the logged error message: deliver(stefan at roese.nl): 2009-05-06 11:57:36 Panic: file index-mail-headers.c: line 141 (index_mail_parse_header_finish): assertion failed: ((match[match_idx] & HEADER_MATCH_FLAG_FOUND) == 0) deliver(stefan at roese.nl): 2009-05-06 11:57:36 Error: Raw backtrace: /usr/lib/dovecot/deliver

Hi gang, I recently set up a smb server on rh7.2 to be able to share files with my 2k boxes. I am able to see the Linux smb server via network neighborhood on the win2k boxes but cannot connect. I get a path not found error. Can anyone give me a few pointers where the problem may be and how to fix? Thanks in advance for all replies. tt

Hi list, Can someone please clarify the difference between variables %S %U %u in smb.conf? It is not clearly defined in man smb.conf page (at least for me) %U - session username (the username that the client wanted, not necessarily the same as the one they got). %S - the name of the current service, if any. %u - username of the current service, if any. That is "session username",

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

I originally asked in a hardware/software forum, but, got basically no results. It occured to me that if anyone would know, it would be you people. What I'm wanting to do is set up a rescue disc for a really old laptop. It needs to boot up a linux based CD, hopefully with minimal to no working stuff on the harddrive (I plan to put a floppy image to be written to a disk when needed to do the

I am having a problem assigning write permissions to shares. I have joined my RHEL 4 server to our Windows 2003 domain and have gotten to authenticate through Active Directory. I can log on to the machine using my Windows AD account. However, any shares I create seem to be read only. I can't create files/folders in the shares or modify the documents from my Windows machine. One of my

We apologize for multiple receipts. -------------------------------------------------------------------------------- Eighth Real-Time Linux Workshop October 12-15, 2006 Lanzhou University - SISE Tianshui South Road 222 Lanzhou, Gansu 730000

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

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