27 replies to this topic

[alacran]

There is a new thread on MSFN about a new PE Builder project (open source) compatible with our good old WB 0.82:

 

http://www.msfn.org/...77249-pebakery/

 

Just tested it and it is very fast.

 

 PEBakery.png   136.7KB   12 downloads

alacran

[Brito]

Looks like a good tool, in the end I think that language or correctness are the least of the worries. The focus should really be more about making simpler projects that work well for end-users.

 

I would be thumbsup to open a forum section here for the new tool and help with the visibility portion (e.g. newsletters) in case the author sees interest on that possibility.

 

[Wonko the Sane]

, in the end I think that language or correctness are the least of the worries. The focus should really be more about making simpler projects that work well for end-users.

Still in denial mode, I see.

 

The end-users are (largely, of course not all of them) a mass of selfish leechers that simply press the green button, they get a .script/project written by a .script developer and run it.

 

The issue has been traditionally the difficulties that good willing .script developers had to face to write something working [1] and the initial very steep learning curve for the (anyway very few) end-users attempting to become .script developers and hopefully giving back something to the community.

 

Nothing is overly difficult or impossible, as it was demonstrated by our good friend Misty  , in his own words:

 

http://reboot.pro/to...-role/?p=205009

 

still very few people have/had a similar perseverance and dedication.

 

Wonko

 

[1] ... having something working AND actually having it written in such a way that a new, good willing padawan can actually read it, understand it and learn from it would be a plus...

[misty]

...Nothing is overly difficult or impossible, as it was demonstrated by our good friend Misty  ...

I'm actually blushing. You are too kind.

[Wonko the Sane]

I'm actually blushing. You are too kind.

Naah, I am still an old and grumpy bastard (and cheap, but this is unrelated), maybe I am softening a bit with the years passing by


Wonko

[alacran]

New version available, Source:  http://www.msfn.org/...comment=1148222

 

 

TestBuild 20171210

Download
https://drive.google...Xnk7ngxEzrIVDNs

1. BugFix
- Stop button now terminates subprocess immediately.
- Support multiline code (line end with \)
- Fix DirCopy overwrite bug when used with wildcard compatibility flag.
- When multiline code has error, CodeParser now reports correct command.
- '\' will be added to FileBox's direcotry path.
- Left plugin tree will be refreshed after refresh of plugin.
- SectionName/HideProgress is properly recognized in ComboBox.

2. Feature Add
- If,ExistRegMulti implemented.
- Escape sequence of # (##) implemented.

Thanks to all who reported unknown bugs!

EDIT
Please redownload build 20171210, a critical bug resides in ShellExecute.

 

Edited

yesterday at 07:42 AMby Joveler

 

alacran

[misty]

PEBakery updated (see here)

Build 20171216

Changelog
- Fix TXTDelLineOp optimization bug
- Fix NullReferenceException in System,RefreshInterface
- Disable System,SaveLog when logger is turned off
- Recognize "PathSetting=False" in "script.project - [Main]" and disable path setting.
- Prevent possible UI exceptions.
- "[Main] - Description=" line is no longer mandatory in plugin.
- CodeParser.GetNextArgument will not slice argument with "".
- Support legacy branch condition when compatibility option is set.
- Support 4-argument 0x7 RegWrite.
- Do not touch escape characters when setting variables.
- Ignore the plugin itself in "[Main] - Disable" directive.
It fixes a bug VMWare.script is uncheckable.
- TXTReplace will be optimized to TXTReplaceOp if condition is met.
- IniReadOp will set varible to empty string when key is not found.
- Do not escape variables imported from interface.
- Pressing Update button of LogWindow while building no longer crashes program.
- Log stdout and stderr in ShellExecute,Hide.
- Implement ShellExecute,Min.
- Implement GetParam, PackParam.
- Implement "#a" to track section parameter count.
- Allow "-" in variable name, for compatibility with Gena_Meal.
- Fix IOException in CopyOrExpand.
- Fix UIParser to recognize tooltip in TextFile

1. Update to .Net Framework 4.7.1
PEBakery uses several libraries.
Update of some library caused PEBakery to malfunction (problem with .Net Standard 2.0), so I had to update .Net Framework to 4.7.1.

2. [New] ShellExecute
ShellExecute,Min added to execute programs minimized.
ShellExecute,Hide will show and log stdout and stderr.

3. [New] parameter count token #a
To deprecate PackParam, #a token is added.
When used in command, #a denotes section parameter's number.

[misty]

