PEBakery Test Build

I have opened a new board reserved for PEBakery discussion. See http://theoven.org/index.php?board=38.0

This sole development topic was becoming quite wieldly, to say the least.

Let me know if sub-boards would be useful, or we can just play it by ear anyway.

Regards,
Galapo.

This would make Win8PESE default build also work.

Wrong info, Win8PESE default build do not contain ShutDownPE.

Anyway, ShutDownPE at Win8PESE updated now.

Thanks Galapo,

Now we can post Request: Bug: etc. on separate topics. 

Wrong info, Win8PESE default build do not contain ShutDownPE.

Anyway, ShutDownPE at Win8PESE updated now.

Ah yes, sorry 'bout that. ShutDownPE was non-critical.

Oscar told me 8.1se also builds ok for him, but I get an error in 1-copy files (will examine more later).
10pese (obviously), 7pese, 8pese conformed ok (still like 8pese for its compactness compared to 8.1se/10pese).

My question: how will new releases of the projects be handled now?

TestBuild 20171213 released.

EDIT
TestBuild taken down because of potential license issue.
Please use beta 2 or later, sorry for inconvenience.

Changelog
- Halt command kills subprocess immediately.
- If WorkDir is specified in ShellExecute, WorkDir is added to PATH temporary.
- Set command supports add/remove of macro command.
- AddVariables adds local macro.
- Added SetMacro command to manage macro only.
- In HTML log export, write [ and ] near LogState.
- System,RefreshInterface will block until refresh is done.
- Change of interface section will be updated by System,RefreshInterface.
- Added compatibility option for FileRename/DirMove to move file and directory.
- Added PathMove, a command works like FileRename + DirMove.
- Variable and Macro's Name is restricted to regex "[a-zA-Z0-9_\(\)\.]+".
- Fix TXTReplace to treat case insensitive string.


1.
Thanks for providing board for PEBakery, Galapo.
Now we can keep things more organized.

And test plugins for new feature/bug are very useful in debugging, thanks!


2. GetParam, PackParam

Thanks for all your work on this. It is amazing!!

Here is a test plugin for the WB command PackParam. Documentation is here: http://wb.paraglidernc.com/Help/packparam.html

In WB082, these 2 commands do not work properly (thus no occurence in Win10PESE).
PEBakery can recognize section parameter bigger than 9 (Ex #10, #12), so I expect PackParam and GetParam will not be necessary in future.
Galapo, do you think this commands are still worth to implement? I will do so if you want.


3. [New] SetMacro
SetMacro command is a subset of Set command, dedicated for managing macro.

Its syntax is similar with Set.

Code: [Select]

SetMacro,<MacroName>,<MacroCommand>,[PERMANENT]

If PERMANENT flag is used, new macro will be treated as global macro.
Otherwise, new macro is effective in one plugin (local macro).

Placing NIL in MacroCommand will delete command.
Notice that global macro can be only deleted with PERMANENT flag.

4. [New] PathMove
I put an compatibility ption to let FileRename/DirMove to move file and directory both.
But the command names are giving confuse, I thought adding explicit command for moving file/dir is better.
So PathMove command is introduced.

Syntax is same with FileRename/DirMove.

Code: [Select]

PathMove,<SrcPath>,<DestPath>

When compatibility option is on, FileRename / DirMove / PathMove works same.
Otherwise, FileRename is solely for file movement and DirMove is only for directory.

5. Variable and Macro Name
I restricted variable and macro's name to use only alphabet, numeric, and some special chars.
It will decrease PEBakery's potential parser error.

Code: [Select]

a-z
A-Z
0-9
_ ( ) .

(There are exceptions like %#2All%)

6. Logging Options

So it will be better if Export Log have option to ignore MacroLibrary lines.

I was also suggested about this by others.
I will try to add checkbox to let user exclue macros in LogWindow/Exporting when time permits.

7. Warning Logs

There are too many Warnings ...

When you have time, can you split some of them (and on html with Blue Info icon you use with Info ):

[FileOverWriteInfo]
[RegOverWriteInfo]

Yes, there are too many file/registry overwrite warning. I am curious why they did not appear in WinBuilder 082.

There are options:
1) Do not log overwrite as warning.
2) Fix System,ErrorOff in PEBakery and add lots of them to plugins to prevent overwrite warning.
3) Group overwrite warning to special category, like [FileOverWriteInfo] and [RegOverWriteInfo].

I am tempted to do option 1, but it can hide potential error, any ideas?

PS)
Starting from next release, let's seperate release news thread and bug thread.

Thanks ied206,
 

*

Yes, there are too many file/registry overwrite warning. I am curious why they did not appear in WinBuilder 082.

Because we could not update closed source winbuilder to give only info for
[FileOverWriteInfo]
[RegOverWriteInfo]
we update design bug of winbuilder with System,ErrorOff

Code: [Select]

IniRead,%ProjectDir%\script.project,IniVariables,NoWarnRegOverWrite,%NoWarnROW%
...
If,%NoWarnROW%,Equal,True,System,ERROROFF

IniRead,%ProjectDir%\script.project,IniVariables,NoWarnRegOverWrite,%NoWarnROW%
..
If,%NoWarnROW%,Equal,True,System,ERROROFF,4

If you want to see warnings on winbuilder build:
SE\Main Configuration -> Advanced -> Click buttons:
NoWarnRegOverWrite
NoWarnFileOverWrite
--> buttons will appear "unchecked" , than make your build.

This will create MANY warnings on wb log, which is VERY scary for Normal Users.
Keep in mind, Normal Users never use Compilers that produce warnings. 

Than we update old plugins that really use System,ErrorOff with other ways.

So shortly :
System,ErrorOff not required on PEBakery, only improvments on Log is enough. 
It will be time saver for PEBakery development.



==> Above also replies to your question:

There are options:
1) Do not log overwrite as warning.
2) Fix System,ErrorOff in PEBakery and add lots of them to plugins to prevent overwrite warning.
3) Group overwrite warning to special category, like [FileOverWriteInfo] and [RegOverWriteInfo].

I am tempted to do option 1, but it can hide potential error, any ideas?

3) solves troubles. 

-->

1) log provides special info for overwrites
but do not put log as warning, put log as info :
[FileOverWriteInfo]
[RegOverWriteInfo]

2) with [FileOverWriteInfo] [RegOverWriteInfo] -> System,ErrorOff will not be required.
( when found can be updated with other ways)



*

PS)
Starting from next release, let's seperate release news thread and bug thread.

I agree,
open a topic at:
http://theoven.org/index.php?board=38.0
Topic Subject:
PEBakery Release

After open topic, You will notice "Lock Topic" and "Set Topic Sticky" buttons at the bottom of your new topic.

<====>
This is ChrisR  way on SE Release topics.   
<====>


******
More later.....

Well, the release of the new PEBakery was more important of course, but I would like to ask again:
- How will new full releases of the projects be handled now? ChrisR is not doing them anymore, I guess...
As far as I can see, 8.1se needs a bit of work still, but after that full releases with PEBakery could happen?

I would like to ask again:
- How will new full releases of the projects be handled now? ChrisR is not doing them anymore, I guess...

You are on wrong topic :
Correct topic: http://theoven.org/index.php?topic=2300

Hi.
First I just tried PEBakery and say that I love it, it's very quick visually it's nice. I offer myself if you need to translate it into Spanish.

Second, I have wall that the script: Plugin Chef Cache does not work. I usually create Win10PE on a tablet with few resources and I use this script to make it faster. It may be because it is the first time I run PEBakery.

Third and most important. Before in BuilderSE, you could modify things in the scripts as the author image and dependencies that could be added. In PEBakery, when I hit the edit icon (Làpiz), I open notepad to see the code directly, but it will not let me edit the elements. I am doing something wrong?

Greetings and encouragement with this new tool that has a great future. 

 I open notepad to see the code directly, but it will not let me edit the elements. I am doing something wrong?

Yes, you are doing something wrong, the pencil is working fine.

When should I fully switch to PEBakery? Im assuming these changes will eventually break Winbuilder usage? I want to switch for 10PESE and know its "almost" ready but should I switch today or give it a little bit more time?

First I just tried PEBakery and say that I love it, it's very quick visually it's nice. I offer myself if you need to translate it into Spanish.

Hello teik, thanks for your offer!
PEBakery need extra work to support multilanguage, there is even no korean support even though it is my mother tongue.
I plan to support it after first stable release, so please wait for a while.

Second, I have wall that the script: Plugin Chef Cache does not work. I usually create Win10PE on a tablet with few resources and I use this script to make it faster. It may be because it is the first time I run PEBakery.

Currently PluginChefCache is disabled in PEBakery, it was done by Lancelot. After PEBakery becomes more stable, it can be enabled later.

Third and most important. Before in BuilderSE, you could modify things in the scripts as the author image and dependencies that could be added. In PEBakery, when I hit the edit icon (Làpiz), I open notepad to see the code directly, but it will not let me edit the elements. I am doing something wrong?

PEBakery does not support editing plugin interface yet, will be added later.
Until then, edit button will open code editor directly.

When should I fully switch to PEBakery? Im assuming these changes will eventually break Winbuilder usage? I want to switch for 10PESE and know its "almost" ready but should I switch today or give it a little bit more time?

Hello bob.omb, I will update PEBakery to beta after it becomes more stable and able to build PESEs correctly.
Personally I am already using PEBakery to make my personal PE build.

Third and most important. Before in BuilderSE, you could modify things in the scripts as the author image and dependencies that could be added. In PEBakery, when I hit the edit icon (Làpiz), I open notepad to see the code directly, but it will not let me edit the elements. I am doing something wrong?

PEBakery does not support editing plugin interface yet, will be added later.
Until then, edit button will open code editor directly.

Hi teik,

Tip:
After you edit a plugin and save on editor (notepad)

Click "Refreh Button" on plugin at PEBakery. (over Edit Plugin button)


*
@ied206

More later at weekend......

I like PEBakery, it's faster then BuilderSE and looks better on high resolution monitors with scaling.
I used it to create Win10PESE and it works very well after I got some issues sorted out.

Looking forward to the final version

re   PEBakery_20171216
didn't want to load up ied260's main thread with thanks, but 
 it's fixed a load of things that were giving me a real headache 

with PEBakery_20171216 build, i now get a build error at create iso stage

<Errors>
- [1] Error in Plugin [Create ISO] (Win10PESE\Finals\yy_2-iso.script)
[Error] ExtractFile - File [C:\BAKE\ISO\TI\WIM\Boot] is not a directory. (ExtractFile,%IsoScript%,Grub,memdisk,%TargetImage%\Boot)

<Plugins>
[1/1] Create ISO v80 (0.524sec)
Total 1 Plugins
repeatable even bugging create iso button

I am getting error when trying to pick shell loader.

I click PeShell and it shows "Build stopped by error", then I click Pecmd and it shows "Build stopped by error" again.

In the log it shows: [Error] Invalid URI: The URI is empty. [WebLabel_Homepg=HomePage,1,10,343,20,55,18,]

I am getting error when trying to pick shell loader.

I click PeShell and it shows "Build stopped by error", then I click Pecmd and it shows "Build stopped by error" again.

In the log it shows: [Error] Invalid URI: The URI is empty. [WebLabel_Homepg=HomePage,1,10,343,20,55,18,]

This isn't a PEBakery issue, its a bug in the shell loader plugin.
add the following line to the [Interface] section to fix it.

Code: [Select]

ExtCustomW_TextLabel="",0,1,5,164,380,32,8,Normal

- Recognize "PathSetting=False" in "script.project - [Main]" and disable path setting.

All script.project files (11) updated now ( 4+1 project + 4 MyPlugins + 1 Yomi + 1 Yomi-Gena)

Thanks for reporting Desmond,

All relevant plugins updated:

Win10PE SE\Shell\0 - Shell Loader
Win8.1 SE\Shell\0 - Pecmd Loader
Win8PE SE\Shell\0 - Shell Loader
Win7PE SE\Shell\0 - Shell Loader

Tip:

Tip:
After you edit a plugin and save on editor (notepad)

Click "Refresh Plugin Button" on the plugin at PEBakery. (over Edit Plugin button)

Same valid when you download new plugin for now.

After you download a new plugin,

Click "Refresh Plugin Button" on the plugin at PEBakery. (Right - Top : over Edit Plugin button (pencil))

ps:
"Refresh Plugin Button" will not be required for Download and Later for Edit with some future PEBakery version ...