Yes Sir.
@
lacruelrealidad : You have to go a long way ahead!
1. Use good portable programs. Actually, an ideal / good portable program is one that have all the required things already included in the folder or executable. If not, portability is not practical but there are such programs.
I used some portable programs packed by PortableApps.com & they came out to be good enough but you never know.
I am planning to give them a try :
Turbo Studio Express & VMware ThinApp
2. Try to make plugins with your portable programs. Its quite easy.
Create Portable App Packed Plugins
Why ? Because once you make your plugin, you can analyze your plugin with an inbuilt Utility :
Check Target Sys Files
Besides, you should always have a look on logs after performing anything to watch for
Warnings &
Errors
To get a plugin integration log, one need not run the whole project. Just run the plugin / script by clicking the
Green Play Button & go to logs.
For eg.
Run the Green Play Button to Integrate DISM++64
Attachment 247428
After the runing completed, the logs are written for DISM++64. To see the related log, immediately go to the logs. If you run / do something else, the logs will be changed & updated for that.
Attachment 247429
3. Try to include / check some essential items in the Project Interface to make sure that your programs dependencies are automatically met. It may increase the size but you have to try out the things!
Theortically : As many things you include, the more chances that you have a sufficient registry & everything there to run your portable programs. I think many things are shared between different apps.
But on other side : it may create some problems & conflict.
( To say again : Go through the logs after doing anything! )
I would suggest consider adding :
(i)
Build Core > Main Interface >
Network Additions,
Microsoft .NETFx4,
Switch to Admin
( & You may want to increase
WinPE Cache Size to
2048 MB )
(ii)
You may try adding : Build Core > Build Options >
Use Full Win10 Software Hive,
Add All Win10 Catalogs
(iii)
In Apps > Components >
NET Framework 3.5 ,
MS Visual C++ Runtime & OTHERS!
(iv) Up to you!
4. Its clear whenever you make changes & run the project, the
Win10XPE ISO in the
win10XPE Folder is changed. If you find one useful, copy it to somewhere else before trying other things.
5. To ease up your experimenting : You need not burn it to a DVD or Pen drive each time you want to test the new ISO / options. You can add them directly to your pc boot menu using the Utility :
XPE Host Boot Option : You can select between UEFI or MBR according to your system.
Add Host Boot Menu Option & Remove The Host Boot Menu Entry
Thanks & Regards. ...
( All Thanks To The Guide :
Win10XPE - How To Quick Start Guide )
