Reason to exclude X:\ Drive from "Use a custom .cmd script to handle the Windows PE stage"

[MaKaNu]

The first step of the example script excludes the X:\ drive from the variable search.

In my scenario the WinPE is loaded from netbootxyz and the WinPE Drive already provides all our Drivers now under X:\$WinPEDrivers$.
Further the WinPE has already the network drivers loaded since the Installation Medium is mounted via SMB.

Is there a reason why in the search loop at the beginning of the custom .cmd the X: Drive was excluded.

Since I already need the network driver backed into the winpe I don't see a reason why mount the drivers separately.

Would adding X in the for loop cause any harm or side effect?

This question is related to #298 and #288

[cschneegans]

Thank you for bringing this to my attention! I did not think about custom boot.wim images that may include $WinPEDrivers$ or $OEM$ folders. There is certainly no harm in searching the X: drive for these items as well.

I have now modified the sample script (i.e. the Use a custom .cmd script… option) as well as the script generation code (i.e. the Generate a .cmd script… option) to include this drive, via 99629e4.