The Oven

Plugin World => General Plugins => Plugins => Topic started by: RoyM on November 22, 2019, 07:01:14 PM

Title: Converting script between PESE and XPE
Post by: RoyM on November 22, 2019, 07:01:14 PM
Converting script between PESE and XPE
Continued from HERE:  http://theoven.org/index.php?topic=2979.0
As suggested.

Thanks Malok.
I didn't wanna do a TXTReplace, I could see it going wrong very easily.
As I see you found out also....

Copying the plugin to a \temp folder and then TXTReplace would be safer, That way the original stays intact.

I have fixed the Add_Shortcut problem, but I did have to edit %API%.
Call, is also giving me problems, For now, I think it will have to be
done manually with a search and replace by the operator.

RegAddBoot is another problem child, For now, RegAddBoot will be ran as a RegWrite.

@All, I'm sure other issues will arise, please reply with issues and/or improvements.

Follow the directions in the [INFO] section, to use this plugin/converter.

Regards.
RoyM
Title: Re: Converting script between PESE and XPE
Post by: RoyM on November 22, 2019, 08:03:12 PM

There was an error on attached plugin above:                                         Change From

[ApiVar]
Add_Shortcut=Run,%API%,MAddShortcut  <-- add this line manually to (script.project), under ApiVar.
AddShortcut=Run,%API%,MAddShortcut

                                                                                                          Change To, Do not include ()
[ApiVar]
Add_Shortcut=Run,%API%,MAddShortcut  <-- add this line manually to (Macro.script), under ApiVar.
AddShortcut=Run,%API%,MAddShortcut

A new one has been attached with better directions and annotations.
Regards.
RoyM
Title: Re: Converting script between PESE and XPE
Post by: 0scar on November 23, 2019, 12:52:55 AM
An updated version of PESE2XPE plugin converter for XPE:



Title: Re: Converting script between PESE and XPE
Post by: RoyM on November 23, 2019, 01:34:19 AM
Very Nice Oscar, a True converter.

To explain, what Oscar's converter does, is to take a .script or plugin,
and rewrites it to %Basedir%\Projects\MyPlugins\Apps\XPE Plugin Creator\*.script
as well as making it XPE compatible..

What se2xpe does, it is mostly a wrapper for the (plugin to convert),
When the (plugin to convert) runs, the first thing it does is to call se2xpe.
se2xpe then changes the variables on-the-fly, so that the (plugin to convert) is XPE compatible.
se2xpe does not change the original script, except for the initial 3 lines of code that are inserted.

Well Done Oscar.
Regards.
RoyM



Title: Re: Converting script between PESE and XPE
Post by: James on November 23, 2019, 02:41:38 AM
Quote from: 0scar on October 13, 2018, 07:07:57 PM
First there was James
XPE code checker (aka PESE2XPE converter)
then oscar wrote
XPE2PESE converter (an 180º turn of XPE code checker)
now there is Prz42
PESE2XPE converter (an 180º turn of XPE2PESE converter, and de facto a 360º turn of XPE code checker)
 :lol:

So some of this is not new - just a rehash of the old...
Only the names have changed...

[attach=1]

History001=KYHI Initial XPE Plugin Created 2018.09.20
http://theoven.org/index.php?topic=2488.msg27818#msg27818
Which was removed from the Project Utilities...
Worked with Simple SE code changes..
But did not address the more complex SE Macro's...



Title: Re: Converting script between PESE and XPE
Post by: Lancelot on November 23, 2019, 09:44:33 PM
Thanks RoyM opening the topic,

now we are sure posts will not be deleted.  :great:

Long story to short, Here is the package,
 just extract to Win10XPE folder to test (does not overwrite anything)

