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

Hi slore,

*
Good you can reproduce now, yes v1909 has the same issue. (just downloaded and tested)

fallback mui needs change many scripts.
* AddFiles macro
* RemoveMui batch

yes this discovery at that times had a similar effect on our side too,
 lots of basic plugins and some macros (AddFiles - Require_FileQ) updated,
   other plugins continue working without a need to update.

On your side Even twice a year, there will be similar or other updates.

Same old story since PE1,
I remember BartPE development days come to an end of mature with LOTS of development history,
 After BartPE mature,
  SherpyaXPE add over BartPE that make PE feel like full OS (add explorer shell and other things)
   Later starting with Galapo and after I join to Galapo, after focusing on optimizations and get mature on many things,
    A unique build method with FxScript RegFactory (build with virtualization and later create iso)
     and JFX Theme support, olegpov boot screen support, Nikkzzzz wim support
       Later saydin77 support to build PE1-x64, JFX support for PE1-x64-Wow64
         Short story of ~ 15 years

With this short story, I try to explain you, after things get mature, improvment path goes to a next level (with feedbacks, with windows changes or with your own motivation),
  even you spend very low time, but you need to be patient and keep having fun.

After "wimbuilder - a tiny framework which for editing the wim file " http://theoven.org/index.php?topic=1969
 and current topic "WimBuilder2"
  and you get your pe-build very mature.
    you continue to next steps. 

*
Distribution way,
 I will follow what you do. 

On my side, It would be good to have such a search button to find available plugins, and download the one,
 technically all ready here  ,
  nobody including me had time to create such software.

If I get screen like "Visual Studio Code" search button with "Install" button on your post picture,
"Install" button would:
Download: ..\Workbench\Common\Download_Yomi\Projects\Yomi\AppY\Supplementary\Caffeine.Script
Copy: .\Projects\Yomi\AppY\Supplementary\Caffeine.Script
Create: .\Projects\Win10PESE\AppY\Supplementary\Caffeine.Link

and continue things keep tidy. 

Only sharing idea, I will follow what you do. 

*

I will try to make it be good for other projects. (Maybe Only packages for PE?)

Giving a simple example:
Assume Caffeine plugin is only for PE,
and not suitable for the project:
..\Projects\OnlineHostOS\
.\Projects\Win10PESE\OnlineHostOS\Supplementary\Caffeine.Link file will not be created 

Since I limit myself to PE only with reasons on the previous post, I did not work on such a thing but easy to implement.
As written:

All gates open to you, use wisely. 

*

* Win10XPE_2019-11-20.7z
   cmd.exe /d /c   (What you feedback for WimBuilder2 very long time before, the inital time?)

Current topic Lancelot Reply #1 on: 2018-01-26
probably before.
 I follow good things, not a project fanatic at all  ,
  I follow Galapo ~10 years ago (when I had lots of BartPE plugins using with SherpyaXPE and trying to boot from boot.img (fat32) )
   I also follow JFX (Multi7PE project) and later ChrisR when there was bad times for them too before current forum.
    I met Kare (CD-RW) because of Dipe and was around at first LiveSystemPro times (after some years Dipe)
      (TeutonPE and some other PE project things, PEBakery initially I was there too)
         I also sadly experience how things go bad with post-pm games, fabricated compatibility etc.

      Generally, I become the only one who is interested in something alone (or limited number of people) at first times.
       After some feedbacks followed by the author It gets quite a lot popular.
        After popular It depends ... I hope you have a strong character. 

          And now here with WimBuilder2 , I hope with having a very good head start you continue to things I had dreamed 12 years ago. 


*

I don't need that, but be curious about how you deal with the Interface(UI options).
Publish it when you feel it be ready.

No mystery,
 At first I was using a text replace routine to change settings
  now I do not need that, thanks to your update now interface save settings automatically.
    I only provide source folder, change settings with WimBuilderUI, rest done with WimBuilder2
