Win10XPE Project General Discussions

Hi James
opening same project with PEBakery, all the new apps display OK, closing it and reopen with BuilderSE (Win10XPE.exe) problem exists.
Once corrected via BuilderSE editor it's fine after multiple re-opening

There was a question about an attempt to Create Plugin Creator For PEBakery..
I know JohnC has used C'T Magazine's Spin-off version of XPE and with distributed PEBakery..

So Not Sure.. What is happening with Here..

 

Sorry about that. I‘ve testet my uploaded plugins only with the pebakery builder and there were no errors.
Can you delete my uploaded plugins please?

Sorry John, No Moderation..
But You Can Delete Attachment...

Special Care was taken with Plugin Creator (which has evolved over time) and XPE WinBuilder project to be PEBakery compatible...

Thus if Creating PEBakery Plugins - TYPE=PEBakery
As PEBakery Editor not backwards compatible...

And PEBakery is Topic in another forum board...

Are all 7 plugins broken?
The incorrect username can be fixed by myself, but only tomorrow.

Hi

As PEBakery Editor not backwards compatible...

see http://theoven.org/index.php?topic=2651.msg29463#msg29463

Are all 7 plugins broken?
The incorrect username can be fixed by myself, but only tomorrow.

None of the Plugins Work with XPE as released...
None of the Plugins where tested with XPE as released...

Again, PEBakery is another topic and has it's own Board....

@ JohnC

HWinfo is already a XPE project plugin

Your Other 6 Plugins where Edited For XPE Release

Are all 7 plugins broken?

Hi JohnC,

change your encode settings to Ascii (or ANSI) on the text editor you use. 

Hi Lancelot

from what I can see from JohnC's original 7z files that I downloaded yesterday, they all seem to be encoded in ANSI already
Regards APT

Hi Lancelot

from what I can see from JohnC's original 7z files that I downloaded yesterday, they all seem to be encoded in ANSI already
Regards APT

HWInfo XPE-Plugin - System Information and Diagnostics


https://my.pcloud.com/publink/show?code=XZ12mg7ZnMpJS5BAsspe8opftANYvjjf8AMV

Check
HWinfo_XPE_File
with hexeditor
 See things before after [main]
I just re check with phone ;)

Tip:
Open HWinfo_XPE_File with notepad
Change Encoding to ASCII or ANSI or  ASCII/ANSI  (depends on txt editor gui ..)
Save
-->
This should fix.

*
It is known since first day of PEBakery and LiveSystemPro , nothing new.
I am the one who ask developers of PEBakery and LiveSystemPro to support utf unicode etc. when they first start developing their builders. 

Hi Lancelot

my apologies, you're correct, my haste in not checking them all
GPU-Z_XPE_File.Script
HWinfo_XPE_File.Script
HWMonitor_XPE_File.Script
WinContig_XPE.Script
WinContig_XPE_File.Script
WinSCP_XPE.Script
WinSCP_XPE_File.Script
are indeed UTF-8-BOM encoded, the remaining ones in ANSI

Hi @all.

Thanks for the massive feedback.

I‘m not a programmer.
I  did not realize that there are such problems   between the builders. I just created the plugins with the XPE Packed Plugin Creator and most of them worked for me.
I did not think about the text coding.
My thought was that if the plugins work with pebakery, they will work with win10xpe as well.
I wil test this in the future.

My thought was that if the plugins work with pebakery, they will work with win10xpe as well.

It is opposite.
If XPEPlugins works with Win10XPE (and Plugins with BuilderSE) they should work with PEBakery !*
If not it is PEBakery bug or design trouble or options required or .....
  whatever issue would be all about PEBakery, not related to Win10XPE or other projects around.

Shortly:
To keep on safe side, use Win10XPE.exe on Win10XPE. 
After Everything works fine with Win10XPE.exe on Win10XPE , you can test with PEBakery.

To keep on safe side, use Win10XPE.exe on Win10XPE. 
After Everything works fine with Win10XPE.exe on Win10XPE , you can test with PEBakery.


[/quote]

Thanks. Yes, I will do so in the future

John,
If you would Edit your XPE Plugin Posts attaching the edited plugins..
That would be great...

Hi Lancelot

my apologies, you're correct, my haste in not checking them all
GPU-Z_XPE_File.Script
HWinfo_XPE_File.Script
HWMonitor_XPE_File.Script
WinContig_XPE.Script
WinContig_XPE_File.Script
WinSCP_XPE.Script
WinSCP_XPE_File.Script
are indeed UTF-8-BOM encoded, the remaining ones in ANSI

To have compatibility with a WinBuilder, PEBakery must not write UTF-8 BOM to new text files.
If it doesn't, then it is a PEBakery's bug. I am looking though the issue, and will report to the forum ASAP.

My thought was that if the plugins work with pebakery, they will work with win10xpe as well.

Disclaimer: I started the PEBakery builder.

PEBakery's additional features are usually disabled with compatibility options because they aren't available on WinBuilder.
But sometimes PEBakery can behave differently from WinBuilder, mostly due to my mistake.
Until PEBakery v1.0 release (where most of the bug will be squashed), it is safer to use WinBuilder for now.

Congrat for Win10XPE Optional Member Plugins topic, great work
I have a little time now and early next week, I'll try to update with a new package (Already started)

Fixed the ImgBurn FileCopy oversight...

After creating a group of x86 Packed Plugin..

I updated and verified the [PluginSetx64] Process
History Change on Both Creators - Date: 2018.11.30

http://theoven.org/index.php?topic=2607.msg28490#msg28490

New AOMEI Backupper_XPE Auto-Update plugin to avoid the very long innounp extraction.
On an empty container:
Backupper.exe is downloaded and extracted with Innounp @Listfiles (only the needed files)
Folders (Backupper, Drivers x64/x86) are reorganized and files with comma are renamed.
The folders are packed in 7z and encoded in the container file.

Then the process is classic same as the Packed plugins and it is really much faster.
It's just a little long the first time to load the container.

I put it here for not to disturb the other plugin with the same name. I'll let you look at James.

 AOMEI Backupper_XPE.7z (29.13 kB - downloaded 53 times.)

Thank you for your feedback