similar to: how do the isolinux.bin to be produced?

Hi, all I can't boot from local drive on some machines(thinkpad x200 and thinkpad x1 carbon) using syslinux 3.05 or syslinux 4.05. And i change localboot 0xffff to localboot 0x80, boot from local drive is available. I find "0x80 is the primary hard drive. The special value -1(0xffff) causes ISOLINUX to report failure to the BIOS, which, on recent BIOSes, should mean that the next

I have tried "LOCALBOOT -1" , it still didn't work. ? 2014?02?25? 12:44, Gene Cumm ??: > On Mon, Feb 24, 2014 at 10:27 PM, ?? <lei.xia at cs2c.com.cn> wrote: >> Hi, all >> >> I can't boot from local drive on some machines(thinkpad x200 and >> thinkpad x1 carbon) using >> syslinux 3.05 or syslinux 4.05. >> >> And i change

Hi, When we meet UEFI or EFI firmware, lots of linux os release use GRUB bootloader. But I wanna use isolinux to boot the installation environment and also the linux os installed. Some question puzzled me. Now, I look for your help: 1. I didn't found information about how to use syslinux(isolinux,etc.) in uefi. I wanna know that are there some differences of the isolinux configuration

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

Hello, I wish to recompile only isolinux.bin and nothing else. I made some changes to core/fs/lib/loadconfig.c and now I wish to make (compile) isolinux.bin only. The only way how to do it seems to be "make" in the directory of syslinux sources. But this takes very long and compiles everything. Is there a better way to make only isolinux.bin? Something like "make isolinux"

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

hi I have download the syslinux-3.51 source package and i have tried to compile syslinux with MinGw. I got the following error message. *********************************************************************** $ make nasm -O99 -f bin -DDATE_STR="'0x47bd5366'" -DHEXDATE="0x47bd5366" \ -DMAP=isolinux.map -l isolinux.lst -o isolinux.bin isolinux.asm

We use "isolinux.bin" 3.72 and meet an issue : we put all the files(including config file, kernel and initrd file) under the root directory and some additional normal files in it. If adding enough files in the root directory, the created ISO will fail to boot, hanging at "ISOLINUX 3.72 3.72 ETCD Copyright (C) 1994-2008 H. Peter Anvin". Is this a known issue? Is it fixed in the

Until Syslinux 3.86, isolinux.bin contained a checksum that was calculated by 'core/checksumiso.pl'. The checksum is related to the patching of the boot info table. 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

Hi, Ady wrote: > This is a quote from Wonko/Jaclaz, who has also been investigation this > issue and deserves credit for it: > Ok, not that I understand the code, but what *somehow* happens is that > the "embedded" checksum in Isolinux.bin (starting from 4.00) is the > checksum of the WHOLE file (i.e. starting from offset 0 instead of 64) > at a time when: > 1)

David Christensen wrote: > This is how I prepared an ADATA USB Flash Drive 4 GB: ... install-mbr /dev/sdb ... [Rest of very clear description snipped.] What's that? That desn't exist in the Debian I'm running. Otherwise you gave a very good description of what you're doing. >From another message: > Please provide a URL for documentation that explains how to build a >

Hi, i am looking now at the code which i assume loads the rest of isolinux.bin. The entry point for program execution from the MBR is obviously at http://git.zytor.com/syslinux/syslinux.git/tree/core/isolinux.asm#n186 (Do i get it right that this is the Intel syntax ? (Gronfff)) If POP yields the victim of the most recent not yet popped PUSH, then this does not look correctly coordinated

H, Ady wrote: > A_ The default checksum included in the tested isolinux.bin (offset 20, > 4-bytes-long) is the "correct" one (as oppose to the current situation, > since version 4.00). That's good news. > F_ In the tested isolinux.bin file, there are two additional bytes that > I found to be changed/affected by some ISO-building tools (e.g. > mkisofs), at

Thomas Schmitt wrote: > I have some problems understanding the details of the program's flow. > > - The code inside PARTITION_SUPPORT is supposed to be inactive with > MBR isohdpfx.bin. It belongs to isohybrid --partok which is equivalent > to MBRs isohdppx*.bin. Debian uses isohdpfx.bin. Yes. isohdpfx.bin is generated from isohdpfx.S in which PARTITION_SUPPORT is not