Syslinux - Jul 2013 - make efi64 install in syslinux-6.02-pre3 fail

Am 12. Juli 2013 15:06:54 schrieb Matt Fleming <matt at
console-pimps.org>:
> Which installer? I would hazard a guess that the installer is also bios
> specific and is going to need to be tailored for EFI boot anyway.
>
> --
> Matt Fleming, Intel Open Source Technology Center
It's a little be complex.
It's a DVD based installer where I try to change this to be installable via 
network.
The DVD are masterpreloads from a Notebook company. I think you know which :-)

We have a lot of this notebook to install so it's easier to do this via 
network (also different models/types).

OK, now the problem:
You are right, the old versions of the installer (XP and Win7) run under 
BIOS. The new (Win8) require EFI boot.
I test it with BIOS boot, but the preload install script from this company 
check if the boot is EFI or legancy.
If it's not EFI it stop with the info that the boot methode must be EFI. 
Next I tried to boot via some windows pxe methodes and
wimboot to only need some boot files and the wim image. But when I do it 
this way the installer fail with the info that the system
must be booted from CD/DVD.

I tried to change the installer and also found the registry key with the 
boot info, but the installer perform a wpeutil
which set the registry back to 'ramdisk' when I not boot from CD or
stored
iso image in memdisk.

It's very frustrating

Thanks and regards
Michael


Gesendet mit AquaMail f?r Android
http://www.aqua-mail.com

On 7/12/2013 14:22, Michael Szerencsits wrote:
> Am 12. Juli 2013 15:06:54 schrieb Matt Fleming <matt at
console-pimps.org>:
>> Which installer? I would hazard a guess that the installer is also bios
>> specific and is going to need to be tailored for EFI boot anyway.
>
> It's a little be complex.
> It's a DVD based installer where I try to change this to be installable
> via network.
> The DVD are masterpreloads from a Notebook company. I think you know
> which :-)
>
Which one, just out of curiosity?
> We have a lot of this notebook to install so it's easier to do this via
> network (also different models/types).
>
> OK, now the problem:
> You are right, the old versions of the installer (XP and Win7) run under
> BIOS. The new (Win8) require EFI boot.
> I test it with BIOS boot, but the preload install script from this
> company check if the boot is EFI or legancy.
> If it's not EFI it stop with the info that the boot methode must be
EFI.
What is the "preload install script"?  Is the DVD El-Torito-bootable
and
it runs something which reports that the system must be EFI _before_ it 
boots any OS?
> Next I tried to boot via some windows pxe methodes and
> wimboot to only need some boot files and the wim image. But when I do it
> this way the installer fail with the info that the system
> must be booted from CD/DVD.
>
If you are using PXE, then that's along the same lines as BIOS.  If they 
want EFI, that's a stronger requirement than CD/DVD.  If you are certain 
that the OS can be installed to a non-EFI system, then your PXE method 
doesn't seem like it matches whichever PXE method the OS supports.
> I tried to change the installer and also found the registry key with the
> boot info, but the installer perform a wpeutil
> which set the registry back to 'ramdisk' when I not boot from CD or
> stored iso image in memdisk.
>
> It's very frustrating
Perhaps there is a supported network-boot-installation process for this 
OS.  If you can find the NBP and DHCP parameters it needs, you can 
likely chain the Network Bootstrap Program from a nice PXELINUX menu.

- Shao Miller

> Which one, just out of curiosity?
They are Sony notbooks
> What is the "preload install script"?  Is the DVD
El-Torito-bootable and
> it runs something which reports that the system must be EFI _before_ it 
> boots any OS?
> If you are using PXE, then that's along the same lines as BIOS.  If
they
> want EFI, that's a stronger requirement than CD/DVD.  If you are
certain
> that the OS can be installed to a non-EFI system, then your PXE method 
> doesn't seem like it matches whichever PXE method the OS supports.
> Perhaps there is a supported network-boot-installation process for this 
> OS.  If you can find the NBP and DHCP parameters it needs, you can 
> likely chain the Network Bootstrap Program from a nice PXELINUX menu.
> 
> - Shao Miller
> 
The CD is based on Windows PE. It can be bootet in BIOS and EFI mode. 
I already tried the bootmgfw.efi from Windows. This work, but after the WinPE is
booted a program is stated and this check the BIOS
if it is set to EFI boot. If not it fail. This program also check the registry
for the boot media.
I tried to manually change it from Ramdisk to CDROM, but before it check the
registry it call a program named wpeutil and this change
the registry back to Ramdisk. I also can't rename the wpeutil because than
the program fail.

I tried to set the bootmode to legancy and was able to boot and run the program,
but before start to recover the system it checks the
boot mode and than it fails with the message that it isn't set to EFI.

The previos version of the recovery CD (WinXP and Win7) use a similar script,
but doesn't require EFI. I also can't use the older script
for the new systems, because the notebook types are hard coded in the script.

Regards
Michael