similar to: Is this email the public list?

Thus the rub: The exe seems to have disappeared from winbin as well. It's there, but downloads as a zero-byte file. > Date: Sun, 6 Jul 2014 22:40:21 +0200 > From: herbszt at gmx.de > To: sha0.miller at gmail.com > CC: syslinux at zytor.com; jml9904 at hotmail.com > Subject: Re: [syslinux] mdiskchk and WinPE > > Shao Miller wrote: > > On 7/6/2014 01:55, Ady wrote:

Hello all. Here[1] is a branch where chain.c32 can chain-boot a partition on a GPT disk when given the partition index. boot: chain hd1 84 (For example.) - Shao Miller [1] http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/ chain_gpt

Just a slight poke regarding the MEMDISK and MDISKCHK.COM possibilities available here[1]. Review by non-hpas is welcome, too. Thanks! - Shao [1] http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/ mdiskchk_enh2

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

Attached are 4 patches against Syslinux 4.06 providing two new options for the linux.c32 ComBoot32 module. If we are shifting gears towards 4.10 or 5 any time soon, feel free to let me know and I'll attempt to apply the patches to those and to deal with any conflicts. You can merge these commits onto your 4.06 from my 'multi_initrd' branch at:

Maybe you know, Ram? - Shao -----Original Message----- From: Shao [mailto:sha0.miller at gmail.com] Sent: Saturday, December 01, 2012 00:58 To: 'For discussion of Syslinux and tftp-hpa' Subject: VMware ESXi safeboot.c32 Source Code Does anyone know where to find the source code for VMware's ESXi's safeboot.c32 module? There is a question in the http://reboot.pro Syslinux forum

Good day, Mr. David Juhl. Yes, as long as you keep the syslinux at zytor.com address in either "To", "CC" or "BCC", you'll keep your discussion with the mailing-list. - Shao Miller

and there it was. Thanks, all, that did the trick! jml > From: sha0.miller at gmail.com > To: jml9904 at hotmail.com > CC: syslinux at zytor.com > Subject: RE: [syslinux] mdiskchk and WinPE > Date: Mon, 7 Jul 2014 00:14:27 -0400 > > Please try clicking the "raw" link to the right of the .exe found here: > >

Same CD. Any Linux distribution without the 5.X series boots on this machine. We can use 4.06 and it boots just fine. It's not the computer's hardware. Like I said, we can take the CD out of the GX620 and place it in the 9010 and it boots. Put 4.06 on the CD, and they both boot. Patrick On Sat, Jul 6, 2013 at 7:18 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Fri, Jul 5,

The following comment in win/syslinux.c seems fairly innocent: /* Map the file (is there a better way to do this?) */ So I?ve got an ?ntfssect? git repository going: http://git.zytor.com/?p=users/sha0/ntfssect.git;a=summary Hopefully Paulo can plug its functions into his NTFS working repository. It appears that we?ll have to take one path (in the Windows installer) for FAT and one path

In Syslinux-5.00, is the goal that the core and .c32 modules alike will use the same heap? There is a bug I am thinking about: - QEmu with 1024 MiB RAM - Syslinux 4.06 - .c32 can realloc() up to 1013 MiB - QEmu with 1024 MiB RAM - Syslinux 5.00-pre9 - .c32 can realloc() up to 45 MiB I am wondering if there's a maximum-allocation-size being hit, or if it's actually a bug I should look

Below, attached, and available at the 'ifmemdsk' branch at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=a975c12919bbd48739fede4ebfe099d98b87192e Review welcome! - Shao Miller ----- From a975c12919bbd48739fede4ebfe099d98b87192e Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sat, 6 Aug 2011 05:24:46 -0400 Subject: [PATCH]

Hello, on a somewhat recent machine (Dell T1600) I'm unable to use my usual setup (pxelinux as a boatloader also for local OS - typically windows). The BIOS is capable of using UEFI, but this is turned off. Unfortunately all I get is a message telling me that pxelinux is unable to boot from local disk. The config entry looks like this: LABEL local MENU LABEL OS installed on local disk

For anyone wanting to boot an .ISO with MEMDISK: http://git.etherboot.org/?p=people/andytim/syslinux.git;a=shortlog;h=ref s/heads/memdisk-iso NOTE: Your protected-mode OS (Windows, Linux, *BSD) booted from such a MEMDISK will not magically find the MEMDISK image in RAM and use it as a CD without a MEMDISK driver. There are currently 0 MEMDISK drivers in the field, but that might change someday.

Hi there, i just build a new ipxelinux.0 with an EMBED=../../syslinux-5/core/pxelinux.0. i'm trying to load up my vesamenu.c32 menu from http:. and offcorse i want this as optimal as possible, with the least needed GET requests. OLD situation with v4: PXE ROM -> ipxelinux.0 (tftp) -> menu.php (http) -> vesamenu.c32 (http) NEW situation with v5: PXE ROM -> ipxelinux.0 (tftp)

Hi Community - I would like to request that SYSLINUX be extended to install on a filesystem image file on the Windows platform. This feature is available on Linux (option -t); however, on Windows SYSLINUX only installs with a raw device path. This feature would be use by another open source project. As an small incentive, I'll offer a small, token bounty ($50) for the developer that

Good day to you, too. No worries about the delay. I understand how busy everyone is with SYSLINUX. Gladly, the project continues to develop and improve. With that said, thanks for today's flurry of activity regarding my reported problem. Impressively, the debug version of MEMDISK that you had directed me to use appears to have done the trick. Results below. command line:

On 8/27/2014 18:05, Bill Cunningham wrote: > I have just jined this list. I can't seem to boot from a USB and my > BIOS > recognizes my sandisk USB by name. I can't figure out what modules to use. > mbr.bin and parted is one method. Then syslinux is run and a > syslinux.cfg is > needed. Is this sufficent for syslinux? > > LINUX bzImage //kernel image > INITRD

On 7/6/2014 01:55, Ady wrote: > > I can see 1 branch in Shao's git repo that might be relevant: > > mdiskchk_win > > [quote] > > mdiskchk.exe will be the Windows counterpart for the DOS version > mdiskchk.com. The purpose is to be able to scan low memory for > instances > of Syslinux' MEMDISK and report these instances' parameters to a > user

Is there a specific version of MinGW which is supposed to work for this? Any guidelines for building on Windows? Chris