(2014-04-01 08:44)KingBonecrusher Wrote:  I think there is a "BUG" in wimboot. Iam using the same files of pxelinux on a windows based server and on an linux based server. On the linux system wimboot loads everything without any problem, on the windows system it fails with missing bootmgr.exe. After a lot of troubleshooting it could only be the slash and blackslash problem.

(2014-04-01 11:54)mcb30 Wrote:  

(2014-04-01 08:44)KingBonecrusher Wrote:  I think there is a "BUG" in wimboot. Iam using the same files of pxelinux on a windows based server and on an linux based server. On the linux system wimboot loads everything without any problem, on the windows system it fails with missing bootmgr.exe. After a lot of troubleshooting it could only be the slash and blackslash problem.

The "bug" is in syslinux's com32/modules/linux.c, in the code

Code:

    /* Forget the source path */
    target_fname = fname;
    while ((p = strchr(target_fname, '/')))
        target_fname = p + 1;

As can be seen, this code is attempting to find the filename by finding the last '/' character in the path. In the case of a path using backslashes, this will end up with "filenames" such as "pxelinux.cfg\images\winpe\boot.wim" rather than "boot.wim".

Use normal (forward) slashes instead. The use of backslash as a path delimiter is an abomination.

If your Windows server refuses to understand normal slashes as a path delimiter (which is unlikely; the Windows kernel will accept either normal slashes or backslashes), then you can use the "@filename" extension to "initrdfile" to explicitly specify a location. For example (untested):

Code:

LABEL wimbootpe
menu label WindowsPE
    COM32  pxelinux.cfg\modules\linux.c32
    APPEND pxelinux.cfg\images\loader\wimboot initrdfile=pxelinux.cfg\images\winpe\bootmgr@bootmgr,pxelinux.cfg\images\winpe\b​cd@bcd,pxelinux.cfg\images\winpe\boot.sdi@boot.sdi,pxelinux.cfg\images\winpe\boo​t.wim@boot.wim

Michael

(2014-04-01 12:00)KingBonecrusher Wrote:  Thank you for your fast answer! I was thinking that the files inside the encapsulated cpio are in folders and wimboot creates the basename, but ok that makes also sense for me :-) I will try the "@" sign. I must use an pxelinux 4.06 with initrdfile patch, because a needed software will not boot with 6.02 or ipxe itself.

(2014-04-01 12:02)mcb30 Wrote:  

(2014-04-01 12:00)KingBonecrusher Wrote:  Thank you for your fast answer! I was thinking that the files inside the encapsulated cpio are in folders and wimboot creates the basename, but ok that makes also sense for me :-) I will try the "@" sign. I must use an pxelinux 4.06 with initrdfile patch, because a needed software will not boot with 6.02 or ipxe itself.

Which needed software doesn't work with iPXE, and what goes wrong?

Michael