ps:
I use WimBuilder2 as my base build following WimBuilderUI, later use Plugins. I do not make WimBuilder2 patch-plugin conversion etc.
 Similar things I had done with BartPE, SherpyaXPE years years ago
   The only difference, I do not need to re-write plugins again and again.

It is easy to use at home, but with a lack of time I avoid publish for now (I am aware I need lots of lines to avoid misuse by public),
 I still change and test some of design ideas which gives some fun time to me.


Long post again, Let me know If I miss a point,
next post a question.

Hi Slore,

also for easy to test, I use Y:\PEMaterial (ISO) without rebuild boot.wim, just update in _ISO_\.

as far as I remember, WimBuilder2-PE do not change cd drive letter to Y: on my tests. It remained D: ?

+
with cd drive letter Y: ->Y:\PEMaterial

You mean If
I put my .bat files to Y:\PEMaterial   ...\Startup\ to start after shell and ....\Startup\BeforeShell\ inside iso (Y:) they will work.
?

Here is a custom patch,  make loader start  the *:\PEMaterial folder,  only for me do something rest of the scripts in PEMaterial.  after testing,  the loader just call X:\ one.

It is designed for loading APPs,  component packages,  drivers without including them in boot.wim,  update Apps will be easy without rebuild boot. wim,  so good for testing.

update Apps will be easy without rebuild boot. wim,  so good for testing.

Yes we do similar with the same reasons. 
(difference: search for a special .cmd file to start at boot)

I wrote info to my home "WimBuilder Help 2" 



*
I believe the time to inform things related to RunFrom ...

For now I use Plugins with only the option to add boot.wim , boot.wim file size gets bigger.

Since WimBuilder do not have much App patches for now (packages .. for now I continue saying patch, let me know when you decide a name change)
eg.
Customize-Apps\"7-zip" Patch add to boot.wim , no option on 7-zip Patch to add to cd (iso)
----> When number of WimBuilder App Patches increase, you will get Boot.wim size troubles

on my side, 7-zip plugin have options with RunFrom ( Apps\File Tasks\Compression\"7-Zip File Manager" plugin )

Run From Normal do nothing but only follows default Project settings (Normal)
 --> To me WimBuilder current default Project setting is Ram (boot.wim)
 --> Win10PE SE default Project setting is iso (RAM)
Run From RAM add to boot.wim
Run From CD  add to iso

Shortly on my side, App Plugins Normally add to cd without getting boot.wim bigger. 

To get things work, we use a dirty solution that fits MOST users, at boot time before shell, change drive letter to Y:


* Dirty Solution :
How RunFrom macro works:
RunFrom,Ram changes 2 variables till the end of the plugin.

%Target_Prog% = %TargetDir%\Program Files
%PE_Programs% = X:\Program Files

RunFrom,CD changes 2 variables till the end of the plugin,
on SE :

%Target_Prog% = %TargetFinalDirr%\Programs
%PE_Programs% = Y:\Programs

on LiveSystemPro (Win7PE - Win8PE - Win10PE)
%Target_Prog% = %TargetFinalDir%\Program Files
%PE_Programs% = Y:\Program Files

reminding, Since RunFrom,CD is default (normal) setting, all Apps plugins work without using RunFrom macro all goes to cd.

ps: %PE_Programs% used to add registry and to create shortcut

* Why Dirty:
If cd drive not available for any reason, pxe boot most popular reason, registry + shortcut will not work ........


* Clean Solution:
I remember VistaPE times Nightman tried to provide a clean solution but not finished, later since Dirty solution was easy to implement things goes that way ...

When you decide to implement RunFrom options, IF you do not want to spend much time, use Dirty solution, It will work and will be quick. 
On my side,
 If you only add a BeforeShell task to change cd drive letter to Y: , I can quickly get Plugins add to cd as default (for now to boot.wim as default following WimBuilder)
and
On your side,
 It will be easy too.


* If more time here is the Clean one:

RunFrom,CD changing location to
%Target_Prog% = %TargetFinalDirr%\Programs
%PE_Programs% = Y:\Programs

but also changing registry hive locations:

%RegSystem%= %TargetFinalDir%\PEMaterial\config\System
%RegSoftware%=%TargetFinalDir%\PEMaterial\config\Software
%RegDefault%=%TargetFinalDir%\PEMaterial\config\Default
%RegComponents%=%TargetFinalDir%\PEMaterial\config\Components
%RegDrivers%=%TargetFinalDir%\PEMaterial\config\Drivers

and also shortcut locations:
eg.
%TargetFinalDir%\PEMaterial\Shortcuts\Users\Default\Desktop"
%TargetFinalDir%\PEMaterial\Shortcuts\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\

This way when WimBuilder Boots, Before shell:
After finding driver letter:
- change drive letter to Y:   (Using Y: helps to write registry easier)
- add environmental variable %CDDrive%=Y:  (helps to write .cmd easier ;))
- reg add hives at CD:\PEMaterial\config\....
- copy shortcuts at CD:\PEMaterial\Shortcuts\
- continue other CD:\PEMaterial\....

and all ready. 

If cd fails (pxe boot), there will not be CD:\PEMaterial\config\....  no CD:\PEMaterial\Shortcuts\ , there will not be not working shortcuts or bad registry pointing to cd drive.

On my side, since using dirty solution, we ask end user change project setting to "Run All From Ram", so plugin default behaviour changed to always add to boot.wim

With Clean Solution, no need another special pxe boot iso.

Clean but requires a lot work, with small-time and no request I always postpone this idea for 10 years now .... 

Tips:
Find drive letter: See Apps\System Tools\"Portable Finder Startup" plugin
add environmental variable %CDDrive% : See Utils\"BroadcastEnvChange.exe by Galapo" Plugin
change drive letter to Y: See Build\"CdDrive - X: - Y:" Plugin




******
Clean or Dirty or Have no interest or Have no time = All fine to me.
Reminding Above is not a request.


I have a good time testing and using WinBuilder2 with all inside Boot.wim 

Only sharing some info and experience for your future development.   

Hi slore,

A little bug report or my mistake !?

Source: Win10 10.0.18362.1 ( Win10_1903_V2_English_x64 )

here is how to reproduce:
open WimBuilder.cmd
select source
change "Patch Preset" setting to Full
close WimBuilder

open cmd prompt and use:
WimBuilder.cmd --build-with-log --make-iso --close-ui

--->
bug: the result is not Full,
I check current.js , It is full.js 
 I believe bug happens not using current.js but default.js when cmd line used like above.

I hope you can easily reproduce.

  It should be current with the full preset.
I will check it later.

You didn't see any "change" today?

You didn't see any "change" today?

Just came around, with your post I decided to open Wimbuilder, and see nice snow.   




Well Done. 

Thanks Galapo,

We can continue cooking
 

      

Well, I can reproduce it.

I disable the auto save preset feature, when building from command line, like other option.
So the "current" preset wouldn't be overwrite by command line build --preset option one.

tell you want to to build with "current" preset.

Code: [Select]

WimBuilder.cmd --build-with-log --preset current --make-iso --close-ui

I will fix it in next release.

and see nice snow.

OK, the festival theme works good. Well, I forgot the timezone.

Today is The Winter Solstice, the Chinese have the festival.

  is soon, and with bonus : )

Just tested 20H2 (10.0.19536.1000)

MTP, Printer, RemoteDesktopSerivce are fine, hope MS don't change them again.
Only IE can't open, all other features work.

Just tested 20H2 (10.0.19536.1000)
MTP, Printer, RemoteDesktopSerivce are fine, hope MS don't change them again.
Only IE can't open, all other features work.

Add For IE

Code: [Select]

\Windows\System32\IEProxyDesktop.dll

 

added next and tested, IE works. Thanks for sharing the information.

Code: [Select]

+ver > 19500
IEProxyDesktop.dll
+ver*

and see nice snow.

OK, the festival theme works good. Well, I forgot the timezone.

Today is The Winter Solstice, the Chinese have the festival.

  is soon, and with bonus : )

