similar to: Comments about documentation as of 4.06 - 5.00pre9

> > SYSLINUX 6.03 CHS 6.03-pre1 ... > > Failed to load ldlinux.c32 > Boot failed: please change disks and press a key to continue. > First, let me clarify that all the scripts and procedures in the Clonezilla site are not related to this official Syslinux mailing list or to The Syslinux Project. They are done by the Clonezilla team. Now that I know you are working

> If I understand the syntax correct, it is: > (hdX,Y)/path/to/file", where X is disk number and Y is partition number. > As far as I understand X and Y are zero based. > > I've tested it with qemu and 2 disks: > - the first with bootloader > - the second with kernel+rootfs > > I've used the following configuration file label: > > label MULTIFS >

> Both sticks show very unusual factors for heads and sectors > which are hardly intentional. If BIOS gets confused like fdisk, > then the failure to find files is quite plausible. > > ------------------------------------------------------------- > > Could you please exercise what is described for Linux in > http://www.syslinux.org/doc/usbkey.txt > and check whether

> > Hi > I have tried to install syslinux 4.06 on the SD card again, it works > like a charm. > > I am being very carefull with c32 files from the same version > bootloader. No success. > > I am also unmounting /dev/sdb1 before installing syslinux, as mentioned > in the given documentations. > In the pasted syslinux.cfg content--- I have also tried using only

>Several points (please read the whole email before doing anything else): > >1_ It is not clear whether you still need/want to "avoid displaying" the menu border (i.e. make it transparent). You mentioned that you >eventually managed to do so, but then you also ask (again) about vesamenu.c regarding the menu border. Or, perhaps... Do you >actually, really, want to

> I'm starting this thread to discuss what git repository should be > designated as primary and which repositories should be designated as > secondary. > > For years, git.kernel.org has been the primary repo, updated at least > with every full and pre- release. git.zytor.com has been the > secondary and development repo. > > Additionally, I've maintained my

> > http://www.syslinux.org/wiki/index.php/Common_Problems#Modules > > Shouldn't be enough copy modules from /user/lib/syslinux....? > 1_ Booting with Syslinux, in the Syslinux "boot:" prompt press "Ctrl+V" so to see relevant information. The c32 modules shall match the same version. 2_ The Current Working Directory is relevant, specially for relative

On Sun, Jun 14, 2015 at 4:33 PM, Geert Stappers via Syslinux <syslinux at zytor.com> wrote: > On Sat, Jun 13, 2015 at 10:44:11PM +0300, Ady via Syslinux wrote: >> >> > I'm starting this thread to discuss what git repository should be >> > designated as primary and which repositories should be designated as >> > secondary. >> > >> >

Hi, First of all thank you so much for your prompt suggestions/help. I really appreciate this. Here is the syslinux.cfg which works perfect with syslinux-4.06 ---- PROMPT 0 TIMEOUT 50 SERIAL 0 DEFAULT mylabel LABEL mylabel KERNEL vmlinuz0 APPEND initrd=initrd.img root=/dev/mmcblk0p2 rootwait rootfstype=ext3 console=tty0 console=ttyS0,9600 ---- To further round off the error possibilities I used

Hi Matt, First comments about 5.00-pre10. 1_ When using "ctrl+v" in the boot prompt, there is no space character between the version and the boot mode. Additionally, the main version number is shown twice. For example, "SYSLINUX 5.00 5.00-PRE10CHS" should be: "SYSLINUX 5.00-PRE10 CHS" 2_ Boot to menu.c32, press [ESC] to go to the boot prompt. Pressing [ESC]

After some discussion/debugging behind the scenes, we are back on track, with updated Debian packages. 0_ Starting from an _original_ (so-called "hd-media") boot.img mounted in "target" (or "$target", or some similar notation), and the version of Syslinux-related packages in the OS should be "6.04~git20171011.af7e95c3+dfsg1-6" or newer. At the moment

On Sat, Jun 13, 2015 at 10:44:11PM +0300, Ady via Syslinux wrote: > > > I'm starting this thread to discuss what git repository should be > > designated as primary and which repositories should be designated as > > secondary. > > > > For years, git.kernel.org has been the primary repo, updated at least > > with every full and pre- release.

This is an attempt to avoid potential confusion. Here are some example sizes for the two Syslinux versions mentioned in the e-mail subject. Your build results might be different. 4.06: 1 55 Sep 22 22:23 modules/int18.com 1 108 Nov 1 18:07 version.mk 1 138 Nov 1 18:07 version.gen 1 138 Nov 1 18:07 version.h 1 239 Sep 22 22:23 modules/poweroff.com 1 408 Sep 22 22:25

Testing the following (uncommon) syslinux.cfg with different Syslinux versions allows getting to several observations; some might be of interest to users, and some for the Syslinux developers. syslinux.cfg *** UI menu.c32 DEFAULT help TIMEOUT 30 # ONTIMEOUT help LABEL pwd COM32 pwd.c32 LABEL help MENU HELP help.txt *** 1_ For the TIMEOUT-related directives to behave as expected,

This is a bug report about Syslinux 6.03-pre11 in EFI. To Syslinux EFI developers; the results can be replicated in real hardware. I apologize for the length of the email; I am describing the steps necessary to reproduce the confusing behaviors the best I can. I have been experimenting with VBox and Syslinux EFI32. In EFI, the default screen resolution for [vesa]menu.c32 is not 640 x 480

Hello. I'm testing version 4.06-pre5. Using the CONFIG + APPEND directive with RELATIVE paths and changing the base directory is sometimes failing. Booting with ISOLINUX is OK but SYSLINUX is not. To demonstrate an example, I have uploaded a little 7z archive containing: _ a little ISO image; _ a 1440KiB floppy image. Both images have the same directory tree and cfg files. The only

> I proposed -h 252 -s 63 because it yields the largest > possible cylinder size which is divisible by 4 (i.e. > the byte count is divisible by 512*4 = 2048). > -h 240 -s 63 would fulfill this constraint, too. > Size limits are 252*63*1024*512 = 8,323,596,288 > resp. 240*63*1024*512 = 7,927,234,560 bytes. > > > The workaround cannot be temporal, because the

> Hi, > > it would be interesting to know for what solution > TAILS decides and whether any problems arise with it. > > ------------------------------------------------------- > On with the fundamental discussion of MBR cylinders: > > Ady wrote: > > 1_ The resulting ISO9660 file system size shall be a multiple of 2048 > > (bytes_per_sector). > >

> Thanks Gregory, my mistake, your explanation was half right and your code was > fully right, I meant to say the key is setting the first two digits in the > foreground and background to "00" (which means transparent) this will delete the > color of the border, and then making the shadowing variable equal to "none" this > will delete the shadowing black line

Just achieved success using syslinux to multi-OS boot, including a WinXP System (boot) partition that's been encrypted with TrueCrypt (TC). You'll need syslinux version 3.81-pre13 or newer to get a working altmbr.bin file. I used: http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/syslinux-3.81-pre13.zip Background: I started with a 'normal' multi-OS boot setup as