Azin - Plugin Liberty and Flexibility

Azin
:)

A New Project using Plugins and "Macro Library" high flexibility features with other Projects.






Short instructions:
1) Extract to a short simple folder and start eg. D:\Oven\BuildAzin.exe
2) Click Blue Play button at top of UI
3) When asked select source folder eg. containing Win10RTM (eg. Win10 20H2 x64)

* Azin Supports: Vista Win7 Win8 Win8.1 Win10 RTM

Make at least one build after you extract to see Default Result.
Later spend time to modify settings etc.

********************************************************

Special thanks to Galapo providing forum and servers to distribute
Special thanks to Kare (CD-RW) giving permission to distribute LiveSystemPro and giving a lot of support for the shortcut and LiveSystemPro.
Special thanks to slore giving permission to distribute WimBuilder
 and self-proving a batch-engine (cmd with WimBuilder) with nice ui is good enough for a pe/win/etc. creation and for all support on posts about WimBuilder.
Special thanks to JFX for GetWaikTools, WOW64, Gena Theme, Generic Theme Patch, Generic Driver Patch, NVidia trim ..... for all things shared so far all through years.
( @JFX, see Azin\Basic\"Azin Download" Plugin  )
Special thanks to noelBlanc for "MicroWinpeBuilder to adapt its own Winpe : tutorial or 'under the hood'?"
And Thanks to everybody who shared Plugins and Feedback on topics. 

********************************************************


The latest Azin can be found here:
Azin Download Page

Azin

Have Fun
 

*
To update Wimbuilder or LiveSystemPro inside Azin, use simple to follow Update Plugins


Utils\"Update LiveSystemPro - Azin"




Utils\"Update Wimbuilder - Azin"





*
To update Azin using Azin Distribution Packages use Utils\"Update via Package"
+
Azin server only holds Azin-Core Plugins unlike other projects,
 to update all additional Plugins
  (ComponentsY , TweaksY, AppY, DriversY, VirtualTestY, WriteMediaY, DownloadsY, UtilsY)
   you have to update via Package. (or use Small Green Download button at right-top of all plugins ui)
+
Bonus:
With this, you can also quickly use any distribution you like to test with if required.
+
ps: Reminding, Personal Plugins or other Project Plugins not affected with this update, they are all safe.

Additional Tutorials:

*
Since >10 years, All Projects which use Plugins works on the same folder without touching each other
 and all can use same Plugins. (no need conversion etc.  )

(without touching = Deleting ALL files of a Project have no effect on another Project = fully divided)

To demonstrate, I put a picture with all current Projects (Azin Gena Win7PESE Win8PESE Win8.1SE Win10PESE) with Plugins
 and as an example same "Q-Dir Nenad" Plugin working fine with all.
--> Personal Plugin work out of box and easier to test between projects and easier to improve Plugins up to needs in passing time.




*
Configure WimBuilder settings:
eg. How to enable "Administrator account" with WimBuilder ?
1)


2)



*
Configure LiveSystemPro settings:
eg. How to enable "SystemRecovery" with LiveSystemPro ?
1)


2)



Have Fun

More Info:
Azin, for today, gets end-user use Plugins with WimBuilder and LiveSystemPro projects.

Azin, for today, supports Win8.0 Win8.1 via LiveSystemPro and Win10 via LiveSystemPro and WimBuilder. - 2020.01.24
Azin, for today, supports Vista Win7 Win8.0 Win8.1 via LiveSystemPro and Win10 via LiveSystemPro and WimBuilder. - 2021.05.09

In the future more support down to Gena and up to new projects.

You can have Azin on the same folder with
 Gena, Win7PESE, Win8PESE, Win8.1SE, Win10PESE along with Yomi (Plugin server) and your personal plugins (MyPlugins, MyPlugins_Direct)
  All 6+1+2 projects Designed to work on the same base folder eg. D:\Oven\
    (with other words, you can delete any one of them without touching other since all use their own subfolder, or add all of them to the same base folder for the very same reason)

