similar to: How to make isolinux.bin only?

Hi, I am trying to track down a ISOLINUX boot problem on my workhorse computer. Booting slax-6.0.0-rc5.iso from www.slax.org (a live distro) from CD gives the following messages: Loading /boot/vmlinuz ........... Loading /boot/initrd.gz ............ Ready. _ Silence. The next message should be, but does not appear: Uncompressing Linux ........... This message appears with the same CD on an old

This one is the most critical for my app, but also possibly the most controversial to integrate. A few applications that convert isolinux ISOs to bootable USB, including mine, copy the ISO content to a VFAT formatted partition and then add syslinux to make it bootable. This would work great... if isolinux and syslinux shared the same defaults when it comes to configuration files.

> Hello Ady & list, > > On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > > Hello Ady, > > > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > > > (with an optional Syslinux menu containing multiple entries). > > > > >

New idea proposal: Currently syslinux (and others) searches in for its config file, say syslinux.cfg, in a hardcoded list of directories. I propose that if the config file is not found, instead of producing an error message like "unable to locate config file", it should try to search in root directories and its subdirectories. There is -d option to install syslinux to any directory

On Wed, Aug 27, 2014 at 2:08 AM, Prof. Dipl.-Ing. Klaus Knopper <syslinux at knopper.net> wrote: > Apparently, the rename of ldlinux.e32 to ldlinux.e64 for the 64bit > variant is already in the mainline git, so the only change left for > automatically chosing a different config file is the tiny patch attached > here, which will > > - prepend syslnx64.cfg to the config file

Hi, Ady: > I am using the ISO image from TAILS as an excuse to "tease" TAILS' devs > and other users of Syslinux. If intrigeri (TAILS developer) "bites". > then users reading this mailing list might learn one thing or two about > Syslinux (6.04-pre1+). :) > 1_ EFI/BOOT/isolinux.bin is probably a mistake (or misunderstanding) > originated in the ISO

> I'm the developer of manjaroiso, the tool we use to build our install > medias for Manjaro Linux. > During our testings we found out, that syslinux6 won't work on older > hardware. I've a new Lenovo i7 notebook which booted up our images > just fine. Even with syslinux6. On my other PCs I got similar error > messages as Carl got. (snip) > > In

> Their isolinux/isolinux.cfg has > DEFAULT loadconfig > LABEL loadconfig > CONFIG /arch/boot/syslinux/archiso.cfg > The file arch/boot/syslinux/archiso.cfg is readable too. > IIRC, Arch isolinux/isolinux.cfg should say: DEFAULT loadconfig LABEL loadconfig CONFIG /arch/boot/syslinux/archiso.cfg APPEND /arch/ Or it might be using relative paths: DEFAULT

I just encountered my only bug w/ the ISOLINUX+VESAMENU combination from 3.52-pre5. Updated a *working* CD project w/ the new ISOLINUX+VESAMENU combo just last week. Booting my preferred Linux distro (Slax-6) from my custom CDs work perfectly, however when I updated a CD project that includes BartPE/WinPE, BartPE fails to boot w/ 'CDBoot can not boot CD: error 4" msg. For the

Hello Ady & list, On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > Hello Ady, > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > > (with an optional Syslinux menu containing multiple entries). > > > > > > Problem (solved) #1: The default

Hi We have a couple of FSC Computers here which seem to have a very strange bios. I am trying to boot a MS-DOS disk to flash an Scsi Raid controller. Since the computer doesn't have a floppy anymore I tried syslinux from an usb stick. The menu loads fine but I cannot boot disc images with memdisk on this computer. It works fine on others, of course. But now comes the weird part, if I use the

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

Hi, all I am confused, I run the ?make? command in the directory which is the sources of syslinux, and storage the output to a file, but i cannot find to how do the isolinux.bin to be produced. Also, I find that the isolinux.bin file is in the sources of syslinux(bios/core). So, I am curious how do the isolinux.bin to be produced, and where can I get the sources of isolinux.bin? Could

Hi, David Christensen wrote: > The USB flash drive boots the Debian installer in the old PC! Congrats. > There is no syslinux.cfg on debian-8.7.1-i386-xfce-CD-1.iso: The configuration is named /isolinux/isolinux.cfg. Looks like it is surrounded by a little empire of .cfg files: /isolinux/adgtk.cfg /isolinux/adtxt.cfg /isolinux/exithelp.cfg /isolinux/gtk.cfg

Hi, i think i found a suspect in lzo/prepcore.c and it would indeed be a wrong range of checksumming (speculative congratulations to Ady). Looking at http://repo.or.cz/syslinux.git/blob/0d82b71304d596d80f3c4520f9dcf90048ca50b7:/lzo/prepcore.c it seems that this change in line 374 could yield correct checksums: unsigned int ptr; - for (ptr = 64; ptr < offset; ptr += 4) +

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

> Hi, > > Ady wrote: > > During May 2009, a commit by Peter deleted the checksumiso.pl file. The > > commit is: > > core: LZO compress the PM part of the core > > repo.or.cz/syslinux.git/commit/0d82b71304d596d80f3c4520f9dcf90048ca50b7 > > And so, since version 4.00, the 'code/checksumiso.pl' file is no longer > > included. > > How is

Improving chain.c32 help message Impact: Error message is more detailed In case of syntax error, the message is far more detailed and provides the same content as the documentation integrated in the source code. You can get this patch from Erwan's git repo: http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=3fc3126d0c7df5701680e043c34f200166f24564 Add 'isolinux=' option to

I was given a custom CentOS 5.4 DVD, containing some Digium software for one of our customers. I need to turn this burned DVD into an image that can be written to a USB thumb drive. First, I ripped the DVD to an ISO image. That part works OK, my testing VM can load and run the custom kickstart script on the image. After totally frying my unetbootin install, I decided to try and use isohybrid

Hi, C/H/S addressing and reading of first block seems to be ok in isohdpfd.bin. The main suspect for the failure of the attempt with isohdpfd.bin is the number or content of the blocks read after the first one. But i have no clue why isohdpfc.bin should do better than isohdpfd.bin. They differ just by one instruction (JC = 0x72 versus JMP = 0xEB) which both are performed before the reading and