similar to: Making isolinux boot menu: problems

Hello Brian, On 26/08/2019 13:20, Brian Peregrine via Syslinux wrote: > We're currently working on a custom distro which would have an > isolinux boot menu. > We're currently not able to make it work, and are looking for a good > example of an isolinux/ directory of an iso with such a boot menu. If > anyone knows one (on github, ...) please let us know. They are plenty!

Thanks Didier, Stephanie used Anarchy Linux to make our menu work. Regarding the missing instructions at https://wiki.syslinux.org/wiki/index.php?title=Menu After comparing the (now working) menu with our old non-working menu made using the instructions from the syslinux wiki page, she found that it had many more .c32 files copied from /usr/share/syslinux and there were a few critical ones to

Hey Guys, I am trying to use the simple menu system to provide menus on my boot CDs. For testing, I have the following entry in my isolinux.cfg file: label linuxmenu kernel menu.c32 append menu32.cfg The option work as it should. I am trying to display two sets of menus. At the bottom of the menu32.cfg I have the following: label 64 menu label Press enter here for

I'm trying to get the menu working with ISOLINUX. So far any time I use a memory test such as ram stress test or memtest86 it reboots or locks up.. If any one could point me in the right place to get some info on how to set up the menu It would be greatly appreciated. Right now I'm using the "simple menu" that is included with the SYSLINUX package. I've used ISOLINUX for

Hello, I am an active member of the Vinux community and have taken on a project of remastering a Ubuntu installation Cd in order to make it accessable to a blind user. I am able to sound the system bell when the boot menu loads by adding a ^G to the label statement which works well to tell a blind user they are at the boot menu. My intent is to sound the bell at each menu item, but I'm unable

Hey Folks, Sorry if this has been asked before; hard to get a usable search on 'isolinux OR syslinux pxe-boot' with just the info I need! I work in a large organization, and the group which manages the network may not be the guys managing the hosts. I have a network and dhcp server, and pxelinux is working very well on that net. I want to make my net-install resources available to

We have a system that is designed with no VGA port, graphics card, or keyboard, only a serial console. We're trying to boot a Linux via ISOLINUX. The problem is that when ISOLINUX comes up, the screen is usually garbled. Not always; sometimes it's intact, sometimes it's completely blank. When it is garbled, it is NOT the garbled text of a wrong baud rate. Rather, it looks like

I have just created an ISO containing Fedora and ISOLinux as the bootloader. This is the ISO creation command: genisoimage -U -r -v -T -J -joliet-long -V "Fedora-WS-Live-31-1-9" -volset "Fedora-WS-Live-31-1-9" -A "Fedora-WS-Live-31-1-9" -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot -e

I'm looking for a well-supported ExpressCard or PCMCIA/CardBus SCSI card that can do at least FastSCSI (Narrow, Wide not necessary) that is supported by CentOS 7. I have an Adaptec SlimSCSI 1460D, but it doesn't seem to be supported (it's previously supported by the aha152x driver). Any ideas are welcomed, other than 'just use a desktop.' I am not sure a USB or Firewire

Hi Peter, I'm doing some work for HP creating various flavours of bootable CDs, and am using isolinux for i386 and elilo for ia64. We wanted the same interface on both systems, with the ability to choose a boot option from a menu with the cursor keys. To implement this I enhanced isolinux to support two new control fields in the message file: 0x01 ^A Mark left- or right-hand end of the

For posterity's sake, this problem was solved by removing the "serial" command and restoring "console" to the default of 1, thus completely relying on the BIOS console redirection instead of having ISOLINUX write to and read from the serial port. Thanks to Peter for his help a while back. -----Original Message----- From: Syslinux [mailto:syslinux-bounces at zytor.com] On

Comments inline > -----Original Message----- > From: H. Peter Anvin [mailto:hpa at zytor.com] > Posted At: Thursday, November 14, 2002 1:40 AM > Posted To: Syslinux > Conversation: [syslinux] MSDOS not working: problem Solved > Subject: Re: [syslinux] MSDOS not working: problem Solved > > > G. Murali Krishnan wrote: > > > > In short: Is it possible to

chain.c32 of SYSLINUX 3.82 does set the boot drive passed to the DL register to 0x80 and not to the boot drive (CD-drive). This can be a problem if you want to chainload grldr (grub4dos bootloader) from a CD and if you want to let grldr search for its menu.lst file on the CD. For more info: http://www.boot-land.net/forums/index.php?showtopic=8457 This 1 line patch fixes the issue (Thanks to

i am trying to use chain.c32 with isolinux to load WinPE/BartPE/etc and I can not get it to work. I have tried with the simple.c32, and just from the isolinux prompt. I have tried 3.32-pre6, 3.20, and jumped back and tried 3.08. All configurations fail with 'Cannot read Master Boot Record'. The boot sectors are known to be good, and are known to work with chain.c32 with pxelinux.

Hi there, i just build a new ipxelinux.0 with an EMBED=../../syslinux-5/core/pxelinux.0. i'm trying to load up my vesamenu.c32 menu from http:. and offcorse i want this as optimal as possible, with the least needed GET requests. OLD situation with v4: PXE ROM -> ipxelinux.0 (tftp) -> menu.php (http) -> vesamenu.c32 (http) NEW situation with v5: PXE ROM -> ipxelinux.0 (tftp)

Hello, First of all, thanks very much for this piece of software, it's working like a charm. I'm using it to boot a Linux distro I'm working on. What I want to deal with is the display of accented characters in ISOLINUX. First, I set EXTLINUX up to boot an ext2-formatted USB stick. No problem so far. I wrote a config file ordering to load a font (lat-9w) to display french

On 3/8/2016 14:26, Pete Batard via Syslinux wrote: > [...] > But in essence, yes, that's pretty much it. So then some thoughts: 1. Did you mean a truly "merged" file, where the very same file could be used for ISOLINUX and for disk-based Syslinux? Or did you mean "tacked on," where ldlinux.bin would be appended to isolinux.bin so that you could later

I have a USB disk with syslinux files installed in /boot/syslinux, and the bootloader is installed into MBR or VBR I then extracted a *.iso file which uses syslinux as the bootloader, into root dir of the disk. The iso file contains a rescue OS or an OS installer. Now I got the directory /isolinux with files isolinux.bin and isolinux.cfg in this folder I can now boot into syslinux, but *what to

On Thu, May 12, 2016 at 06:16:46PM +0200, Good Old Idea via Syslinux wrote: > On Thu, May 12, 2016 at 02:29:52PM +0000, Janz, Burt via Syslinux wrote: > > I have a need to display text to COM2 before loading a kernel. > > The easiest way to do this was to invade menu.c32 (menumain.c) and > > add a function to send the string out to the serial port just before > > the

On Thu, May 12, 2016 at 2:14 PM, Janz, Burt via Syslinux <syslinux at zytor.com> wrote: > Hi Geert, > > I'm building syslinux 6.04 from scratch to prevent any issues with mismatched com32 modules. This gives me a "pure" set of modules as well as "pure" isolinux and syslinux cores. 6.04 hasn't seen a full release, only the pre1 pre-release. >