Azin\"Azin Configure" Plugin you can select a project to build with (Today LiveSystemPro and WimBuilder)

Azin\"Azin Configure" Plugin have "Configuration" Buttons for both LiveSystemPro and WimBuilder

----------------------------------------------------------------------------------------------------------------------------------------------------------------------
| Configure-LiveSystemPro:
| LiveSystemPro has its own LSP-Script server, you can download LiveSystemPro scripts from its server using:
|    LiveSystemPro\Utils\"Update Center"
|     See: How to use the Update Center of LiveSystemPro : http://TheOven.org/index.php?topic=3367.0
|
| LiveSystemPro contains 4 projects,
| For today Azin works with LiveSystemPro Win10PE Win8PE Win7PE in future WinXPE
|     (WinXPE - do not mix with other projects, I mean WinXPE Project distributed with LiveSystemPro which is a PE1 project ...)
| Configure LiveSystemPro the way you like following LiveSystemPro UI, It is quite easy to figure out.
|
| For more Info to configure LiveSystemPro, you can ask at LiveSystemPro Section.
|
| How to update Azin-LiveSystemPro Manually:
| Lancelot Reply 53 - http://TheOven.org/index.php?topic=3052.msg37493#msg37493
|
----------------------------------------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------------------------------------
| Configure-WimBuilder:
| WimBuilder has web pages for WimBuilder patches and WimBuilder projects,
|  check WimBuilder topic and webpages for patches and projects.
| For today there is only 1 project to be tested and supported by Azin for now (there seems 2 more on the way),
|  in a future time will show.
|
| Tip: WimBuilder-Left there you will see
|--> "Customize" --> Change "Patch Preset" to Full - Close WimBuilder - Click BluePlay Button
|---------> You will get a build with A LOT of features. (Login As Admin, Remote Connect etc. etc.)
|
| Tip: If you use WimBuilder Patch Preset-Default also
|   Enable Customize-Configures-Build-->'WOW64 Support' to get your 32bit applications to work.
|
| For more Info to configure WimBuilder, you can ask at WimBuilder Topic
|
| How to update Azin-WimBuilder Manually:
| Lancelot Reply 53 - http://TheOven.org/index.php?topic=3052.msg37493#msg37493
|
----------------------------------------------------------------------------------------------------------------------------------------------------------------------



Azin:
*
You can download other Plugins from the server by using Azin\Downloads(Y)\"Download Plugins"
See
Adding 3rd party plugins: \Downloads\ - MyPlugins_Direct - Yomi Topic
Reminding not all plugins on server,
 You can also download or share individual Plugins at Plugin Section See:
Plugin Section

*
Memo:
 Azin Naturally Provides all options available by projects like "Login As Administrator", "Network Options" , "MMC" etc. etc.
  As mentioned before, use Configuration Button to configure projects.


*
Proxy Users:
+
If you made proxy settings before with one of the Projects -> Gena, Win7PESE, Win8PESE, Win8.1SE, Win10PESE
 and extract Azin to the same folder,
   no need to make Proxy settings again, It will work out of box. 
+
If you are a new user or use Azin on a separate folder :
Check Utils(Y)\"Proxy Settings" and "Proxy Settings - WinHTTP" Plugins
Azin (default settings) for today must Downloads ADK files (~ 10 MB) once so you should at least make proxy setting with "Proxy Settings - WinHTTP" Plugin.
and
better also use "Proxy Settings" plugin so you can download required files by individual plugins. (eg. App\Network\"Mozilla Firefox ESR (P)" Plugin needs to download FireFox setup file)

*
Azin has a Simple Cache mechanism for some projects
 Today Azin implement Simple Cache for both WimBuilder and LiveSystemPro
  As a result, 2nd build will be faster
   Today building with WimBuilder and LiveSystemPro using the same source,
      2nd build naturally has ~same time results.

On my pc:
Source: Win10 1909 x64 (en-us)
Using normal 5600 rpm disk (not SSD)

WimBuilder and LiveSystemPro 2nd build: 6 minutes, 25 seconds

