similar to: problem loading a dos bss

I dont know if this will be of any interest to you guys. I have a lexar 1GB flash drive. I used the mkdiskimage script and then did syslinux as described in the readme.usbkey. (the script took a REALLY long time too) I booted into 3.7 knoppix. Copied all the directories onto the key. Then copied the contents of the /boot dir into the root dir. I renamed isolinux.cfg to syslinux.cfg I had

Hi. I've recently picked up a 256MB compact flash card and CF->IDE adapter. I'm wanting to put a smaller version of knoppix on here. I came across miniknoppix here: http://www.inittab.org and decided to have a play around with that. So far I have opened up the ISO image and copied all the files out. I have put a boot sector onto the CF by putting the CF into the IDER adpater then

I used syslinux 4.03 for my brand new usb-stick (16GB FAT32, no Partition Table). It works, but on some computers i get "boot error". My investigation reveals three bugs in the boot code. Int 13 function 8 destroys the contents of register ES. Ah, now it is corrected in version 4.04 pre 5. Well done. I am happy now. But there are still other bugs. Look on version 4.04 pre 5,

Hi, The bios is not able to boot from usb, but only from floppy. I want to boot an Ubuntu-installation from usb. The iso-file was moved with usb-creator to the usb-stick. I have got a boot-floppy, which starts an DamnSmallLinux usb-stick. But this bootfloppy doesn't start the Ubuntu-usb-stick. Which parameters in syslinux.cfg I must change to start Ubuntu-Linux? There are the following

In Syslinux 6.03-pre6: _ The txt/html/*.html files are currently created 3 times, one for each firmware. I think they should be created only once (under the main txt/html/ directory), just as the rest of the documentation is. In that case, the <respective_firmware>/txt/html/ subdirectories should not even be created. _ The bios/dosutil/ directory contains copybs.com and eltorito.sys,

On Mar 4, 2014 7:42 PM, "Ady" <ady-sf at hotmail.com> wrote: > > > > In Syslinux 6.03-pre6: > > > > _ The txt/html/*.html files are currently created 3 times, one for > > each firmware. I think they should be created only once (under the > > main txt/html/ directory), just as the rest of the documentation is. > > In that case, 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

I'm building on Debian (Woody) though I don't think that's relevant. Having found no build instructions, no configure script I decided on 'make' It worked, except the ls command showed some files were not built because there are old versions in the tarball. I tried 'make clean all' but still I have old files: ls -ltr kwdhash.gen version.gen ldlinux.bss ldlinux.sys

"make install" fails on non mingw platform because "win32/syslinux.exe" isn't build. This patch removes "win32/syslinux.exe" from the "INSTALL_AUX" variable. It's already part of "INSTALL_AUX_OPT" allowing the installation to fail. Signed-off-by: Marc Kleine-Budde <mkl at pengutronix.de> --- Makefile | 2 +- 1 files changed, 1

> In Syslinux 6.03-pre6: > > _ The txt/html/*.html files are currently created 3 times, one for > each firmware. I think they should be created only once (under the > main txt/html/ directory), just as the rest of the documentation is. > In that case, the <respective_firmware>/txt/html/ subdirectories > should not even be created. > > _ The bios/dosutil/

> On Mar 4, 2014 7:42 PM, "Ady" <ady-sf at hotmail.com> wrote: > > > > > > > In Syslinux 6.03-pre6: > > > > > > _ The txt/html/*.html files are currently created 3 times, one for > > > each firmware. I think they should be created only once (under the > > > main txt/html/ directory), just as the rest of the documentation

On 2019-4-13 8:45, Lu Wei wrote: > On 2019-4-13 4:23, C. Masloch via Syslinux wrote: >> MS-DOS 7.10 (first appearing in MSW 95 OSR2, later re-used in MSW 98 >> and 98 SE) and 8.00 (MSW Me, and MSW XP DOS boot diskettes) both >> support FAT32 equally well. >> >> MS-DOS 8.00 (without some patches that are around) only supports >> booting in DOS mode from

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

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

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

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

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