similar to: VMware ESXi safeboot.c32 Source Code

Displaying 20 results from an estimated 6000 matches similar to: "VMware ESXi safeboot.c32 Source Code"

2009 Oct 29
2
Patches for chain.c32: Error message is more detailed and chainload another isolinux.bin
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
2010 Jun 25
1
chain.c32 GPT Support
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
2012 Oct 26
2
[PATCH] 4 Patches for initrd+= and initrdfile= Options
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:
2012 Nov 23
1
[PATCH] nictype.c32: PXELINUX module to display UNDI NIC bus type...
Applies to Syslinux 4.06. Attached, below, and available at: Repository: git://git.zytor.com/users/sha0/syslinux.git Branch: nictype - Shao Miller ----- From 2764e260e12d9769e3b699e4213b9a164e64924a Mon Sep 17 00:00:00 2001 From: Shao Miller <sha0.miller at gmail.com> Date: Thu, 22 Nov 2012 20:43:25 -0500 Subject: [PATCH] nictype.c32: PXELINUX module to display UNDI NIC bus
2012 Nov 04
1
hexdump.c32 for Syslinux 5.00-pre9
Applies to Syslinux 5.00-pre9. Attached, below, and available at: Repository: git://git.zytor.com/users/sha0/syslinux.git Branch: hexdump - Shao Miller From c9c67dd61ba0b11e46d514601cf0722e1b43017c Mon Sep 17 00:00:00 2001 From: Shao Miller <sha0.miller at gmail.com> Date: Sun, 4 Nov 2012 00:26:32 -0400 Subject: [PATCH] hexdump.c32: Simple file hex-dumper Usage: %s
2010 Jun 12
1
[PATCH] ifcpuXX: Support multiple parameters with labels
Even though Doug's out of the office, I'm submitting a patch to the ifcpu[|64].c32 COMBOOT32 modules for testing. Also available for perusal with a web browser at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=cc70d0fa5 5e35fabf250f4dccbaed2fa44f56da7 - Shao Miller --- >From cc70d0fa55e35fabf250f4dccbaed2fa44f56da7 Mon Sep 17 00:00:00 2001 From: Shao
2011 Aug 06
4
[PATCH] ifmemdsk.c32: Allow boot options based on presence of MEMDISK
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]
2012 Oct 03
1
[PATCH] pxedump.c32: Simple PXE cached packet dumping
Not much to it, but thought I'd offer. - Shao From c668e24421a344231fc3fba31a26c88e92d03f43 Mon Sep 17 00:00:00 2001 From: Shao Miller <sha0.miller at gmail.com> Date: Tue, 2 Oct 2012 22:02:04 -0400 Subject: [PATCH] pxedump.c32: Simple PXE cached packet dumping Usage: pxedump.c32 --cached Mostly useful with a serial connection, to capture the lengthy output Signed-off-by: Shao
2014 Jul 07
2
mdiskchk and WinPE
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: > >
2014 Jul 06
4
mdiskchk and WinPE
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:
2010 Mar 30
1
Req
[1} Gert Hulselmans wrote: > > ...Thanks. > > I still think chain.c32 should be able to do a reverse partition > lookup, to determine from which partition it was booted. This would be > useful to boot ntldr, setupldr.bin, bootmgr, grldr, ... when you want > to boot it from the same partition as from which SYSLINUX is booted, > without specifying the partition explicitly
2010 Jun 17
2
MEMDISK, MDISKCHK.COM
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
2024 Jan 21
1
Running VMware ESXi network installer via syslinux/menu
Hello, On 1/20/2024 1:03 AM, Adan Calderon wrote: > Remember the vmware versions of their loader are diffrent. Phew, what does that mean? It's their "bootx64.efi". Running "file" on it says it's an "MS-DOS executable". > I remember looking at the source for the mboot file and it was > diffrent from the syslinux version. Not sure what this means
2011 Aug 13
1
NTFS File Sectors
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
2024 Jan 19
2
Running VMware ESXi network installer via syslinux/menu
Hello, So I'm running syslinux.efi Which loads menu.c32 Which is supposed to start ESXi's bootx64.efi/mboot.efi But that gives """ Loading mboot.efi... ok Invalid Boot signature 0x2, bailing out Booting kernel failed: Bad file number """ Secure boot is disabled. Thoughts? The reason why it would be nice using PXE and syslinux here is because we have
2024 Jan 20
1
Running VMware ESXi network installer via syslinux/menu
On Sat, Jan 20, 2024 at 12:21:37AM +0100, marki via Syslinux wrote: > Hello, > > So I'm running syslinux.efi > Which loads menu.c32 > Which is supposed to start ESXi's bootx64.efi/mboot.efi > > But that gives > > """ > Loading mboot.efi... ok > Invalid Boot signature 0x2, bailing out > Booting kernel failed: Bad file number >
2011 Jan 25
2
MEMDISK issue with OptiPlex GX280,620
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:
2024 Jan 20
1
Running VMware ESXi network installer via syslinux/menu
Remember the vmware versions of their loader are diffrent. I remember looking at the source for the mboot file and it was diffrent from the syslinux version. On Fri, Jan 19, 2024, 5:25 PM marki via Syslinux <syslinux at syslinux.org> wrote: > Hello, > > So I'm running syslinux.efi > Which loads menu.c32 > Which is supposed to start ESXi's bootx64.efi/mboot.efi >
2024 Jan 21
1
Running VMware ESXi network installer via syslinux/menu
On 1/20/2024 1:29 AM, Ralph Ronnquist via Syslinux wrote: > On Sat, Jan 20, 2024 at 12:21:37AM +0100, marki via Syslinux wrote: >> Hello, >> >> So I'm running syslinux.efi >> Which loads menu.c32 >> Which is supposed to start ESXi's bootx64.efi/mboot.efi >> >> But that gives >> >> """ >> Loading mboot.efi... ok
2012 Nov 05
2
New Memory Allocation
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