Kare report better result 5 min 20 seconds
Again proves the fact, I have a slow laptop.   

slore report build is very slow on the first run (+15 min) on old pc with win7
slore reply 290 http://theoven.org/index.php?topic=2390.msg36513#msg36513
It will be improved later with improvements using Azin-WimBuilder cases

With ssd disk, results will be a lot faster.

*
Azin supports Junction Target folders,
(Gena, Win7PESE, Win8PESE, Win8.1SE, Win10PESE also have this feature)
If you have an idea to build faster by putting all project to a "Ram Drive" (you have lots of ram to waste),
 Keep in mind there is a better way without losing space (and on some cases files) by using "Ram Drive". 
  Only junction target folders to "Ram Drive". 

See Lancelot Reply 61 http://TheOven.org/index.php?topic=3052.msg38174#msg38174

*
With Azin, being able to easily use the same plugins with all projects
 ( Today: LiveSystemPro-Win10PE, LiveSystemPro-Win8, LiveSystemPro-Win7, WimBuilder,  Gena, Win7PESE, Win8PESE, Win8.1SE, Win10PESE
    later: LiveSystemPro-WinXPE)
   is quite fun,
   and self Proves "Macro Library" and "Plugin design" is close to perfect. 

eg. "QtWeb" Plugin, "7-Zip File Manager" Plugin, "VirtualBox Emulation" Plugin .....

*
Azin self proves "Macro Library" is
 very fast {see individual plugin time at log after build plugins (eg. Dism++ Plugin  1.565 seconds )}
 and
 very flexible {now building Plugins for WimBuilder and LiveSystemPro}

Azin also self proves Project Build times or how plugins are written (slow or fast) is not related to "Macro Library" at all.

*
Azin is in fact small,
Inspecting Initial Azin Release (2020.01.24)
Inside 240.3 MB (zip compressed 188 MB)
 -167.3 MB are Plugins out of Azin {161.1 MB (Yomi) 3.1 MB My Plugins Direct  3.1 MB My Plugins) (not required to Build Azin)
 -1.4 MB VirtualTest Plugins (not required to Build Azin)
 -0.3 MB Builder Language Files and info (not required to Build Azin)
 -20 MB WimBuilder
 -15MB LiveSystemPro
 -31.0 MB Utils Plugins help me a lot to create Azin without writing the same things again and again to create a project.
    (Utils Plugins are the same Plugins for all 6 or 5 Projects and created and used before Azin, Self proves good design  )
 -1.3 MB Macro Library
 -0.9 MB builder

Shortly Azin is I guess 3.3 MB 
with other words,
Minimum Azin to build both Projects:
 3.3 (Azin) + 0.9 (builder) + 1.3 Macro Library+ 31 Utils + 20 (WimBuilder) + 15 (LiveSystemPro) =~ 71 MB uncompressed.
 

Naturally, numbers will increase with passing time like with all projects.

ps: Azin server also with only ~ 72 MB

*
Azin update by using server:
Use
Utils\"Update Project (Exact and Secure)" Plugin
--> Using "Update (Download + Copy)" Button will update Azin without downloading ~190 MB like with zip file. 

Unlike other projects, to keep Azin updates small-sized (server ~72 MB uncompressed),
 Azin server only holds Azin Plugins, so better:
   First Extract zip and later update with Utils\"Update Project (Exact and Secure)" Plugin.

See Lancelot Reply 19 http://theoven.org/index.php?topic=3052.msg36531#msg36531

*
Azin Future:
Azin in its root (like Gena) provides a Layer to start a new project with everything ready at hand ('Macro Library' and all rest working Plugins )
 that makes it very simple to create a project for a project admin. ( Self proof current Azin  )
 I am still slowly documenting related things when I find free time. (writing help document is boring but required)

It is now quite easier to create a project via Azin, I have some project ideas for the future.


