Win10XPE App plugins request

Would you add a script for aomei backupper technician plus 

Would you add a script for aomei backupper technician plus 

ABU Free and Pro use the same setup file - all the other use a different setup file..
And without a valid key testing would be a guess, as to it's proper function...

Welcome To Forum
Please Use This Topic For General Discussions > http://theoven.org/index.php?topic=2488.0
As This Topic is Reserved For Member Optional Plugins

I couldn't find a script for WinToHDD Technician Edition, is there any possibility to prepare it?

For me, the easiest Windows installation via Winpe is happening with this program.

please password
login password open session winXPE tank you for works future update

Split Topic!
Again, please, "Win10XPE Optional Member Plugins" Topic is Reserved For Member Optional Plugins

ChrisR,
Jumping ahead of you a little to test your latest revisions to ABU Plugin with the " Tech Edition Request "
As I have a feeling it may work here.... As the Files Used In x64 ABU Boot Media Are The Same For Tech Edition also...

Also Another Note:

ABU File Versions ,1.dll  > Signed
And File Versions ,2.dll  > unsigned

Also figured out the "Tech Edition" / "Image Redeploy"
Is just ABU 3.0.0.0

Index 2 seems to be used during installation but at the same time, it's probably better with index 1 and signed dlls
Seems to work in both cases, don't know, I will try using index 1

Good to know for the Tech Edition

If possible can we get these extras from PESE

CMD Settings_Color.script
CMD Settings_Console.script
CMD Settings_Options Layout.script
ContextMenu.script
Exp ContextMenu_ShellNew.script
Exp IconSize.Script
IconPositions.script
Steps Recorder.Script
Tweak UserPreferencesMask.Script
Tweak Visual Effects.Script

If possible can we get these extras from PESE

Most Some of them should already compatible to Win10XPE

test and see. 

If possible can we get these extras from PESE

Most Some of them should already compatible to Win10XPE

test and see. 

I used the XPE Code checker with full convert. No luck. ill try without full conversion.

I used the XPE Code checker with full convert. No luck. ill try without full conversion.

I do not know XPE code checker.
As I wrote try without conversion.

as far as I remember,
CMD Settings_Color
CMD Settings_Console
CMD Settings_Options Layout
should work

ContextMenu
probably work

Exp ContextMenu_ShellNew
Exp IconSize
IconPositions
probably work

should: let me know
probably: let me know

Tweak UserPreferencesMask.Script
Tweak Visual Effects.Script
will not work (with or without conversion) but you can work around that

Keep in mind, all these conversions stuff happening only because of a fabricated incompatibility,
eg. http://theoven.org/index.php?topic=2488.msg31384#msg31384
....
In some close future, there will not be a conversion requirement.
I do not need conversion at home since 3 months I guess 

If You Want PESE Features - Then Use PESE Project
The Goal of XPE was not to be PESE

Win10XPE a rather simple in its design and at the same time fairly complete project .
With a simplified user interface and fewer options.

And YES, this "Fabricated Incompatibility" was by Design.
As ChrisR had no desire to continue to support the PESE project with a History of supporting every version of windows.
Thus we now have Extend Support for the PESE Project and a Reduced (Windows 10) Project in XPE

And YES, this "Fabricated Incompatibility" was by Design.

 
(...something about the floodgates opening...)

And YES, this "Fabricated Incompatibility" was by Design.

Design -> Intentional

And your further post only hides your real goal,
 you like to put your name on plugins that is all. 

As ChrisR had no desire to continue to support the PESE project with a History of supporting every version of windows.

NO: PESE have no such "primary goal" to support every version of windows !
only it is quite easy to do such a thing with Win10PESE.

Thus we now have Extend Support for the PESE Project and

Win10PESE Extended support will continue to no extent.
From Atari800xl point of view, Flood gates are open. 

a Reduced (Windows 10) Project in XPE

No
%GTools% -> %Tools%   
etc.
have nothing to do with such a fake reason.
Anyone can create a "Reduced" (Windows 10) project without breaking compatibility of plugins.
Well the only idea is writing James name on plugins,
 fine to me,
  but have a self-respect and post correct arguments on topics,
   no need to hide behind a fake reason.


next project with %FTools% is enough to "fabricate" fake reason write another name on plugins. 
 
In reality, one do not need a fake reason for that, this only cause incompatibility that is all.

Come on

(...something about the floodgates opening...)

If You Want PESE Features - Then Use PESE Project

I agree, only from another point of view.
 

My Goal is to Support ChrisR's XPE Project..
And appear to be the only one do so by Creating 3rd Party Member Optional Program Plugins..
I have no need to follow other plugins, as I have long history of plugin creation in this forum..
But, yet then we ALL seem to follow the same process that works..

Lance,
Over the years I have learned a lot from you, from your posts and this forum.
You have helped me figure many things out along the way.
And for that I offer my sincere sense of gratitude..
 

My Goal is to Support ChrisR's XPE Project..
And appear to be the only one do so by Creating 3rd Party Member Optional Program Plugins..
I have no need to follow other plugins, as I have long history of plugin creation in this forum..
But, yet then we ALL seem to follow the same process that works..

Lance,
Over the years I have learned a lot from you, from your posts and this forum.
You have helped me figure many things out along the way.
And for that I offer my sincere sense of gratitude..
 

Does my little contribution not help :(