Now to correct my oops 
. I saw the patching requirement but couldn't find the acutal patches from the webarchiver to patch 4.06 syslinux. I did some digging and found that the fixes were mirged into 5.00 pre. I grabbed the latest of 5.00 pre 13 and wimboot i grabbed the latest as well. Compairing 1.03 files to the "latest" file they appear to be the same. I'm going to say i'm on 1.03 wimboot. I haven't downloaded anything with iPXE at this time.
Ok, so the latest
Syslinux +
wimboot should be working, as long as wimboot supports this
Windows PE 4.0 you're talking about. It's possible that it doesn't!
Forgive the lack of knowledge, can you provide an example with the @. All the example setups i saw for initrdfile were done with ',' However I'm not that versed in it yet.
Sure.
LABEL x86
MENU PASSWD P
MENU LABEL (32bit)
COM32 linux.c32
APPEND PXEImages/winpex86/wimboot initrdfile=PXEImages/winpex86/bootmgr@bootmgr,PXEImages/winpex86/Boot/BCD@BCD,PXEImages/winpex86/boot/fonts/segmono_boot.ttf@segmono_boot.ttf,PXEImages/winpex86/boot/fonts/segoe_slboot.ttf@segoe_slboot.ttf,PXEImages/winpex86/boot/fonts/wgl4_boot.ttf@wg14_boot.ttf,PXEImages/winpex86/boot/boot.sdi@boot.sdi,PXEImages/winpex86/Sources/boot.wim@boot.wim
I noticed that you might've had a typo for segoe_
slboot.ttf in your original. However, the
source_path@dest_path examples I gave just above probably won't help, as each of the filenames is the same. Maybe the typographical error correction will help.
I did some more testing last night as well with 5.00. It seems 5.00 pre13 with the memdisk fixes the issue i was having with "not enough memory to load specified image" on some of my systems/images but as you stated sha0 its not efficent. However i will still probably need this for booting the legacy XP SP3 CD we have at this time.
How? Are you using a
MEMDISK driver?
The updated version didn't work with WinPE 4.0 it allowed it to boot showing the fish however failed to complete the boot into PE. I haven't looked more into why but i'd still rather go to the WimBoot direction as it was faster even with TFTP. The only thing i didn't like about the new version of memdisk is it doesn't show the old dots that it's acutally doing something. Trivial i know but i have my reasons .
That isn't MEMDISK showing the dots, it's the boot-loader (
PXELINUX, in your case). If this change is a major irritant, please report it to the Syslinux mailing-list for consideration.
Incase you're wondering here's what im using for my XP CD
LABEL XP Sp3 Disk
MENU PASSWD XP
MENU LABEL XP Sp3 Disk
KERNEL PXEImages/memdisk/memdisk
APPEND iso initrd=PXEImages/WinXP/Windows_XP_Professional_32BIT.ISO ro
Please do
not use spaces in your
LABEL entries. Also, I'd prefer using the
INITRD directive and using some nice indentation, personally:
LABEL xpsp3disk
MENU PASSWD XP
MENU LABEL XP Sp3 Disk
KERNEL PXEImages/memdisk/memdisk
APPEND iso
INITRD PXEImages/WinXP/Windows_XP_Professional_32BIT.ISO
Anything else i can test with i'd be glad too. I'm working on a global deployment and troubleshooting solution at this time for PC class devices but that will move to servers as well.
I haven't seen much about wimboot and Windows PE 4.0. Just in case there's a Syslinux + wimboot problem, could you please try
iPXE + wimboot? From the iPXE CLI, you'd do:
dhcp net0
kernel PXEImages/winpex86/wimboot
initrd PXEImages/winpex86/bootmgr bootmgr
initrd PXEImages/winpex86/Boot/BCD BCD
initrd PXEImages/winpex86/boot/fonts/segmono_boot.ttf segmono_boot.ttf
initrd PXEImages/winpex86/boot/fonts/segoe_slboot.ttf segoe_slboot.ttf
initrd PXEImages/winpex86/boot/fonts/wgl4_boot.ttf wg14_boot.ttf
initrd PXEImages/winpex86/boot/boot.sdi boot.sdi
initrd PXEImages/winpex86/Sources/boot.wim boot.wim
boot
If it doesn't work with iPXE + wimboot either, then it might be worth asking the iPXE mailing-list if anyone has tried wimboot with Windows PE 4.0 and if it's expected to work.
