Syslinux - Feb 2015 - VMWare ESX mboot.c32

Hi.

VMWare has an own/modified mboot.c32, which is capable of using
Configfiles. This mboot.c32 is on every Installsystem for their ESXi
hypervisor install-iso.
Until syslinux 4.07 this works with pxelinux out of the box.
Since 5.x this mboot.c32 will not work anymore.
There seem to be more modifications than only a parameter "-c".

Does anyone has an idea what has changed so this mboot.c32 is not
working anymore and/or how to get it working again?

Using original mboot.c32, I tried to give it all parameters which are in the
configfile, did not boot the ESXi installer.

MfG regards,
Holger Baust

-- 
freenet Datenkommunikations GmbH
Ein Unternehmen der freenet Group
Willst?tterstra?e 13
D-40549 D?sseldorf

Tel.: +49 (0) 211 53087 519
Fax: +49 (0) 211 5381573
Mobil: +49 (0) 170 4930127

holger.baust at freenet.ag
www.freenet.de
mobil.freenet.de
www.mobilcom-debitel.de

Gesch?ftsf?hrung: Andreas J?rgensen, Dr. Frank R?ders
Sitz der Gesellschaft: Hamburg
HRB 88147, Amtsgericht Hamburg


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL:
<http://www.zytor.com/pipermail/syslinux/attachments/20150206/3dc00358/attachment.sig>

On Fri, Feb 6, 2015 at 8:27 AM, Holger Baust via Syslinux
<syslinux at zytor.com> wrote:
> Hi.
>
> VMWare has an own/modified mboot.c32, which is capable of using
> Configfiles. This mboot.c32 is on every Installsystem for their ESXi
> hypervisor install-iso.
> Until syslinux 4.07 this works with pxelinux out of the box.
> Since 5.x this mboot.c32 will not work anymore.
> There seem to be more modifications than only a parameter "-c".
>
> Does anyone has an idea what has changed so this mboot.c32 is not
> working anymore and/or how to get it working again?
Everything.  You can't mix COM32s with various versions of Syslinux,
especially across major versions which have breaking compatibility.

-- 
-Gene