The majority of the project options are contained in the Mini-WinFE project script - to display them, ensure that the Script button is selected and click on Mini-WinFE at the top of the directory tree on the left....
...this will display one of the screens below (toggle between them by clicking on the tab buttons (Options1, Options2, etc.)) -
Make sure this option is set to NO for the first run of the project. Source files will be added to a cache for use when re-building the project - x86 source files will be cached to \Projects\Cache\source\x86, x64 source files will be cached to \Projects\Cache\source\x64.
Set this option to YES to use an existing cache, and change option 3 to toggle between x86 and x64 caches.
NOTE - only one x64 and one x86 build can be added to the cache at any one time. If the cache contains 64-bit Windows 10(.0.14393) files for example, then they will need to be overwritten if you want to create a build for a different 64-bit version of Windows (e.g. Windows 8.1).
Use this option to set the size of the RAM Disk (in MB) - this is the amount of writable space on the SYSTEMDRIVE that will be available when WinPE is running.
This setting is ignored in WinPE 5.x if system RAM is greater than 1GB. It will only be used when RAM is less than (or equal to) 1GB.
If option 1 (Attempt to use Existing Cache?) is set to NO, then the source architecture will be obtained using wimlib-imagex and the WinPE Processor Architecture setting is ignored unless the source files fail verification checks.
If option 1 is set to YES, then the WinPE Processor Architecture should be used to identify the cache to be used. Basically, if the first run of the project used x86 source files then they will have been cached to \Projects\Cache\source\x86. If x64 source files were used on a previous run then they will have been cached to \Projects\Cache\source\x64. Using option 3 allows you to choose between the two different caches.
SysWoW64 is required in order to run 32-bit applications on a 64-bit WinPE. The following information is from here -
SysWoW64 is not included in 64-bit versions of WinPE, however it is possible to add limited SysWoW64 support in this project (LinuxReader is not working and FTK Imager only works with some sources). Please note that SysWoW64 is only supported when the following 64-bit source files are used -
The Cache Files script included in the Tools folder will add the SysWoW64 dependencies to the cache. Please note that if your source files are compiled from Option 3 in the Cache Files script then SysWoW64 support might not include the full registry support that is added when using Windows Installation media sources.
When using Windows Installation Media source files, if NO is selected during the build process and 64-bit source files are detected, then you will be prompted to add the SysWoW64 dependencies to the Cache.
The 5-Wow64 script (hosted on TheOven.org) was used as a base to identify SysWoW64 file and registry dependencies. Credits therefore go to everyone involved in the 5-Wow64.script (including JFX, Lancelot, 2aCD, ChrisR. Note from the script - "...All credits go to Microsoft for developing this Operative System and to everybody on the BootLand forums for helping on the debuggind and improvement of this plugin. yamingw setWow64 tool.").
Use image number 2 when using Windows installation media. The only time you should need to use image number 1 is when using boot.wim from the WAIK or ADK - which I consider to be more advanced usage.
If an existing cache is used, then the configuration file created when the cache was created will be read and the image number of boot.wim will be checked. If this is different to the image number selected in this option, then the user will be asked which image to use - either the image number from the configuration file, or the image number specified in this option.
In the majority of cases, image number 1 should be selected when using Windows installation media. The only time you might need to use a different image number is when using a Windows Server source. Windows 2008 R2 (SP1) and Windows 2012 R2 releases for example contain multiple images (in install.wim) - image number 1 is a Server Core Installation and doesn't contain some of the file dependencies required in Mini-WinFE.
I would personally recommend using the INJECT method as it's faster and requires less free storage space. If the EXTRACT method is used then all of the files contained in boot.wim will be extracted, modified and repacked.
If the DEFAULT setting is used then no settings will be changed and the keyboard layout from the existing source files will be used. There are a limited range of alternative Keyboard Layout's available in this script.
This setting is only used if the source file language cannot be verified by wimlib-imagex.
Mini-WinFE is intended to be a light build of WinPE, aimed primarily at system deployment, backup, repair and restore. Some of the applications are relatively large in size and add significantly to the size of boot.wim - the file containing the WinPE operating system. FTK Imager (version 220.127.116.11) for example is 74 MB when unpacked.
Mini-WinFE has an option to copy the majority of the Program files to an external directory so that they are not packed in to boot.wim. There are a number of advantages to this approach - the main one being the ability to update individual programs without having to rebuild the project. As an added advantage boot.wim will be smaller in size and less RAM is required to boot Mini-WinFE.
If this option is selected, the programs will be copied to the \WinFE.Project.Output\ISO.ROOT\ directory (this path is relative to WinBuilder.exe), and will be added to the root of the CD\DVD image if the Create ISO script is enabled. Alternatively, manually copy the Programs directory to the root of a USB drive.
To enable this option, select NO in option 8] Programs in boot.wim. Essential programs (file manager, WProtect.exe, etc) will still be copied to boot.wim. The Programs that will be copied to the \WinFE.Project.Output\ISO.ROOT\ directory currently include -
These programs are self-contained and all dependencies are added to individual program directories - they should therefore work in other WinFE/WinPE builds based on the same Windows source files (e.g. processor architecture and build versions match).
If you chose not to add Programs to boot.wim then a menu option (Find Programs) will be added to the bblean menu...
...Selecting Find Programs will launch a batch file that will check the root of all mounted drives (the drive must be visible from WinPE) and depending on the settings used in the project, will either start LaunchBar or search for (and run) \Programs.x86\MiniWinFE.menu.cmd / \Programs.x64\MiniWinFE.menu.cmd.
The MiniWinFE.menu.cmd file will (if found) add menu entries for all of the programs listed above if they were included in the build - it will also add registry entries for some programs including 7-zip, Sumatra and Opera. Optionally, MiniWinFE.menu.cmd can be executed manually if you want to use a different folder path - or simply launch the executables using a file manager.
Document date - 27th April 2017