Best posts made by dangbird

I did create the Boot Files after...
Assuming we just wanted to do it with the Boot Files ISO and not PXE...

I have done the below with another platform Will not mention here to not have others bail from this Great Product.

So I think I just have a syntax issue with TheOpenEm.
Assuming I copy the appropriate files to the correct folders..

kernel http://x.x.x.x/iso/pcunlocker/wimboot
initrd http://x.x.x.x/iso/pcunlocker/bootmgr.efi
initrd http://x.x.x.x/iso/pcunlocker/Boot/BCD bcd
initrd http://x.x.x.x/iso/pcunlocker/Boot/boot.sdi boot.sdi
initrd http://x.x.x.x/iso/pcunlocker/sources/boot.wim boot.wim
boot

NEW Entry with TheOpenEm
IF I create a folder called "pcunlocker" in this case...

kernel pcunlocker/wimboot
initrd pcunlocker/bootmgr.efi
initrd pcunlocker/Boot/BCD bcd
initrd pcunlocker/Boot/boot.sdi boot.sdi
initrd pcunlocker/sources/boot.wim boot.wim
boot

Hope that is clear as mud. I appreciate the feedback.

As a follow up, I noticed the system does create the Database Entry for the Custom Menu Entry, but sometimes does not update the files in the pxelinux.cfg folder. So possibly the system reads one but not the other. It may be my ignorance as to how the custom entry works. Basic goal is to boot an ISO using PXE. Possibly this is a bug who knows.

Hello - I wanted to create a pxe booted ISO from the Custom Boot Entry. Was hoping someone could point out the steps. I basically copied the Current Menu Option..
kernel http://ipofmyopenemserver/fileIwantToBoot

Getting "error: can't find command kernel.
Thank You!