Help - Search - Members - Calendar
Full Version: WinBuilder 071 - beta version
Boot Land > Groups > WinBuilder
Pages: 1, 2, 3, 4
Nuno Brito
Hi everyone!

This topic is meant to discuss WinBuilder.exe.

Everyone is welcome to download the latest beta and post requests of features or bug support for the newer version.

To keep this topic centered on the just the executable please post any issues regarding scripts or projects on the respective sub-forums to keep things tidy and organized (except if directly related to changes introduced by a beta).. smile.gif




Beta 11 (2007-07-12)

- Syntax errors are added on log along with the full syntax used
- some bugfixings of previously added features.
- Added quick navigation buttons to allow pressing forward and backward while browsing scripts
- Modified the unattended box for running projects - also added /debug switch to help evaluate used parameters
- Main window will automatically remember and open the last selected project in winbuilder.ini
- Modified the Interface handling when scripts are executed - it was buggy under some conditions


Click to view attachment

------------------------------------------------------------------------------------------------





Beta 10b (2007-07-09)

- more bugfixes and small improvements
- Limited treeview on main window to avoid excessive width
- Added more informations when using webget
- Changed default logo image for scripts without logo
- Added new parameter on FileCopy - using "show" as last parameter will display the advance of the file copy operation.
- Fixed ExtractAndRun - wasn't working correctly.


Click to view attachment


------------------------------------------------------------------------------------------------


Beta 9 (2007-07-08)

- changed tab titles to be larger on script editor
- small bugfixes
- Added a better web server manager
- Added missing translation texts


Click to view attachment


------------------------------------------------------------------------------------------------



Beta 8 (2007-07-05)

- Overall bugfixing from latest changes
- Added the option to print the currently viewed page on the Help Manual
- Moved Create Script tab to be the first visible tool
- Removed the option to lock the interface - became obsolete


Click to view attachment



------------------------------------------------------------------------------------------------



Beta 7 (2007-06-25)

This beta jumped from 6 to 7 because of some testing in the script engine
to ensure more stable results.

change on beta 6:

- Removed an unneeded setting which always wrote a locked=true value on the [main] section
- Recoded interface, file search/filter and settings to load much faster.
- Bugfixed error message when selecting to show log after running a project.
- Replaced external download functions with internal IE download function
- Bugfixed open handles when scanning directories


changes on beta 7:

- run command can support up to 9 parameters
- Added a code box window to test new commands under a specific project


Click to view attachment


--------------------------------------------------------------------


Beta 5 (2007-06-14)

- Removed property on text labels that wouldn't allow using & chars
- corrected a bug on regwrite introduced on beta 4

-- Review B

- Corrected a bug found which caused shellexecute to run without parameters, introduced on beta 4

Click to view attachment

--------------------------------------------------------------------


Beta 4 (2007-06-11)

- Recoded script engine to improve performance
- Removed words !#2057 and !#2060
- Fixed Refresh button - wasn't updating correctly the Paths Tab
- FileDelete is now based on Win32API for code efficiency
- ShellExecute was improved to be (much) less CPU intensive while waiting for launched program to finish
- Added an error handler on the script engine - now it won't abort when invalid syntax is found.


Click to view attachment

--------------------------------------------------------------------


Beta 3 (2007-06-09)

- Scripts can be displayed without state button - useful for scripts not meant to be run (use Selected=None) on [Main] section.
- If all scripts on a folder have no state seletect (Selected = None) then the respective folder also omits any state
- Removed right-click menu from main window (became obsolete)
- Removed MD5 calculate tool from Script Edit --> Options --> Calculate MD5 checksum
- Removed language entries: !#1519,!#1520,!#1521,!#1522 related to MD5 calculate tool inside Script Edit --> Options tab.
- Added option to use wb without Download Center, Upload and Web tab for use under restricted network conditions
- Tools tab was made a bit bigger hiding the tab title
- Script Edit tab title was also hidden along with script treeview to give more room to editor
- Corrected bug which allowed to erroneously select more than one script on main window
- Corrected minimum allowed width and height for interface checkboxes
- Moved Paths and Log tab to the scripts tab
- Added a Help tab which will hold help contents about wb, it will use a html file from %basedir%\Projects\Tools\Help\index.html
- Corrected the back colors for some objects under some XP themes.
- Recoded the Create Script tab to become more functional
- Added CopyExpand command using setupapi.dll (thanks to Peter and Smiley)
- Modified ShellExecute and ShellExecuteEx to support work directories as the 4th parameter
- Modifed ShellExecute and ShellExecuteEx to work without adding parameters, ex: ShellExecute,Open,cmd.exe
- Removed "Enter" from the keyboard shortcut list (it was being trigered after exiting windows screensaver protection )
- Corrected a bug which occured when trying to echo a section with brackets


Click to view attachment




--------------------------------------------------------------------

Beta 2 (2007-05-19)

- Added /runsingle= switch which allows to run a single script

Click to view attachment


--------------------------------------------------------------------

Beta 1 (2007-05-14)

- Removed MD5 box on the options tab inside script editor (download center always checks md5 automatically)
- Added support for running projects in unnatended mode


Click to view attachment
Nuno Brito
As promissed to Peter and Alexei, the new beta already comes with support for unnatended project building.


Here's an example of command line syntax:

/run="%basedir%\Projects\LiveXP"
/source="C:\Documentos\SourceDir\Windows XP SP2 PortuguÍs"
/target="%basedir%\Target\LiveXP2"
/ISO="%basedir%\ISO\LiveXP2.iso"
/title="My Project"
/x=10
/y=50
/log="%basedir%\log_silent.html"
/showlog
/beep

This is what I use on my case - I will write more extensive details soon.

Please add only correct values on the dir paths.

run, source, target and iso are obrigatory.


Have fun! cheers.gif
psc
QUOTE(Nuno Brito @ May 14 2007, 11:57 PM) *
As promissed to Peter and Alexei, the new beta already comes with support for unnatended project building.


Here's an example of command line syntax:

/run="%basedir%\Projects\LiveXP"
/source="C:\Documentos\SourceDir\Windows XP SP2 PortuguÍs"
/target="%basedir%\Target\LiveXP2"
/ISO="%basedir%\ISO\LiveXP2.iso"
/title="My Project"
/x=10
/y=50
/log="%basedir%\log_silent.html"
/showlog /beep

This is what I use on my case - I will write more extensive details soon.

Please add only correct values on the dir paths.

run, source, target and iso are obrigatory.


Have fun! cheers.gif


thumbup.gif

Does it mean that I write a myWB.cmd like
CODE
Winbuilder /source=source1 /ISO=ISO1 /....
Winbuilder /source=source2 /ISO=ISO2 /....
...


?

I need one additional switch (usable multiple)
/Option=<script>:<section>.<key>,"<value>"
e.g.
CODE
/Option=!Fundamentals.script:Interface.pScrollBox1,"B:"
/Option=!Fundamentals.script:Interface.pScrollBox3,"RAM Drive"
/Option=RAMDisk.script:Main.Selected,"True"
  /Option=BootSDI.script:Main.Selected,"False"


Peter

EDIT: See post #5
smiley
Interesting... I have a new idea. What about batch build?
It would be the same with unattended mode but a bit more organized.
The command line should be:
CODE
Winbuilder /batch=batchfile


And the contents of batchfile should be :
CODE
[BatchRun]
Number=2

[Run-1]
run="%basedir%\Projects\LiveXP"
source="C:\Documentos\SourceDir\Windows XP SP2 PortuguÍs"
target="%basedir%\Target\LiveXP2"
ISO="%basedir%\ISO\LiveXP2.iso"
title="My Project"
x=10
y=50
log="%basedir%\log_silent.html"
showlog = true
beep = true

[Run-2]
run="%basedir%\Projects\NativePE"
source="C:\Documentos\SourceDir\Windows XP SP2"
target="%basedir%\Target\NativePE"
ISO="%basedir%\ISO\NativePE.iso"
title="NativePE"
x=10
y=50
log="%basedir%\log_silent.html"
showlog = true
beep = true


What do you think?
psc
For first, I wrote me a program setOptions (attached) which handles the options.

Syntax:
QUOTE
setOptions {/|-}O[:]<script>:<section>.<key>=<value> {/|-}P[:]<Project Dir>) [{/|-}S[:]<typ>]


It can change the components:
QUOTE
pScrollBox
pFileBox
pTextBox
pNumberBox
pCheckBox
pRadioButton


The /P switch is only necessary if <key> does not contain a valid component name.

Sample:
QUOTE
setOptions "-O:!Fundamentals.script:Interface.pScrollBox3=RAM Drive" "-P:C:\Dokumente und Einstellungen\Peter\Desktop\WB Archiv\Beta8\Projects\nativeEx_barebone"


Peter

EDIT: New version handles 'Main.Selected', too:

Click to view attachment
Alexei
@Nuno
First of all, it's just great thumbup.gif