**
Short History:
Azin Idea was there for years now (without project name) but I feel It will not be morally right to create such a thing years ago, Something rare happened and I was wrong.
 Gena project has the roots of Azin's idea in its design (When creating Gena, the Idea was there to be ready to implement later .......),
  developing Azin makes me remember times when we (Galapo, Lancelot) had created Gena ~10 years ago (~2010.09).
      The project started quickly working at home but the name later was found by a friend at 2018.10.24 ~1:30 after we had lunch.

      Creating a project at home is easy, preparing a hobby project ready to distribute to the public is not, and I do not have free time as before so all done very very slowly.

       Honestly, I never wanted to create a public project and be a project admin since ~12 years,
         working on post-core related things is still more fun for me on my hobby time.
           Life always has other plans ...

**
Last Words:
Well, It is now quite easy to build with LiveSystemPro and WimBuilder with Plugins,
 make me feedback on both projects about things I notice during the build.

Let me know if you have a working Plugin not working as before. 
 I am sure there will very rare cases and there are only a few lines to update. 

Azin provides required things to create Plugins with simple syntax provided by "Macro Library". 

ps: Azin First Public Release: 2020.01.24

Wow,  the description is more than I thought

Nice idea and a Gift for the Spring Festival.

Hi

link to 'Plugin Section' is failing in first post - missing : (colon)

Added info to More Info at Reply 3

Proxy Users:
+
If you made proxy settings before with one of the Projects -> Gena, Win7PESE, Win8PESE, Win8.1SE, Win10PESE
 and extract Azin to the same folder,
   no need to make Proxy settings again, It will work out of box. 


*
Azin has a Simple Cache mechanism for some projects
 Today Azin implement Simple Cache for both WimBuilder and LiveSystemPro
  As a result, 2nd build will be faster
   Today building with WimBuilder and LiveSystemPro using the same source,
      2nd build naturally has ~same time results.

On my pc:
Source: Win10 1909 x64 (en-us)
Using normal 5600 rpm disk (not SSD)

WimBuilder and LiveSystemPro 2nd build: 6 minutes, 25 seconds

Kare report better result 5 min 20 seconds
Again proves the fact, I have a slow laptop.   

With ssd disk, results will be a lot faster.


*
Azin supports Junction Target folders,
(Gena, Win7PESE, Win8PESE, Win8.1SE, Win10PESE also have this feature)
If you have an idea to build faster by putting all project to a ramdrive (you have lots of ram to waste),
 Keep in mind there is a better way without losing space (and on some cases files) by using ramdrive. 
  Only junction target folders to ramdrive. 
 
 
*
Azin is in fact small,
Inspecting Initial Azin Release (2020.01.24)
Inside 240.3 MB (zip compressed 188 MB)
 -167.3 MB are Plugins out of Azin {161.1 MB (Yomi) 3.1 MB My Plugins Direct  3.1 MB My Plugins) (not required to Build Azin)
 -1.4 MB VirtualTest Plugins (not required to Build Azin)
 -0.3 MB Builder Language Files and info (not required to Build Azin)
 -20 MB WimBuilder
 -15MB LiveSystemPro
 -31.0 MB Utils Plugins help me a lot to create Azin without writing same things again and again to create a project.
    (Utils Plugins are the same Plugins for all 6 or 5 Projects and created and used before Azin, Self proves good design  )
 -1.3 MB Macro Library
 -0.9 MB builder

Shortly Azin is I guess 3.3 MB 
with other words,
Minimum Azin to build both Projects:
 3.3 (Azin) + 0.9 (builder) + 1.3 Macro Library+ 31 Utils + 20 (WimBuilder) + 15 (LiveSystemPro) =~ 71 MB uncompressed.
 

Naturally, numbers will increase with passing time like with all projects.

*

link to 'Plugin Section' is failing in first post - missing : (colon)

Fixed 

*
Made reply 1 and 2 longer, hoping new users only read reply 1 which is short and enough for a beginner.
reply 3 is for experienced users.

*
Also updated Vmware Plugin for Vmware Player users following Kare feedback.
 Again workaround winbuilder bug even after 10 years.

Wow,  the description is more than I thought

