similar to: Installers options with additional arguments

Why doesn't the Windows Syslinux installer show: --offset and --directory too (I know it is not supported)? Because the Linux versions show the Windows/dos specific commands: --mbr --active and --force I didn't check the DOS version. If all options will be displayed unconditionally for all installers, it might be a good idea to add: --offset -t Offset of the file system on the

> Hi, > > i now realized that > http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#USB-Geometry > http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#USB-Miscellaneous > are the new wiki sections by Gene Cumm. (Sorry for not reading > them when they were announced.) > > So i ask especially him whether the statement > > "An examle

On Wed, Jan 22, 2014 at 3:20 AM, Thomas Schmitt <scdbackup at gmx.net> wrote: > > Now in a new thread with updated subject. > > ----- Forwarded message from Thomas Schmitt ----- > > Date: Wed, 22 Jan 2014 08:45:51 +0100 >>From: Thomas Schmitt > To: syslinux at zytor.com > Subject: Re: [syslinux] Advice/directions to users of Syslinux > Message-Id:

Now in a new thread with updated subject. ----- Forwarded message from Thomas Schmitt ----- Date: Wed, 22 Jan 2014 08:45:51 +0100 >From: Thomas Schmitt To: syslinux at zytor.com Subject: Re: [syslinux] Advice/directions to users of Syslinux Message-Id: <29490645553171871372 at scdbackup.webframe.org> Reply-To: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com> Hi, i

Windows uses several sectors in the _partition_ for booting. Windows only uses sector 0 of the Disk (the MBR), and does not use any other sectors. Other boot managers and copy protection software (the stuff that comes with TurboTax this year uses track 0, evil...) For FAT16 filesystems, only the first sector is used. For FAT32, there are 32 sectors that are reserved by the FS, and I've come

Hi, Ady wrote: > Is this "32MiB" a limitation related to the UEFI specs in any way? Or > is it relevant for BIOS (non-EFI) too? It comes from El Torito specs which are referred to by UEFI 2.4 specs. In EL Torito 1.0, Figures 3 and 5, "Sector Count" is a 2-byte "Word". So it can count up to 65535. Sector count gives the number of "virtual/emulated

Hi, funny or enlightening observation: With my qemu-system-i386 it would work if the detected Heads/Cylinder and Sectors/Head factors would change positions ! The effective read operation seems to use H/C = 32 , S/H = 63. The correct LBA would be addressed by H/C = 63 , S/H = 32. -------------------------------------------------------------------------- Reasoning: I have transplanted the

CentOS-6.6 virt-manager 0.9.0 I have cloned a template server with a 32GB virtio HDD already defined and am attempting to add additional virtio disks. The basic cloned system boots without error. If I create a virtio disk with 32000/32000 megabytes I can add it and the system reboots; providing that I do not first create a partition: fdisk -l /dev/vg_vhost03/lv_vm_inet11.harte-lyne.ca_03

Correct typos. Improve format for asciidoc-to-manpage conversion. Wrap text. Correct info. Help phase-out deprecated and/or conflicting options. diff U3 /syslinux-6.03/txt/syslinux.txt /wip/txt/syslinux.txt --- /syslinux-6.03/txt/syslinux.txt Mon Oct 06 16:27:44 2014 +++ /wip/txt/syslinux.txt Sat Dec 27 18:20:27 2014 @@ -30,9 +30,10 @@ unmounted file system. For the DOS/Win32/Win64 installers,

> Hi Ady, > > On 2016.02.25 02:08, Ady via Syslinux wrote: > > There is an "extra" sector, in comparison to... what exactly? > > Sorry if I wasn't clear. I think I implied that the Large FAT32 fat size > had an extra sector compared to minfatsize, when of course I meant the > opposite (the Large FAT32 has one less sector than the minfatsize >

> 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 now realized that http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#USB-Geometry http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#USB-Miscellaneous are the new wiki sections by Gene Cumm. (Sorry for not reading them when they were announced.) So i ask especially him whether the statement "An examle is a drive of 128,64,32 with a partition ending at

In the following text, I am about to use terms such as "inaccurate". I don't mean to question what some code does, but rather to compare the expressions against what I think is a more accurate one, in theory. I mean no disrespect, and I am not saying that developers are doing the wrong thing. In addition, of course I could be wrong (or type in incorrectly, or some formatting

Hi, I encounter a problem with Syslinux 5.00 I cannot really describe. So I created two small videos: Booting with Syslinux 5.00 (1.3 MB): <https://www.dropbox.com/s/b6g8cdf2t9v48c6/boot-syslinux5-fail.mp4> How I fixed the problem by downgrading to Syslinux 4.06 and how booting should look like (6.5 MB): <https://www.dropbox.com/s/lt7cpgfm0qvqtba/boot-syslinux5-how-i-fixed-it.mp4>

Hi, Ady wrote: > The whole "booting business" is bigger than one specific bootloader. Too many participants at too many interfaces. > IMHO, there is more-than-enough to do about The Syslinux Project > itself Nevertheless i believe that the SYSLINUX wiki could be more tangible about what is a "normal" MS-DOS formatted disk. At least for those who seek help for

On Tue, 08 Jul 2014 15:54, H. Peter Anvin wrote: > >On 07/08/2014 11:26 AM, Ady wrote: >> >> It's interesting that you ask this, because every document related to >> newmkfloppyimg.sh specifically recommends adding: >> floppy c=$CYLINDERS s=$SECTORS h=$HEADS >> to the MEMDISK arguments. >> > >It would be important for floppies to know

On Sun, May 17, 2015 at 05:06:15PM +0200, Hilko Bengen wrote: > Hi, > > it was brought to my attention that sfdisk has lost the ability to deal > with C/H/S addressing as of util-linux 2.26, so the -C ,-H, -S command > line parameters are no longer supported. Should there be a compile-time > check based on "sfdisk -h" output that would cause daemon/sfdisk.c to be >

On 07/09/2014 01:54 PM, Alexander Perlis wrote: > > Ah, this might explain things although I don't know what is meant by > "intended". First, to clarify, newmkfloppyimg calls mkdosfs 3.0.12, and > grabs H/S from the output and then computes C. For all the sizes I've > tried, newmkfloppyimg always tells me H=64 S=32 and then C is the > approximately the number

Some people have reported portability problems with SYSLINUX 3.00, mostly due to the use of HDIO_GETGEO_BIG, which is deprecated; additionally, the advanced menu system wouldn't build for everyone due to a spurious reference to %ebp. This release fixes these things, plus makes the extlinux installer default to zipdisk geometry (64 heads, 32 sectors) if it can't guess anything else.

This is part of some patches to support sectors > 512. Currently I'm able to boot a Ubuntu kernel but seems that mboot is not working for some reason. This patch try to fix first stage of extlinux bootloader but have some problems with ADV Signed-off-by: Frediano Ziglio <frediano.ziglio at citrix.com> --- dos/syslinux.c | 2 +- extlinux/main.c | 36