Win10XPE_Plugin_Compatibility_20191225.zip (http://lancelot.theoven.org/TheOvenAttach/Win10XPE_Plugin_Compatibility_20191225.zip)

Only extract to Win10XPE , and click BigBlue, all should work fine.
( I just extract Win10XPE_2019-11-20.7z and Win10XPE_Plugin_Compatibility_20191223.zip to same folder, work fine here)

In the future, If not sabotage with another fake fabricated excuse, it will continue to work fine too.

****
To demonstrate all work fine, I add some plugins to the package
"OneLoupe"
"Steps Recorder"
"Mouse_Cursors_Breeze Cursors by niivu"  :lol:
"ExeProperties (ExtraBit)"

Plugins work fine out of the box without change or convert.

To exaggerate, I also add "VirtualBox Emulation" and "VMware Emulation" plugins, they work fine too without change or convert. :lol: :cool:

******** This quick Package even today naturally works better compared to any "to xpe Converter" ********

- Require_FileQ all working fine
- Require, all working fine  (Require,FileList etc.)
- Call, should be fully working (my quick tests are ok)
- RunFrom partially working, following current Win10XPE design
- ChangeInterface, etc. should be working fine.
- RegAddBoot
I guess Win10XPE still uses pecmd, whatever the loader add a line equal to following cmd line JUST BEFORE Shell load :
Code: [Select]
If Exist %SystemRoot%\System32\ExpEnvVar.exe Start /Wait ExpEnvVar.exe
this should get RegAddBoot lines to work.
(see "Add Shortcut etc." plugin lines)


**
I hope this package stops black propaganda about Macro Library, Syntax and Plugins.
 eg. "complex SE Macro's" -> wrong  ----> correct: "Simple Plugin Macro's not available with Win10XPE so conversion can not fully work" etc.
   In reality, you can convert App xpe-plugin to plugin easily, but the opposite is not easy.  (to plugin converter will always result much better)

 Macro Library, Syntax and Plugins designed well,
  And Plugins works fine even with WimBuilder2 (http://theoven.org/index.php?topic=2390.0) and LiveSystemPro (http://theoven.org/index.php?topic=296.msg35404#msg35404) here with another method,
    Half-day work to create the above package self proves Plugin concept with its Syntax is very good.  :cool:
     Still better hope package stop this fabricated incompatibility relevant things to re-write or convert and posts etc...



***
This is a half-day Saturday work just to prove the concept with Win10XPE like I did a year ago but did not publish that times,
 I do not have any more time, feel free to improve and distribute further, It is a very mature head start, I can assure all plugins %100 work if one improve the rest*.
  At least you will not need conversions anymore,
   ps: I can post feedback when required If I am around, see notes inside plugins ....

rest*: rest is mostly project-specific things.
 eg. LiveSystemPro, WimBuilder2, Gena use different tools/methods (syntax) to create shortcuts during build, Win10XPE use pecmd to create shortcut at boot,  ... etc.
    Such things are out of Macro Library and Plugins, controlled by separate plugins.
       eg. The current package has a separate "Add Shortcut" plugin for Win10XPE, Gena always has separate "Add Shortcut" plugin .....

Have fun. :turtle:


Edit:
\DownloadsY\ Added to package, giving example:

On builder UI under Win10XPE
Win10XPE\DownloadsY\
"Downloads Plugin Compatibility TOP" Plugin ----> Click Green Play Button
"Download Plugins - 1"" Plugin
 ----> Click Download button at the LEFT of \Appy\Accessibility\Zzoom_omiod
 ----> (you can Click Other Plugins Download buttons)
 ----> Click 'ReScan (Refresh) Plugins' button (Restart Button) (Green circle button on Plugin UI) ==> This will restart builder
"Downloads Plugin Compatibility END" Plugin ----> Click Green Play Button

You will see Win10XPE\Appy\Accessbility\Zzoom plugin available ;)

instruction with pictures also available here: http://theoven.org/index.php?topic=1208
Title: Re: Converting script between PESE and XPE
Post by: APT on November 23, 2019, 11:29:51 PM
Hi Lancelot

Thanks for all that work, went to give it a go but then got stuck.
I can't find any plugin that I'm interested in personally that doesn't already have an XPE version already available and up to date.
But I'm sure RoyM will have one in mind, anyway thanks again
Title: Re: Converting script between PESE and XPE
Post by: James on November 24, 2019, 01:32:59 AM
A little more then 200 lines of code required it seems....
But 2 questions - why folder with plugin .lnk and another with script ??
Why not use existing tools ?? - see some new others same
Title: Re: Converting script between PESE and XPE
Post by: James on November 24, 2019, 02:08:02 AM
Hope we can discuss this in a meaningful manner for the sake of development...
Would it be possible to use a folder structure similar to what already exists in XPE ?

[attach=1]

This way SEPlugins can interface nicely with others - rather then have additional App folders

This should allow any Pre-checks or SE process to be run at start of /SEPlugins/Apps and end there after
Title: Re: Converting script between PESE and XPE
Post by: slore on November 24, 2019, 03:02:23 AM
Quote from: James on November 24, 2019, 01:32:59 AM
Why not use existing tools ??

Are there existing tools for making Script out of WinBuilder project's box(world)?

Quote
And Plugins works fine even with WimBuilder2 and LiveSystemPro here with another method

This is new thing. I'm glad to see it. Lancelot  :thumbsup:

My project(WimBuilder2) has more functional Windows components, but it leaks of 3rd apps, or some tweaks, because it is new, less people create patch for it.
My personal is using PETools for loading/mounting the applications to do that, no need to add them in building.
But for the PE SE users,  Lancelot's work can:
Quote
WIN10XPE + Plugin_Compatibility => v1903, v1909 supported Win10PE SE.
LiveSystemPro + Plugin_Compatibility => v1903, v1909 supported Win10PE SE.
WimBuilder2 + Plugin_Compatibility => v1903, v1909, 20H1 supported Win10PE SE.
(I don't try it yet, but the UI part is different, the plugin Interface won't be used, maybe build with default options.)

for the XPE  users,  Lancelot's work can:
Quote
Use existing good plugins with WIN10XPE project. Use those assets without spending time to make convert plugins, leave the plugin(s) work fine in both projects.

But for the WimBuilder2 users ,  Lancelot's work can:
Quote
Use existing good plugins with WimBuilder2. Use those assets without spending time.

Well, on WimBuilder2's design roadmap, In funture, The end users will add/update applications in the simplest way ---Just update the official download url or dist.

Chrome is updated in with next change lines in GoogleChrome_xxxx.script in Win10XPE-11-20.7z:
Code: [Select]
Title=Google Chrome v78.0.3904.97
Description=(v78.0.3904.97) Fast Free Web Browser. One browser for your computer, phone and tablet.
Date=2019.11.12
History001=KYHI Initial XPE Packed Plugin Created 2019.11.12

%SetupURL%=https://dl.google.com/release2/chrome/Z4qsd_C-892jH1fG88zAOg_78.0.3904.97/78.0.3904.97_chrome_installer.exe
%SetupURLx64%=https://dl.google.com/release2/chrome/APxmP00ERnxueB1YewL8360_78.0.3904.97/78.0.3904.97_chrome_installer.exe
%FileContainer%=%ScriptDir%\GoogleChrome_78.0.3904.97_XPE_File.Script

If,Not,ExistFile,%FileContainer%,ExtractFile,%ScriptFile%,Folder,GoogleChrome_78.0.3904.97_XPE_File.Script,%ScriptDir%
chrome.VisualElementsManifest.xml=320,427
GoogleChrome_78.0.3904.97_XPE_File.Script=4479,5972
[EncodedFile-Folder-chrome.VisualElementsManifest.xml]
lines=0
0=eJydkU9LxDAQxe+C36HgISeTrM1ud5dWUHFPqx4q4mEvoYY0mMzUJCX5+LYIi38QxIE5zLz3foeZ+moYrOlkNAhFdhbCNgfTkD7GYctYSommkqLX7ILzBXu+27ddr5w8NxCihE6Ry9OToqifTBilvbXKKYhhXs3V9pjupVMP0L6N0qvFkuep96ixIQjk6PupVmvKabnhgm6qw1f6YXbQAfS3fMVz9Yd066S1vyCEyEL8F7FDr7THEV4eVY4NsUb38ahey+71Q71Bi74hZ8vdqlytCZsuWLNPf5jmd2C9fOx4nFNMzijKz03VC8ssLk3Mcc1JzU3NKyn2TczLTEstLtGryM1hGAXDGExnhNAPcMj/6TNZzsAEAL5AERSNJrrOAQAAAAIAAAA8AAAA4AAAAAAAAAABAAAAAAAAAAAAAAA

[EncodedFile-Folder-GoogleChrome_78.0.3904.97_XPE_File.Script]
lines=1
0=eJx9WMfS40iOvldEvcMffWVP07tDHUjRi06i58TEBr33RiSfflnVvRvTcxgqJCUTmR+QADIB5D+1qOr/9f2bXa1t9kMchqLNvh7lPHTZF0n9Af2B0hD2B01+CdVPwtCv9/hsviecY/bDN3mz3Yqq//6Ny5Zkrsa1Gvoffx/7JQzz19+R93+H/v6N2dZymH88A0m+gaI1+4FAMP0HDP8BI9+/PeYsrdblh11mxp71fwxz8RNy627STx7J+uP7Nzebl5+sIQj+/k3N9qz9Ad1Yw6dvhyj9nz97bjAra7NkzdIf+tBn379pUZ9G6zCfP4SoXe4OffCiua/64v86pGr5Sb9xf8n3JffVWkXt1730LzNKmiz9+lMFX7ect+jp17/L/v+zkVvG79/+KfdrNudRkt0qH+3sWNnhgH/8Zg9fUpX+TWc/VfgXsHDr7Mues+zrH19Wtv7nqH/+MuHXX4v+7Xf45wf+nYB+x9G7Rf1O/c4ObfqLvxvNVRS32fKvX6/mPCTZ8vOFT8rh99/+w3B/8f/H1636OfuSly99WMtbOV+3wH/N/e0X0J8W5PtkSLP0hvvT3H9a2xzm9SdPjMKoP6pk+IFSCPE7DkO3ftShGH78t8G/0P/C/SndP/7G6R//beotRnsvY/lxewT0I1OutetTzBV84jipzWIF7oG8aiJGXg0/El3Ya6OuzE9+UJ7Ftm3VMhTdwQiddcgSzI68zigM4ijTS+KLUikUhrcMShnZhzZp4A5c+775+UNkZVuCUfqgzAtPTxxPL5NG0TwBsJRtpOHIMcxg6iU+tfJsP693UT0CzefTor1YnwdXp7ywBERSYxdgZRtNXPOgg+niKC6l6LVKqWFdG7T6+SqtXhYATavJeLOwttSSzQewJSzFH1qa4JwhWW2KQFREgHkz7uXbfDaVH7vrqj3XsJy3VCirLiPOS51lmZaNelu8j1SSwqrDogiQ3Gisns0RmPh8v7x3sm1EFdtbnnwwbUS2VoutVssB36xqPw8r0dpTaMWrCSQkVRuX6rq8Got7g7dJMAn8/Y0QrxiMxFjR/JgBkiLtjmAsJSGRKIJDAulR8WdKxpo+wgwVkEsnYpj7fNuLJUmfsfKXs13yRd5ROHXcj/gQVaO3jk4UsWRBFGdOE0Kh4pnbG086KwSAxMPBIsb3ZT5/hsxHxPCdI8xCFCjjdZhubACPJjpc+2HMAze2iK+5n1bjyvhBqMYtx+T49V7hDoVAa22Zr0DeYWiLlKvvnFMyPmeE7RMSR6TPUuQHAV7s8cLBxk9NRrHJjsGGwT6b0pg+j2XmYmkDmTk43gRLLm+RQK+LeQD5HgAWzm5VPgUmS7zn7QDejRGcJir7b5zMih0ULLJ5mIlrDv4q0zkBSXq8CYhncfR1+cYcEgs4vkjT7jU33mQYc10+C4biWRoLDslFxfrYaL2nvsjRj5iy+nMIUYLXdNurmWp6OcTDQRMe7N8BjA0m/vILyBA0/XQhYqBjGiZT7WYbiSnqTcZtxb2Ofq5XbpON8gPqDHecxQZMe4ua5oiYymwsw2tRa7A1DxYxA4JWI4ZxWCZ8EJfthQuNebtqCzSVs6tcSoTAhnOYWR82QzUy9Z4RNKUeCwWZZynWFpyN4rHgtbru62OzU6ZWs6gDhSPcnnp4zULKDc7LBZTH8DHLaiB4ebIxQrR72WBhEpQ+z2un8hM+qMtMj1rbY+vcuZO3O/nyOwaY1BgaqK3MwcJYBTC3S1xTwjDXpnTk3uVorjp0e35Pjo8jm6QI773qjOCu7StuH0PoXaqxu3inpHy0UjIXBLto+RU3oMz1ywxKCS77c7SZmYsNCvzOc8THB66rBHhh90hHNd8+FGoREodECYsncW8a6iFFOjOVyAkFDBApzGfdaC+KGt7CrsdJR+LdZySs5wOIqbPTn6LwwUqfwE1CBqu8fWWHQFdmE7Rr9ORDS30gJ3DAflUmmjC/NEejND7x0NV6o++EspM8gtV1owwJl2jvyQQUXRubQndw+yoMnJ4qs6JriJSoo3dRWY9Im9gs1BcSiqcUzruylJf7sDwJgwC6CpEvLAfMoKLpqRT0DSTjNW04PA70bGpEAEfyPgKe47S+k8x9cNVSiH4Cj+Anun0Zx9SOnahen0FXGiI6A1n65R8GCH8MQkB51Fzr+Zhxv2+ktOo3M6jxmVn2oO3PpLsUVI5Wm192dTG0ju0SnwxNNkOa/oHRzgMf+lajubinHg99qD1lbiDceQWIU6B4uugmJXVP9BAJGEUwcEkJEH5WobTaKjG/YEsb1bckvc3w5Qio6LalhT4B1+PbKPUC6e14dP0x3d0Ac2Y0OpZqHvAoIYTYmN77CXmHlAHXGlTZSKVE7CsERlYDr1DcLOLIaGD29UEFL937zk/eSY1lFVDBEPq41pbr5PAkg+bz1i7iTEqlakIhezcbrpxClDxde2/IbGKjoe7WK429IMkv8lNX3mqRC9qQWl81qAiY0u1S0G7IM9DQAQ8AfXCQgJ28di9Y6IX0PyAm59mRRzLDieuQBwFLP8DXe0Pv3b6RrUzyH+4a8NmFyUGYn+AgmSw85oTfoDdpBRo8lTe6kroF37cNg3wA3OECTdLnNSkbntXkLsnDM64UpH0fknD0BSIqXK6KPGE7da8zL9Lejbrx6evFHdPhDc8Hzttiy7XgGSX47CnhoBYn6LyQ/cr82YSAic+xmlQWmgdCkVFQ37YTZLdcQKVmxer1BWOsHIyHM9Chz5v+0NdhgjYz5XcmY48r8Wm8THXMEw21187vXScSeqo3Krcqqe3CHZu8svx6PVDdKKcEkd/sG6EaqzeKgDYRcKLN4MXGODpEAG7Fz6Q0ayCj/BOBj7Ft9bpGr6pKfIQwHwBgtJvNZPSIkiVE9hIaCy1wJVRrQrF3Wc+KAEENDwS1fz02mA3Mqiru8+GNrogckxJuKWkKcAhPESZruELmysjhs1tQX1gz9Ip69bX2dtX2UCb4xPm5TRCO931R7XPVfBT5hqdbseqc7XyAy6MvVLutC6krIskSkefjDC7KubaUlB4t5krYqFgX/khdp+VXEm3HIoyAV6A8aeRNjZNNWAvlqSc8Mr2JBwmRBHQTZk6dCEMuMfkyqHtWv8xVKAy2CpB0aXbjHPyIyGI9SXHAORdv7IRuHKergbVDyYm9Ai2wgjmkHgRoTSSQt6AaI9p59+t8KVVnes3dOERLpDZQAp4rkDGz43DNuBF4DXSEFOucXBhFSOrSdGRpYOo7PIuYJZwzrtXgS2vVjpI/o6fL9z7ThLclGrdBcB9kDelkz6nRTmCMQBivxynuSLFapR0AW1mnHXolhzH30DAZXInskzwDR1/IRIGXl0gKIxHYCyzsiOwAHgMukkKX15/MvVL90F1TAcxohPVPnGvOuiBQ9JZPE++YWgZFrQJZVMtd1TZf0Co/skyqpV2wubsrgnifQjP51O+gnGwmS5kMydpQaoEcannxRd4OCYLdkvnJoR6tOD+RMjMJuu1l9M52KzLaY3xT5gdqb29wK9BmrXSEKbErNw1AIveuTaNyBxodWnx8At7kecG5yPq+Et8HkOmZZmFIssrWM55xCWKNDh65Z99t8XipYiLaeyebie8b91mxZHH/QXqkYUmkza8F87d3fr7ybthwQ1lAP4UxItoR0EuBkpysMCfutBlO6b4HQbzQa8bu9jxDFqyWDzt4Wj7nmbSvFBHaxDwqyZBu47dzfQhpBRKQJGXPAzc/qCgwoiqSYirHu0h4JfzklpvZsDqj0qUVrqiAMtOb+AE0O9iBTdPvdm4Bkun6bOl+gRC9XiNo0fhqyiO4PPZPx9hA2ZlbOKefuQqeV0RwAwrrcUmTApQR8E76i7QW2B3ODHt/cjXBFlONdjZNUAW4yja5mS3O3hFh5t+z89ENmLuqNIVtcCXCmmZIZaPz15bvMQkvKPlKr7whYRnsgcVLOuRdJYp+CKR/GfTmy5xZm+O8wwRP0Tbbq9hBMGgGePJI+iTBZWeef1LIPmEWI1lQNu+w+lwNE2ulK/deyKqpRVJsEFSSFZBs6+10mf0yTmnSwXRNgUqggxx5QJDpooBPAndOip+tzt
1=o47sZ3EAeSEDoncpRtAmEiyPRoIUjfmRs56Svt+KvatMp5n6C4Of5KcJ1XvyMJtuo5gnQtc1aNx4cPxyEqi0QUw3JNORyG2oQF3aM0JKT36XiBtkCMtN0/XBjMCQmp9XSbT//0RIcE8Qp1+9iIW1mzcGV8RJfWaYeqSbqoxHiJgkmmc/AjoA00EsftBeuqiE+hVxIIdkcO7Qw6GFLRlHWhfZrFitNgUSI2bp17gu5JM9cvJ3/alkREyA4Pmg2aYx2VKXpl/CSRJMjRoIMNz9HqC+Ihd8VxbdQbofswO7px/Xjv8FEus7KtFqIodylzqFiGe2XbXdPMTMtAqGuLSi2lTSNzejYbs6HNmM/BCZuzGRf21fmimxyN2CRlIVWX8modBtVUoKrQnkwZEgEep3dYdWkYdH01ZCKIerXOvOM5yXG1d9bcCb37GUngUoMaCc+npg/NpDWErYFHZ0vXZF6EO5/Wio1s+TKtKwDQKK3j8Km9y5Cxz/RIXnQ1IzjdC7lhp6a/JwRWQe72BMWs13vgEWWcczWJn8wlzk9TYRrBCN0eeMd0HL1PuXuNYFopGOneNQ87O6kmLe99CKdEMXMQfSITXRbknanAS6enS+BHex/u2xl26dvFqwQV9+K5SmwSYlrfup8FjpsFsON03om7en0DuZ1mlpQRErVIFQTAXF/Q3ljlWHqMoA/q37/BP7LyTSCCDxLxhzPEsulLYQvRQNTjy6DqpNm147Ee2V4cgJuzDnxH3auzi/a10r1ymMfPgt40R2AfsnKSjkk/Iv96PglqdUfKG/c0IG9z21cygmzuXK6WXdq57eJwESWhZp8uQZ33VlXdkQikSDyRpRyAiZ0JVs8ZdR5EsNyqKz4Y2wCIejYigOAmWDgm85hcyqmx4aBj720z6PbROdDadrCYkbQAPHjsdqRe3E/S6bOFAFGHV/MQ5AGomXPAUzMbPRPnqqOD/wwZoRxrfoD581jDh2D1RGADAKNc2CCdxLKOR+AHUHRlUUy78AuVMI7uA3PdgxDCIYq8i75szD8GK6PUm4mTaOhgS/hYNfIY16DO2NlOVd6UZ4melhZ2eGLBQLy5Hjsum4BjEsN6Lu7QnmpgpMe6zpzcmVi8TGusHrukc7rfU7LDQU64oYB7aghWcULzrtFHWIcFaXzEWlmvHUYhwzs8BlI5kSx6ailpTQcB2ZM3U7SWsr73msESBuU7ygJrwE1T91PrgKs7aZJVPO9cQvdlR315Zz1EkOG0rcwgo2i+qT2chx5ctqfGPJDQH7Py3w+wKVCFB3LZDH2NHJhjAxu3tTsCVz8bSAEgk0+88MA9+84FuRB+1akU6MpyzgdgCVxYARPTXGB1H8FTRkPLXUcp8F1ich+xKnoX4oG9lAE58fB4flJlTF0plXvWFZdl18qAjrQYjE01TmH7Xdo4zSs1uvkBChN/Wb3JhaMnTkCQSNkY0qwLtOhQgxfIoABi4guDTpVPP7UCEKRcYSpu4qlXqdIvieqerT8CjcVREugvHX2asLkonz53xIscO6LI6edrH2Jyby6CBWaQSnxY6geCknJkyKORngDzJZUp3Ovvw6Gyw88GDCRtML+OIfFLrL9j1kXR5gW18FXVzwuC9PNBTZZzPS3bOzRVep3QZYRHIXwOdHEw/wWB1ecEkzsfx8uAkRlU5/U9FC5aDVjm51PcX+7nz8P79ffr4Zm/P3+7OhzaNJt/XnT+2fpF+7P56yb0fwHehJdceJzTdM/PT89Jdc4oys9NjTe30DPQM7Y0MNGzNI+PCHCNd8vMSdULTi7KLChhGAXDELCLQ2gxQezy887c+8nABAD2rhEDIl1THQEAAAACAAAARQAAABYRAAAAAAAAAQAAAAAAAAAAAAAA

For WimBuilder2 is like:

use lastest version [Normal User]:
Just put downloaded 78.0.3904.97_chrome_installer.exe into vendor\Chrome\ folder with:
Code: [Select]
78.0.3904.97_chrome_installer_x64.exe
78.0.3904.97_chrome_installer_x86.exe

Or (Auto Download)

Code: [Select]
set SetupURL=https://dl.google.com/release2/chrome/Z4qsd_C-892jH1fG88zAOg_78.0.3904.97/78.0.3904.97_chrome_installer.exe
set SetupURLx64=https://dl.google.com/release2/chrome/APxmP00ERnxueB1YewL8360_78.0.3904.97/78.0.3904.97_chrome_installer.exe

select version on UI(define new version) [Practised User]:
Quote
  "versions":{
    "78.0.3904.97": {"alias":"latest", "x64": "APxmP00ERnxueB1YewL8360", "x86" : "Z4qsd_C-892jH1fG88zAOg"},
    "77.0.3865.75": {"x64": "DwRvDRtUADLGWiTxTGOE6A", "x86" : "ALZQVEfNiq-Fl8VbcSwmquI"},
    ...
  }


WimBuilder2's design roadmap is off topic, I will remove them if someone PM me. (Those words come out on the topic, I wrote for recording it.)

Also this update design could be done with WinBuilder's script,    if someone need simple way, he/her can try to make a plugin like this.
Title: Re: Converting script between PESE and XPE
Post by: James on November 24, 2019, 03:30:30 AM
Slore, Thanks for clarifying why all this has come into fruition...
Title: Re: Converting script between PESE and XPE
Post by: slore on November 24, 2019, 04:35:03 AM
Quote from: James on November 24, 2019, 03:30:30 AM
Slore, Thanks for clarifying why all this has come into fruition...

Well, As I said, WimBuilder2 won't use the *.Script desgin. It is not usefull for me,
But someone needs some plugins to WIN10XPE, so there was PESE2XPE, the other side, there was XPE2PESE.
There would be XPE2PEBakery, later.

That is nature. Because NONE of the exsting Project can be complate alternate for others for now.
Lancelot did some work, make *.script be out-of-box, can be used into ANY project, It is good work,
For you gays who just focus on WIN10XPE project, it is not usefull for you.

YOU should know:
WIN10XPE can't full instead of WIN10 PE SE, Re:WIN10XPE can't full instead of WIN10XPE, ...

Like you ported Printer, MTP support from WimBuilder2, some one need RNDIS later, they may also do that, too.
But port to diffierent syntax, need some time for someone.If there is  a plugin that, can let XPE project use WimBuilder2's main.bat,
I think it is good for others, like sharp, Jon_2030. Not everyone is script developer, they can't port it in right to XPE.
(Well, actually They can build PE with WIN10XPE project first, then use WIN10XPE's boot.wim as the base wim, use WimBuilder2 to add the single feature to WIN10XPE.iso\sources\boot.wim.)

Even you. You needn't have to update the ported script with update main.bat.
(Device and Printers.script [2019-9-30]can't work for RS5 and later, unless you update it with my _printer.bat [2019-11-11], and it will work for v1903, v1909, 20H1 source to get the working Printers.)

Actually, It is very easy for me, to make Batch2XPE, let WIN10XPE use WimBuilder2's macros, patches without modify it.
But I don't have strong desire that make everything in ONE project.

I can use WimBuilder2 to build the core features, and use WIN10XPE or WIN10PESE project to add the "Apps".
Combine them to build PE.

Title: Re: Converting script between PESE and XPE
Post by: Lancelot on November 24, 2019, 06:27:40 AM
Hi APT,

Most (not all) plugins converted to xpe with James / KYHI name on it deleting my name Lancelot and other names.
It is the subject of "Fabricated Incompatibility" topic http://theoven.org/index.php?topic=2697
Idea: Fabricate an incompatibility to create an excuse to delete names on plugins during conversion.

From end-user side , free things without pay always good,
 One can take neighour's car adding the one name on it,
   and friends of the one do not care as long as they have good times driving that car.

Anyway, such comments like yours belongs to
"Fabricated Incompatibility" topic http://theoven.org/index.php?topic=2697

Further post such things there.

:turtle:

Title: Re: Converting script between PESE and XPE
Post by: Lancelot on November 24, 2019, 06:58:06 AM
Hi James,

Meaningless Fabricated Incompatibility with syntax AND folder structure discussed last year. EOD (End of Discussion)
eg.
I had already written "MyPlugins" "MoPlugins" create troubles and break many things, they should be "MyXPEPlugins"
and things with other folders, etc. etc.

All ignored with your support. :thumbsup:

So it is meaningless following your folder things today,
 Fabricated Incompatibility folder structure already break many things (180 degree)
   Today I create package following this Fabricated Incompatibility folder structure without asking anything,
     now you ask some other folder structure  (180 degree)
       Come on, you like to draw circles, I do not.  :lol:

Quote from: James on November 24, 2019, 01:32:59 AM
A little more then 200 lines of code required it seems....
No, less than 200, you post without count.

First plugin with 104 lines is only a start that add compatible variables avoiding fabricated incompatiblity
If you do not count 104, number below 100.

The reason RoyM and Sandy need more than 200 lines, they create RoyM-Macro and Sandy-Macro
 I use Macro Library where universal syntax works out of the box without new lines.

It is only surprising someone (Sandy) write this solution after a year, which was already there for everyone and I had written around topics.
 Nobody reads.  :wink:


Quote from: James on November 24, 2019, 03:30:30 AM
Slore, Thanks for clarifying why all this has come into fruition...
No, you intentionally black propaganda what is written.
 Macro Library and Plugins designed to work with other projects much before slore, even before ChrisR around,
  ~9 years ago I was building with UBCDWin and BartPE builder using Macro Library.

The package proves this to the one who likes to see the truth.
 Still not all like to see the truth, Human nature or Hidden Agenda,
  There are still people on earth saying the earth is flat   :lol: :lol:

Fruition came last year with Fabricated Incompatibility,
 I already wrote last year and recently, similar to the above package already created last year.
  This is very old news.

Last year I only figure out,
 Fabricated Incompatibility is intentional and only serves to an excuse to delete author of plugins during conversion,
   which at last I understand why all this has come into fruition at "Fabricated Incompatibility" topic http://theoven.org/index.php?topic=2697


Please post such things out of topics like current topic where things related to development discussed,
 eg. use an existing topic  "Fabricated Incompatibility" topic http://theoven.org/index.php?topic=2697

So normal people can have real development posts or attachments.
 (Knowing you for years, I know you intentionally jump to such topics to stop things like that, but I will not tolerate that further)

:turtle:
Title: Re: Converting script between PESE and XPE
Post by: Lancelot on November 24, 2019, 07:40:04 AM
Hi slore,

Quote from: slore on November 24, 2019, 03:02:23 AM
This is new thing. I'm glad to see it. Lancelot  :thumbsup:
Not new, I had written related things last year but do not publish,
 expecting others to follow like you on some of your posts.
  eg. Slore reply 5 http://theoven.org/index.php?topic=1863.msg35469#msg35469
   you show the path with a post but you do not provide any plugin or xpeplugin.

The only difference is, I got tired to see same conversion posts again and again,
 I only provide a simple package to demonstrate all working fine without conversion.

Package is more like MS decide to change %windir% to %Gwindir% with 21H1 with a fabricated excuse,
and you only add Set %windir%=%Gwindir% to the top of your cmd to get your patches work instead of converting to xpepatch with %Gwindir%  :lol:

Method used here is NOT the one I use at home for WimBuilder2 and LiveSystemPro, naturally, similarities exists anyway but much better organized.

I hope I can find to finish the development and publish at the end of this summer. I am sure both WimBuilder2 and LiveSystemPro (+ some others) benefit from using plugins, and developers will have more time to focus on core development. (eg. Printer, MTP, future win distribution support etc.)

*
Before you were around, we initially create the current forum to avoid rewriting plugins again and again forced by builders or projects.
eg. PEBakery topic - http://theoven.org/index.php?topic=2958.0
eg. WinBuilder - ... you will find similar post games on winbuilder discussion topics about incompatibility like at PEBakery topic.
----- Peter (author of winbuilder) was doing quite the same with James following fabricated incompatibility on builder side to re-create scripts with his name on it. James things are not new to us.
eg. Incompatible projects that require rewrite the same plugins. (In the past giving example plugin written for Win7PESE not work with Win10PESE, not work with Gena --- but as you see all work today with same plugin)

In the past with respect to ChrisR, I did not work on Plugin work with WimBuilder2 and LiveSystemPro, my bad mistake.
 Today I do not have free time to do such thing, but I can say %99 ready out of box.
   I feel quick test with the package self-proves this argument.  :thumbsup:

*
When I find time, I follow WimBuilder2 design roadmap, as well as LiveSystemPro and others.  :thumbsup:
 To me current important is setting saved with WimBuilder2 when closed or with a save button.

not WimBuilder2 or any other road map, but anyone can create a "batch" utility (cmdplugin.exe) to process plugins which as you know work with batch way. This will get plugins work out of box more widely. Only sharing the idea since the concept is there.

There are a lot of things to consider during project/builder development and a lot time required, I wish my best luck to you.

Keep your posts. It is always good post with people like you instead of responding to fanatics.  :thumbsup:

:turtle:
Title: Re: Converting script between PESE and XPE
Post by: Lancelot on November 24, 2019, 07:48:19 AM
Hi All,

updated package at reply 5 http://theoven.org/index.php?topic=2982.msg35499#msg35499


+
added innounp support and some other minor things.
added
"ExeProperties (ExtraBit)"
plugin to demonstrate innounp plugins work fine.

I do not have enough time or much interest to improve this package,
 further feel free to improve to better.  :thumbsup:

:turtle:
Title: Re: Converting script between PESE and XPE
Post by: RoyM on November 24, 2019, 05:34:37 PM

Thanks Lancelot, Very Nice work.
I would also like to thank everyone else involved in this subject.
This has been a great learning experience.
And I have lots of material to examine and learn from now.
Vacation is over for now, back to the real world.....

Thanks Guys.
RoyM
Title: Re: Converting script between PESE and XPE
Post by: Lancelot on November 25, 2019, 01:49:36 PM
Hi RoyM,

 :thumbsup:

A little update :
updated package at Lancelot Reply 5 http://theoven.org/index.php?topic=2982.msg35499#msg35499
Win10XPE_Plugin_Compatibility_20191225.zip (http://lancelot.theoven.org/TheOvenAttach/Win10XPE_Plugin_Compatibility_20191225.zip)

with minor things (fix-organize .lnk files, add Yomi operational, add \DownloadsY\ , simplify start compatibility )

About Downloads:

On builder UI under Win10XPE
Win10XPE\DownloadsY\
"Downloads Plugin Compatibility TOP" Plugin ----> Click Green Play Button
"Download Plugins - 1"" Plugin
 ----> Click Download button at the LEFT of \Appy\Accessibility\Zzoom_omiod
 ----> (you can Click Other Plugins Download buttons)
 ----> Click 'ReScan (Refresh) Plugins' button (Restart Button) (Green circle button on Plugin UI) ==> This will restart builder
"Downloads Plugin Compatibility END" Plugin ----> Click Green Play Button

You will see Win10XPE\Appy\Accessbility\Zzoom plugin available ;)

instruction with pictures also available here: http://theoven.org/index.php?topic=1208

+ I Add \DownloadsY\ demonstrate why .link files etc. organized that way with folders.  :wink:
 Before someone misguide about this subject again ...
  Bonus: One can download Plugins on servers easily.

I guess 4 new lines (- deleted lines probably total result = 0  :lol:), rest is copy-paste Plugins etc. files  :wink:
I hope you, sandy or anyother improve this package. Or I will see same package after a year again.  :lol:

:turtle:
Title: Re: Converting script between PESE and XPE
Post by: RoyM on March 07, 2020, 08:53:41 PM
I am posting my works as is, This is still an unfinished project.
Please use with caution, and use at your own risk.
Poorly written .scripts may trash things.
Use This on a non-critical PC, aka Tech-PC.
Just keeping the code together so that others may profit.

How to USE.
Put se2xpe.script in %BaseDir%\Projects\Tools\se2xpe.script
Put Macro_Library.script in %BaseDir%\Projects\Win10XPE\Macro_Library.script

In the plugin that you want to convert, directly under [process]
ADD NEXT 3 LINES:
Echo,".....Calling se2xpe.script",WARN
Run,%GTools%\se2xpe.script,Process
[processs]

So it will now look like This:
[process]
Echo,".....Calling se2xpe.script",WARN
Run,%GTools%\se2xpe.script,Process
[processs]

se2xpe.script runs like a wrapper, it get's called before the plugin to convert.
And just Gang replaces the variables that were meant for other projects or API's,
and makes them compatible with the builder.
It's not perfect, I had minimal time to test and code.

Ideally, se2xpe.script would parse the plugin to convert,
try to identify keywords to decide exactly which API it was written for,
and then proceed with conversions.

Have Fun.
RoyM
Title: Re: Converting script between PESE and XPE
Post by: Lancelot on March 08, 2020, 01:46:14 PM
Hi RoyM,

Aside from wrong naming  :lol:

We have Azin now
http://theoven.org/index.php?topic=3052

I can use Plugins I created for Gena via Azin, no need trouble creator conversions anymore.
Title: Re: Converting script between PESE and XPE
Post by: Malok on March 08, 2020, 05:42:45 PM
Hi Roy

Here's a couple logs from my build maybe it will give a hand.
Title: Re: Converting script between PESE and XPE
Post by: RoyM on March 08, 2020, 08:02:34 PM

Thanks Malok:

There's lots of API calls not implemented.
There's just so many of them over the years, projects, builds, etc.
Not possible to add them all in the short time that I could devote.

NOT IMPLEMENTED: Arch_Set, Arch_On, Arch_Off
[Success] SetVar - Sucessfuly changed the value of [%arch_onoff%] to: [Ignore] IF - [x86] is not equal to: [off] evaluated string: [If,#1,Equal,Off,Run,%api%,Arch_Off]
                   [Ignore] IF - [x86] is not equal to: [on] evaluated string: [If,#1,Equal,On,Run,%api%,Arch_On]
                   [Success] IF - [Failed] Run - Failed to find section [Arch_Set] in file: [%BaseDir%\Projects\Win10XPE\Macro.script]

You might solve this one by adding to se2xpe.script under [Win10xpe]
Set,Arch_On,x86
Set,Arch_Off,x64
You will have to find the API these calls came from.???
Then go see what these calls do.

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

For Add_Shortcut failures:  <-- TRY BELOW FIRST.
Try running this in codebox before building:  Run,%GTools%\se2xpe.script,API1
Notes are in se2xpe.script/[API1]
**********************************************

A43: All these variables should not be under [process/S]
 Run - Processing section: [ProcessS] From file: [%BaseDir%\Projects\MyPlugins\Apps\TEST2\a43_JGL.script]
            [Warning] Unrecognized command: [%ProgramTitle%=a43]
            [Warning] Unrecognized command: [%ProgramEXE%=A43.exe]
            [Warning] Unrecognized command: [%ProgramFolder%=a43]
            [Warning] Unrecognized command: [%SetupFile%=a43.zip]
**********************************************


@Lancelot, Yes, I am already building with Azin. (Nice Work)
 One important file was missing to make se2xpe.script work.
 It is included now, just wanted to keep all work together so others may use and play with.
 I am no longer developing this plugin, others may feel free to do so.
 It is a great learning aid.

Regards
RoyM


Title: Re: Converting script between PESE and XPE
Post by: Lancelot on March 08, 2020, 08:19:55 PM
Hi RoyM

Arch Info here:
http://theoven.org/index.php?topic=1464.0

(for now not added Arm Arm64, probably on the way in some future ;))

*
Quote from: RoyM on March 08, 2020, 08:02:34 PM
There's just so many of them over the years, projects, builds, etc.
I cut many of them over the years that can not be compatible (can not be generic)
 So Macro Library slowly become flexible and generic in passing years,
  That is the reason I can ~ quickly create Azin with Macro Library supporting Plugins out of box
    (after I cut rest of old bad designed syntax .... etc.)

So, in theory, today one can duplicate Macro Library with any other language etc. now
 (
  I had done some work for Macro_Library.cmd in the past but I do not trust cmd.exe  :wink:
    In theory, It is now possible to create
     Macro_Library.cmd for WimBuilder
     and
     Macro_Library.srt for LiveSystemPro
       That will make Plugins work out of box......
)


AND
Only informing, a lot more syntax already implemented .... with next package this week.  :wink:
It is hard to catch a moving target like "Macro Library"

So, Good luck.

:turtle: