[ipxe-devel] wimboot with Windows 2016

Christian Nilsson nikize at gmail.com
Fri Oct 28 17:34:06 UTC 2016


Nice to see the issue was found! (?)

I think that the proper thing here would be for wimlib to check for
existing paths and use the same casing.
If we consider how dism does this it will have the path and when you add a
file it will add it to the existing path and using existing casing. Then
when the wim is commited the changed files is stored, using that existing
path and casing.

On Fri, Oct 28, 2016 at 10:04 AM, Floris Bos <bos at je-eigen-domein.nl> wrote:

> On 10/28/2016 08:35 AM, Andreas Hammarskjöld wrote:
>
>> Where did you get the boot.wim from, which ADK?
>>
>
> I am not using the ADK, but just copy sources/boot.wim from the Windows
> installation ISO (SW_DVD9_NTRL_Win_Svr_Essentia
> ls_2016_64Bit_English_-2_X21-22603.ISO), and patch that with
> wimlib-imagex to have a custom startnet.cmd
>
> And I think I found the issue.
> It has to do with my patching.
>
> I use a wimlib-imagex script that looks like:
>
> ==
> delete --force /setup.exe
> delete --force /Windows/System32/startnet.cmd
> add /tmp/startnet.cmd /Windows/System32/startnet.cmd
> ==
>
> However in the final 2016 release, the existing folder is no longer called
> /Windows/System32 but /windows/system32
> And ipxe doesn't seem to handle the case when there is both a /Windows and
> /windows added to the .wim
> Not sure whether or not it should.
>
>
>
> Yours sincerely,
>
> Floris Bos
>
> _______________________________________________
> ipxe-devel mailing list
> ipxe-devel at lists.ipxe.org
> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20161028/66aa450b/attachment.htm>


More information about the ipxe-devel mailing list