Story of History is longer.
 At a point, I consider using WimBuilder to create Azin .....
  I also made some beta work on Macro Library to create Macro_Library.cmd to be used by WimBuilder  ...
    I have reactos cmd.exe (x64/x86) files somewhere around from last year .... 

Lots of trials and changing decisions during development, I guess this is Azin5 at home, a very loooong story...
 I keep short at History on reply 3 
  But the taste of adventure is nice on my side.

Nice idea and a Gift for the Spring Festival.

Happy Spring Festival. 

I do not follow bbs forums, feel free to share Azin there as a Gift for the Spring Festival   

*
Btw, Kare asked me to ask you, If you can provide your language support to LiveSystemPro.
http://theoven.org/index.php?topic=3022.0

See You

It seems that Azin use LiveSystemPro or WimBuilder to build a BASE boot.wim, than WinBuilder for the "Plugins".

What I thought is:
When WinBuilder's project's option changed, you update the current.js preset and the X drive to Target folder.
WimBuilder as a "Plugins" for WinBuilder project to build the system features.

Something can be improved:
1.Keep LiveSystemPro or WimBuilder distribution as LSP-xxx.zip, WimBuilder2-Full.xxxxxx.7z than *.script.
Easy for updating, and high speed for opening the Builder Configuration.
(I don't check the code, but it take 15~30 seconds for "Configuration" button of the builders, needs 5 seconds for the next click.)

I think it just extract the *.7z and update some config files could be done. and 9LSP, 9WBS for cache,
shouldn't needs such time.

_CustomFile_ folder for WimBuilder can be copied.

2. No need Make-ISO be default selected for WimBuilder, Final, ISO will do it.

3. The process should be:
extract the boot.wim to target folder, mount it to X for WimBuilder,
WimBuilder run
Plugin run
pack the Target folde to be boot.wim, it will save the time to dism /mount, /commit, /unmout.

Hi slore,

If you reply, please reply Kare post on LSP topic http://theoven.org/index.php?topic=3022.0
I will move above Kare post there later ....

See You on next post... 

edit:
Previous Kare post on current topic moved to other topic:
http://theoven.org/index.php?topic=3022.msg36472#msg36472

Hi slore,

*

It seems that Azin use LiveSystemPro or WimBuilder to build a BASE boot.wim, than WinBuilder for the "Plugins".

Correct. 

*

What they need is the words in *.srt files, like WinBuilder projects' plugins, It seems no interface for that without modifing the origin *.srt file.

I replied that on WimBuilder topic when we talk about indent a year ago:
 Lancelot Reply 18 http://theoven.org/index.php?topic=2390.msg29339#msg29339

..... (click small edit button at right of icon of any plugin)

Maybe better with pictures!

To see SourceCodes of Plugins:
1)

2)


Interface Editor, Description, Attachments also edit Plugin 
(Options is problematic not used by plugins ....)

Following is Picture with "Source"

3)




To see LiveSystemPro srt files with LSP editor :
1)


2)


ps: Click on pictures to see bigger if required.

Maybe I misunderstand what you are talking about with my bad English ! If so can you help me understand.

***
I will respond to other parts of your posts later today. 

Sorry for my bad English.

I know how to see the source code of Plugins.

if there is 9WimBS folder, I thought when I click the WimBuilder Settings button again(Azin Configure),
it should be just execute 9WimBS\WimBuilder.cmd, but

6 seconds for starting WimBuilder
20 seconds for starting LiveSystemPro

It is too long than what I imaged of the code.

I don't check the source code to see what you did. (Not  mean I don't know how to see the source code)

I try build with WimBuilder, It commited the boot.wim, and create BOOTPE.ISO,
then you mount it again to process the plugins.

I think there is a way to mount the winre.wim once, and process WimBuilder, and plugins in one shot.

I think about the implement like you create macro wrapper for the final action to Boot.wim of the file/hive.

FileRequire to create AddFileList.txt, RegHiveLoad => NOTHING (WimBuilder load the hives),
RegWrite to reg add ...

Well, I realized that, some commands are built-in commands of the WinBuilder, maybe you can't change the implement.

