Win10XPE Project

Live your idea James. Will start doing that.

Also good to know that moplugins will have higher priority. I kept on deleting the included from my plug-ins.

To Add To That:

Chris is the one who develops the Core Project...
And He Includes Any Updates to Project Plugins.. (Which he lists in his Release Notes)

To Update Just The "Core Project" Copy Just > "\Win10XPE\Projects\Win10XPE" < from New Release To Current Working Win10XPE Folder..
Then Follow Release Notes For Plugin Updates in "MyPlugins"

Although there may be New "Tools" and "Include" Files...
Either way you choose - you'll figure out what works for you...

Note: By renaming Win10XPE Working Folder to Win10XPE-1 = You'll Have a Backup Working Folder...

Thank you for the direction and prompt response. I'll give it a go. 

2019-01-22, 2019-01-23, Let's go for 2019-01-24   
Not to stay with a mistake on Backupper for support

Win10XPE_2019-01-24 update

AOMEI Backupper: updated to v4.6.1

Hallo,
i used Version 23/01/2019!
When running Macrium Reflect, there is an error message. (see image)
This message appears 5 times before the application starts. 

I Was Not Able To Produce The Error

I have come to a conclusion - That maybe Anti-Virus Software on your Host - is removing certain program.exe(s) from the Project Directory..
Verify If This File Exists > \Win10XPE\Target\Windows\System32\LetterSwap.exe

If,Not,ExistFile
Allow an Exception With Your A/V software for the Project Folder..
Then Re-Extract The Release....

I don't reproduce either for Macrium Reflect

Package updated with the same date, change:

 AOMEI Backupper_XPE.Script (50.44 kB - downloaded 55 times.) updated v4.6.2

 AOMEI Partition Assistant_XPE.Script (50.33 kB - downloaded 60 times.) updated v8.0.0

I checked. The file exists in the folder.

Macrium Reflect now works fine.
I have deleted the old project folder.
Then I started with version Win10XPE_2019-01-24 from the beginning.
As operating system I have now WIN10 Pro 1809 chosen.
Thank you for your support! 

Win10XPE_2019-02-02 update

StartIsBack: v2.7.3  StartIsBack has been moved to a new independent plugin, hidden. It uses StartIsBackPlusPlus_setup.exe, easier for updates.
PowerShell Core-6: download link changed to v6.1.2
Everything: updated v1.4.1.932
AOMEI Backupper: v4.6.2  Add Import from host or Copy Paste a valide Serial Number for Professional, Server or Technician Edition
   Otherwise, the Standard Free version is Applied.
AOMEI Partition Assistant: v8.0  Enter your Registration Key for Standard, Professional, Server, Technician or Unlimited Edition
   Otherwise, the Standard Free version is Used
WinNTSetup3: updated v3.9.3.1
XPE Startup: (new) Add XPEStartup.cmd and(or) XPEStartup.ini at root of your USB, to customize some tasks without having to rebuild project. They Will Be Called at Startup Before Explorer Shell.
and other minor things...

Enjoy 

Would Like To Make Members Aware Of A New Feature Being Slowly Rolled Out For XPE Plugins...
We Have Started To Implement An AutoBackup For The AutoUpdate XPE Plugins...

How It Works Is:
When You Select To Update The Container File - The Old Container File Is Renamed With Program Version
Example: AOMEI Backupper_XPE_File.Script Is Backed Up and Renamed To AOMEI Backupper_XPE_File.Script.4.6.2.0
Thus Giving You The Ability To Restore An Older Program Version If Needed...

@ChrisR,

Would Like To Make Members Aware Of A New Feature Being Slowly Rolled Out For XPE Plugins...

The Old Container File Is Renamed With Program Version

Thus Giving You The Ability To Restore An Older Program Version If Needed...

   Besides I am sure in the end (we made after some years) you will do similar going on the same path.
   Circle development: one way or another always go to the same directions or motivation lost during the path. Most important: very valuable time lost.

Good for XPEPlugins,
Just a reminder for your Circle development and to put a post to history it is not a new invention.
( at least posts not deleted like plugins *)
since posted here, writing here.

Such plugins already exist on "Plugin" side since Date:2017.10.21 where download simply backup file on provided folder during an update.
PC Packed -> + Add Download Button + Add 'Provide File' Option

James already knows this since XPE Packed is modified from PC Packed.

eg. Aida and some other very frequently updated plugins on Yomi
Initial idea from gbrao Date:2015.07.02 on Partition Guru plugin History002= ... (implemented to PC Packed nicer and much later following limited free time.)

