WimBuilder2 - New Builder with Re:WIN10XPE project(~20H2 Supported)

Hi, Lancelot

I considered tutorial mode for first startup WimBuilderUI.
With html power, step by step teach people to click the button(s) with notice flow box for the description dynamically.
(like some game for first player, show [AWSD + OO] to prompt MOVE,  press [SPACE BAR] to JUMP)

The framework(html+js+bat) can do very cool things, but I have no much time on it. (I'm not good at the Web UI develop)

I posted GIF for how to build, but theoven.org only show 1 frame picture. It can't move.

Good to add it to WimBuilderUI directly, to show the GIF on "Tutorial" page.
<img src="tutorial.gif" />

Well, another viewpoint, I hope WimBuilderUI to be simple/easy to use enough for user to use it without "How To Use" Help.

A lots of programs, we use without reading the help.
notepad.exe, mspaint.exe, explorer.exe, even Office, Windows. (use basic function)

I thought it is simple enough, maybe my English is to bad to understand the click action order 

Maybe at .\Help\ folder 

I will add "Tutorial" or "Help" page at the WimBuilderUI's left navigation menu sometime.

The framework(html+js+bat) can do very cool things, but I have no much time on it. (I'm not good at the Web UI develop)

Yes I have same problem....
That is the reason I only take the pictures and prepare only notepad style html when required.... 

Well sometimes only taking 1 2 3 pictures is enough (like language change example on previous post.. 1 2 3)

ps: not using "HTML Power" or prepare GIF (+videos etc.) gain great time. 

Time.........

*

I posted GIF for how to build, but theoven.org only show 1 frame picture. It can't move.

I feel we can solve this problem in future...
Let me have the gif (or remind me where it is, I could not find tutorial.gif inside your package )

*

I thought it is simple enough, maybe my English is to bad to understand the click action order 

Same trouble here, I changed many of my initial ideas in passing ~10 years after I see things not intuitive enough to new users.
 (well many of my ideas were right and now used by all  )

I feel now I am experienced enough what is intuitive to a new user,
 but mostly free time limitation does not help me,
  and sometimes It is not possible to get the developer to understand when I feedback...
   In the end, they always do what I had written one way or another if they keep active around,
    sometimes after some years.... Time lost... 
     sometimes motivation lost project ends, or sometimes long time no progress on project .....

*
Very simple 1 2 3 pictures will be enough for simple use to test a build. 
I mostly use the last free version of FastStoneCapture (v5.3)
  (also available via plugin if required) (probably last free ...)

Well only sharing ideas.... See You ...

Hi,

Let me have the gif (or remind me where it is, I could not find tutorial.gif inside your package )

see the attachment. (It was recorded in Chinese OS, so the UI text is in Chinese.)
I can install English OS and record again.

but I think you are right for 1,2,3 Pictures for this is fine.

For simple building it is good, but actrually here are some "advanced mode" options, that made people  without any description...

* use test\boot.wim (for quick mount, test main.bat, check added files, registry items, and easy to know the increased size.)
* the difference of run(cmd), exec(log)
* [VBox.cmd vm] , [Launch] button

Hi slore,

Here I get your makepe3.gif without animation.

Workaround Idea:
can you attach your animated gif file via .7z
eg.
makepe3.7z (inside makepe3.gif) 

Updated the attachment.

I guess this will help.

WimBuilderUI - Chinese Video Tutorial ( 3 MB Animated Gif)

*
My memory says we had this conversation before, or I have a De Ja Vu ...

Anyway, my HTML skills are bad (better say not exists),
 Good, you like 1 2 3 ... picture idea which makes things faster and simpler... 

Hi slore,

a small feedback :

You can not mount at \Desktop\ folder of HostOS.
(eg. C:\Users\slore\Desktop\WimBuilder\WimBuilder.cmd )
whatever reason behind, dism etc. do not like to mount this folder.


On WimBuilder, If you choose "mount path" to build (on my side %BuildClass%=2),
 you need to precheck if builder runs under Desktop --> If yes --> halt and message
  eg Message:

You Must Run Wimbuilder under a simple folder
eg.
D:\WimBuilder\WimBuilder.cmd

Alternate:
Instead of "mount path" using "Extract path" (Today most popular via wimlib)
( ps:
 on my side "mount path" %BuildClass%=2 - "Extract path" %BuildClass%=3 
  I will provide both paths optional in future, %99 ready and working experimentally. )

*
Can you verify, WimBuilder supports Space Path
eg.
D:\Wim Builder\WimBuilder.cmd

I do not want to test here to avoid failures on my hostos.

whatever reason behind, dism etc. do not like to mount this folder.

donwload wimbuilder2-master.zip from github to Desktop, and tested(everytime I push a release version, I will do this.)
 

I just know that in PE should call startnet.exe -wg WORKGROUP, or dism failed on mount.
C:\Users\Slore\Desktop is in normal Windows, but it is fine on my side.

If there is more report or get the real reason, I will add a option for change the workspace dir.

Can you verify, WimBuilder supports Space Path

D:\D e v\WimBuilder2 is OK. just builded with 10.0.18362.

Can you verify, WimBuilder supports Space Path

D:\D e v\WimBuilder2 is OK. just builded with 10.0.18362.

Thanks, Further I will always use WimBuilder under space folder like your example.
Back to My tidy D:\ 

*

If there is more report or get the real reason, I will add a option for change the workspace dir.

There is misunderstanding I guess.
I did not ask an option for change the workspace dir.

Only a message on cmd screen
eg.

Code: [Select]

cls
@Echo Off
Echo.
Echo.
Echo.
Echo    ********** Build Can not Continue **************
Echo.
Echo     You Must Run Wimbuilder under a simple folder
Echo     eg.
Echo     D:\WimBuilder\WimBuilder.cmd
Echo.
Echo.
Echo     Press Any Key to Close current cmd Screen
Echo.
Echo.
Echo.
Echo.
Echo.
Echo.
Echo.
Echo.
Echo.
Echo.
Echo.
Echo.
pause
exit

Further up to you...
Above is a very old story (8 or 10 years) on our side when people start to complain about build failure,
 later figured out that is because of the end user using desktop sub folder.
   We only put a message and stop build at an early stage, after that no post about failure.
    People smart enough to copy to another folder, no need an option for auto change the workspace dir, only a message is enough.

Anyway, up to you. 

Hi slore,

related to
> For WimBuilderUI, I'm working on a Ultra-Slim(experimental) option,

Let us know if you find a distributable free with command line support hopefully without .net resource hacker to slim down 

*
On project design, on the road of very small build, things can get complicated ...,
 you may end with another project eg. "WimBuilderUI-Slim"

Another way is embedding slim inside WimBuilderUI.
 I had done it for Gena with \"Basic Project" .....
  The idea is after the core project step of the build, start to slim down with another path of the build.
   Such design keeps things to maintain much easier compared to 2 projects.

    Experience: Others who decide to go with the path with "2 Projects" (eg. WimBuilderUI and WimBuilderUI-Slim) always fail to maintain Slim with passing time.....
      Sometimes things that look better and easier with the first decision later create troubles ...

I mean:
with build path: WimBuilderUI -> after Configures\* ---> Continue \Components\* ----> WimBuilderUI
with build path: WimBuilderUI -> after Configures\* ---> Continue \Slim\*  ----> WimBuilderUI-Slim

Continue \Slim\* have its own path up to the creation of wim etc.....

(
with \Slim\ I mean very same \Basic Project plugin which,
 since you have your builder design power you will get better UI instead of me try to do everything with single plugin....
  The logic behind Idea is the same
)


**
Also a memo,
 Slim builds only required by 1% 1/10000 or fewer end users.
   I remember It was only fun and educational to me working on smaller and smaller.
     Majority users never ask such things, only time to time we see a related post.

Hi, Lancelot

Thanks for sharing the experience.

about the Ultra-Slim(experimental) option, for now is just like:



and

Ultra-Slim.bat

Code: [Select]

if not "x%opt[slim.ultra]%"=="xtrue" goto :EOF
echo Ultra Sliming...

call :DEL_FONTS browalia.ttc
call :DEL_FONTS "c,d,e,g,h,i,j,k,l" "*.*"
call :DEL_FONTS "mangal.ttf,mangalb.ttf,mmrtext.ttf,mmrtextb.ttf,monbaiti.ttf,msyhl.ttc,msyi.ttf"
call :DEL_FONTS "n,p,r" "*.*"
call :DEL_FONTS "segoeui.ttf,segoeuii.ttf,segoeuil.ttf,segoeuisl.ttf,segoeuiz.ttf"
call :DEL_FONTS "seguibl.ttf,seguibli.ttf,seguiemj.ttf,seguihis.ttf,seguili.ttf,seguisb.ttf,seguisli.ttf,shruti.ttf,shrutib.ttf"
call :DEL_FONTS "tahomabd.ttf,taile*.ttf,taileb.ttf,tunga.ttf,tungab.ttf,vrinda.ttf,vrindab.ttf"

for %%i in (DVD,PCAT,PXE) do (
  rd /q /s "%X_WIN%\Boot\%%i"
)
for %%i in (chs_boot.ttf,cht_boot.ttf,jpn_boot.ttf,kor_boot.ttf) do (
  del /a /f /q "%X_WIN%\Boot\Fonts\%%i"
)

del /q "%X_SYS%\Boot\winresume.*"
del /q "%X_SYS%\Boot\%WB_PE_LANG%\winresume.*"


if not "x%opt[support.wow64]%"=="xtrue" (
  for %%i in (WOW64) do (
    del /a /f /q "%X_SYS%\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\*-%%i-*"
  )
)

if not "x%opt[support.audio]%"=="xtrue" (
  for %%i in (AudioDriversCore,MMECoreBase,MMECoreWdmAudio,AudioCore,AudioDrivers) do (
    del /a /f /q "%X_SYS%\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\*-%%i-*"
  )
)

if not "x%opt[support.network]%"=="xtrue" (
  for %%i in (Network,WiFi) do (
    del /a /f /q "%X_SYS%\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\*-%%i-*"
  )
)

for %%i in (HyperV) do (
  del /a /f /q "%X_SYS%\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\%%i-*"
)

for %%i in (ATBroker,MDAC,Hyper-V,Rejuv,WCN,ServicingStack) do (
  del /a /f /q "%X_SYS%\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\*-%%i-*"
)

for %%i in (BootEnvironment-Dvd,OneCore-TroubleShooting,OneCore-Multimedia) do (
  del /a /f /q "%X_SYS%\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\*-%%i-*"
)
:END_CATALOG

if not "x%opt[support.network]%"=="xtrue" (
  for /f "delims=" %%i in ('dir /b /ad "%X_SYS%\DriverStore\FileRepository\net*"') do (
    echo rd /s /q "%X_SYS%\DriverStore\FileRepository\%%i"
    rd /s /q "%X_SYS%\DriverStore\FileRepository\%%i"
  )
)


rd /q /s "%X_SYS%\DiagSvcs"

rd /q /s "%X_SYS%\wbem\Repository"
md "%X_SYS%\wbem\Repository"

rd /q /s "%X_SYS%\WindowsPowerShell\v1.0\Modules\Storage"
rd /q /s "%X_SYS%\WindowsPowerShell\v1.0\Modules\StorageBusCache"
rd /q /s "%X_SYS%\WindowsPowerShell\v1.0\Modules\iSCSI"

del /a /f /q "%X_SYS%\AtBroker.exe"
del /a /f /q "%X_SYS%\audioresourceregistrar.dll"
del /a /f /q "%X_SYS%\autochk.exe"
del /a /f /q "%X_SYS%\autoconv.exe"

del /a /f /q "%X_SYS%\CloudRecApi.dll"
del /a /f /q "%X_SYS%\CloudRecSvc.exe"
del /a /f /q "%X_SYS%\clusapi.dll"

del /a /f /q "%X_SYS%\cmi2migxml.dll"
del /a /f /q "%X_SYS%\CompPkgSrv.exe"

del /a /f /q "%X_SYS%\csiagent.dll"

del /a /f /q "%X_SYS%\dbgeng.dll"
del /a /f /q "%X_SYS%\DbgModel.dll"
del /a /f /q "%X_SYS%\diagER.dll"
del /a /f /q "%X_SYS%\diagtrack.dll"
del /a /f /q "%X_SYS%\edgeIso.dll"
del /a /f /q "%X_SYS%\EdgeManager.dll"
del /a /f /q "%X_SYS%\Faultrep.dll"
del /a /f /q "%X_SYS%\FlightSettings.dll"

if "x%opt[shell.app]%"=="xwinxshell" (
  del /a /f /q "%X_WIN%\SystemResources\ieframe.dll.mun"
  del /a /f /q "%X_SYS%\ieframe.dll"
  del /a /f /q "%X_SYS%\%WB_PE_LANG%\ieframe.dll.mui"
)

del /a /f /q "%X_SYS%\migapp.xml"
del /a /f /q "%X_SYS%\migcore.dll"
del /a /f /q "%X_SYS%\migisol.dll"
del /a /f /q "%X_SYS%\migres.dll"
del /a /f /q "%X_SYS%\migstore.dll"
del /a /f /q "%X_SYS%\migsys.dll"

del /a /f /q "%X_SYS%\ReserveManager.dll"
del /a /f /q "%X_SYS%\reseteng.dll"
del /a /f /q "%X_SYS%\ResetEngine.dll"
del /a /f /q "%X_SYS%\ResetEngine.exe"
del /a /f /q "%X_SYS%\ResetEngInterfaces.exe"
del /a /f /q "%X_SYS%\resetengmig.dll"
del /a /f /q "%X_SYS%\ResetPluginHost.exe"

del /a /f /q "%X_SYS%\setupplatform.cfg"
del /a /f /q "%X_SYS%\setupplatform.dll"
del /a /f /q "%X_SYS%\setupplatform.exe"

del /a /f /q "%X_SYS%\SFCN.dat"
del /a /f /q "%X_SYS%\SFL*.dat"
del /a /f /q "%X_SYS%\SFPAT*.inf"

if exist "%X_SYS%\StartTileData.dll" del /a /f /q "%X_SYS%\StartTileData.dll"

del /a /f /q "%X_SYS%\storagewmi.dll"
del /a /f /q "%X_SYS%\%WB_PE_LANG%\storagewmi.dll.mui"

del /a /f /q "%X_SYS%\storagewmi_passthru.dll"

del /a /f /q "%X_SYS%\SysFxUI.dll"

del /a /f /q "%X_SYS%\sysreset.exe"

if exist "%X_SYS%\TDLMigration.dll" del /a /f /q "%X_SYS%\TDLMigration.dll"
del /a /f /q "%X_SYS%\tier2punctuations.dll"

del /a /f /q "%X_SYS%\TimeBrokerClient.dll"
del /a /f /q "%X_SYS%\TimeBrokerServer.dll"

if 1==0 (
  del /a /f /q "%X_SYS%\appinfo.dll"
  del /a /f /q "%X_SYS%\appinfoext.dll"
  del /a /f /q "%X_SYS%\twinapi.appcore.dll"
  del /a /f /q "%X_SYS%\twinapi.dll"
  del /a /f /q "%X_SYS%\twinui.appcore.dll"
  del /a /f /q "%X_SYS%\twinui.dll"
  del /a /f /q "%X_SYS%\twinui.pcshell.dll"
  del /a /f /q "%X_SYS%\twinapi.appcore.dll"

  del /a /f /q "%X_SYS%\UIRibbon.dll"
  del /a /f /q "%X_SYS%\UIRibbonRes.dll"
)

del /a /f /q "%X_SYS%\unbcl.dll"
del /a /f /q "%X_SYS%\uninstall.xml"
del /a /f /q "%X_SYS%\uninstall_data.xml"
del /a /f /q "%X_SYS%\unlodctr.exe"
del /a /f /q "%X_SYS%\upgradeagent.dll"
del /a /f /q "%X_SYS%\upgrade*.xml"
del /a /f /q "%X_SYS%\upgWow_bulk.xml"
rem del /a /f /q "%X_SYS%\unlodctr.exe"

del /a /f /q "%X_SYS%\VSSVC.exe"
del /a /f /q "%X_SYS%\wbengine.exe"

del /a /f /q "%X_SYS%\Wcn*.dll"

del /a /f /q "%X_SYS%\wdscapture.exe"
del /a /f /q "%X_SYS%\wdscapture.inf"
del /a /f /q "%X_SYS%\wdsclient.exe"
del /a /f /q "%X_SYS%\wdscsl.dll"
del /a /f /q "%X_SYS%\WdsDiag.dll"
del /a /f /q "%X_SYS%\WdsImage.dll"
del /a /f /q "%X_SYS%\wdsmcast.exe"
del /a /f /q "%X_SYS%\wdstptc.dll"
del /a /f /q "%X_SYS%\wdsutil.dll"

del /a /f /q "%X_SYS%\webplatstorageserver.dll"
del /a /f /q "%X_SYS%\webservices.dll"

del /a /f /q "%X_SYS%\Wer*.exe"

del /a /f /q "%X_SYS%\winquic.dll"

del /a /f /q "%X_SYS%\winresume.efi"
del /a /f /q "%X_SYS%\winresume.exe"

del /a /f /q "%X_SYS%\winsqlite3.dll"

del /a /f /q "%X_SYS%\wpr.config.xml"
del /a /f /q "%X_SYS%\wpr.exe"

del /a /f /q "%X_SYS%\wpx.dll"

goto :EOF

:DEL_FONTS
for %%i in (%~1) do (
  del /a /f /q "%X_WIN%\Fonts\%%i%~2"
)
goto :EOF

With WimBuilderUI's framework, it could be
Projects\LitePE\Slim\main.bat (standalone project)
or
Projects\WIN10XPE\za-MySlim\main.bat (standalone patch "plugin")

I remember It was only fun and educational to me working on smaller and smaller.

With new/high hardware, less people care about the size now.
It is good to findout the undocment relation in Windows files.

For Now I got:
compmgmt.msc needs jscript  (custom msc with devmgmt,diskmgmt,services is OK)
diskmgmt.msc needs WMI      (diskpart.exe, PartitionGuru is OK)
bitlocker needs WMI
shortcut's opencontainingfolder menu needs ieframe.dll(12MB) (WinXShell.exe has wxsStub.dll(100kb))
URL assocation(http/ms-settings) needs ieframe.dll [ms-settings:taskbar]  (modify registy + binmay)

Let us know if you find a distributable free with command line support hopefully without .net resource hacker to slim down

smaller font files can be created with FontCreator.

about resource dlls, maybe old reshacker.exe and irfanview.exe is OK. I don't deal with them yet.

Hi, slore

With WimBuilderUI's framework, it could be
Projects\LitePE\Slim\main.bat (standalone project)
or
Projects\WIN10XPE\za-MySlim\main.bat (standalone patch "plugin")

If only 2 choice,
I vote
Projects\WIN10XPE\za-MySlim\main.bat (standalone patch "plugin")

+
Since WimBuilderUI already have "Slim" patch, and you post with name "MySlim" patch,
I will follow your post naming "MySlim" but will follow ui of "Slim" patch.

*
Following similarities since the idea is the same, what I did:
I put a "Build" icon button at top of "MySlim" patch UI
I made "MySlim" Patch "Build" icon to first run "Configures" + "Configures\Build"

After that point, "MySlim" Patch continue with its own path.
(
 without "Configures\System" "Configures\Customization" "Configures\PECmd" "Components\*" "Drivers\*" "Apps\*"
 )
And do other things with options on "MySlim" Patch


==> Reason behind:
1)
It is more logical to start a smaller size at early steps.
eg.
First running Components\Shell\"Explorer" patch and later removing files added by Components\Shell\"Explorer" patch ...
Instead, you can add "Small Explorer" option to UI of "MySlim" Patch which only adds minimum files..
ps:
Historically, JFX wrote "µExplorer Shell" for 'Multi7PE SE' for that goal (available at Win7PESE)

But As I had written, small builds are not popular, and nearly always the same people ask for such things once in 3 years I guess.

2)
Main advantage is, you can more easily maintain slimmed down version of the patch on the same patch and under the same project which helps to maintain easier in passing time.
eg. one can use same \Drivers\* patches with MySlim Patch (MySlim Patch having checkbox "use Drivers\SystemDrivers" etc.)

To see what I mean see Gena\Basic Project -> "a" advanced ui --> "Interface Gena Development ---> "
---> It is a working "beta" stage ....
(since it is not another project, gain time to use existing plugins and maintain easier...  ..... )
Gena\Basic\Shells\Core\CoreMain - Enable RegFactory
---> It will demonstrate what I mean with \Slim\*

(no need build, only hit buttons ... )

ps:
Just to make you smile with diskpart:
Gena\Components\Core\1 System\MMC --> "MMC CMD" button -->  "Disk Management" (diskpart) --> I create "MMC CMD" during research of smallest possible using "Basic Project" Plugin. 

You can combine "Enable RegFactory" and "Small build with Basic Project" related things easier since you can fully design your builder ui.

Anyway, all about sharing experience, further up to you. 

See you next post...

about resource dlls, maybe old reshacker.exe and irfanview.exe is OK. I don't deal with them yet.

I guess reshacker never be distributable!

I do not know irfanview can change resource! (will check when I find time)

but your post made me realize IcoFX 1.6.4 have internal Resource Editor which I guess (not tested but see on internet) change .exe .dll icons ..  (not tested if command available)
+ last free 2 also on website ....

 Make me feel, Maybe there are some picture editors (eg. IrfanView) that have the ability to only change resource pictures & icons with cmd line .... which is enough for slim goals...   

