[gPXE] Win PE

[Kyle Kienapfel]

C:\Windows\system32>bcdedit -create -application osloader /d "WinPE"
The entry {e130d653-5b23-11df-aac2-bac3ae784ab1} was successfully created.

^ randomly generated number, thats the WinPE GUID, edit out the %WinPE
GUID% accordingly


bcdedit says:
Many of the Bcdedit commands require identifiers. An identifier
uniquely identifies entries contained in the store. An identifier takes the
form of a globally unique identifier, or GUID. A GUID has the following format,
where each "x" represents a hexadecimal digit.

    {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}

hard coding a GUID into the instructions might be an idea, eg

C:\Windows\system32>bcdedit -create
{01234567-0123-0123-0123-123456789abc} -application osloader /d
"WinPE"
The entry {01234567-0123-0123-0123-123456789abc} was successfully created.




On Fri, May 21, 2010 at 2:33 PM, Luca <lucarx76 at gmail.com> wrote:
> Hi all,
>  I'm trying to gPXE boot WinPE with Memdisk. I followed the instruction I
> founf here
>
> http://www.etherboot.org/wiki/winpe_memdisk
>
> When I boot a VM with Windows Vista Recovery CD, while executing the
> instructions
>
> bcdedit -set {bootmgr} default %WinPE GUID%
>
> I get an error. It says "The entry data is not valid as specified".
>
> Tried using bcdedit /? for help, but with no luck so far.
>
> Does anyone know if there is a different approach to gPXE boot WinPE using
> an HTTP server?
>
> Thank you,
>  Luca
>
> _______________________________________________
> gPXE mailing list
> gPXE at etherboot.org
> http://etherboot.org/mailman/listinfo/gpxe
>
>