Thanks!
The only way I could see to write to a file is using the win32 version and
specifying a file after the drive letter.
syslinux.exe D: syslinux.bin
This throws the same message on to boot and just says Boot error.
Is that what you meant to write it to a file? I tried in Linux:
syslinux --install syslinux.bin
and that did not work(throws an error that syslinux.bin does not exist). I
checked the docs and don't see any flags to tell syslinux to install to a
file instead of a device.
I tried this with 3.86 and 4 (as Wes suggested he has had success with this
in the past).
On Mon, May 11, 2020 at 5:01 PM Adan Calderon <adancalderon at gmail.com>
wrote:
> try installing syslinux 3.86 or 4 to a boot sector "file" not the
actual
> boot sector. then chainload that file.
>
> On Mon, May 11, 2020, 3:57 PM Adan Calderon <adancalderon at
gmail.com>
> wrote:
>
>> the mboot file from esxi is not the same as syslinux. i once saw the
>> source as it is avilable from vmware and it's not the same as the
one from
>> syslinux. you can chain load an older syslinux (4.something works)
that
>> then can run vmware's version of mboot. or maybe you make
vmware's version
>> work i think the source was GPL.
>>
>> On Mon, May 11, 2020, 3:45 PM Max via Syslinux <syslinux at
syslinux.org>
>> wrote:
>>
>>> Hello,
>>> I was wondering if someone might give me a hand. I have a
multiboot
>>> drive I maintain and I am trying to add the ESXi installer to it.
>>> It seems well documented that VMWare uses their own mboot.c32
file
>>> which
>>> is built from not the same code in SYSLINUX mboot.c32 3.86 .
I'm using
>>> the
>>> Syslinux 6.04 from the Ubuntu repositories. I have compiled
Syslinux
>>> 3.86
>>> . I thought I could try to load the older version of syslinux by
>>> chainloading it.
>>>
>>> This is what I have in the config:
>>> COM32 chain.c32
>>> APPEND FILE=/ESXi/syslinux
>>>
>>> syslinux is the compiled 3.86 binary.
>>>
>>> I get :
>>> "WARN: The sector won't be mmapped, as it would conflict
with the boot
>>> file.
>>> Booting...."
>>> It just hangs there.
>>>
>>> I am doing this in good old BIOS mode.
>>>
>>> Can you guys shed any light on the error and give me some
indication of
>>> what documentation to read next?
>>>
>>> Is this even possible?
>>>
>>> Thanks,
>>> Max
>>> _______________________________________________
>>> Syslinux mailing list
>>> Submissions to Syslinux at syslinux.org
>>> Unsubscribe or set options at:
>>> https://lists.syslinux.org/syslinux
>>>
>>