Going more history, idea was there and used time to time but always failed due to 2 missing things.
1) download was not stable with current builder. Everybody was using a different tool to download.
 Around 2015-08-30 Call,Download created. ( History42rev49=Lancelot Added  )
  Today it is a very stable syntax supporting 2-3 downloader with fallbacks.....
2) It will always fail in time with changing weblinks and changing setup files.
eg. there was a recent post that requires one of James plugin updated since setup file changed.
ps: Above invention will still fail if one do not have old download.
Solved with providing FileContainer side by side with plugin. ( PC Packed - History021=Lancelot FileContainer )
(which seems James like more to play with FileContainer)

some references to plugins written.
Call,DownloadX,"%BaseDir%\Projects\Yomi\AppY\HD Tasks\Partition Guru.Script"
Call,DownloadX,"%BaseDir%\Projects\Yomi\AppY\System Tools\HW Info\AIDA64 Business.Script"
.... I am sure you can find more ...

+
I will not surprise next invention on this area become providing FileContainer with a separate package like already done with PC Packed.


****
Anyway, keep going. 
Above is only to put a post to history

@ChrisR

thanks for the project updates

@James
thanks for the oncoming AutoBackup of _File's, perhaps it could be optional via checkbox

there was a recent post that requires one of James plugin updated since setup file changed.

Sorry Do Not Recall Such Change

there was a recent post that requires one of James plugin updated since setup file changed.

Sorry Do Not Recall Such Change

I am sure all setup distributions of your XPEPlugins not changed and hence your XPEPlugins never need such updates.  (sarcasm)

Anyway, my previous post is only to put a post to history , that is all.
 I know you already aware :
  Some setup file updates result with any plugin without Provided File or FileContainer have to be updated to fit changes.
    If you like, share around some real examples of your XPEPlugins that had such troubles.

     Rest written in details on the previous post with last words on this:

****
Anyway, keep going. 
Above is only to put a post to history

Win10XPE_2019-02-02 update
XPE Startup: (new) Add XPEStartup.cmd and(or) XPEStartup.ini at root of your USB, to customize some tasks without having to rebuild project. They Will Be Called at Startup Before Explorer Shell.

Thanks ChrisR!

XPE Startup is really useful.
I did some tests with XPEStartup.ini.
By the way, '//' in XPEStartup.ini is not override over pecmd.ini. Is it normal?

for example,
pecmd.ini: LINK %Desktop%\Explorer,%WinDir%\Explorer.exe
XPEStartup.ini: //LINK %Desktop%\Explorer,%WinDir%\Explorer.exe
Result: Explorer icon is shown.  ---->This is your intension?

pecmd.ini: //EXEC %ProgramFiles%\PENetwork\PENetwork.exe
XPEStartup.ini: EXEC %ProgramFiles%\PENetwork\PENetwork.exe
Result: PENetwork.exe is launched as expected.
(Reversely,
pecmd.ini: EXEC %ProgramFiles%\PENetwork\PENetwork.exe
XPEStartup.ini: //EXEC %ProgramFiles%\PENetwork\PENetwork.exe
Result: PENetwork.exe is launched.  ---->This is your intension?
)

Regards.

Hi circcc,

You already know, for others, in XPEStartup.ini as in pecmd.ini
// corresponds to a comment

XPEStartup.ini is just given as an example. In the script all the lines are commented and so it does nothing at startup
The commented command lines are there only to show pecmd syntax.
You must use the Edit button to customize the script or modify it later, at the root of the USB key.

XPEStartup.ini is not override over pecmd.ini,
It is just an extra addition to pecmd.ini, both scripts are loaded.

At startup pecmd.ini is launched, it does the first steps
Then it starts XPEStartup.ini if it exists  (IFEX Y:\XPEStartup.ini,LOAD Y:\XPEStartup.ini)
before continuing its work normally by launching explorer shell and the following commands. 

Code: [Select]

pecmd.ini: //EXEC %ProgramFiles%\PENetwork\PENetwork.exe
XPEStartup.ini: EXEC %ProgramFiles%\PENetwork\PENetwork.exe

Result: PENetwork.exe is launched as expected, Before Explorer Shell   (XPEStartup.ini is launched before SHEL Explorer)
Reversely:

Code: [Select]

pecmd.ini: EXEC %ProgramFiles%\PENetwork\PENetwork.exe
XPEStartup.ini: //EXEC %ProgramFiles%\PENetwork\PENetwork.exe

Result: PENetwork.exe is launched too, but this time After explorer Shell, as currently

It is the same for XPEStartup.cmd, it's just an example
To allow users to add their own tasks, if needed.

ChrisR, thanks you for your kind explanation.