similar to: Syslinux Digest, Vol 164, Issue 2

Sounds like we should change the "and cx" mask to 5 so that if either EHDD support or LBA is announced by the bios, the correct EHDD path will be taken. Phil P. -- Philip Pokorny, RHCE Chief Technology Officer PENGUIN COMPUTING, Inc www.penguincomputing.com Changing the world through technical innovation

I've been trying to get syslinux.efi working in my environment again... Found what look like a bunch of little bugs that are very frustrating... First, the documentation on the Wiki says that as of 5.11, the list separator is space, not colon. But I can find no evidence that 5.11 was ever officially released or that a commit to git was made to make this change. 6.00 and following still use

I need to create one bootable UEFI disk partition that contains all the space on the disk. The steps must work in a shell script. Ideally with syslinux/extlinux but if not possible then grub. How to do this? Surely it should be dead easy, a handful of lines? Nothing I do works. This is what I have so far: DISK_DEVICE_NAME_CURRENT_OS=hda echo remove all partitions sudo /usr/local/sbin/sgdisk -Z

I am trying to use rsync (3.0.6) to keep two directories as exact duplicates. I would normally run: rsync -av -S --delete /path/to/src/ /path/to/dst/ to do this. Unfortunately, the directories have become rather large (2TB, a million files) and so the tree walk has become a prohibitively time consuming part of the operation. However, I have a way to generate a list of file changes

On 11/07/16 14:27, Phil Pokorny via Syslinux wrote: > > EFI requires a FAT filesystem. Ideally FAT32 but that might be encumbered > by Microsoft patents? Maximum size of a FAT16 partition is 2GB. > > Use mkfs.vfat You can try the "-F 32" if you're not worried about being > sued by Microsoft. > I'm not a lawyer, and this is NOT legal advice, but: 1.

Does the reason Theora is relatively safe from patent infringement lawsuit have more to do with it actually not being encumbered, or is it because its use is decentralized? For example, FreeType is not patent-free, nor is Linux, yet they succeed because on the one hand, they are open source, and those who maintain them do not guarantee anything regarding patents, it is up to each individual user

I see that there seems to be patches being accepted... Please consider committing these two: You should be able to cherry pick them from my syslinux repo at http://github.com/ppokorny/syslinux I would think? commit 64fb71b87a625d70ea8c6127f18fe96d3f4fdc89 Author: Philip Pokorny <ppokorny at penguincomputing.com> Date: Sun Mar 5 21:07:48 2017 -0800 Fix PATH parsing to match the

Hello. I have Centos 4.4 with the NTFS read-only driver from http://www.linux-ntfs.org/content/view/135/71/ I would like know if someone who installed this can test if Centos 5 can read/write NTFS,. Thanks Josep --------------------------------- LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y m?viles desde 1 c?ntimo por minuto. http://es.voice.yahoo.com -------------- next part

Phil, I gave a presentation last month on how to set up a DHCP + TFTP server. Using syslinux 6.03-pre* to support both Legacy and EFI PXE boot. Here's the link to the presentation. My slides are there. http://2014.texaslinuxfest.org/content/creating-legacy-efi-pxe-server-using-pxelinux The presentation models a small lab-sized env. I start simple; supporting legacy PXE boot only. Then

Hi, "Mircea Popescu" <nufarul.alb at go.ro> schrieb am 29.01.02: > I have this problem: > I've partitioned my hard drive with PQMagic 7 in the following way: > hda1 - fat32 > hda2 - ext2 > hda3 - fat16 > hda4 - extended > hda5 - Linux Swap > hda6 - fat32 > hda7 - ext2 > hda8 - fat32 > > I've put syslinux on

Hi All, First post and hopefully someone can steer me in the right direction for this problem. I did a bit of googling and found some hints but nothing concrete. We are using Syslinux and a FAT32 USB thumb drive (single partition) to boot a customized Debian OS which works very well with newer motherboards. However we have a few older Dell machines that simply hangs when trying to boot

I know syslinux supports FAT16 and works very well, but how about FAT32? Does syslinux support FAT32? If so, which version? eg., 3.11 and above Thanks!

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

Gene, thanks for doing "Reply-All". I only get digest, so this keeps me in the loop. Appreciated. > which appears to be included in diskstart.inc. I will have to dig in and > see > > how this all gets compiled (pointers always appreciated :-) ). > > Yes. > Is the build process documented? Or am I just going to have to plod through the makefiles? > As Ady said,

On 07/09/2014 04:00 PM, H. Peter Anvin wrote: > > So this would seem consistent that this is the FAT12/FAT16 boundary that > breaks stuff. Perhaps FreeDOS has a problem with FAT16 on floppies? If I understand things correctly, a bootable floppy has two key pieces of executable code: the 512-byte boot sector, and the kernel loaded by that boot sector. The kernel can be large, and thus

> On 2019-4-11 13:29, Lu Wei wrote: > > On 2019-4-10 1:20, Ady Ady via Syslinux wrote: > >>>>> #This item fails > >>>>> label dos > >>>>> menu label MS-^DOS 7.1 > >>>>> com32 chain.c32 msdos7=io.sys > >>> > >>> IO.SYS and COMMAND.COM are copied from a Windows98 system on another >

[disclaimer: I am the author of Rufus] Hi, On 2014.01.15 10:10, Thomas Schmitt wrote: > As producer of MBRs i wonder where that LBA-flag is located. > In bit 0 to bit 6 of byte 446 (where bit 7 means active/bootable) ? I haven't looked at what GParted does, so I may be off mark, but I have a strong suspicion that this LBA "flag" is a fake flag that simply indicates if a

Hi Ady, Your insightful post prompted me to to a little bit more digging as to how the Ridgecrop algorithm computed its FAT size, with the result of my investigations presented below. NB: For those who don't want to go through this whole part, there's a TL;DR near the end. For reference, the computation of the FAT size all done in the GetFATSizeSectors(), the code of which is at [1]

I would like to boot FreeDOS ISO image from USB memory stick using syslinux. I have done following: 1) I created a partition to my 2GB memory stick: root at debian64:~# fdisk -lu /dev/sdb Disk /dev/sdb: 2013 MB, 2013265920 bytes 62 heads, 62 sectors/track, 1022 cylinders, total 3932160 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size

> > > Is the build process documented? Or am I just going to have to plod > through > > the makefiles? > > I don't think so. > Oh well... > > 1. Run installer > > 2. Installer loads ldlinux.sys onto the filesystem (and copies > ldlinux.c32, > > but irrelevant for now). > > 3. Installer calculates which blocks in the filesystem contain