Hi slore,

I feel writing about development history is better to help you figure out. (as mentioned before It is a long history  )

*
Yes I start with very same ideas you wrote when I first create Azin (after the decision to use wb instead of cmd .. Azin2 or 3 .. )

*
First thing I like to mention which you did not wrote :
++
I could make Plugins work inside WimBuilder/LiveSystemPro - But requires too much work for today, possible in the future. 
 During Azin Development, I also made a lot of work to get this idea easier in the future. 
  When this happens, there will be no need Azin (and wb) to get Plugins work with LiveSystemPro and WimBuilder 
   Till that day Azin is working fine today.  (I guess some years more, I have very low hobby time ...)
    ps: Seeds of this idea and Azin idea is back to Gena development 10 years ago. I am a slow turtle that always goes forward...

++
Another thing is using builders on same base folder (not subfolder)
 But neither WimBuilder nor LiveSystemPro have a tidy folder organization following their build goals
  With this way, it would be easier to use ready target folders, but it is logically not possible with multi admins of different builders,  only sharing ideas.


**
Further What I wrote about WimBuilder is also valid with LiveSystemPro,
 I work on both of them at the same time which makes me better understand what is required.

*
> When WinBuilder's project's option changed, you update the current.js preset and the X drive to Target folder.

Yes I started that way (early Azin)
 There is a natural same path at the first steps of anything designed. 

A set of Plugins to change current.js with available WimBuilder options following the same WimBuilder-Customize design
eg.
Azin\WimBuilder\Customize\"Build" Plugin
Azin\WimBuilder\Customize\"Loader" Plugin
.....

with BigBluePlay,
+ Azin\WimBuilder\Customize\ Plugins,
+ WimBuilder auto start and build ( no create iso and NO unmount) and finish and close
+ Azin continues processing Plugins ( ComponentsY , AppsY ..... )
+ unmount
+ create iso

I did that, faster Azin Build  but there are drawbacks
- No need configure buttons -> I miss UI features of WimBuilder (eg. Today additional Chinese UI ) (eg. LiveSystemPro German UI on srt)
- With this method, It may look like Azin is hiding the real builder behind, which is not my goal at all.
I like end-user very aware all build done by the selected project (WimBuilder/LiveSystemPro)
I even ask Kare for another build ui on LSP on a LSP topic for that goal.
- Harder to maintain
---- Azin\WimBuilder\Customize\ Plugins need to be check and updated at each WimBuilder release and different patches
---- LiveSystemPro also have its own server with other srt .....
- requires at least 2 hardcode patches (via Azin) to WimBuilder for "No unmount" and "Check Finish build successfully"
I do not like such patches, I have to check them at each WimBuilder update ....
- for WimBuilder builds, need an additional configuration to get small green buttons work on plugins (mount-greenplay-unmount)

Keeping things simple is better,
 all projects have their own special features (current LiveSystemPro/WimBuilder)

so I changed my idea to Azin4 later 5 ... and today first public Azin.

What left from those days, I use a personal Plugin to change settings of WimBuilder/LiveSystemPro with the way I like.
(eg. WimBuilder Restart Explorer - Logon As Admin with 1 secs System Default ..... via plugin)

In future If someone asks to add some settings to Azin UI for projects,
 It is easy to implement to the current design (already available but not used). 


ps: Development path is full of changing ideas and design, and start from the begining 

*

Something can be improved:
1.Keep LiveSystemPro or WimBuilder distribution as LSP-xxx.zip, WimBuilder2-Full.xxxxxx.7z than *.script.

It is already that way, you can see both distribution zip files under their respective folders. 

It is also ready to build with Wimbuilder and LiveSystemPro without Azin,
 They are extracted, source folder/index info added and ready to build with selected options.

*

I think it just extract the *.7z and update some config files could be done. and 9LSP, 9WBS for cache,
shouldn't needs such time.

cache is final iso file.

Final iso file is 1) Flag file to see build success 2) cache file following its nature.