now AddFiles macro support "+if" conditions(can be nested win 100 level).

D:\D e v\WimBuilder2\Projects\WIN10XPE\00-Configures\Build\Catalog.bat

Code: [Select]

@echo off

rem [Catalog_AddFiles_Info]
rem Use signtool.exe to find Catalogs ex: Signtool verify /kp /v /a X:\Windows\System32\drivers\*.sys > B:\SignDrivers.txt


if not "x%opt[build.catalog]%"=="xfull" goto :CATALOG_ADDFILES
rem Full Catalogs
call AddFiles \Windows\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
goto :EOF

:CATALOG_ADDFILES

if exist "%X_SYS%\mstsc.exe" set opt[component.mstsc]=true

call AddFiles %0 :end_files
goto :end_files

@\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\

Microsoft-Windows-Basic-Http-Minio-Package~*.cat
Microsoft-Windows-SMB1-Package~*.cat
Microsoft-Windows-DataCenterBridging-Package~*.cat

+if "x%opt[shell.app]%"<>"xwinxshell"
+ver >= 17763
Microsoft-Windows-Client-Desktop-Required-Package*.cat
Microsoft-Windows-Client-Desktop-Required-WOW64-Package*.cat
+ver*
Microsoft-Windows-Client-Features-Package*.cat
Microsoft-Windows-Client-Features-WOW64-Package*.cat
-if