And to keep things together, my feedback re PEBakery elsewhere on reboot -
 

...It seams to me for people runing Win7 (as me) or Win8.x, WB 0.82 is the best alternative for this project (MistyPE) and no need to install more than 1 GB of .NET Framework 4.7.1 just to run PEBakery.

On the other hand people runing last version of Win10 already have it into OS and then PEBakery is a very good option for them.

This is not the case if you are building a 10 PE SE on Win7, then PEBakery is very much faster than WB 0.82...

@alacran
I attempted to run PEBakery on a Windows 7 SP1 host OS after installing .NET Framework - a tremendous ammount of bloat (.NET - not PEBakery). Unfortunately this was the wrong .NET package and the program failed to run with error PEBakery has stopped working (see screenshot below) -



Same error on Windows 8.1 Update host OS. No warning about not having the wrong .NET Framework version - just the error.

Started ok on my newly installed (for testing purposes) Windows 10 host OS partition. Also now running on Windows 8.1 Update host OS after installing the correct .NET package. A warning about an incompatible version of .NET would be useful.

I haven't played around with PEBakery much due to testing recent additions to MistyPE. First impresssions - a very very promising bit of software.

Brief note on PEBakery compatibility with MistyPE - it's not working with all project scripts.

Tools > Cache Files - Option 3
This script is used to create a Cache using files copied from the host OS. Using PEBakery the script fails to copy required file dependencies to the cache. This is likely to be due to failing to redirect to the Sysnative directory. The Sysnative redirects are required in the 32-bit WinBuilder, however if PEBakery is a native 64-bit application then the current coding will fail and will need some significant changes to work in PEBakery and WinBuilder. I'm not sure how many project scripts are affected and will check this shortly.

Build time comparison with same settings -

• PEBakery - 1 minute 23 seconds
• WinBuilder - 1 minute 3 seconds

Regards,

Misty

UPDATE - Three program scripts have references to sysnative

• Core\required.files.hostos.script
• Core\syswow64.files.hostos.script
• Core\verify.script

[misty]

Just ran one of the new MistyPE package scripts and discovered the nice code "Syntax check" function built into PEBakery.

Bad code -

System,Erroroff,1,nowarn

Should read -

System,Erroroff,1

Really great feature

Misty

[misty]

Just posted in the PEBakery thread on MSFN

Found a problem in MistyPE.

If the Options 2 tab is selected in the main project script (with settings for Build Method, Keyboard Layout, etc) then the build fails. Clicking on the HELP button for Option 7] Build Method also fails.

The error appears to be due to the content of the message in the [HELP.7] section of the script. I can't actually see what code in the Message is causing the issue and am about to leave for work. Not sure if it's my code or a PEBakery issue.

Regards,

Misty

[misty]

Looks like a good tool, in the end I think that language or correctness are the least of the worries. The focus should really be more about making simpler projects that work well for end-users.

I would be thumbsup to open a forum section here for the new tool and help with the visibility portion (e.g. newsletters) in case the author sees interest on that possibility.

I have encouraged ied206 (aka Joveler) to maintain a PEBakery thread on reboot.

If he does decide to do so then please extend him a friendly reboot.pro welcome.

I fully support any discussion on PEBakery - I'm seriously impressed with ied206's work and truely excited to see how it develops over time. It would be nice if it led to a new projects here using the skills and talents of our members.

ied206 has opened threads on a number of forums including msfn, mdl and a very active PEBakery subforum on theoven.org. The developer himself remains neutral and continues to do some fantastic work.

I respectfully ask that anyone posting here at reboot do so respectfully and professionally and remain neutral about posts on any other sites.

Kind regards,

Misty

[misty]

From here - http://www.msfn.org/...77249-pebakery/

What is PEBakery?
PEBakery is a builder specialized in customizing Windows PE.
It is intended to be used with Win10PESE, MistyPE project.

Why PEBakery was written?
PEBakery is compatible with WinBuilder 082.
Projects like Win10PESE are dependent on WinBuilder 082, but WB082's development went discontinued.
PEBakery works as a drop-in replacement of WB082, while providing much improved envrionment.

Other threads -
http://theoven.org/index.php?PHPSESSID=853be47bb7131faa83127a26d9805878&board=38.0
https://forums.mydig...pebakery.75896/



Misty

[ied206]

Hello, I am a developer of PEBakery (@joveler at MSFN).

 

Although WinBuilder 082 is discontinued, it has been powering several projects.

I hope PEBakery paves an easy path for users and developers.

 

Changelog of PEBakery Build 20180103 (Beta 1).

Changelog
- [Added] ReadInterface, WriteInterface
- [Added] WimMount, WimUnmount
- [Added] ProgressBar for WebGet/WimMount/WimUnmount
- [Added] Flag GLOBAL introduced to SetMacro
- [Added] FileCopy/RegWrite produce LogState.Overwrite instead of LogState.Warning
- [Added] Print summary of warning as well as error in exported log.

- [Changed] Improved Console Output in ShellExecute,Hide.

- [Fixed] Handle negative number properly in Command 'If'.
- [Fixed] Fix hang in System,Cursor.
- [Fixed] Fix hang in UserInput,Dir.
- [Fixed] Fix crash in SettingWindow.
- [Fixed] OnPluginExit/OnBuildExit produces proper #1 argument.
- [Fixed] ShellExecute,Hide,XCOPY.exe,... now work properly on Windows 7

1. Improved Console Output in ShellExecute,Hide
PEBakery will display and log stdout and stderr as unified one output, to simulate real console print.

 

2. ReadInterface, WriteInterface
See manual for usage.

 

3. WimMount, WimUnmount
Native commands for handling wim files are being added.
WimMount and WimUnmount depends on wimgapi, and the other commands are planed to use wimlib.
See manual for usage.

 

4. ProgressBar for Current Command
PEBakery will display current progress in some commands.
Currently WebGet, WimMount, WimUnmount is supported.

 

5. FileCopy/RegWrite produce [Overwrite] log instead of [Warning] log
PEBakery was producing too much overwrite warning, making hard to find more important warnings.
So FileCopy and RegWrite will generate [Overwrite] log instead of [Warning].

 

 

EDIT

Am I unable to add a link?

Edited by ied206, 02 January 2018 - 06:14 PM.

[Wonko the Sane]

EDIT

Am I unable to add a link?

Unfortunately you cannot add that link.

 

But these will do :

https://goo.gl/yiELJf

 

http://bit.ly/2qeEqOB

 

Wonko

[Atari800XL]

Hello, I am a developer of PEBakery (@joveler at MSFN).

 

LOL... "A developer"

 

I would say: "The developer"

 

Edited by Atari800XL, 02 January 2018 - 07:53 PM.

[ied206]

LOL... "A developer"

 

I would say: "The developer"

 

Sorry for my bad english, I just missed it.

[Atari800XL]

No problem, I just liked your modesty!

I hope reboot will like PEBakery!

Edited by Atari800XL, 02 January 2018 - 08:06 PM.

[misty]

I can't speak for anyone else, however I'm loving it!

[alacran]

@ ied206

 

Wellcome, I have followed all your threads in MSFN and MDL, your project is evolving very fine and very fast, it is good to see you call it now Beta 1.      You need to have a certain number of post in order to have full capavilities for modify one of your post and to do some other things.  Anyway the forum software do not acept links to -t h e  o v e n-

[ambralivio]

Anyway the forum software do not acept links to -t h e  o v e n-

Why ?

Where is this written and described ?

[alacran]

Why ?

Where is this written and described ?

 

The answer to both is: I don't know.

But in case you don't believe me you can test this by yourself.

[misty]

In the past there was boot-land.net and many of the members got on happily reasonably well together. Then there was a (bigger) falling out and a number of members left and formed theoven.org, with reboot.pro rising like a phoenix from the ashes of the mighty boot-land.

This forum history is no doubt written somewhere. As Nuno is not one for censorship (and is in my opinion a very fair admin that we are extremely lucky to have) then the reasons are likely to be out there - written across multiple topics no doubt.

For many members this all occurred before they joined reboot.pro. I have stumbled across the odd topic with references to the history and arguments. Whilst there are others that could probably provide some more detail, dragging up the history would not serve any real purpose and would do more harm than good.

For whatever reason though, a decision was made at a senior level to restrict (block) any links to theoven. It would be nice if after all this time the restriction could be lifted, however that is not my decision to make.

Misty

[ambralivio]

The answer to both is: I don't know.

But in case you don't believe me you can test this by yourself.

 

I think that one cannot (reliably) state something for which cannot give a (minimal) explanation...

However, let's wait for some clarification from someone (more distinguished here in the forum)...

[erwan.l]

Looking at the forum settings, I can confirm these are blocked.

It is up to the moderators to decide whether or not this restriction should be taken off.

[ambralivio]

@ misty,

thanks for the clarification.

 

I completely agree with your position, as (at first sight) the restriction looks like too much despotic...