1)  If build failure for whatever reason (eg. you stop build ) Azin will not continue (halt)
Using final iso as flag file to see build success or not loose time
 but requires no additional patch or srt to WimBuilder and LivesSystemPro, keeps things simple that way :)

2) After decision 1) and after some passing time, Idea came to my mind, why not use iso for cache.
This way lost time at first build by creating iso gained for 2nd build.

ps: If one change the configuration, cache not used, build again.

*

6 seconds for starting WimBuilder
20 seconds for starting LiveSystemPro

I guess 6 seconds for starting WimBuilder is 2nd and later use of the Configure button.

Configure button, before starting builder do this:
If used without BigBluePlay, very first time after Azin extract,
---> configure button once extract builder distribution to folder

2nd and later use of Configure button:
-------- Add source folder info (and index) to selected project (or select project)
(Source Folder can be changed via Azin UI)

2nd and later use of Configure button is very fast with WimBuilder.
If you make a BigBluePlay and later use ConfigureButton, It is slow because of winbuilder memory bug, 3rd use will be faster ;)

LiveSystemPro Configure button today do more job compared to WimBuilder
1) LSP use utf8 files (or unicode bom) which makes things longer for now.... can be faster in future ...
2) If Win8 source selected, Azin should figure out which LiveSystemPro project to add source info ;)
so Azin first check source, up to source add source info to LiveSystemPro project (Win8.1 source - LSP-Win8PE configuration file)
and open LSP with LSP-Win8PE selected on UI

then you mount it again to process the plugins.

I extract so green play buttons on plugins operational. 


****
Writing long and there is a long development history,
Shortly,
I try to simplify as much as possible providing maximum flexibility.
 I know there is some time lost for the flexibility and simplification, but acceptable small time for a regular user.

Some different options to build faster already available but not good for regular user for today,
 no need to mix regular user mind.
  When I find the time to add such features with simple ui design, I will implement such things to projects slowly.

********
Already a long post, I ate my dinner, made 2 phone calls when writing this single post 
I will check your posts again to see If I miss something.
Feel free to ask things again If I missed replying.

I don't check the source code to see what you did. (Not  mean I don't know how to see the source code)

Tip:
Instead of source code,
on winbuilder ui, after hitting a button (or green play), click log button on wb interface, click "View last log" at bottom

It will be easier for you to figure out things by quick looking such small log files instead of reading source code. 

I think about the implement like you create macro wrapper for the final action to Boot.wim of the file/hive.

FileRequire to create AddFileList.txt, RegHiveLoad => NOTHING (WimBuilder load the hives),
RegWrite to reg add ...

Well, I realized that, some commands are built-in commands of the WinBuilder, maybe you can't change the implement.

Another method I did not mention on my previous post but considered last year,
start Azin inside WimBuilder as custom line ...... probably with patch without unmount  ....

ps:
All Plugins designed to load and unload hives, as a result WimBuilder ready load hives not possible via wnb.
 Only by using Plugins directly inside WimBuilder, WimBuilder can ignore Plugin lines to load/unload hives...
 ......

checking your other posts .....

It seems that Azin use LiveSystemPro or WimBuilder to build a BASE boot.wim, than WinBuilder for the "Plugins".

I still do not understand what you mean with that ... ?

*
As mentioned before, Let me know if I miss something on your posts. 

Congratulations on releasing your project! It's no small accomplishment and great for the community to have a choice and variety in builders, projects, and "plugins"

It seems that Azin use LiveSystemPro or WimBuilder to build a BASE boot.wim, than WinBuilder for the "Plugins".

I still do not understand what you mean with that ... ?

Now I understand .... 

I also wrote about the same subject for WimBuilder at Lancelot Reply 282

maybe ! since you use hta ... ! if there is a free translator service ! one can change ui setting "Translate English" "Translate Korean" ....

Well, from my point of view, only WimBuilder has a chance to do that properly. 

As I wrote a couple of time before and recently,

There is a natural same path at the first steps of anything designed. 