+ver < 17763
Microsoft-Windows-Client-Drivers-drivers-Package~*.cat
Microsoft-Windows-Client-Drivers-net-Package~*.cat
Microsoft-Windows-Client-Drivers-Package~*.cat
Microsoft-Windows-Client-Drivers-Package-net~*.cat
Microsoft-Windows-Desktop-Shared-Drivers-*.cat
Microsoft-Client-Features-Classic-WOW64-*.cat
+ver*

; For updates
Package_*

; Additions
Microsoft-Windows-Browser-Package~*.cat
Microsoft-Windows-Dedup-ChunkLibrary-Package~*.cat

+ver < 17763
Microsoft-Windows-BusinessScanning-Feature-Package-admin~*.cat
Microsoft-Windows-Common-Modem-Drivers-Package~*.cat
;Microsoft-Windows-SnippingTool-Package~*.cat
Microsoft-Windows-PeerToPeer-Full-Package~*.cat

+if "x%opt[component.wcn]%"="xtrue"
Microsoft-Windows-OneCoreUAP-WCN-Package~*.cat
Microsoft-Windows-OneCoreUAP-WCN-WOW64-Package~*.cat
Microsoft-Windows-WCN-net-Package~*.cat
Microsoft-Windows-WCN-WOW64-net-Package~*.cat
-if

