PEBakery Test Build

Hi APT,

Reply 155 http://theoven.org/index.php?topic=2271.msg25086#msg25086
Thanks for reporting,
but I could not reproduce here with default build.

Still, I try to make a fix, check latest CreateISO on the server. Let me know the result.

PS:
If failure continues (can be), give me exact step by step path to reproduce here.....
Start with the latest project from the server on an empty folder with latest PEBakery .......

Hi Lancelot

create fresh on existing fast SSD and older SSD   on win7sp1(full updates) all give same error
(multiple attempts on each in new dir's with various permutations)

1.   win10PESE from Win10PE_SE_2017-12-02.zip   MD5: 68EF10876F95BB9413DACF70B746E3D7
2.   win10PESE updated with exact&secure
3.    WB finishes build with working iso
4
5.    add PEBakery_20171216.7z   MD5: A9667BB0DD063A3E834E2C36C22F17AE
6.   consistent build error at Create ISO plugin v80   
7.       you have to delete faulty boot file (boot.wim) to continue

Apologies just found your post re v81

8.    with Create ISO plugin v81 error has changed , (i see you added folder)

  progress  -you now get a MacroLib error    see folder v81 but you get a boot.wim
   approx 630 MB(opens with 7z) in \ISO\TI\WIM\sources

P.S. still works fully all drives/folders with 
PEBakery_20171202.7z   MD5:DF81602CF1FC427B66718892DF647712
PEBakery_20171213.7z   MD5: 733EC10AA896E9F98003F483B8DA6530

various logs/pics attached

Looks like the next line is copying the file "grldr" to a *file* named "boot", instead of to a *folder* named "boot"?

Code: [Select]

FileCopy,%GlobalTemplates%\Grub4Dos\grldr,%TargetImage%\Boot

Oh, sorry, previous issue was already known and fixed in v81. Please ignore.

Let me try once more. In line 1031, I see:

Code: [Select]

TxtAddLine,%w%,"Echo ErrorLevel #$pErrorLevel#$p",Append

I guess there should be a "=" in there, like it is in ML:
(example):

Code: [Select]

TxtAddLine,%BaseDir%\Temp\Macro_Library\Start_Extended.cmd,"Echo ErrorLevel=#$pErrorLevel#$p",Append

Hi APT,

mkisof gives ErrorLevel -1 on your build.

I could not find ErrorLevel -1 meaning for mkisof yet.

Try:
Create ISO -> Create ISO Tool -> change mikisofs to oscdimage
see how things goes ?

@Atari800xl

line 1031 is correct, nothing to fix there.



Edit:
My archive notes from my old experiements says
When you close cmd window (using X at right top of cmd screen), it creates an ErrorLevel <0
But here I can not reproduce -1 case APT have.

Hi Lancelot
 tried with  oscdimage
 and it errors with 'Failed to create the ISO image with oscdimg!!! Exit code : 1'

have attached  pics of what is created in wim folder
thanks for your perserverance on this one!

Hi APT,

oscdimage Exit code : 1 should mean unable to create iso file, but this does not give a clue...

try this:

Create ISO -> Create ISO Tool -> change to mikisofs
Create ISO -> click "Create a new ISO file" button
you will get failure...
Open %ProjectTemp% folder ( .....\Temp\Win10PESE )
you will see
CreateISO_Debug.cmd
Right Click - Edit
Replace

Code: [Select]

//Pause

-->

Code: [Select]

cmd

Save and exit...

Double Click
CreateISO_Debug.cmd

See what will happen.
Window can give more info about failure.
and may give us a clue.

+
If you can not figure out, reply same test with oscdimg
 and see what will happen..

hopefully, one of them will give us reason of failure.

ps:
Be sure you have free space.
Working on SE mostly get you run out of space.

Hi Lancelot

when i doubleclick the cmd files nothing happens
have attached them anyway
but noticed an error on the adjacent logHTML.html

Code: [Select]

1 Error in Plugin [Create ISO] (Win10PESE\Finals\yy_2-iso.script)
State Message
Error Error - Command [TXTAddLine] can have [3] ~ [4] arguments (TxtAddLine,%w%,"#$q%CreateCDTool%#$q %CreateCD_Parm%")

not sure of the relevance

Hi
 it must be getting late, can't follow simple instructions now
have attached resultant output of running cmd's in  txt

but noticed an error on the adjacent logHTML.html

Code: [Select]

1 Error in Plugin [Create ISO] (Win10PESE\Finals\yy_2-iso.script)
State Message
Error Error - Command [TXTAddLine] can have [3] ~ [4] arguments (TxtAddLine,%w%,"#$q%CreateCDTool%#$q %CreateCD_Parm%")

not sure of the relevance

I see line is correct at Create ISO plugin

Code: [Select]

TxtAddLine,%w%,"#$q%CreateCDTool%#$q %CreateCD_Parm%",Append

I feel ied206 should check what is going on for such "Error - Command" on PEBakery.

Hi
 it must be getting late, can't follow simple instructions now
have attached resultant output of running cmd's in  txt

Thanks, this give more info. Missing efisys.bin !

I will download en-gb to hopefully reproduce your trouble.
Win10_1709_EnglishInternational_x64.iso
( en-gb_windows_10_multi-edition_version_1709_updated_sept_2017_x64_dvd_100090819.iso )

 Tonight or tomorrow ....

Let me try once more. In line 1031, I see:

Code: [Select]

TxtAddLine,%w%,"Echo ErrorLevel #$pErrorLevel#$p",Append

I guess there should be a "=" in there, like it is in ML:
(example):

Code: [Select]

TxtAddLine,%BaseDir%\Temp\Macro_Library\Start_Extended.cmd,"Echo ErrorLevel=#$pErrorLevel#$p",Append

Sorry, this was stupid of me... I was half asleep I guess, because I thought a variable was being set here (so the missing "=" would make sense as an error). Turns out it was just an "Echo"...

Hi APT,

I will download en-gb to hopefully reproduce your trouble.
Win10_1709_EnglishInternational_x64.iso
( en-gb_windows_10_multi-edition_version_1709_updated_sept_2017_x64_dvd_100090819.iso )

I make a quick build with PEBakery with en-gb. It works fine here.

I will check more at CreateISO plugin about missing efisys.bin ......

Hi
it's beats me, the fact that you can run BuilderSE in exactly the same folder,and it creates the ISO
rules out space/antivirus etc (although have tried with A/V off) and on my older sdd there's 100GB left.
coupled with the fact that if you remove PEBakery files from the 16th and put either
PEBakery_20171202.7z 
PEBakery_20171213.7z
the problem does not arise, and the build completes normally suggests its something that changed in PEBakery_20171216.7z
why nobody else has experienced this error beats me totally

btw a temporary workaround has just dawned on me
       if i use PEBakery without CreateISO enabled, then just run up BuilderSE and 'Create newTarget Image and ISO'
       I get a working ISO - at least it allows me to continue making my plugins PEBakery compatible

btw a temporary workaround has just dawned on me
       if i use PEBakery without CreateISO enabled, then just run up BuilderSE and 'Create newTarget Image and ISO'
       I get a working ISO - at least it allows me to continue making my plugins PEBakery compatible

Thanks for the workaround info.
So we can focus on CreateISO plugin. 
Time.....

*
Funny , I do very same with Gena to get VMware tests.
(Build with 77rc2 , test with 82 or 80 for VMware emulation plugin.. Now with PEBakery all fine )

With PEBakery we will get rid of all this mess. Continue feedback.

PS:
I updated all "Plugin Creator" plugins yesterday to avoid warning with weblabel.
They require more tests with  PEBakery when time found, besides good now with wb to create PEBakery compatible new plugins ....

Hi APT,

check your source folder:
Source -> \efi\microsoft\boot\

Do you see 2 files:
efisys.bin
efisys_noprompt.bin

*
After CreateISO with PEBakery fails:
check your target folder:
\Target\Win10PESE\efi\microsoft\boot

Do you see 2 files:
efisys.bin
efisys_noprompt.bin

?

Hi Lancelot
yes those files exist in my source and are copied to C:\BAKE\Target\Win10PESE\efi\microsoft\boot
but wouldn't they need to be, for it to work with BuilderSE and the other versions of PEBakery

With a errored build both the Wim and the Wim\Boot have missing files compared to a successful build
see attached files

Hi APT,

let's synchronize logs. Maybe we are after a bug that is related to hostos difference.

Download this Win10PESE:
https://www.dropbox.com/s/nf1nuqyvye16drh/20171221_APT_Win10PESE.7z?dl=0

+ Extract to empty folder
+ Launcher.exe
+ Config Source - Select Source
+ Build
+ After Build ends (with error)
Log -> Build Log - (Log Detail) - Export - Build_0_APT.txt

Than again
+ Build
+ After Build ends (with error)
Log -> Build Log - (Log Detail) - Export - Build_1_APT.txt

This way we will have 2 very same build logs to compare and figure out things easily.

giving example:
Here is my 2 build logs:
https://www.dropbox.com/s/splooizhavmprp5/20171221_APT_Win10PESE_Lancelot_Logs.7z?dl=0

ps:
WOW, 2 minutes 14 seconds to build Win10PESE Basic 
Thanks again ied206.
This remind me discussions about speed 8 years ago we all made.... (Yes I was again bad man)
 Nice to see we do all right way since than, proven by PEBakery.

ps:
WOW, 2 minutes 14 seconds to build Win10PESE Basic 
Thanks again ied206.
This remind me discussions about speed 8 years ago we all made.... (Yes I was again bad man)
 Nice to see we do all right way since than, proven by PEBakery.

And with ChiefPlugin Cache,
https://www.dropbox.com/s/93krqo6la4pbpk8/Build_2_Lancelot_Chief.7z?dl=0
only 51 Seconds.
Took 0:00:51 

ps: I feel we need to remove "Build Complete" Dialog (5 Seconds) which effects total build speed now
51-5 =46 Seconds
 

It will be nice to have more International users around (Russian, Korean, Chinese, French, Turkish, German...) after we have stable PEBakery.

A dream I have and work on 7 years ago (but impossible with wb) at last coming slowly true. Thanks again ied206.