Win10XPE Project General Discussions

Looking At MouseKey Plugin From Latest Release Package.
Such An Issue Was Not Found..

Im pretty sure i did not mess with the code. Regardless thats what i had so just giving heads up if anyone uses PEBakery and finds the same issue.

Hi Bigbadmoshe
just checked last two XPE releases, neither have double comma in mousekey plugin for me

ps I primarily use PEBakery, so I guess I would have noticed

Hi Bigbadmoshe
just checked last two XPE releases, neither have double comma in mousekey plugin for me

ps I primarily use PEBakery, so I guess I would have noticed

It must be something on my side. o well.

@Chris

I'm not sure why this is happening

FileCopy - Failed to copy [%BaseDir%\Temp\XPEStartup.cmd.txt] to: [%BaseDir%\ISO_x64\XPEStartup.cmd]: The directory name is invalid.
FileCopy - Failed to copy [%BaseDir%\Temp\XPEStartup.ini.txt] to: [%BaseDir%\ISO_x64\XPEStartup.ini]: The directory name is invalid.

If i do it manually it works but on auto build always get this.

What does Download_Level=2 mean ?

[%BaseDir%\ISO_x64\XPEStartup.cmd]: The directory name is invalid.

Verify > [%BaseDir%\ISO_x64 < Exists

What does Download_Level=2 mean ?

Means the plugin is processed at a sub level

Dir exist if I do the plug-in manually it works fine.

I am also not having any luck with it actually working. All the files are there I changed my custom pecmd.ini but shortcuts not getting created and apps not launching.

hi AuraticTrance

Failed Downloading...
Aria2c return:1 - An unknown error occured.
Please Help...

this is due to the name of your folder ...

0b) Be sure your base folder is short, under "root\sub folder"

... (But > D:\Oven  < Even Better for project, because shorter name length)

FAQ - Frequently Asked Questions - Introduction - Beginner questions
http://theoven.org/index.php?topic=834.0
or
How To Guide For New Users...
http://theoven.org/index.php?topic=1666.0

ex:
C:\Oven
C:\Oven\Custom
C:\Oven\Projects
C:\Oven\Support Win10XPE dev.url
C:\Oven\Win10XPE - How To Quick Start Guide.pdf
C:\Oven\Win10XPE.exe
C:\Oven\Win10XPE.ini
C:\Oven\...

hi Bigbadmoshe

@Chris

I'm not sure why this is happening

FileCopy - Failed to copy [%BaseDir%\Temp\XPEStartup.cmd.txt] to: [%BaseDir%\ISO_x64\XPEStartup.cmd]: The directory name is invalid.
FileCopy - Failed to copy [%BaseDir%\Temp\XPEStartup.ini.txt] to: [%BaseDir%\ISO_x64\XPEStartup.ini]: The directory name is invalid.

If i do it manually it works but on auto build always get this.

try to hit Init Button ( Initialize global variables and interfaces values) ...

Hi cretino,

better use desired separate folder inside package ( \Win10XPE\ ) with Win10XPE project
I mean on your post:

C:\Oven
-->
C:\Win10XPE

C:\Win10XPE\Win10XPE.exe
C:\Win10XPE\Win10XPE.ini

Win10XPE fabricated incompatibility breaks availability of all projects under same main folder.
(tutorials, faq will be updated ..... brrrr ....)
With other words:
use a separate folder with Win10XPE,
 as you already wrote in case of trouble better short, simple (ascii) and without space. eg. C:\Win10XPE   

ps: 3 months ago I had tested with spaced sub folder "C:\bla bla\Win10XPE" and working nice,
still it is always better to use a short, simple (ascii) and without space folder to avoid possible troubles like C:\Win10XPE 

I have used > D:\Win10XPE_2019-02-02 as a root path without issue
Although User Must complete one base build to populate Global Variables
The Dr Web download in question is 233 MB and was tested after report...

Using Latest PEBakery and have alway had this message

Code: [Select]

[Warning] Echo - Wimlib Cleanup and reduce Winre.wim return : -1 (Else,Echo,"Wimlib Cleanup and reduce Winre.wim return : %ExitCode%",Warn) (Line 802)

anyone have an idea?

this is due to the name of your folder ...

Thank you.. it works well now...

For Testing:

This is original from Bob.Omb. I just fixed it up a little and updated to latest version. I have personally tested it.

James please let me know if its good.

DISM++

I did not test your version of DISM++
But did notice this > Type=CodeCheckerPlugin

That was a little utility I played with for no other reason then to see if it would work...
That was never intended to be a user method..
It has been depicted from the forum for a while now...

You should update your project to reflect what has been tested and released...

I have noticed you are posting error messages that can not be confirmed - even by looking back several releases...
I have noticed you are uploading plugins with a lot of copy and paste mistakes..
I have noticed that there are file process errors in those same plugins...
I have noticed that you PM me a lot and ask advise and then choose not to follow..
I have noticed that you call me by Name in the forum as if I am the only user testing XPE.

I have noticed that you clearly write Fixed by James on your plugin topic - for which I do Not Approve
As those (Fixes) were my suggested fixes to you to Fix and learn from..
Otherwise it seems to comes off ( to me anyway ) - Like your plugin has my seal of approval

I have also told you I can not fault you for trying to learn and try new things or otherwise figure out the process we all follow...

Now for my thoughts, I think you still have a lot to learn and you seem to be getting way ahead of yourself, based on you short experience with PE
I am not a hard nose and try to help everybody, but it also becomes a little annoying to me when I see the same type of posts..
As you seem to jump around a lot and start playing and experimenting with different things - when you have not mastered the most basic of things..

That is the reason I asked you via a PM Response to upload your plugin version to this discussion topic - So as other came help you as well...

The best I can suggest to you is - Do a clean update of the project and if desired my plugin pack.
Use the utilities provided and master the plugin creation process using those utilities.

Compressed (Packed) Files are the easiest to master..

But there is a catch (as I found with your screen recorder plugin)
You also have to follow the files - as it is not always just as simple as expanding the package or manually packing the programs folder from your host...
There are other thing to consider - drivers (driver pack) - registry entries - appdata entries - programdata entries - system files - program dependencies' - etc..

This is all homework you need to do and learn in order to master a reliable plugin for distribution..

This forum is not the best for feedback, but it is a source for a lot of project related downloads..

Anyway the rest is up to you...
Enjoy!

Hi Bigbadmoshe,

I did not test your version of DISM++
But did notice this > Type=CodeCheckerPlugin

do not change Type=
change Author name
eg.
Author=Bigbadmoshe
-->
Author=Bigbadmoshe converted with CodeCheckerXPEPlugin

or whatever.
Type= value reserved for Type, such Type values you write will fail in some future....

Well use things provided with the project and available xpeplugins by mostly James. Life will be easier for you.
And so far it is a complete project and can be used for PE stuff, with a great set of xpeplugins.

Hi James,

not related to topic, but since you write here reply here :
edit: or partially related to topic.

*

That was a little utility I played with for no other reason then to see if it would work...
That was never intended to be a user method..
It has been depicted from the forum for a while now...

Well I am sure it did not work nicely but only partially.
That is the reason we do not put things to the public posts without getting ready enough.  and other methods ....
I remember you were having a big fun time at those times, I am here before summer only because I very very accidentally see "converter" word on a post. 

Anyway, learning requires experience and mistakes. 

*
Teaching things to users can be complicated ......

As far as I remember we also agree not to mix public mind by calling Win10XPE xpeplugins with the name given by you XPEplugin (Type=XPEPlugin)
Although we are at "Win10XPE Project General Discussions " topic, public miss topics and behave that way.

Years ago when I name current plugins with "Type=Plugin" name,
 First idea was naming right,
 Other idea is underlining they are compatible with only projects around here (at that times only Win7PESE and Gena),
   Big Red Line from other Type= values at that times that clearly avoid public mix mind.

Since then you can see I only use plugin name on public posts.

With Circle development (means you are naturally going to same path),
 follow the same steps to avoid public misunderstanding,
  and I will be very happy not to fix end user mind on such future posts. 

I have noticed you are uploading plugins xpeplugins with a lot of copy and paste mistakes..

I have noticed that there are file process errors in those same plugins xpeplugins...

Otherwise it seems to comes off ( to me anyway ) - Like your xpeplugins has my seal of approval

That is the reason I asked you via a PM Response to upload your plugin xpeplugin version to this discussion topic

The best I can suggest to you is - Do a clean update of the project and if desired my plugin xpeplugin pack.

Use the utilities provided and master the plugin xpeplugin creation process using those utilities.

This is all homework you need to do and learn in order to master a reliable plugin xpeplugin for distribution..

I am going to drop the subject of PESE from XPE Forum.

Thanks to you all

All,

If this post is in wrong place, please move.  This is about a few errors using some of the newly posted XPE plugins for Win10XPE.  The build doesn't error out, but when you are in PE, they have errors.

For the "WinContig" XPE plugin, when you go to launch it in PE, it gives the error that it can't load the language file from the Y drive, and then just defaults to Italian and you can't change it back to English.  Here is the error:



For the "Macrorit Disk Scanner" XPE Plugin, when you attempt to launch it in PE, it gives this error, then the program never loads after clicking OK:



For the "Macrorit Partition Extender" XPE Plugin, when you attempt to launch it in PE, it gives this error, then the program never loads after clicking OK:



Is it something I am doing wrong?  Have others tested launching these programs in PE or just to see if build fails?

For Wincontig Verify If Exist
\WinContig\Lang\WinContig_EN-US.lng

I will reply to others in a bit...