+if "x%opt[component.ie]%"="xtrue"
Microsoft-Windows-InternetExplorer-inetcore-Package~*.cat
Microsoft-Windows-InternetExplorer-onecoreuap-Package~*.cat
-if

+ver >= 17763
LanguageFeatures-WordBreaking-*.cat
Microsoft-Windows-SecureStartup-Subsystem-base-Package~*.cat
+ver*

+if "x%opt[support.media]%"="xtrue"
Microsoft-Windows-Media-Format-multimedia-Package~*.cat
Microsoft-Windows-Multimedia-RestrictedCodecs-multimedia-Package~*.cat
Microsoft-Windows-Multimedia-RestrictedCodecs-WOW64-multimedia-Package~*.cat
Multimedia-MFCore-Package~*.cat
Multimedia-MFCore-WOW64-Package~*.cat
+ver >= 17763
Multimedia-RestrictedCodecsCore-Package~*.cat
Multimedia-RestrictedCodecsExt-Package~*.cat
+ver*
-if

+if "x%opt[component.netfx]%"="xtrue"
Microsoft-Windows-NetFx4-US-OC-Package~*.cat
+ver >= 17763
Microsoft-Windows-NetFx-Shared-Package~*.cat
+ver*
-if

+if "x%opt[support.photo]%"="xtrue"
Microsoft-Windows-PhotoBasic-Feature-Package~*.cat
+ver >= 17763
Microsoft-Windows-PhotoBasic-PictureTools-Package~*.cat
+ver*
-if