Which continue with,
   there are some natural same mistakes by following previous wrong design
    (eg. PEBakery, LSP inherited some winbuilder mistakes, WimBuilder inherited Win10XPE project source selection as a builder)

edit:
eg. I wrote Azin history mistakes and updates on the previous posts. 

So shortly;
Simply, follow (to me) the wrong design of current builders about multi-language support,
 Digest the experience not about success but also about failures,
  and do better with WimBuilder 

Above is just a first step of using translator idea for WimBuilder, which I can not do for Azin.
 next steps for WimBuilder will be finding some smart solutions for WimBuilderUI you handle ui for different languages since what is written can be longer/shorter - bigger/smaller - lefttoright/righttoleft 
  Translator at least can help you to experiment with such things. 
   Things I can not work on, but only have good ideas with my past experience. 

What I did for plugins for multi-language users is keeping Plugin UI very tidy using the same templates,
 So any smart user (which a PE user should be) can figure out basic things quickly.
 This help multi-language users figure out how to create good working plugins and we get written plugin feedback in passing time. 
  I did never translate them even to Turkish.  since the current design, they will vanish in some close future.
   And It is not possible with current wb ui handling, we use pixels on wb to organize ui .....

Who knows, maybe Azin with WimBuilder in future. 

Hi slore,


*

For the latest version, you can add "exit 0" to _CustomFiles_\final.bat, to keep the winre.wim be mounted, and the reg HIVEs be there,
you can continue do something with other builder, commit the modification, and create ISO by yourself.

Thanks, I add info to personal help file 
In some future, Azin with WimBuilder will probably unmount hives and continue with mounted wim with Plugins  
 which will gain a lot time ....

Things to do after I get some more Azin stability and after I finish things with Azin.


I am replying other things on WimBuilder topics. 

Good, there is no bug report with Azin so far. 

Hi slore,

You like cmd files so here are attached are some .cmd files (ps do not use with Azin_2020-01-24 ;)) to use at basefolder
(base folder where builder exists eg. D:\Oven\BuildAzin.exe - basefolder : D:\Oven\ )

They simply summarize using the same base folder with different projects each using its subfolder,
 and as a result (which also demonstrated by cmd files)
 one can safely enable/disable/delete/add new projects using same base folder,
  without folders mess, all in one place. 
   with no personal plugin lost etc.... 
     I hope this helps you on your wimbuilder-project design in future.


Tip:
put Azin_2020-02-01.zip and "Azin_2020-02-01 Update.cmd" to base folder (with 7z.exe) and double click "Azin_2020-02-01 Update.cmd"

History:
In the past (more than 10 years ago), we had to extract all projects to different folders, which cause lots of folders ....
Still valid today for different projects .....
But It was annoying to me, especially when using same plugin/patch etc. with different projects,
Updating a plugin on one project was requiring the same update on another on different folder ...
not maintainable in the long term ...
So I made adjustments (demonstrated at cmd) to fix that troubles. 
eg.
 updating 7z plugin updates all projects (Azin (WimBuilder+LiveSystemPro projects) + Gena +Yomi +Win10PESE +Win8.1PESE +Win8PESE +Win7PESE )



See you on next post....

Hi All,

Azin updated to 2020-02-01

Extract Azin_2020-02-01.zip to a simple base folder eg. D:\Oven\

Main Change:
Azin added to server with Download/Update buttons on Azin Plugins. 
+
You will notice new plugin:
Azin\Utils\'Update Project' Plugin
--> Using "Update" Button will update Azin without downloading ~190 MB like with zip file.   
+
And other plugins updated ...


*
Unlike other projects, to keep Azin updates small-sized (server 72 MB uncompressed),
 Azin server only holds Azin Plugins, so better:
   First Extract zip and later update with Azin\Utils\'Update Project' Plugin.

*
Memo:
Download buttons on plugins only Download if there is a new plugin on the server,
 if there is no new plugin on the server, nothing downloaded and plugin reverts back to default settings.
See: Small Green Download Button on Plugins - Reply 1: Update Plugins


*
Latest Azin can be found here:
Azin Download Page