Happy times with Winter Solstice 
No festival here, nobody aware such thing around 

Nice show to demonstrate WimBuilder open gate future.

I expect other surprises with "New Year" , "Spring Festival" etc. 

Reminding, aside timezone,
You also forgot It is Summer Solstice for Galapo now (Southern Hemisphere) 

See You on next post. 

A Little request :

can we have something like:

WimBuilder.cmd --wait

This way something like this can be done:
Eg. Test.cmd

Code: [Select]

Echo Start WimBuilder
WimBuilder.cmd --wait
Echo WimBuilder UI closed Continue

Another little request on next post after some tests. 

Hi slore,

A little bug report:

Customize-> _Personal-Tailor_ -----> click to the left of _Personal-Tailor_ to see sub tree "My Theme"

Click "My Theme"
-->
Script Error
Line: 2
Char: 704
Error: Permission Denied
Code: 0
Url: file:///................./assets/vendor/jquery-3.3.1.min.js

After this error, WimBuilder never works fine again, close open etc. always fails when I click Customize

See you on next post. 

Hi slore,

and a little request :
can you avoid cmd popup with probably cmd minimize

I mean:
During build 3 cmd window popup (In the past I guess 4, 4th adding log to WimBuilder UI with "1-build(Log)" )
1- First one quickly disappears
2- Second one with title: "WimBuilder(BaseFolder)" popup continues during build
3- Create ISO - when enabled again popup without title, It also cause popup of WimBuilderUI

Reason I ask:
eg. When writing current post, and was building with WimBuilder behind, build came to create iso step,
 cmd and WimBuilderUI popup in front of browser and I was hitting keyboard keys .......

  I hope you understand what I mean.

Maybe at 3- Create ISO step, you can avoid this with /Min and also use Title WimBuilder 

Overall, It will be good to have all project cmd popups with /Min and with Title WimBuilder

Sorry, I make quick tests with quick posts,
 I could more check codes to point you better but I hope you understand from the post.

Time to go.... See You

+
Aside Title WimBuilder

Echo WimBuilder Working DO NOT close this cmd screen

maybe nice too 

See You....

WimBuilder.cmd --wait

--wait parameter already be in Wimbuilder.cmd.

BUT remember two things:

One:

Echo Start WimBuilder
call WimBuilder.cmd --wait
Echo WimBuilder UI closed Continue

Two:
for use Dism command, WimBuilder.cmd will restart itself if it don't run in Administrator privilege, so the --wait parameter will be lost.

Make your run batch start with cmd (Administrator), will be what you like.
(you can use bin\isAdmin.exe, and ElevateMe.vbs as well)

A little bug report:
Customize-> _Personal-Tailor_ -----> click to the left of _Personal-Tailor_ to see sub tree "My Theme"

I can't reproduce the issue.
If you can't click "Customize" again, this must some wrong option(language?) write to the current preset.
send me the _Assets_\preset\current.js to check.

Can you try to rename the current.js to be test.js, and reopen WimBuilder.cmd again, could it be fixed?

Hi slore,

Following your post

> if it don't run in Administrator
If yes

Test.cmd run as admin will get this work
Echo Start WimBuilder
Call WimBuilder.cmd --wait
Echo WimBuilder UI closed Continue

Ps: I very recently start to write my wimbuilder 2 help,
Probably I forgot --wait on one of previous post
I will read all topic again for help doc

*
I will test js fhe way you wrote when I get back home

about the cmd windows.

This is a little ugly than other builders. The UI just save the build option, the real work is done by batch.
nsudo.exe to get the TrustInstaller, so here is some cmd Windows.


for "build(cmd)" button, somethings, we need some interactive operations, like
pause
set /p message=

so the Windows should be on the top.

for Build(log), make-iso button, seem good to hide the cmd Window.

In future version, they will be a button to save the current build option to a batch file, then we can build by double click the batch file without HTA UI.
so there won't be many cmd Windows, just one cmd.exe process for --- build, make-iso, and test.

There will be option for MIN them, or hide them.
At first, I will change the title for this ...