+if "x%opt[component.search]%"="xtrue"
Microsoft-Windows-SearchEngine-Client-Package~*.cat
+ver >= 17763
WindowsSearchEngineSKU-Group-Package~*.cat
+ver*
-if

+if "x%opt[component.mstsc]%"="xtrue"
+ver < 17763
Microsoft-Windows-RemoteDesktop-*.cat
+ver >= 17763
Microsoft-Windows-TerminalServices-CommandLineTools-Package~*.cat
+ver*
-if

+if "x%opt[component.MTP]%"="xtrue"
Microsoft-Windows-WPD-UltimatePortableDeviceFeature-Feature-Package~*.cat
-if

:end_files

First running Components\Shell\"Explorer" patch and later removing files added by Components\Shell\"Explorer" patch ...

won't add them if using:

Code: [Select]

+if "x%opt[slim.ultra]%"<>"xtrue"
...
...
...
-if

Instead, you can add "Small Explorer" option to UI of "MySlim" Patch which only adds minimum files..

Yes, I can. but I want to keep option be simple. no needs lots "Small XXX" on each component patch.

The final delete action just take < 10 seconds, I think keep each main.bat be simple, and delete the added files in MySlim\main.bat is fine.

Keeping short :

The only comment to this, I do not have "lots "Small XXX" on each component patch" on my design ...
 And I do not use a special variable like "x%opt[slim.ultra]%" (eg. %SmallBuild%)
   I was able to keep everything very simple, only by creating a nice well-organized design.
