I believe your only chance is to put all the required parts (bootmgr.exe,
boot.sdi, BCD, boot.wim) onto some sort og an image (iso, hdd,,,) and download
and emulate it with for instance memdisk. I personally never really got
reliable results with memdisk and any winpe3.0 iso, so I ended up with
chainloading grub.exe for that job. Did anybody have success with memdisk and
winpe3.0 iso?
So when putting the 4 required parts on an image, you don't need bootmgr.exe
and use bootmgr instead. The reason is simply because bootmgr.exe only "speak
TFTP", and cannot be chained over HTTP. And you don't need the nbp that you
otherwise use in your pure ms environment.
I have experienced rather good results with pxelinux and gpxe (with iso
emulation) compared to standard bootmgr.exe/wim. But as people pointed out at
the msfn forums, it could be that my bootmgr.exe/wim results are not entirely
correct when done in a non-natively supported environment (not through WDS).
But the wim method was beaten by the iso method by much, while still over tftp.
Have not done exact comparisons of tftp vs http yet. Do we know of a link to
such a report?
Joakim Schicht
_________________________________________________________________
Få nye Windows Live™ Messenger.
http://download.live.com/messenger_______________________________________________
gPXE mailing list
[email protected]
http://etherboot.org/mailman/listinfo/gpxe