Let's move forward smile.gif
What about having several sections, like
[download] - what to download
[settings] - what to set in scripts (input for Peter's SetOptions)
[build] - what and how to build (that's what Nuno added)
Note, the sections are very different from smiley's proposal.

cheers.gif
Alexei

PS
WB connects to www.coolwebtoys.com any idea why?
psc
The cmd line option is great!
roll1.gif
I created just a small batch file:
CODE
set BaseDir=C:\Dokumente und Einstellungen\Peter\Desktop\WB Archiv\Beta8
set setOpt=%BaseDir%\pscProgs\setOptions\setOptions.exe
set Project=%BaseDir%\Projects\nativeEx_barebone
set WB=%BaseDir%\WinBuilder071B1.exe
set WBConst=/run="%Project%" /source="V:\BCD\cds\XPP_DE_SP2" /title="My Project" /x=10 /y=50  /showlog /beep
set tg=%BaseDir%\Target\nativeEx
set iso=%BaseDir%\ISO\nativeEx
set log=%BaseDir%\log_silent

set index=STD_R_R
REM Standard ISO, RAMDisk
"%setOpt%" "-O:!Fundamentals.script:Interface.pScrollBox1=B:" "-P:%Project%"
"%setOpt%" "-O:!Fundamentals.script:Interface.pScrollBox3=RAM Drive" "-P:%Project%"
"%setOpt%" "-O:RAMDisk.script:Main.Selected=True" "-P:%Project%"
"%setOpt%" "-O:CreateISO.script:Main.Selected=True" "-P:%Project%"
"%setOpt%" "-O:BootSDI.script:Main.Selected=False" "-P:%Project%"
"%WB%" %WBConst% /target="%tg%%index%" /ISO="%iso%%index%.iso" /log="%log%%index%.html"

set index=SDI_R_R
REM BootSDI, RAMDisk, SettingsDrive = RAM Drive
"%setOpt%" "-O:!Fundamentals.script:Interface.pScrollBox3=RAM Drive" "-P:%Project%"
"%setOpt%" "-O:CreateISO.script:Main.Selected=False" "-P:%Project%"
"%setOpt%" "-O:BootSDI.script:Main.Selected=True" "-P:%Project%"
"%WB%" %WBConst% /target="%tg%%index%" /ISO="%iso%%index%.iso" /log="%log%%index%.html"


set index=SDI_R_S
REM BootSDI, RAMDisk, SettingsDrive = System Drive
"%setOpt%" "-O:!Fundamentals.script:Interface.pScrollBox3=System Drive" "-P:%Project%"
"%WB%" %WBConst% /target="%tg%%index%" /ISO="%iso%%index%.iso" /log="%log%%index%.html"

set index=SDI_N_N
REM BootSDI, no RAMDisk
"%setOpt%" "-O:!Fundamentals.script:Interface.pScrollBox1=--" "-P:%Project%"
"%setOpt%" "-O:RAMDisk.script:Main.Selected=False" "-P:%Project%"
"%WB%" %WBConst% /target="%tg%%index%" /ISO="%iso%%index%.iso" /log="%log%%index%.html"
, and I got:
  • persistent ISO
  • persistent Target directory
  • persistent log file
for
  • Standard ISO
  • BootSDI ISO with RAM disk and settings on RAM disk
  • BootSDI ISO with RAM disk and settings on system disk
  • BootSDI ISO without RAM disk.
Next I'm going to write 'parent' batches for
  • OS
  • language
Then I have everything I wanted to have in my primary suggestion to do 'universal' tests.

Thanks, Nuno thumbsup.gif

Peter
Nuno Brito
Sorry for the short description of syntax - I've been a bit short in time and was just online long enough to upload the beta.

Still missing to add errorlevels for winbuilder.exe whenever errors are outputed while running a project.

By default there is only support for english language (faster) - but I can add normal language translation if needed.


It is possible to add a list of locations (projects) like the one specified on a /run=

Alexei, what do you mean by a [download] section? Is it something like the download center where it would download based on a selected download profile/webserver?

coolwebtoys is the service that provides the chat box - you can click on the chat link on the top of this page to view the chat window straight from their site.

We could also host our own chat, but it's wiser this way to have an alternative external way to comunicate on those times when boot-land.net gets offline for some reason.


Smiley - will try to add an answer file similar to the one you've proposed.. smile.gif

psc
QUOTE(Nuno Brito @ May 15 2007, 06:37 PM) *
Smiley - will try to add an answer file similar to the one you've proposed.. smile.gif

If you have a look here, everything can be done by a small batch.
It is not necessary to extend WinBuilder to a development IDE.

Peter

BTW: The only thing I'm missing is the ability to have a /runsingle.
If we have it, I can load different constellations by WBManager and then create the ISO with this constellation.
Of course it is already possible with my script, but that takes a long tome to write all the 'setOptions' statements.
Nuno Brito
/runsingle would also have to specify a /run= switch so that it could run script.project [variables] and [process] sections, otherwise it would output different results from the main window..

smile.gif
psc
QUOTE(Nuno Brito @ May 15 2007, 08:17 PM) *
/runsingle would also have to specify a /run= switch so that it could run script.project [variables] and [process] sections, otherwise it would output different results from the main window..

smile.gif


Of course. thumbup.gif
I thought that in addition to the 'Standard' switch set a /runsingle should cause something like the 'click the green play triangle' inside the open script, rather than to play the whole project.
(If different, also for my purposes it propably would not work)

Peter
euhenio
QUOTE
/run= switch so that it could run script.project [variables] and [process] sections


now needed command for exiting Winbuilder
Alexei
QUOTE(Nuno Brito @ May 15 2007, 09:37 AM) *
Alexei, what do you mean by a [download] section? Is it something like the download center where it would download based on a selected download profile/webserver?

Yes, I meant automatic invocation of download center (with specified parameters).
cheers.gif
Alexei

Ove
I have downloaded this beta, and it gives me an error that "you need to be connected to the internet to download these files".
Maybe the ping isn't working properly, or the computer I'm using connects trough a proxy or something (I don't know what influence that might have)

The thing is I can use any browser to download and view pages, even WinBuilder's internal browser.
So I think I should be able to use WinBuilder to download files from the internet (scripts)
Nuno Brito
Hi Ove!

We've been discussing this for some time since the last beta topic (069) - proxy support is very limited and you can try to add your account configuration on the download center - press the "Options" and fill your proxy details to see how it works.

Please let me know if you are indeed using a proxy and if this is your case I would like to know what protocol it is using (direct http, SOCKS, etc..) if possible..

Thanks! smile.gif
Ove
QUOTE(Nuno Brito @ May 17 2007, 11:49 AM) *
Hi Ove!

We've been discussing this for some time since the last beta topic (069) - proxy support is very limited and you can try to add your account configuration on the download center - press the "Options" and fill your proxy details to see how it works.

Please let me know if you are indeed using a proxy and if this is your case I would like to know what protocol it is using (direct http, SOCKS, etc..) if possible..

Thanks! smile.gif


I'm sorry I can't do that. I don't have internet at home and the computer that WinBuilder didn't want to download was a computer at school. I don't know the proxy for that computer so I can't post it.
Isn't there a way of making it work the same way that IE downloads files? IE works, Firefox works, Opera works, but WinBuilder doesn't
Nuno Brito
Yes, there is a way to add try to copy the values from IE - I will try to implement it.. smile.gif
Nuno Brito
A new beta was uploaded, this time the changes were only done on the command line switches allowing to simply run a single script instead of the whole project.

smile.gif
TheHive
Suggestion.
When download scripts for project if there is an error message of failed download or something of that nature can there be added a place where it will place that message so that we can post it in the authors thread so that he can know the error or error when trying to download a project.

If you download only one project. For this example NativePE for testing.
You download no other project because you deselected it. When the downloading is finished.
No project shows up.
Alexei
QUOTE(TheHive @ May 28 2007, 01:33 PM) *
Suggestion.
When download scripts for project if there is an error message of failed download or something of that nature can there be added a place where it will place that message so that we can post it in the authors thread so that he can know the error or error when trying to download a project.

If you download only one project. For this example NativePE for testing.
You download no other project because you deselected it. When the downloading is finished.
No project shows up.

Good idea thumbsup.gif
However, why limit log to downloads? It may be useful if WB would be able to log whole "session" (in a separate log file).
Something like:
- WB started <date time>
- WB parameters <parameters>
- Download <name> <date time>
- download successful <bytes> <date time>
- Build paroject <name> <date time>
- Build ended <number of errors> <number of warnings> <date time>
- WB ended <date time>
It should be WB setting that defines log level (from "No" to "Complete").
cheers.gif
Alexei
psc
QUOTE(Nuno Brito @ May 19 2007, 03:02 PM) *
A new beta was uploaded, this time the changes were only done on the command line switches allowing to simply run a single script instead of the whole project.

smile.gif

@Nuno
You seem to be back. I hope with the health of your wife is everything ok again.

Can you please give a sample how to run a single script?
I tried a lot of syntax combinations, but all of them w/o success frusty.gif

What I finally want to do in a batch:
  • Change the configuration name (pScrollBox1) in WBManager (I can do by setOptions)
  • Run WBManager[Restore-Set] to load the new configuration (I cannot do)
  • Run the complete project to make a new ISO (I can do)
Peter
Nuno Brito
blink.gif !

Sorry Peter - thanks for pointing this gap, guess it's been a bit harder to focus lately and I've forgot to mention the syntax which is simple but should still be explained.

You can use the same command line you use to run the project as before, but you should add /runsingle=myDemo.script

Where myDemo.script represents the script and relative path counting from the project folder.

Using as example qemu you should add /runsingle=Finish\qEmu.Script

Hope you find this syntax logic to use - there's still some code needed to optimize. When only a single script is ran it is not needed to scan the projects folder and classify all found scripts, next betas should be "smarter" and just run the specified script making start-up much faster.

smile.gif


ps: Alexei, I will try to work on the log later, your idea is good! thumbsup.gif




Nuno Brito
A new beta was uploaded and is available for download on the first post.. smile.gif

Here's the detailed log of changes:
QUOTE
- Scripts can be displayed without state button - useful for scripts not meant to be run (use Selected=None) on [Main] section.
- If all scripts on a folder have no state seletect (Selected = None) then the respective folder also omits any state
- Removed right-click menu from main window (became obsolete)
- Removed MD5 calculate tool from Script Edit --> Options --> Calculate MD5 checksum
- Removed language entries: !#1519,!#1520,!#1521,!#1522 related to MD5 calculate tool inside Script Edit --> Options tab.
- Added option to use wb without Download Center, Upload and Web tab for use under restricted network conditions
- Tools tab was made a bit bigger hiding the tab title
- Script Edit tab title was also hidden along with script treeview to give more room to editor
- Corrected bug which allowed to erroneously select more than one script on main window
- Corrected minimum allowed width and height for interface checkboxes
- Moved Paths and Log tab to the scripts tab
- Added a Help tab which will hold help contents about wb, it will use a html file from %basedir%\Projects\Tools\Help\index.html
- Corrected the back colors for some objects under some XP themes.
- Recoded the Create Script tab to become more functional
- Added CopyExpand command using setupapi.dll (thanks to Peter and Smiley)
- Modified ShellExecute and ShellExecuteEx to support work directories as the 4th parameter
- Modifed ShellExecute and ShellExecuteEx to work without adding parameters, ex: ShellExecute,Open,cmd.exe
- Removed "Enter" from the keyboard shortcut list (it was being trigered after exiting windows screensaver protection )
- Corrected a bug which occured when trying to echo a section with brackets




A lot of bugfixes and changes were made on this beta - most of them regarding some visual aspects so I will try to explain them the best I can in a resumed way.

- Scripts can be listed on the main window without having a enable or disable state. As mentioned on the log of changes, all you need to do is using the Selected = None value to remove the script checkbox. I thought this would be particulary usefull for those tools which aren't meant to be run but are handy to be listed. If all scripts on a folder have no state, then the folder itself won't have a state checkbox.

- Right click from main window was removed because it wasn't used anymore - the same applies for the enter key which caused some buggy behavior when the computer left the screensaver.

- Removed MD5 single check from the script editor tab because it was also a bit redundant and not a very usefull feature.

- Added CopyOrExpand command by request of Smiley and help from Peter, hope this new function can help extracting those cabbed files since it seems much faster that the current expand command which is based on extract.exe



- wb can now work separated from network connectivity - you can select to use or not the download center, ftp upload and web tabs. This was requested to allow wb work better under x64 OS's and machines with heavy security policies.

- Proxy support was removed, I am working on direct integration with IE but there is still some coding left to learn before it can completely replace the present download components. When it's finished it should work without need to configure any proxies at all.

- Paths and Log tabs are now next to the script itself. This seems a more logical organization and had been requested some time ago, I finally managed to find a simple solution wich seems to fit nice enough in a smaller space.

- A few bugfixes were done on the script engine and shellexecute can also select which folder it will use as work dir.


--------------------------------

New tools:

Important to say that a builtin help system is being implemented inside wb. It is going to be based on html pages to ensure that anyone can edit or add new pages, and it's placed under the tools folder to ensure that the download center can update it immediatelly by script developers with acess to the update servers.

You can test it on this beta, all that is required to do:

- Create a folder called Help under the Tools folder
- Place an html file named as: "index.html"

If this file is detected when wb starts up then a new tab called "Help" will appear and load this index.html page. This way I hope that this system can grow with the help of everyone and progressively contain syntax information and informations as needed.

-------------------

Create Script

The former create script tool was removed and is progressively being replaced with a more flexible way to create scripts.

Current features include the hability to browse and add code snippets onto the script that is being created. I've followed a similar method used by the help system, so a new folder is also placed inside the Tools folder.

As in the example before you can test it right away:

- Create a folder called "Templates" under "Projects\Tools" folder
- Place any .script or .txt files meant to be used as code snippet examples.

This template folders also supports subfolders to allow categories to be used, once you want to add a script just click on the arrow button to include it's contents on the new script.

I've also been testing MakeScript by Pedrole15 and started adding direct support for this program so that it can work along with this new tool.
Besides browsing text and script files, you can also include exe files wich will be executed when the user clicks on them.

When running an application from "Templates" two parameters will be added. The first parameter is the complete path of %basedir%, the second path is the location and file name of the script to be created.

Example:
QUOTE
myApp.exe c:\winbuilder c:\winbuilder\Projects\LiveXP\Apps\myNew.script


Exe files are only executed when the user adds a valid filename and location (a warning message is displayed when this information is not complete)

After the application is closed, the new script file is read from disk and it's content is displayed on the source code window for aditional changes (if required)

This is still the preliminary version - my intention is to also add a tab for attaching files and also add this template tab on the source code editor to ease posterior codings.

Another good feature would be the hability to actually merge equal sections and settings, but this might take some more time to get done.

Last but not least, html pages can also be included on this template folder and they are displayed on the description box - this can be a good resource for creating interactive pages to create scripts where the user can write customized settings or view additional informations.


--------------------------------------------

Sorry for introducing so many different things since last beta, a lot of work still has to be done, but I hope you like the changes so far.. smile.gif

psc
4 first issues with beta 3:

CODE
CopyExpand,%SourceDir%\I386\ACPI.DLL,%TargetDir%\i386\system32

brings error:
QUOTE
FileCopy - Failed to copy [V:\BCD\cds\XPP_DE_SP2\I386\ACPI.SYSC:\Dokumente#$sund#$sEinstellungen\Peter\Desktop\WB#$sArchiv\Beta8\Target\nativeEx\i386\system32\drivers] to: [\]

Systax problem of me?

Do
  • Start project build
  • Click Download tab
  • Download single file
  • Watch what happens
Do
  • Start project build
  • Choose single script
  • Click 'Edit'
  • Watch what happens
Do
  • Choose singel project
  • Click the green 'run' arrow
  • Watch what happens
To complete my remarks with some good news: I like the new designs of tabs, missing tree in edit etc. (inspite it will need some time to become familar)

Peter
Nuno Brito
Downloaded nativeEx to test your results properly and was surprised to see that your server under the minimum download level is less than 1Mb in size - Excellent!! thumbup.gif (I'm a happy dialup user..)

Only one detail: script.project from nativeEx also needs to get adjusted the download level set to minimum.

------------------------

Tested the latest nativeEx and no errors were outputed, have a look on my log at the bottom.

Haven't managed to reproduce.. mellow.gif

Will also look on the issue you've reported - thanks for the very quick testing! smile.gif
psc
QUOTE(Nuno Brito @ Jun 9 2007, 02:38 PM) *
Downloaded nativeEx to test your results properly and was surprised to see that your server under the minimum download level is less than 1Mb in size - Excellent!! thumbup.gif (I'm a happy dialup user..)

Only one detail: script.project from nativeEx also needs to get adjusted the download level set to minimum.

------------------------

Tested the latest nativeEx and no errors were outputed, have a look on my log at the bottom.

Haven't managed to reproduce.. mellow.gif

Will also look on the issue you've reported - thanks for the very quick testing! smile.gif

The issue #1 did not appear with the 'original' from the server, but with a changed version I made to test.:
Click to view attachment

Peter
smiley
thumbup.gif

Everything is perfect except tow things:
  1. The select project frame in the paths tab can now be removed
  2. The rules tab should be moved under the edit script tab. A normal user would never need to change these settings
psc
QUOTE(psc @ Jun 9 2007, 02:08 PM) *
4 first issues with beta 3:

CODE
CopyExpand,%SourceDir%\I386\ACPI.DLL,%TargetDir%\i386\system32

brings error:

Systax problem of me?

Do
  • Start project build
  • Click Download tab
  • Download single file
  • Watch what happens
Do
  • Start project build
  • Choose single script
  • Click 'Edit'
  • Watch what happens
Do
  • Choose singel project
  • Click the green 'run' arrow
  • Watch what happens
To complete my remarks with some good news: I like the new designs of tabs, missing tree in edit etc. (inspite it will need some time to become familar)

Peter

Item #1 has gone. That has been my fault.

But now there's additional new item #5:

After successful built of a project, I see:
Click to view attachment
and the Progress tab does not disappear.
To restart build is not possible. I have to restart WinBuilder before.

Peter
Nuno Brito
Peter, it might be a bug on a System command, can you please try to debug to see where it cause this error message - I'd like to reproduce this same issue on my machine and it get it solved for good.. smile.gif



QUOTE
1. The select project frame in the paths tab can now be removed


I also wanted to remove it and get some extra space to make the edit boxes a bit bigger, but then I remembered that some people made a lot of confusion when selecting a right source. At least this way I think it will be easier for newcomers to understand that each project uses it's own definitions. (along with a small description of what the project does to avoid misunderstandings)

QUOTE
2. The rules tab should be moved under the edit script tab. A normal user would never need to change these settings


I would really like to acomplish your request, but I don't think it would be an appropriate place since this is a project wide definition and scripts should only deal with their own definitions and settings. This could be considered as extra information since it allows to understand which files are supposed to exist on a valid source. Whish there was some space to place a small description on the reason why it exists in the first place but it's already too crowded, sorry.. mellow.gif



psc
QUOTE(Nuno Brito @ Jun 9 2007, 06:18 PM) *
Peter, it might be a bug on a System command, can you please try to debug to see where it cause this error message - I'd like to reproduce this same issue on my machine and it get it solved for good.. smile.gif





I also wanted to remove it and get some extra space to make the edit boxes a bit bigger, but then I remembered that some people made a lot of confusion when selecting a right source. At least this way I think it will be easier for newcomers to understand that each project uses it's own definitions. (along with a small description of what the project does to avoid misunderstandings)



I would really like to acomplish your request, but I don't think it would be an appropriate place since this is a project wide definition and scripts should only deal with their own definitions and settings. This could be considered as extra information since it allows to understand which files are supposed to exist on a valid source. Whish there was some space to place a small description on the reason why it exists in the first place but it's already too crowded, sorry.. mellow.gif


Sorry, Nuno, I'm little bit confused.
I cannot find a corresponding post to the Quotes you made.
And I also do not understand the personal answer (because I'm also do not know to which post)

Peter
Max_Real Qnx
Beta3 in this is three tab support turkish word characters punk.gif

I'm thank you very much Nuno for support & interest cheers.gif

Click to view attachment
Nuno Brito
Thank you for testing!

These are good news.. thumbsup.gif
Max_Real Qnx
QUOTE(Nuno Brito @ Jun 9 2007, 08:34 PM) *
Thank you for testing!

These are good news.. thumbsup.gif


Hi Nuno yammer.gif

But confused1.gif

http://www.boot-land.net/forums/index.php?...t=10#entry15433

Good job wink.gif
TheHive
Just by reading the updates:

QUOTE
- Create a folder called Help under the Tools folder
- Place an html file named as: "index.html"

If this file is detected when wb starts up then a new tab called "Help" will appear and load this index.html page. This way I hope that this system can grow with the help of everyone and progressively contain syntax information and informations as needed.



QUOTE
Current features include the hability to browse and add code snippets onto the script that is being created. I've followed a similar method used by the help system, so a new folder is also placed inside the Tools folder.


Excellent implementation to allow others to contribute to make it easier for people to contribute to Winbuilders growth.


QUOTE
I've also been testing MakeScript by Pedrole15 and started adding direct support for this program so that it can work along with this new tool.
Besides browsing text and script files, you can also include exe files wich will be executed when the user clicks on them.


Congrats Pedrole15.
TheHive
I like the placement of the tabs. thumbup.gif

Winbuilder comes up faster also. The previouse beta 2 was taking a long time to show up.
Nuno Brito
New beta uploaded.. smile.gif


Here are the changes since last beta:
QUOTE
- Recoded script engine to improve performance
- Removed words !#2057 and !#2060
- Fixed Refresh button - wasn't updating correctly the Paths Tab
- FileDelete is now based on Win32API for code efficiency
- ShellExecute was improved to be (much) less CPU intensive while waiting for launched program to finish
- Added an error handler on the script engine - now it won't abort when invalid syntax is found.


Worked on the issues reported since last time and discussed on some other topics, also added an error handler which won't abort the project building when it occurs and will also display a text box with faulty syntax.

Next step should be also adding this faulty command on the log box and gives the option to either continue or quit the project processing.

Also been working on the help html pages and drag and drop support for the attachements..

I'm having some doubts in properly implementing the delphi registry enumeration function - Peter, can you help on this matter? rolleyes.gif

smile.gif
smiley
QUOTE(Nuno Brito @ Jun 11 2007, 11:56 AM) *
- Recoded script engine to improve performance


I don't think that it is optimazed enough. I have encoded in a script a 30MB file. The result was that while processing the memory of winbuilder was going from 15 MB to 100 MB and agin to 15MB 10 times. If my computrer had only 256 MB ram it would REALLY suffer.

Again I think that GetPrivateProfileSection is the best solution. For example when winbuilder needs to run a section it will read only this, or when winbuilder wants to read the interface, it will read only the Interface section and not the whole file. And finally the same should be for extracting files.

While testing I found two more bugs. When I selected the script I mentioned above, the memory from 15 MB went to 100 MB and then to 54MB and took 20 seconds to build the interface

Second, while encoding this big file, winbuilder took ages to complete and couldn't react.

I did some real real tests with GetPrivateProfileSection, and my program could read the main, the interface and the process section in less than one second mellow.gif . And finally it read the section with the big encoded file in 5 sconds. What do you think?
psc
There is something extremely wrong with the Beta 4.
When I got the first troubles, I used old scripts (with Expand rather then CopyOrExpand).

Here a boot built by beta 3 (same as built with 070):
Click to view attachment
When building the same project with beta 4, during boot I saw:
Click to view attachment
And finally:
Click to view attachment

I think 'To show or not to show' of 'My Computer' is anywhere in registry.
Is registry work changed?

Peter
smiley
QUOTE(psc @ Jun 11 2007, 02:50 PM) *
I think 'To show or not to show' of 'My Computer' is anywhere in registry.
Is registry work changed?

Peter


I suspect that the default hive wasn't created properly. Can you post a log to invetigate it?
psc
QUOTE(smiley @ Jun 11 2007, 01:56 PM) *
I suspect that the default hive wasn't created properly. Can you post a log to invetigate it?


The default hive is the hive cached by nativeEx.
Therefore both builds are based on the same default hive.

Peter
smiley
QUOTE(psc @ Jun 11 2007, 03:26 PM) *
The default hive is the hive cached by nativeEx.
Therefore both builds are based on the same default hive.

Peter


Can you try a clean build?
Nuno Brito
Hi..

There was a reorganization on the script engine to optimize it - unfortunately I see that some bugs were also produced along the way.. sad.gif

The vast majority of the commands was left untouched, but here's a list of changed ones:

IF - added a separate TStringlist
ShellExecute - added the new code discussed before
FileByteExtract - added a separate TStringlist*
Strformat - added a separate TStringList*
FileDelete - is now based on the same Win32 API as DirDelete


Items with * are not properly releasing the memory after being used - I've corrected this while verifying the changes, will soon upload a small test beta for checking this behavior.

I wish you good luck debugging where is the difference in behavior from one beta to the previous - I sincerely haven't yet spotted the reason why.. mellow.gif



smiley
Nuno, what method do you use to read scripts?
did you read my post here?
psc
QUOTE(smiley @ Jun 11 2007, 02:39 PM) *
Can you try a clean build?


I did two clean builds:
  • delete Temp directory
  • delete Workbench directory
  • do the build
Beta 4: As before missing 'My Computer' etc.
Beta 3: As before showing 'My Computer' etc.

Peter
smiley
QUOTE(psc @ Jun 11 2007, 04:22 PM) *
I did two clean builds:
  • delete Temp directory
  • delete Workbench directory
  • do the build
Beta 4: As before missing 'My Computer' etc.
Beta 3: As before showing 'My Computer' etc.

Peter

Were the logs identically the same?
psc
QUOTE(smiley @ Jun 11 2007, 03:33 PM) *
Were the logs identically the same?


With beta4 many regwrites are missing. Sample:
Click to view attachment

@Nuno:
Following line is processed by beta3, but not by beta4:

Does beta4 see a syntax error?

QUOTE
RegWrite,"HKLM",0x3,"WB-Default\Software\Microsoft\Windows\CurrentVersion\Explorer\Streams\Desktop",
"Taskbar","0c","00","00","00","08","00","00","00","02","00","00","00","00","00","00","00","b0","e2","2b","d8","64","57",
"d0","11","a9","6e","00","c0","4f","d7","05","a2","22","00","1c","00","0a","10","00","00","1a","00","00","00","01","00","00",
"00","00","00","00","00","00","00","00","00","00","00","00","00","4c","00","00","00","01","14","02","00","00","00","00","00",
"c0","00","00","00","00","00","00","46","81","00","00","00","11","00","00","00","80","f3","5d","ea","f2","35","c4","01","00",
"c0","3b","92","58","35","c4","01","00","32","58","eb","f2","35","c4","01","00","00","00","00","00","00","00","00","01","00",
"00","00","00","00","00","00","00","00","00","00","00","00","00","00","53","02","14","00","1f","50","e0","4f","d0","20","ea",
"3a","69","10","a2","d8","08","00","2b","30","30","9d","19","00","2f","42","3a","5c","00","00","00","00","00","00","00","00",
"00","00","00","00","00","00","00","00","00","00","00","4c","00","31","00","00","00","00","00","a9","30","27","93","11","00",
"54","45","4d","50","00","00","20","00","03","00","04","00","ef","be","a9","30","61","92","a9","30","00","00","14","00","00",
"00","54","00","65","00","6d","00","70","00","00","00","14","00","18","00","00","00","06","00","ef","be","53","00","59","00",
"53","00","54","00","45","00","4d","00","00","00","14","00","66","00","31","00","00","00","00","00","a9","30","61","92","10",
"00","44","4f","4b","55","4d","45","7e","31","00","00","4e","00","03","00","04","00","ef","be","a9","30","61","92","a9","30",
"00","00","14","00","00","00","44","00","6f","00","6b","00","75","00","6d","00","65","00","6e","00","74","00","65","00","20",
"00","75","00","6e","00","64","00","20","00","45","00","69","00","6e","00","73","00","74","00","65","00","6c","00","6c","00",
"75","00","6e","00","67","00","65","00","6e","00","00","00","18","00","48","00","31","00","00","00","00","00","a9","30","61",
"92","10","00","44","45","46","41","55","4c","7e","31","00","00","30","00","03","00","04","00","ef","be","a9","30","61","92",
"a9","30","00","00","14","00","00","00","44","00","65","00","66","00","61","00","75","00","6c","00","74","00","20","00","55",
"00","73","00","65","00","72","00","00","00","18","00","4e","00","31","00","00","00","00","00","a9","30","19","93","10","00",
"41","4e","57","45","4e","44","7e","31","00","00","36","00","03","00","04","00","ef","be","a9","30","19","93","a9","30","00",
"00","14","00","00","00","41","00","6e","00","77","00","65","00","6e","00","64","00","75","00","6e","00","67","00","73","00",
"64","00","61","00","74","00","65","00","6e","00","00","00","18","00","42","00","31","00","00","00","00","00","a9","30","1a",
"93","10","00","4d","49","43","52","4f","53","7e","31","00","00","2a","00","03","00","04","00","ef","be","a9","30","1a","93",
"a9","30","00","00","14","00","00","00","4d","00","69","00","63","00","72","00","6f","00","73","00","6f","00","66","00","74",
"00","00","00","18","00","52","00","31","00","00","00","00","00","a9","30","1a","93","10","00","49","4e","54","45","52","4e",
"7e","31","00","00","3a","00","03","00","04","00","ef","be","a9","30","1a","93","a9","30","00","00","14","00","00","00","49",
"00","6e","00","74","00","65","00","72","00","6e","00","65","00","74","00","20","00","45","00","78","00","70","00","6c","00",
"6f","00","72","00","65","00","72","00","00","00","18","00","48","00","31","00","00","00","00","00","a9","30","1a","93","11",
"00","51","55","49","43","4b","4c","7e","31","00","00","30","00","03","00","04","00","ef","be","a9","30","1a","93","a9","30",
"00","00","14","00","00","00","51","00","75","00","69","00","63","00","6b","00","20","00","4c","00","61","00","75","00","6e",
"00","63","00","68","00","00","00","18","00","00","00","10","00","00","00","05","00","00","a0","1a","00","00","00","75","01",
"00","00","00","00","00","00","00","00","00","00","e0","06","00","00","00","00","00","00","16","00","00","00","00","00","00",
"00","00","00","00","00","16","00","00","00","00","00","00","00","01","00","00","00","01","00","00","00","aa","4f","28","68",
"48","6a","d0","11","8c","78","00","c0","4f","d9","18","b4","0c","03","00","00","e0","0c","00","00","00","00","00","00","16",
"00","00","00","00","00","00","00","00","00","00","00","16","00","00","00","00","00","00","00","01","00","00","00"


Peter
Click to view attachment
Nuno Brito
QUOTE(smiley @ Jun 11 2007, 09:09 AM) *
I don't think that it is optimized enough. I have encoded in a script a 30MB file. The result was that while processing the memory of winbuilder was going from 15 MB to 100 MB and again to 15MB 10 times. If my computer had only 256 MB ram it would REALLY suffer.


I'm testing these projects on a 256Mb laptop with the delphi IDE and Firefox open at the same - haven't tried yet with a 30Mb file but I also think it would be very inconvenient, let's hope to see this solved soon - it's not yet a priority until the script engine is back into a stable behavior.

QUOTE(smiley @ Jun 11 2007, 09:09 AM) *
I did some real real tests with GetPrivateProfileSection, and my program could read the main, the interface and the process section in less than one second mellow.gif . And finally it read the section with the big encoded file in 5 seconds. What do you think?


These sound very good results, but how long would it take on your machine to read the same script with the present wb?

As booty#1 as referred - the open and reset file seems a viable option for further expansion - not just for reading key/values from section but also to obtain all lines from a specific section or later write lines on these sections - I also prefer something that I can modify as needed.

At the moment we still need to see what makes beta 3 different from beta 4.. dry.gif
psc
QUOTE(Nuno Brito @ Jun 11 2007, 04:09 PM) *
At the moment we still need to see what makes beta 3 different from beta 4.. dry.gif


For me currently the answer seems to be:

0x3 and 0x7 writes with a list of hex numbers.
In a quick overview I found no other differences.

Peter
Nuno Brito
Can you replace these faulty hives with previously created hives and still boot your project?

I assume that at least one issue is related to the hives then.. cheers.gif
psc
QUOTE(Nuno Brito @ Jun 11 2007, 04:21 PM) *
Can you replace these faulty hives with previously created hives and still boot your project?

I do not understand what to do.

Even I use cached old hives, the following RegWrite-s fail with 0x3 and 0x7

The result is the same, if I generate the (correct) hives with beta3, do not delete them and build the project by beta4, based on the beta3 hives.

Compare my logs from post #46 and you can see all differences.

Peter
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2007 Invision Power Services, Inc.