.....

Anyway,
 It is hard to keep wheels turning in passing time, first design steps are important.
   I see many projects died after some years because of that ......
     I shared all related experience about the subject, Further up to you. 


*
Catalog.bat looks nice. 

*
+
I could not find an option on irfanview to change picture resources inside .exe .dll etc.
Also I could not find such option on other picture editors...
+
Icofx v2 seems 30 day trial, IcoFX v1 have Resource Editor but only for .ico (not tested)
, I did not notice cmd line support with any IcoFX ..
+
oldest Resouce Hacker I have (3.6.0.92) is not distributable ....

oldest Resouce Hacker I have (3.6.0.92) is not distributable ....

add README.txt, let people download it by themself is simple ...

[WimBuilder]add a list to select preset.
[Project]add Ultra-Slim option for make PE in slim size.


Preset:lite1 -  WinXShell + MMC + UltraSlim (167MB)
2019-04-07 22:55:41 - Building completed in 29 seconds.



Preset:lite2 -  PECMD + WinXShell + MMC  +  WOW64  + UltraSlim (271MB)
2019-04-07 23:17:29 - Building completed in 48 seconds.



Preset:lite3 -  PECMD + Explorer + DWM + MMC  + UltraSlim (206MB)

2019-04-07 23:06:17 - Building completed in 37 seconds.

Preset:lite4 -  PECMD + Explorer + DWM + MMC + WOW64  + UltraSlim (311MB)
2019-04-07 23:10:29 - Building completed in 60 seconds.

WimBuilder2.part1.rar (v2019.04.09.e8ae8977)
WimBuilder2.part2.rar (v2019.04.09.e8ae8977)

(don't download attachment, the attachment is old preivew version v2019.04.07)

(don't download attachment, the attachment is old preivew version v2019.04.07)

oldest Resouce Hacker I have (3.6.0.92) is not distributable ....

add README.txt, let people download it by themself is simple ...

Sure.

README.txt is easier for a developer, even no need WimBuilderUI with a README.txt 

+
Well, I already prefer auto-download "Resouce Hacker" when required which to me better compared to a ReadMe ....
 But I avoid such things as much as possible to get things work out of box and
   I will keep an eye on a distributable, none .net, cmd supported resource editor....


See You next post....