similar to: Chainloading the Menu.

Hello, I'm using Isolinux 3.11 to make a boot image with a variety of 2.6 kernels. I have two Intel-branded motherboards with i915 and i945 chipsets that have trouble booting with menu.c32. If I load the image from the isolinux commandline with a set of append parameters, it works. The same settings loaded from the menu.c32 causes the kernel to load and promptly hang. All I can tell is

DRMK (Dell Real Mode Kernel), now used in their DOS-based diagnostic images (probably about 2-4 years), has a rather unusual entry into the IO file (DELLBIO.BIN; similar to IO.SYS and IBMBIO.COM). After fumbling around with it over the last few days, I _think_ I've figured out the quirks of this entry point (and successfully tweaked chain.c32 to do such). dl Usual; drive number bp 0 cs

Hello, I have now spent 30 hours trying to get this working, so it's time to get some professinoal help. :) In a nutshell, I would like to have a sambda AD PDC that authenticates both Windows and Debian. On Linux, I would like to use SSSD. I have followed the steps on the wiki: - https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO -

I just started to play with syslinux 3.11 and have some problems with the configuration. I want to implement following: wait 5 seconds till the users chooses the right label. if nothing is done for 5 seconds it should boot from next boot device specified by the BIOS. I configured syslinux like that: default menu.c32 prompt 0 timeout 50 ONTIMEOUT localboot totaltimeout 200 display boot.msg MENU

On Mon, Jun 16, 2014 at 10:23 AM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > When chainloading one pxelinux from another (e.g., chainloading from say > pxelinux 4.07 to pxelinux 6.02), can one pass parameters or somehow control > the root directory and/or server IP address? > > Here's the need: we have a loaded-up PXE server working great under 4.07, > and

On 6 June 2015 at 14:03, Didier Spaier via Syslinux <syslinux at zytor.com> wrote: > > > On 06/06/2015 12:19, Stoppa, Igor via Syslinux wrote: > >> So I'd like to not put all the kernels/initrds in it, because when I >> update one of the OSes, I would also have to update the corresponding >> kernel in the EFI partition. > > > IIRC this is not

Inspired from a similar patch posted on grub-devel for Grub2 I immersed myself into the code of Grub Legacy and came up with this absurdedly simple patch to allow syslinux or other bootloaders residing in logical partition to be chainloaded from GRUB Legacy (0.9x). Hoping it to be of help, regards Fulvio Scapin -------------- next part -------------- A non-text attachment was scrubbed... Name:

When chainloading one pxelinux from another (e.g., chainloading from say pxelinux 4.07 to pxelinux 6.02), can one pass parameters or somehow control the root directory and/or server IP address? Here's the need: we have a loaded-up PXE server working great under 4.07, and I'm not prepared to just switch the entire setup to a newer version of pxelinux, too many folks depending on a

Hi, I am having troubles with chainloading and hopefully someone can provide me with some guidance. Here's what I am trying to do: * the media is a USB key * I have created a GPT on it * I have created an EFI partition, where I have installed the EFI flavor of syslinux, the various .c32 files required for chainloading and the configuration file which tells syslinux what to chainload

Hey guys, what I am trying to do is a chainload into grub2 installation in a DomU. So far I determined, PV-GRUB does not understand grub2''s grub.cfg notation. So I created a dummy menu.lst which has the needed root kernel and initrd rows and then referenced this to the DomUs config. The main intention to do this, is to be able to use kernel upgrades without touching the menu.lst for

On 06/06/2015 13:14, Stoppa, Igor wrote: > On 6 June 2015 at 14:03, Didier Spaier via Syslinux <syslinux at zytor.com> wrote: >> >> >> On 06/06/2015 12:19, Stoppa, Igor via Syslinux wrote: >> >>> So I'd like to not put all the kernels/initrds in it, because when I >>> update one of the OSes, I would also have to update the corresponding

On Tue, 2019-12-17 at 22:46 +0100, David Bala?ic via Syslinux wrote: > Hi! > I have bootable (USB flash) disk, that _appears_ to be using syslinux. > (the word syslinux is in the PBR, in the hexdump). > How can I chainload it? The payload seems to be a file that I tried > load with COMBOOT, COM32 etc, but nothing works (they report that the > file is not in proper format, wrong

Hi syslinux list, Some months ago, hpa was kind enough to help me troubleshoot booting Extlinux in a system with the following particulars: * Windows Vista x64 bootloader in the MBR and Vista installed in /dev/sda1 * Extlinux 3.72 installed in the first sector of /dev/sda2 and Foresight Linux installed in /dev/sda2 (at the time I tried, 3.72 was the default bootloader in Foresight) The problem

Hi, we use PXELINUX in our product to show a boot menu on client computers, with options like "Boot from local hard disk", "Install Windows", etc. Unfortunately, a lot of computers seem to have broken BIOSes and won't boot with the LOCALBOOT command, and need to be booted with chain.c32 instead. We also have encountered some computers where it works only the other way -

(snip) > > As per the intended setup, it is not possible. There are several > > reasons for such impossibility. > > Could you elaborate a bit more? What are the impediments? (snip) > -- > igor Posting an explanation for every current impediment (as of v.6.03) and, optionally, potential future improvements, would take (me) some (long) time, it would be boring

Hi, This is off topic for this list, but someone on this list may be able to point me in the right direction. For a couple of years I have been using ISOLINUX + MEMDISK and Smart Boot Manager to chainload a CD-ROM boot after loading a floppy image into RAM with MEMDISK. My problem now is that Smart Boot Manager does not support/detect SATA optical drives used in new hardware. Does anyonw

Woody Suwalski <woody at suwalski.net> schrieb am 07.03.03 17:57:26: > > Peter, we have met in Cyber space looong time ago, when I was requesting > 10:minor numbers for the Netwinder project.... > > Now I am trying to build a network boot for Xandros distribution. > > I have it working, however I need to do 2 DHCP cycles - 1 happens in > PXE, and then it repeats

On Tue, 17 Dec 2019 at 23:19, Gregory Lee Bartholomew < gregory.lee.bartholomew at gmail.com> wrote: > On Tue, 2019-12-17 at 22:46 +0100, David Bala?ic via Syslinux wrote: > > Hi! > > I have bootable (USB flash) disk, that _appears_ to be using syslinux. > > (the word syslinux is in the PBR, in the hexdump). > > How can I chainload it? The payload seems to be a

Hi all, I got swfdec compiled and running, however there are a lot of problems running it ! As a test I tried: swfplay http://www.youtube.com/v/lUR6laFLk0A First of all I see: SWFDEC: ERROR: swfdec_codec_gst.c(231): swfdec_gst_decoder_init: failed to create decoder SWFDEC: ERROR: swfdec_codec_audio.c(192): swfdec_audio_decoder_new: no suitable decoder for audio codec 2 SWFDEC: ERROR:

Hi 2 all ! I want to implement a new option into version 2.11 of syslinux: The feature should do the following: Ask the user if he really wants to boot from dvd. If no keyboard key is pressed in an amount of time it should boot from the next device configured in BIOS (INT 18h). I looked up the isolinux.asm and tried 2 entry points for my code: 1. entry point: label