Printable Version of Topic

Click here to view this topic in its original format

Boot Land _ WinBuilder _ WinBuilder 071 - beta version

Posted by: Nuno Brito May 14 2007, 09:55 PM

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


 WinBuilder071_Beta11.zip ( 821.02k ) : 139


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





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.


 WinBuilder072_Beta10b.zip ( 808.56k ) : 55



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


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


 WinBuilder071_Beta9.zip ( 807.26k ) : 90



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



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


 WinBuilder071_Beta8.zip ( 809.93k ) : 86




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



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


 WinBuilder071_Beta7.zip ( 808.73k ) : 189



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


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

 WinBuilder071_Beta5b.zip ( 805.98k ) : 165


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


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.


 WinBuilder071_Beta4.zip ( 805.95k ) : 81


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


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


 WinBuilder071_Beta3.zip ( 814.16k ) : 60





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

Beta 2 (2007-05-19)

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

 WinBuilder071_Beta2.zip ( 798.72k ) : 452



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

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


 WinBuilder071_beta1.zip ( 798.34k ) : 166


 WinBuilder071_Beta10.zip ( 808.33k ) : 52
 

Posted by: Nuno Brito May 14 2007, 09: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

Posted by: psc May 15 2007, 06:34 AM

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

Posted by: smiley May 15 2007, 07:40 AM

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?

Posted by: psc May 15 2007, 09:32 AM

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:

 setOptions.zip ( 42.62k ) : 22

Posted by: Alexei May 15 2007, 10:23 AM

@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?

Posted by: psc May 15 2007, 11:44 AM

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:forNext I'm going to write 'parent' batches forThen I have everything I wanted to have in my primary suggestion to do 'universal' tests.

Thanks, Nuno thumbsup.gif

Peter

Posted by: Nuno Brito May 15 2007, 04:37 PM

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


Posted by: psc May 15 2007, 04:47 PM

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 http://www.boot-land.net/forums/index.php?s=&showtopic=2200&view=findpost&p=14153 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.

Posted by: Nuno Brito May 15 2007, 06: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

Posted by: psc May 15 2007, 06:26 PM

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

Posted by: euhenio May 16 2007, 01:11 AM

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


now needed command for exiting Winbuilder

Posted by: Alexei May 16 2007, 01:23 AM

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


Posted by: Ove May 17 2007, 06:35 AM

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)

Posted by: Nuno Brito May 17 2007, 08: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

Posted by: Ove May 18 2007, 08:29 AM

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

Posted by: Nuno Brito May 18 2007, 10:32 AM

Yes, there is a way to add try to copy the values from IE - I will try to implement it.. smile.gif

Posted by: Nuno Brito May 19 2007, 01: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

Posted by: TheHive May 28 2007, 08: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.

Posted by: Alexei May 29 2007, 07:11 AM

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

Posted by: psc May 30 2007, 10:26 AM

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:Peter

Posted by: Nuno Brito May 31 2007, 09:47 AM

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





Posted by: Nuno Brito Jun 9 2007, 11:56 AM

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


Posted by: psc Jun 9 2007, 12:08 PM

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?

DoDoDoTo 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

Posted by: Nuno Brito Jun 9 2007, 12: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

 log.7z ( 80.04k ) : 7
 

Posted by: psc Jun 9 2007, 12:56 PM

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.:
 5___CopyAndExpand.Script ( 19.2k ) : 10


Peter

Posted by: smiley Jun 9 2007, 01:25 PM

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

Posted by: psc Jun 9 2007, 02:11 PM

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:

and the Progress tab does not disappear.
To restart build is not possible. I have to restart WinBuilder before.

Peter

Posted by: Nuno Brito Jun 9 2007, 04: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



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




Posted by: psc Jun 9 2007, 04:26 PM

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

Posted by: Max_Real Qnx Jun 9 2007, 05:04 PM

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

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


Posted by: Nuno Brito Jun 9 2007, 05:34 PM

Thank you for testing!

These are good news.. thumbsup.gif

Posted by: Max_Real Qnx Jun 9 2007, 05:37 PM

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?showtopic=2255&st=10#entry15433

Good job wink.gif

Posted by: TheHive Jun 10 2007, 12:06 AM

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.

Posted by: TheHive Jun 10 2007, 12:19 AM

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.

Posted by: Nuno Brito Jun 11 2007, 08:56 AM

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

Posted by: smiley Jun 11 2007, 10:09 AM

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?

Posted by: psc Jun 11 2007, 11:50 AM

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):

When building the same project with beta 4, during boot I saw:

And finally:


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

Peter

Posted by: smiley Jun 11 2007, 11:56 AM

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?

Posted by: psc Jun 11 2007, 12:26 PM

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

Posted by: smiley Jun 11 2007, 12:39 PM

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?

Posted by: Nuno Brito Jun 11 2007, 12:53 PM

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




Posted by: smiley Jun 11 2007, 12:59 PM

Nuno, what method do you use to read scripts?
did you read my post http://www.boot-land.net/forums/index.php?s=&showtopic=2195&view=findpost&p=15635?

Posted by: psc Jun 11 2007, 01:22 PM

QUOTE(smiley @ Jun 11 2007, 02:39 PM) *
Can you try a clean build?


I did two clean builds:Beta 4: As before missing 'My Computer' etc.
Beta 3: As before showing 'My Computer' etc.

Peter

Posted by: smiley Jun 11 2007, 01:33 PM

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?

Posted by: psc Jun 11 2007, 01:58 PM

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


With beta4 many regwrites are missing. Sample:


@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
 logs.zip ( 224.67k ) : 6

Posted by: Nuno Brito Jun 11 2007, 02:09 PM

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

Posted by: psc Jun 11 2007, 02:15 PM

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

Posted by: Nuno Brito Jun 11 2007, 02:21 PM

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

Posted by: psc Jun 11 2007, 02:28 PM

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

Posted by: Nuno Brito Jun 11 2007, 07:44 PM

You're a true pro when it comes to this sort of debugging! thumbup.gif

Please replace the current beta with this new binary:  WinBuilder071_Beta4a.zip ( 805.99k ) : 35


Hope this time it behaves more nicely, thank you for the very detailed logs and pacience.. smile.gif

Posted by: psc Jun 12 2007, 06:41 AM

QUOTE(Nuno Brito @ Jun 11 2007, 09:44 PM) *
You're a true pro when it comes to this sort of debugging! thumbup.gif

Please replace the current beta with this new binary:  WinBuilder071_Beta4a.zip ( 805.99k ) : 35


Hope this time it behaves more nicely, thank you for the very detailed logs and pacience.. smile.gif


The qEmu boot screen looks ok now.
So it can be assumed that the bug is fixed.
Let me do some more tests.

Peter

Posted by: Nuno Brito Jun 12 2007, 09:02 AM

I will get my hands improving the read INI procedures right now.. smile.gif

Posted by: psc Jun 12 2007, 09:52 AM

QUOTE(Nuno Brito @ Jun 12 2007, 11:02 AM) *
I will get my hands improving the read INI procedures right now.. smile.gif

Before starting, pleas think about http://www.boot-land.net/forums/index.php?s=&showtopic=2367&view=findpost&p=15693

Peter

Posted by: Nuno Brito Jun 14 2007, 12:18 AM

New beta uploaded!

This newer binary has addressed the bug on regwrite which kept registry keys from being properly added.

cheers.gif

Posted by: psc Jun 14 2007, 12:58 PM

Maybe it is new, maybe I did not see before:

I have the code:

QUOTE
ShellExecute,Open,"#$q%ProjectTemp%\wbVersion.exe#$q","#$q-F:%ProjectDir%\Script.project#$q -S:Variables -K:#$pWBVersion#$p"

which does not work correctly.

The log shows:
QUOTE
Shellexecute: [Open] using: ["%BaseDir%\Temp\nativeEx_barebone\wbVersion.exe"]

I need the parameters! frusty.gif

Peter

Posted by: Nuno Brito Jun 14 2007, 01:55 PM

Please try this binary:  WinBuilder071_Beta5a.zip ( 805.97k ) : 26


smile.gif

Posted by: psc Jun 14 2007, 02:28 PM

QUOTE(Nuno Brito @ Jun 14 2007, 03:55 PM) *
Please try this binary:  WinBuilder071_Beta5a.zip ( 805.97k ) : 26


smile.gif


I now get an error, no execution


Peter

Posted by: Nuno Brito Jun 14 2007, 02:57 PM

Annoying bug, it was added while recoding shellexecute - I will work on it properly once I get home.. smile.gif

Posted by: Nuno Brito Jun 14 2007, 10:40 PM

A new revised shellexecute has replaced the one found on the previous beta 5.. smile.gif

Posted by: thunn Jun 16 2007, 01:19 AM

thumbsup.gif
thanks for catching that bug!!
.(.....)
(X) (X) raygun.gif
....U
....~

Posted by: Nuno Brito Jun 23 2007, 04:07 PM

Beta 6 - special edition.. beta.gif

Why a special edition? huh.gif

Because it is likely filled with new bugs and it is only recommended to people who like challenges.. laugh.gif

(consider yourself warned..) betasof.gif

This beta contains a lot of changes since the last posted beta, most of them related to speed improvement and memory leak fixes.

It should run with same files and definitions as a direct replacement to the previous betas, but please try running a few projects and check both the qemu emulation and logs to see if it works ok.

Resumed log of changes:

QUOTE
- Removed an unneeded setting which always wrote a locked=true value on the [main] section
- Recoded interface, file search/filter and settings to load faster.
- Bugfixed error message when selecting to show log after running a project.



Tried to removed out most of the new possible issues, but surely some have passed. If this beta works good enough than it will be posted on the first topic.

Some things are still left to further improve - for example: when a user clicks on a very large script it will still load it to memory slowing the interface a bit (still need to look further on why this happens) and optimize the encode/decode functions which should also be done whenever some time is available to work it.

Hope you have fun and thank you for testing!! thumbsup.gif

 WinBuilder071_Beta6.zip ( 790.26k ) : 44



Posted by: booty#1 Jun 23 2007, 04:47 PM

QUOTE(Nuno Brito @ Jun 23 2007, 06:07 PM) *
Beta 6 - special edition.. beta.gif

Ok, here are my first experiences with this beta:
  1. Directly after starting WinBuilder an Information Dialog saying "215" shows up (missing localization?).
  2. Building my adapted VistaPE version (based on 008) the memory usage is usually between 18MB and 20MB, once 40MB + executed programs of course. The built VistaPE version is OK on first impression - no preblem detected. Runs just like the one created by 071beta5.
  3. Attachment encoding hasn't changed (two temporary files, encoding takes ages)
  4. In edit mode on the interface builder page the edit mode closes directly after adding a control
  5. Selecting a script of 45MB without interface section - it takes about >15 seconds with 100% cpu of one core on my system (C2D E6600).
    The several first times I thought WinBuilder crashed and terminated it. I can see in FileMon that WinBuilder read the script in blocks of 128 bytes. This value is very small, if possible I would use a larger value, this should speed up the read process. Memory usage doesn't increase much on loading. After once reading the complete file it reads "randomly" from different offsets within the file and reads up to 10K. I checked the offsets and they are in the middle of the encoded file - is this an inteded behaviour?
  6. On enabling/disabling this script the script is loaded completly into ram (blocksize on reading 65k). The meory usage on loading the 45MB script is 120MB, before and after 14MB -> 106MB memory used for a 45 MB script.

Besides the enabling/disabling issue the the beta has really a small memory footprint. WinBuilder has made IMHO a large step towards better usability on low- and mid-end systems.

In conclusion: Nice work Nuno thumbup.gif

booty#1

Posted by: Nuno Brito Jun 23 2007, 05:54 PM

Thanks for the quick testing! thumbsup.gif

I'll try to reply following the topic order:


1. It was a control message to ensure that all scripts we're correctly counted before and after the code changes, no special relevance.

2. Will keep testing with bigger sized projects, this time I focused on the interface portion.

3. encoding is unchanged, but modified decode to make script loading on the main window faster, next step should be removing the two temporary files (if possible)

4. A bug to be solved.

5. Will repeat your described steps until it works better.

6. That part still uses default delphi tools, I still need to write some functions to also write on INI text files.

Glad to see that most of these bugs are related to the new "heavy" sized scripts support, will keep working on it.

cheers.gif

Posted by: smiley Jun 24 2007, 08:42 AM

thumbup.gif
I just tested decompression . It is very fast thumbsup.gif

However I found a new bug in winbuilder.
I have attached in a script a 30Mb file. Hile editing its interface, even resizing a control took 3secs(in a good computer). While doing this,I had process explorer open and saw that while doing this winbuilder open and closed the script 4 times confused1.gif.

Another problem that I found was that winbuilder has still a serious handle leak. I saved this file with process explorer and shows that winbuilder forgets open all the subfolders of its projects. The attached file shoes all the open handles that winbuilder has. The handles of the folders are in the middle of the file
 WinBuilder.exe.txt ( 9.48k ) : 12


PS: While attaching/expanding files to/from scripts, winbuilder freezes. Can you make this procedure multithreading?

Posted by: Nuno Brito Jun 24 2007, 02:15 PM

Smiley, thanks for finding this open handles bug - I thought they had already been all solved.

I've optimized the functions to read ini files, but I need to code a completely different approach to correctly write them.

At the moment the optimized INI function will only read one at a time, next step should be using this method to retrieve each key inside the section and this way avoid open file/close file just to read a single value.

Funny enough that even using this non-optimized method, it will still be much faster that traditional INI methods..

Please try this new binary and repeat the open handles test to see if it was solved as expected.

--------------------------------------------------------------
booty#1, the bug that closed edit mode when inserting new objects was also corrected.

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

Download Center is now based on IE - this will of course mean that Windows based machines need to have IE installed, but I will also likely leave the old external download method as option for the cases where IE is not available (some nlite customized installations, Win95, ReactOS and wine for example)

In exchange we inherit support to proxy connections from IE itself which should solve the problems with connecting to the download servers and avoid firewall warnings while downloading using non-recognized ports. Should be compatible with all Vista UAC restrictions and XP built in firewall. (only tested on XP) - as long IE works, wb should also get online. yahoo.gif

Also removed the old ping method to test if a server is available and replaced it with a test to check if the updates.ini is correctly downloaded or not.

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

This should hopefully become the base for the next beta and stable version if projects can be downloaded and run without noticeable bugs.

 WinBuilder071_beta6a.zip ( 806.01k ) : 29


cheers.gif

Posted by: booty#1 Jun 24 2007, 03:51 PM

QUOTE(Nuno Brito)
3. encoding is unchanged, but modified decode to make script loading on the main window faster, next step should be removing the two temporary files (if possible)
4. A bug to be solved.
5. Will repeat your described steps until it works better.
6. That part still uses default delphi tools, I still need to write some functions to also write on INI text files.

Hi Nuno.

3. -> Removing the second temporary file will be hard with the current compression algorithm but the first can be done (as I have showed). My posted source code isn't well commented, if you have questions regarding it, just contact me.
4. -> In Beta6a this bug is solved from my observations
5. -> (large script without interface) Well I would at least modify the script editor to always insert an Interface section at the beginning into the script file
6. -> (enabling/disabling scripts) From my point of view it would be the easiest way to put those frequently changing entries into an separate settings file (is enabled and interface values). Values in the settings file "override" those in the script, the script files could remain static. From my point of view it would be the "easiest" (less coding complexity) solution and it would be even backward compatible with old WinBuilder version if you do not publish the settings files.
Additionally this which would make it much more easier to distinguish between an old and an updated script file - but we already had that discussion in another thread.

I found one new minor bug, regarding a newly added FileBox item with a default value. This default value sometime disappears if you switch to another script and the back to the edited script. But that is really a marginal bug.

booty#1

Posted by: MichaelZ Jun 24 2007, 03:56 PM

QUOTE(Nuno Brito @ Jun 24 2007, 04:15 PM) *
This should hopefully become the base for the next beta and stable version if projects can be downloaded and run without noticeable bugs.

Hi Nuno,

WB 071 Beta 6 gave me at start (and I think after downloading files) a dialog with some 'magic' number. But now Beta6a has some serious problem on my computer. Instead of displaying the magic number it gives the error message
QUOTE
'' is not a valid integer value.

After klickin OK nothing happens anymore confused1.gif

Many Greetings
MichaelZ

Posted by: jaclaz Jun 24 2007, 06:49 PM

QUOTE(Nuno Brito)
Download Center is now based on IE - this will of course mean that Windows based machines need to have IE installed, but I will also likely leave the old external download method as option for the cases where IE is not available (some nlite customized installations, Win95, ReactOS and wine for example)

In exchange we inherit support to proxy connections from IE itself which should solve the problems with connecting to the download servers and avoid firewall warnings while downloading using non-recognized ports. Should be compatible with all Vista UAC restrictions and XP built in firewall. (only tested on XP) - as long IE works, wb should also get online.


PERSONAL opinion (and rant):

I don't care what we inherit. sad.gif

This, in my view, equates to admitting that IE has some use, besides occupying large amounts of HD space, which I thought was the exact opposite of the (unspoken of) basic assumption that started the Winbuilder project, i.e. that IE is just a badly written, bloated browser, unneededly intertwined by perverts programmers and marketing strategies into an otherwise good core, that can ANYTIME be removed and substituted by BETTER browsers, like Opera or Firefox.

What will be next, instead of a .html log, a MS XML:
http://ktn.blogsome.com/2007/03/26/ooxml-ms-xml-proprietary-format/
that can only be e-mailed through Outlook Express? w00t.gif

Using IE should be an (unneeded) option, not the default.

jaclaz

Posted by: psc Jun 24 2007, 07:00 PM

QUOTE(jaclaz @ Jun 24 2007, 08:49 PM) *
PERSONAL opinion (and rant):

I don't care what we inherit. sad.gif


I do not really want to tell that I rant, but I was rather astonished when I saw 'Download Center is now based on IE'

I'm using Firefox since (???) and I do not know whether the IE based download center will bring some new issues.

Let me observe the download mechanism next days, and I can tell more.

Peter

Posted by: MichaelZ Jun 24 2007, 08:07 PM

QUOTE(MichaelZ @ Jun 24 2007, 05:56 PM) *
WB 071 Beta 6 gave me at start (and I think after downloading files) a dialog with some 'magic' number. But now Beta6a has some serious problem on my computer. Instead of displaying the magic number it gives the error message

After klickin OK nothing happens anymore confused1.gif

Sorry, but the above statement is incorrect. The issue is already in WB 071 Beta 6 and is not introduced with beta 6a.

The error happend after I moved my other scripts back into the VistaPE project folder (after downloading a new WB and/or VistaPE I always do one build with only the standard scripts). At the same time I downloaded beta 6a so I thought it's a problem with the very last modifications.

WB 071 Beta 1 accepts my other scripts but beta 6 does not anymore. I did not use any betas in between. Tomorrow I will isolate which script confuses WB so much.

Many Greetings
MichaelZ

Posted by: Nuno Brito Jun 24 2007, 10:31 PM

QUOTE(MichaelZ @ Jun 24 2007, 02:56 PM) *
Hi Nuno,

WB 071 Beta 6 gave me at start (and I think after downloading files) a dialog with some 'magic' number. But now Beta6a has some serious problem on my computer. Instead of displaying the magic number it gives the error message

After klickin OK nothing happens anymore confused1.gif

Many Greetings
MichaelZ


This sounds like some number is not being translated properly along the way. I would guess that this might come from the interface section.

If it's at start up then the first file to be displayed will be script.project from the first listed project.

Please try downloading a fresh project on a new folder just to move away the chance of possible file corruption.

If this error box appears again, please post all your steps and I will reproduce to start debugging myself.

Thanks!

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

Jaclaz and Peter - I know that IE is what most people label as evil since it comes from MS, but I try to view it as tool just like any other that has the advantage of being present by default on the vast majority of machines where our projects will run (Windows XP/Vista platforms).

Could we include Opera? I don't know, but I know it would likely add around 8Mb to the standard distribution which is smaller than 900Kb, or perhaps use firefox and add a bit more in overall size and ask users to install an activeX component and having to code by hand all the support for this browser. (which could take a long while for this simple task) and wouldn't likely bring a compatible solution for x64 XP/Vista editions.

IE has the advantage of not needing any installation procedure, already has activeX and well supported components which allows wb to be used on schools and universities where only guest accounts are used or under firewalls which allow no exceptions besides the already available browser.

Plus that we share the same proxy connections so that people can just get connected without effort.

Most users don't even know which type of proxy they use let alone know user and password details on public access machines.

I already escaped coding in .NET to avoid oversized libraries, and I understand your reasons but do you have a better alternative that works under these restrictive conditions?

Maybe someday another solution appears that can effectively replace the one provided by this overgrown corporate evil, but in the meanwhile - please let me see this solved and move on to more important issues in other areas.. rolleyes.gif

Hope this method brings the needed stable network connectivity and start solving this long time question about issues regarding the download center not working under restricted conditions or questions about why it uses strange ports signaled by firewalls.

cheers.gif

Posted by: euhenio Jun 25 2007, 12:43 AM

My opinion.

WB problems:

1.Unicode
2.RegDelete(value),RegRead(binary value)
3.....
.......
.......

Posted by: TheHive Jun 25 2007, 08:46 AM

QUOTE(Nuno Brito @ Jun 23 2007, 11:07 AM) *
Beta 6 - special edition.. beta.gif

On this beta there are no tabs when you first run it.



Posted by: jaclaz Jun 25 2007, 09:14 AM

Nuno,
just wishing to clarify some points:
1) I am not against IE because it is from Microsoft, MS, like I guess all software producers, have made very good things and very bad ones, the NT core has proved in more than 13 years (yes, the real NT core dates back to circa 1993) to be very good, stable and rather fast, IE on the contrary, and its companion app Outlook Express are the two single programs that due to flaws in design, intertwining with the OS, undocumented or poorly documented features have been the cause of the greatest numbers of headaches to technicians, SysAdmins and users in the last 10 years, having caused an unbelievable number of security breaches, data and system corruption and what not.
I have a system that has been switched on 24/24 7/7 for the last 4 (four) years, connected to the Internet, that is used mainly for accounting but also used daily for e-mails (sending and receiving) and for internet browsing that had 1 (one) case of a virus entering (and promptly neutralised by the anti-virus), with NO firewall whatsoever.
I have a Win2K one, with IE and OE stripped, that in 3 (three) years with the same use and setup had none.
Various experiences with similar setups with XP (with firewall enabled), "as is" i.e. with IE and Outlook Express respectively as browser and e-mail app, had several breaches and cases of data corruption in a few months of use.

So, it is not that I do not like IE because it is from MS, I do not like it because it is a possible and probable security breach.

2) For exactly the same reasons I always expressed my opinion against:
a- Winbuilder going on-line by "his own will"
b- Winbuilder opening or accessing ports
c- Winbuilder having inside scripts unknown apps encoded - possibly "transparent" to anti-virus scanning
d- Winbuilder .scripts lack of documentation

3) And of all the potential security concerns of IE, ActiveX is the first one! sad.gif


4) As said elsewhere, it is, in my view, the distribution model of Winbuilder that is flawed, the whole idea of a central, unique repository is wrong as I see it, and before anyone comes out asking for a better alternative, I have NONE, excluding the good ol' way of a number of downloadable files that can also be mirrored by volunteers, maybe it is not "pretty", nor it is "bleeding edge", but it has proved to work for the greatest number of projects for the last years.


5) I know that probably if we go the way above outlined we somehow "deprive" users of a "one-click-does-it-all" experience, but quite frankly I cannot see why one cannot download with ANY app he has, via http or ftp, one or more self-extracting .7z archive and run it unsure.gif

jaclaz

Posted by: Nuno Brito Jun 25 2007, 10:17 AM

QUOTE(euhenio @ Jun 24 2007, 11:43 PM) *
My opinion.

WB problems:

1.Unicode
2.RegDelete(value),RegRead(binary value)
3.....
.......
.......


You mean full support for unicode?

A bit lengthier task and may take a long while to be supported, sorry.. mellow.gif

RegDelete and RegRead should be corrected soon! smile.gif


QUOTE(TheHive @ Jun 25 2007, 07:46 AM) *
On this beta there are no tabs when you first run it.




Thank you!

The whole startup part was recoded, will add back the missing tabs.. smile.gif



Jaclaz, still think that people should have the choice to use whatever method they think more convenient - inside the new betas there is also the option to completely remove all network support, thus removing the web tab, download center and ftp client and removing any potential security breach when accessing the internet - how many will use it? huh.gif


At work I also have a PII with win2000 used as outlook exchange server which has been there for roughly over 4 years never needing any maintenance (changed the power supply once by a more silent one). I can guarantee you that it deals with hundreds of emails a day and most of them also come with suggestive britneyXXX.exe attachments but it always escaped buggy infections.


You can also manually download each script since it will create an html page with all the contents of each server when uploaded, look here for example: http://updates.boot-land.net/


Since beta 5 a new help system was also introduced to make documentation easier to provide to people where they will be able to read it both online and offline - it's on the process of being written (takes some time to finish and upload all the pages).

I also understand how scripts could be coded with malicious intentions and this is the reason why the download servers are not open for everyone to upload files onto it, only available to a few people that we've come to known from our daily talks here.

It will all be up to trusting the server maintainer and if something strange is found inside a script then due responsibility must be taken by this person alone. At the moment no such case has happened and people handling server uploads have so far demonstrated being quite responsible on this matter.

Still a lot of work to do, but we're getting it done.. smile.gif

Posted by: Nuno Brito Jun 25 2007, 11:26 PM

A new beta was uploaded and is available on the first topic.. smile.gif


Here's a resume of the relevant changes:

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



On this binary some more bugfixes were applied, finished up removing the ping function and correcting some of the details reported since the last beta.

The run command can support up to 9 parameters.

Although my initial intention was to unleash the number of parameters (which is actually not limited at all) there is a bug that will only translate up to 9

Imagine this case:

CODE
[process]
run,%scriptfile%,test,A,B,C,D,E,F,G,H,I,J,K,L,M,N

[test]
echo,[#1]-[#2]-[#3]-[#4]-[#5]-[#6]-[#7]-[#8]-[#9]-[#10]-[#11]-[#12]-[#13]-[#14]


Will output:

QUOTE
[A]-[_b]-[C]-[D]-[E]-[F]-[G]-[H]-[I]-[A0]-[B1]-[C2]-[D3]-[E4]


Maybe during the night I figure some efficient solution for this detail.

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

To test these new commands, I've also added a Code Box - which is nothing more than a place where a person can scribble new commands and see how they run.

Much faster than having to edit the interface to add a button and then a section to then close the source code editor and press the run button - now you type the command and press the run button.

Nothing much complicated, it will save all the text inside a CodeBox.txt which can be found on the root of each project where it edited.

One detail (mostly for Peter): When pressing quick play, should this codebox also run the variables from winbuilder.ini/script.project and run the [process] from script.project?

I was in doubt when working on this, but now I'm seeing that this might be useful for your debugging, what do you think? huh.gif

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

It's all for now, hope you have fun with this newer beta. cheers.gif

Posted by: booty#1 Jun 26 2007, 08:38 AM

Hi Nuno,

I just found some bugs while working with interface builder of WinBuilder beta6a:

1. When resizing a FileBox in the Interface builder the file/folder select icon remains and does not stick to the right end of the edit field.

2. I created a new script with an empty interface section and then switched to edit mode in WinBuilder. After adding a TextLabel I am unable to select the label. Even closing the edit mode and re-starting the editor does not change this behaviour, just like adding a second label. But when I add e.g. TextFile all elements become selectable.
When a TextLabel becomes unselectable it can not be deleted even if it is the only interface element left.

3. Sometimes the caption of TextLabels do disappear. This can happen in the non-edit-mode as well as the interface builder. This looks to me like a redraw problem, because if I use the tool "Winspector spy" the labels appear at the right place (and then disappear again).

booty#1

Posted by: Nuno Brito Jun 26 2007, 09:00 AM

Thank you for this report, I'm not sure if they'll be properly adressed on this version but will keep them in mind.
cheers.gif

Posted by: booty#1 Jun 26 2007, 09:30 AM

QUOTE(Nuno Brito @ Jun 26 2007, 11:00 AM) *
Thank you for this report, I'm not sure if they'll be properly adressed on this version but will keep them in mind.


No problem.
I just ran into another minor bug (and a small typo):
When executing the FileDelete function I get a success log entry with an error text:
(Processed) FileDelete - Failed to delete [C:\Temp\WinBuilder\test\test.txt]

And an failure entry with an success message:
(Error) FileDelete - Successfully deleted [test.bin]

If you don't know the causing script exactly it is very confusing.

booty#1

BTW: The forum often responds with HTTP 404 or HTTP 500. is everything ok with the boot-land server?

Posted by: psc Jun 26 2007, 09:31 AM

QUOTE(Nuno Brito @ Jun 26 2007, 01:26 AM) *
The run command can support up to 9 parameters.

To test these new commands, I've also added a Code Box - which is nothing more than a place where a person can scribble new commands and see how they run.

One detail (mostly for Peter): When pressing quick play, should this codebox also run the variables from winbuilder.ini/script.project and run the [process] from script.project?

Thanks, Nuno!
Two really great enhancements thumbsup.gif

The 9 parameters are sufficient to write an API for shortcuts (8 needed).
I my opinion the API call can be identical for nativeEx based and Vista based projects. 1st.gif

I did not think detailled about the variables, but on the first idea they should not be included automatically.

I hope the AddVariables command can do that!

Peter

Posted by: booty#1 Jun 26 2007, 11:59 AM

Hi Nuno,

sorry for bothering you again with the next bug in beta6a - this time IMHO a bug of higher severity:

I am using the latest VistaPE (008) project (only downloaded project) and tried to change some options of the Build\Preconfig script using the interface. The problem is that all changes are reverted if I selected another script and then select again the mentioned script. This happens with other scripts, too.
The only way to write the changes back to disk is from my observation to run the script. Then the changes are stored in the script.

booty#1

Posted by: psc Jun 26 2007, 12:17 PM

Bug found!

A nativeEx_barebone project is well built with beta 6 and booting in VirtualBox.
When building the same project with beta 7, I get a couple of error messages like:


VirtualBox does not start.
Additionally the log reports some other errors.

Peter

 log_B7.html ( 276.69k ) : 8
 log_B6.html ( 345.45k ) : 5

Posted by: Nuno Brito Jun 26 2007, 12:50 PM

QUOTE(booty#1 @ Jun 26 2007, 09:30 AM) *
No problem.
I just ran into another minor bug (and a small typo):
When executing the FileDelete function I get a success log entry with an error text:
(Processed) FileDelete - Failed to delete [C:\Temp\WinBuilder\test\test.txt]

And an failure entry with an success message:
(Error) FileDelete - Successfully deleted [test.bin]

If you don't know the causing script exactly it is very confusing.

booty#1

It's a typo, was likely added when moving the old routine with the one based on win32 API, thanks for spotting it. smile.gif


QUOTE
BTW: The forum often responds with HTTP 404 or HTTP 500. is everything ok with the boot-land server?


I've blogged the details and expected solutions on a near future. cheers.gif

Posted by: Ove Jun 26 2007, 01:44 PM

I have also downloaded beta 6.
I have not really tested it with any scripts, but this is what I have noticed:

It's GREAT!!!
Its speed is higher than the previous versions. The SATA script loads in under 2 seconds. That's a REAL improvement from 20 seconds.
I have also seen a messagebox show up, but with another number (not 215)
The download center didn't appear (maybe this was intended)

Good work

Posted by: Nuno Brito Jun 26 2007, 01:57 PM

QUOTE(booty#1 @ Jun 26 2007, 11:59 AM) *
Hi Nuno,

sorry for bothering you again with the next bug in beta6a - this time IMHO a bug of higher severity:

I am using the latest VistaPE (008) project (only downloaded project) and tried to change some options of the Build\Preconfig script using the interface. The problem is that all changes are reverted if I selected another script and then select again the mentioned script. This happens with other scripts, too.
The only way to write the changes back to disk is from my observation to run the script. Then the changes are stored in the script.

booty#1


Thanks, will keep them in mind.. smile.gif

QUOTE(psc @ Jun 26 2007, 12:17 PM) *
Bug found!

A nativeEx_barebone project is well built with beta 6 and booting in VirtualBox.
When building the same project with beta 7, I get a couple of error messages like:


VirtualBox does not start.
Additionally the log reports some other errors.

Peter

 log_B7.html ( 276.69k ) : 8
 log_B6.html ( 345.45k ) : 5


Important bug - should have been introduced the new run command, will keep debugging it.. cheers.gif

Posted by: Holger Jun 26 2007, 02:41 PM

Hi Nuno

this is what I get at work (firewall...you know).
No download section anywhere.
The tools button does nothing.
Is this what I should expect?

Greets smile.gif
Holger

 

Posted by: Nuno Brito Jun 26 2007, 02:57 PM

Hi holger! thumbup.gif

Thanks for testing, but you should try with the latest beta 7 because the ping on 6x was not prepared for proxies.

smile.gif

Posted by: MichaelZ Jun 26 2007, 03:33 PM

QUOTE(Nuno Brito @ Jun 25 2007, 12:31 AM) *
This sounds like some number is not being translated properly along the way. I would guess that this might come from the interface section.

If it's at start up then the first file to be displayed will be script.project from the first listed project.

Please try downloading a fresh project on a new folder just to move away the chance of possible file corruption.

If this error box appears again, please post all your steps and I will reproduce to start debugging myself.

Nuno, you are correct. I found the script in my other script directory that is causing the trouble (introduced somewhere between beta 1 and beta 6): an empty Version= entry in the [Main] section:
CODE
[Main]
Title=Advanced PCI Info Utility
Author=
Level=7
Version=
Description=
Selected=True

[Process]
Echo,Processing Advanced PCI Info Utility...
.
.

This script is one of those I took over from the Chip Edition.

WB beta 7 can open the script when either Version= is deleted or when a value is assigned to it. Probably one could assign again a default value to the missing one to obtain backward compatibility.

Many Greetings
MichaelZ

Posted by: Nuno Brito Jun 26 2007, 03:55 PM

MichaelZ, thanks for commenting this detail - it will also be adressed.. frusty.gif


Ove, please try beta 7 - I would like to know if you can run it in school. cheers.gif

Posted by: Holger Jun 27 2007, 10:42 AM

Great biggrin.gif
Works now also here smile.gif

Thanks @Nuno for the update and sorry - thought I used the latest version...

Edit:: Problem - WB does not remember selected options if I change from one script to another.

Posted by: Nuno Brito Jun 27 2007, 12:21 PM

Thanks for reporting, there have been a lot of deep changes over these last 3 betas and these are easily correctable details - hopefully they'll be all corrected before the end of this week.

smile.gif

Posted by: C57D Jun 28 2007, 06:47 PM

QUOTE(Nuno Brito @ Jun 26 2007, 08:55 AM) *
MichaelZ, thanks for commenting this detail - it will also be adressed.. frusty.gif
Ove, please try beta 7 - I would like to know if you can run it in school. cheers.gif


Fantastic - Beta 7 works for me too at work behind a proxy server.
Thanks!

thumbup.gif

Posted by: Nuno Brito Jun 29 2007, 08:51 AM

Hi C57D!

Welcome to the board, can you run our projects without visible issues?

Just a bit worried on the latest changes added on the script engine (were a lot) and haven't had much time to debug them intensively.

Thanks for reporting that you can access within a proxy, very good news.. thumbup.gif

Posted by: Ove Jun 29 2007, 12:59 PM

QUOTE(Nuno Brito @ Jun 26 2007, 06:55 PM) *
Ove, please try beta 7 - I would like to know if you can run it in school. cheers.gif

Nope, sorry.
I can't run it in school anymore. I have graduated from high school, and will never see it again smile.gif
I am now in summer break ... somewhat ... (I have passed one week of exams, and have one more week of exams left)
After that ... admission to college, and everything will be over by the end of July

Posted by: C57D Jun 29 2007, 03:34 PM

QUOTE(C57D @ Jun 28 2007, 11:47 AM) *
Fantastic - Beta 7 works for me too at work behind a proxy server.
Thanks!

thumbup.gif


I am trying to build a VistaPE disk.
Eventually I hope to get a boot disk with MS iSCSI on it.
I am a newbee so go easy!

I built one successfully using the winbuilder from: http://vistape.boot-land.net/eng/
Although I am new to this process I have been building BartPE disks for years.

I am trying to build one on my XP w/sp2 laptop using a MSDN VISTA DVD that I am mounting via WinXP Virtual Control Panel.
I used this same process to build a disk on VistaPE 005

This time I am getting multiple errors, they all start out with: "Error - run,%ScriptFile," and after the last "," the error name varies: Find-WinUtil; MountVista; ClearTarget; RecTools; AddFont; CopyNLS; FileCopyStandard; Custom; ExtractSystem32; ExtractFiles; Download; InnoUn

Any thoughts on how to best resolve this?

Thanks.

Posted by: Nuno Brito Jun 29 2007, 09:50 PM

QUOTE(Ove @ Jun 29 2007, 12:59 PM) *
Nope, sorry.
I can't run it in school anymore. I have graduated from high school, and will never see it again smile.gif
I am now in summer break ... somewhat ... (I have passed one week of exams, and have one more week of exams left)
After that ... admission to college, and everything will be over by the end of July


These are good news, an year has passed quickly - congratulations! cheers.gif

Glad you won't be testing it then.. wink.gif




QUOTE(C57D @ Jun 29 2007, 03:34 PM) *
.....

Any thoughts on how to best resolve this?


Yes, it was also reported by other users and it is because of the RUN command. There were a lot of internal changes on these last betas and this is something that will be corrected over the next beta.

In the meanwhile I believe you should be fine trying out beta 5

Welcome to boot-land and good luck! smile.gif

Posted by: Nuno Brito Jul 1 2007, 11:12 AM

A new beta should become available soon, please use the latest stable 070 to properly create your projects.

Thanks! smile.gif

Posted by: Nuno Brito Jul 5 2007, 12:43 PM

QUOTE(MichaelZ @ Jun 26 2007, 03:33 PM) *
...

WB beta 7 can open the script when either Version= is deleted or when a value is assigned to it. Probably one could assign again a default value to the missing one to obtain backward compatibility.
...



Was corrected to check to ensure the result is different from empty.


Interface also gets written correctly and run command was also corrected.


Will be releasing a new beta later today, just missing some details - it should be about time to release a new stable since we've changed a lot of things since last version..

smile.gif

Posted by: MedEvil Jul 5 2007, 02:04 PM

QUOTE(Nuno Brito @ Jul 5 2007, 02:43 PM) *
it should be about time to release a new stable since we've changed a lot of things since last version..

smile.gif

No problem with that, as long as it really is a stable. wink.gif

cheers.gif

Posted by: Nuno Brito Jul 5 2007, 02:11 PM

Been working to see all bugs solved, but there are always a few that appear right after uploading a beta.. frusty.gif


At the moment many changes were introduced so "old" bugs from the interface section and script editing might appear..

smile.gif

Posted by: Nuno Brito Jul 6 2007, 12:01 AM

A new beta has been uploaded and is available on the first post! cheers.gif

Here's a more formal list of relevant changes:

QUOTE
- 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



Not many changes since last time, was an overall cleanup of reported bugs and I think the most critical ones have been properly solved.

Also added some extra functionality in the create script tab to make it more user friendly when adding simple scripts.

The lock button was removed mostly because there was not much point in having it as option - it was adding a locked = false line on each script which is redundant (will finish removal of the behavior soon)

The interface can save changes again and the run command has been corrected, the behavior to deal with invalid webservers of when going offline was a bit improved along the internal script editor which has been a bit enlarged to give more editing room.

Next step should be providing a new beta with the new languages text already prepared to be translated.

Thank you for testing!! thumbup.gif

Posted by: psc Jul 6 2007, 09:05 AM

QUOTE(Nuno Brito @ Jul 6 2007, 02:01 AM) *
A new beta has been uploaded and is available on the first post! cheers.gif

Thank you for testing!! thumbup.gif

Quick test:Peter cheers.gif

Posted by: Nuno Brito Jul 6 2007, 09:13 AM

Hmm.. switched the text message and forgot to change the message identifier.. frusty.gif

Thanks! cheers.gif

Posted by: h7se Jul 6 2007, 01:16 PM

Hi

bug report

1 - when deleting file sucessfully the log entry will be added to Error's section

2 - Locked=True or missing Locked statment will prevent from adding item's to interface

----

thumbup.gif

Posted by: h7se Jul 6 2007, 02:27 PM

Hi

Here's another

if i want to rename file 1 to file 2 but file 2 already exists and error message will appear in the log window "Failed to rename ..."

maybe this is'nt a bug but i think a "File Already Exist" massage will be better than "Fail to Rename ..."

Posted by: Nuno Brito Jul 6 2007, 02:47 PM

Maybe this should be script handled, adding a small command to delete a file if it already exists.. huh.gif

Just a thought. smile.gif

Posted by: h7se Jul 6 2007, 03:59 PM


also it can be done using
If,NotExistFile,"file2",FileRename,"file1","file2"

Thanks Nuno thumbsup.gif


Posted by: MichaelZ Jul 6 2007, 05:53 PM

QUOTE(Nuno Brito @ Jul 5 2007, 02:43 PM) *
Was corrected to check to ensure the result is different from empty.
Interface also gets written correctly and run command was also corrected.
Will be releasing a new beta later today, just missing some details - it should be about time to release a new stable since we've changed a lot of things since last version..

I just tried beta 8. My customized VistaPE-Beta was built just fine. I noticed the already mentioned flaws, but also another (not important one!). The old Vista Chip Edition script that has an empty version= entry still gives the error message. After hitting the OK button, WinBuilder does not display the project tree on the left side anymore. Also switching on other pages like Download does not recover.

Many Greetings
MichaelZ

Posted by: Nuno Brito Jul 6 2007, 06:44 PM

Hmm.. really thought this had been solved for good.. mellow.gif

Can you attach this script so that I can test it and ensure this is bugfixed as expected?



QUOTE
Also switching on other pages like Download does not recover.


This is after the error occurs, right? huh.gif


cheers.gif

Posted by: MichaelZ Jul 7 2007, 09:16 AM

QUOTE(Nuno Brito @ Jul 6 2007, 08:44 PM) *
Hmm.. really thought this had been solved for good.. mellow.gif
Can you attach this script so that I can test it and ensure this is bugfixed as expected?

As I mentioned, this is not really important so actually one should not worry about (it is sooo easy to add avalid version number). Here is the complete script used in VistaPE-Beta:
CODE
[Main]
Title=Advanced PCI Info Utility
Author=
Level=7
Version=
Description=
Selected=True

[Process]
Echo,Processing Advanced PCI Info Utility...
SET,"%LinkDir%","X:\Program Files\Apciinfo"
DirMake,"%TargetDir%\Program Files\Apciinfo"
DirCopy,"%ScriptDir%\Apciinfo\*.*","%TargetDir%\Program Files\Apciinfo"
If,ExistFile,"%TargetDir%\Program Files\BSExplorer\bs_explorer.ini",run,%ScriptFile%,BSLinks

[BSLinks]
TXTAddLine,%BSS%,"<-ItemBegin->","Append"
TXTAddLine,%BSS%,"    ShowState=NORMAL","Append"
TXTAddLine,%BSS%,"    CmdParam=","Append"
TXTAddLine,%BSS%,"    ExeDir=%LinkDir%","Append"
TXTAddLine,%BSS%,"    ExeName=%LinkDir%\Apciinfo.exe","Append"
TXTAddLine,%BSS%,"    IconName=%LinkDir%\Apciinfo.exe","Append"
TXTAddLine,%BSS%,"    Caption=Advanced PCI Info Utility","Append"
TXTAddLine,%BSS%,"    ParentItem=InformationDiagnosticTools","Append"
TXTAddLine,%BSS%,"<-ItemEnd->","Append"

The script still uses the out-of-date method to create shortcuts, only for BSExplorer (but that is my favourite shell...)

QUOTE
This is after the error occurs, right? huh.gif

Yeppp. I can imagine that this is the thing that really makes you curious? rolleyes.gif

Many Greetings
MichaelZ

Posted by: Nuno Brito Jul 7 2007, 09:35 AM

Hmm... blink.gif

I'm starting to believe that some scripts are voodoo - I've copied & paste to notepad and added as a new script (called "tweaks.script") inside a picoXP project (used just for testing the script reading) and wb wouldn't hang as expected - instead it just worked.. dry.gif

Also tried running it and no noticeable bugs were displayed while running too. mellow.gif


You mentioned beta 8 and I'm clueless at this moment on why it is working with empty values on my machine and fails on yours.

CODE

[Main]
Title=Advanced PCI Info Utility
Author=
Level=7
Version=
Description=
Selected=True
Locked=false

[Process]
Echo,Processing Advanced PCI Info Utility...
SET,"%LinkDir%","X:\Program Files\Apciinfo"
DirMake,"%TargetDir%\Program Files\Apciinfo"
DirCopy,"%ScriptDir%\Apciinfo\*.*","%TargetDir%\Program Files\Apciinfo"
If,ExistFile,"%TargetDir%\Program Files\BSExplorer\bs_explorer.ini",run,%ScriptFile%,BSLinks

[BSLinks]
TXTAddLine,%BSS%,"<-ItemBegin->","Append"
TXTAddLine,%BSS%," ShowState=NORMAL","Append"
TXTAddLine,%BSS%," CmdParam=","Append"
TXTAddLine,%BSS%," ExeDir=%LinkDir%","Append"
TXTAddLine,%BSS%," ExeName=%LinkDir%\Apciinfo.exe","Append"
TXTAddLine,%BSS%," IconName=%LinkDir%\Apciinfo.exe","Append"
TXTAddLine,%BSS%," Caption=Advanced PCI Info Utility","Append"
TXTAddLine,%BSS%," ParentItem=InformationDiagnosticTools","Append"
TXTAddLine,%BSS%,"<-ItemEnd->","Append"



Posted by: booty#1 Jul 7 2007, 10:34 AM

Hi Nuno,

from my point of view Beta8 is very good work thumbsup.gif . Unfortunately I have found one last, more or less serious bug:

Under some circumstances WinBuilder copies the interface section of the last script (on other times the first) in the currently selected tree level into the currently selected script. If the currently selected script already has an interface section it get overwritten.
Sometimes this bug isn't easy to reproduce but from my observations this happens often directly after starting WinBuilder or after a refresh.

1. Execute "Refresh"
2. Select a script in the middle of a folder.
3. Execute this script
4. Open the script in an external editor and search for the [Interface] section. It may be modified.

Besides this bug I noticed that a script wont execute (aborts with the error "list index out of bounds(2)") if it contains an empty [Interface] section.

The remaining bugs I found are mostly display problems and already known:

1. Ampersands in Title, Author, Description and Echo/Messages commands are not displayed correctly (Property "ShowAccelChar" has to be set to false for the relevant TLabel components)
2. The Labels of the script Interface (and on the editor page, too) are usually invisible but do reappear after resizing the window, May be a manual call of Repaint() of the tab-sheet solves this or setting the "DoubleBuffered" property to true (which is not visible in the ObjectInspector) can solve this.

booty#1

Posted by: Nuno Brito Jul 7 2007, 10:57 AM

QUOTE(booty#1 @ Jul 7 2007, 10:34 AM) *
..
Under some circumstances WinBuilder copies the interface section of the last script (on other times the first) in the currently selected tree level into the currently selected script. If the currently selected script already has an interface section it get overwritten.
Sometimes this bug isn't easy to reproduce but from my observations this happens often directly after starting WinBuilder or after a refresh.

1. Execute "Refresh"
2. Select a script in the middle of a folder.
3. Execute this script
4. Open the script in an external editor and search for the [Interface] section. It may be modified.


Thank you for testing, I've already noticed this interface bug and went to see where it occurs, but it still a bit difficult to reproduce even with the steps you've mentioned.

QUOTE
Besides this bug I noticed that a script wont execute (aborts with the error "list index out of bounds(2)") if it contains an empty [Interface] section.


Same errors as mentioned by MichaelZ - will change my work environment since the current one seems too permissive about these error details and doesn't output any messages when a section doesn't exist or a value is not found. Really strange why nothing is displayed. Will use a different OS and laptop to compare changes.

QUOTE
The remaining bugs I found are mostly display problems and already known:

1. Ampersands in Title, Author, Description and Echo/Messages commands are not displayed correctly (Property "ShowAccelChar" has to be set to false for the relevant TLabel components)
2. The Labels of the script Interface (and on the editor page, too) are usually invisible but do reappear after resizing the window, May be a manual call of Repaint() of the tab-sheet solves this or setting the "DoubleBuffered" property to true (which is not visible in the ObjectInspector) can solve this.

booty#1


Thanks!

Can you also detail the steps needed to reproduce the missing labels effect or this happens when they are displayed for the first time? huh.gif

Hmm.. I avoid using DoubleBuffered properties - they are usually the reason why objects disappear in the first place, but a repaint migh be necessary althought it can also slowdown the overall display or cause "blinks" on the tabsheet.

I think this may happen because of the graphics card on my computer - it has 4Mb and is very slow redrawing all objects inside wb (I mean all objects not only the interface ones). More specs http://www.pcmag.com/article2/0,1759,685719,00.asp, will also test on other machines.


Thank you for this feedback! cheers.gif

Posted by: booty#1 Jul 7 2007, 12:45 PM

QUOTE(Nuno Brito @ Jul 7 2007, 12:57 PM) *
Thank you for testing, I've already noticed this interface bug and went to see where it occurs, but it still a bit difficult to reproduce even with the steps you've mentioned.


I tried to trace with FileMon when the script gets written but I did not manage to find out anything useful. Besides that I don't even see the point in saving the script before executing (as long as nothing in the interface has been changed).
But I found another better reproducible way to trigger the interface bug:

1. You need two scripts. One with interface elements, the other without.
2. Select the script with the interface elements
3. Select the script without interface elements
4. Enter script edit mode
5. Add an interface element
6. Suddenly the interface elements of the previously selected script appear...

Additionally I noticed that if the description of a script is empty WinBuilder does not change the displayed description to the empty string, instead the previous description is still displayed.

QUOTE(Nuno Brito @ Jul 7 2007, 12:57 PM) *
Can you also detail the steps needed to reproduce the missing labels effect or this happens when they are displayed for the first time?


Well, the labels are missing always after selecting a script. This also applies to the Label right above the TextBox. They re-appear when I resize the WinBuilder window but they re-disappear if I switch to another program and then back to WinBuilder (using Alt-Tab). I am running WinBuilder on XP-SP2 with an NVidia graphics card. I compared the behaviour of different WinBuilder versions:

070 final: Labels are visible after script selection but disappear by program switching
071beta1 to beta5b: same as 070
071beta6 and higher: Labels are invisible after selecting a script.

booty#1

Posted by: Nuno Brito Jul 7 2007, 03:29 PM

Thanks for the description.

I've was able to reproduce and correct this issue, will start on the ghost labels now. thumbsup.gif

Posted by: Nuno Brito Jul 7 2007, 05:16 PM

Would you please check this binary on your machine and see if the labels are displayed properly?

 WinBuilder071_beta8a.zip ( 809k ) : 24


cheers.gif

Posted by: booty#1 Jul 7 2007, 07:43 PM

QUOTE(Nuno Brito @ Jul 7 2007, 07:16 PM) *
Would you please check this binary on your machine and see if the labels are displayed properly?
 WinBuilder071_beta8a.zip ( 809k ) : 24

Sorry Nuno, no luck. I even installed the newest graphic driver from NVidia.
But I made some more tests with "WinSpector" running in background tracing all WM_??? messages of the script TabSheet. I compared the messages that are shown when I select a script or switch back to WinBuilder from another program with those shown when I resize the window. The major difference was the WM_PAINT message.
The I used an XP in a Virtual Machine which always shows the labels. Same procedure with WinSpector and surprise in that environment the WM_Paint message shows up even if I just switch between scripts or between programs.
This is really strange questionmark.gif

booty#1

Posted by: Nuno Brito Jul 7 2007, 07:53 PM

Thank you once again! thumbsup.gif

Too bad about the results.. Will need to find a machine where I can replicate the same issue - on monday I'll go back to work on test there.

Does anyone else also experiences the same ghost labels?

cheers.gif

Posted by: Nuno Brito Jul 8 2007, 01:06 AM

New beta version uploaded! cheers.gif

You can find it on the first topic of the thread.

Log of changes:

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




Took a bit longer but I finally found a machine where the labels weren't also being displayed properly. Done enough testings and now I think it should be working good enough.

Some other corrections and bugfixes were done (mostly cosmetic)


Finished the adding the missing texts to be translated - meaning that people interested in translating can start converting the newly available english words, they're not many - maybe 10 new phrases.

And the Download Center has a built-in web server box that allows to manage the available servers - hopefully this will improve the overall method since people will be able to choose and add the servers they wish to use. This was already available before, but the option to do this action was a bit hidden and hope this make things much more acessible and customizable.

By default the updates server already comes selected.

This saves a considerable bandwidth as servers grow in size and also allows more servers/projects to become available in the future - also added the newer win31 project by asiekierka.


If all goes well, we can finally have a newer stable binary to replace 070.

Michael - is the missing value in the INI key still outputing an error on your machine?

Thanks for testing and hope you enjoy this beta. smile.gif


Posted by: psc Jul 8 2007, 10:10 AM

QUOTE(Nuno Brito @ Jul 8 2007, 03:06 AM) *
New beta version uploaded! cheers.gif

And the Download Center has a built-in web server box that allows to manage the available servers - hopefully this will improve the overall method since people will be able to choose and add the servers they wish to use. This was already available before, but the option to do this action was a bit hidden and hope this make things much more acessible and customizable.

1st.gif

Peter

Posted by: booty#1 Jul 8 2007, 10:19 AM

QUOTE(Nuno Brito @ Jul 8 2007, 03:06 AM) *
Took a bit longer but I finally found a machine where the labels weren't also being displayed properly. Done enough testings and now I think it should be working good enough.

Thank you Nuno. Now it works again as in 070.

QUOTE(Nuno Brito @ Jul 8 2007, 03:06 AM) *
Some other corrections and bugfixes were done (mostly cosmetic)

I noticed that ampersand are now displayed correctly on the script page but not on the progress tab (see the related test script).

CODE
[Main]
Title=&Title - Amp Test
Author=&Author
Level=5
Version=001
Description=&Description
Contact=&Contact
Date=&Date
Selected=False
Locked=false

[Process]
Echo,&Echo...
Message,"&Message",Error
Wait,60


Additionally I found another small display-bug: The main treeview on the left does not resize if the splitter between the treeview and the page control is moved to the right.

In general I agree with you that WinBuilder is now ready for the next stable release. cheers.gif

booty#1

Posted by: Nuno Brito Jul 8 2007, 11:08 AM

Thank you both for testing! thumbup.gif


Already corrected the missing ampersand in the progress tab and limited the treeview so that it wouldn't get excessively big.

Will work on another detail posted by Peter and should be ready to release soon - still some other bugs left out to solve, but it's also time to update the older 070.

smile.gif

Posted by: MichaelZ Jul 8 2007, 01:21 PM

QUOTE(Nuno Brito @ Jul 8 2007, 03:06 AM) *
New beta version uploaded! cheers.gif
...
Michael - is the missing value in the INI key still outputing an error on your machine?
...

Hi Nuno, beta 9 is very fine on my main development computer and that empty version= line does not make any trouble any more thumbsup.gif

Although I setup WinBuilder 071 beta 9 fresh on another computer, downloaded the minimum necessary VistaPE-Beta and included that problematic script. At startup of WinBuilder also no error showed, but during build there was http://michael-zoellner.dyndns.org/Boot-Land/Member/MichaelZ/WB071b9-ErrorOnEmptyVersion-2.gif funny error 'List Index out of bounds (2)'. But on the computer I use most everything is fine.
QUOTE
Thanks for testing and hope you enjoy this beta. smile.gif

I most certainly will be working with this beta. And I hope you can now enjoy the fine weather on the Azores (according to this post; here in Germany we are not that lucky...).

It sounds like you are almost done with beta testing this version. Be assured that I'm very curious about the next series of betas for the following version thumbup.gif

Many Greetings cheers.gif
MichaelZ

Posted by: Nuno Brito Jul 8 2007, 01:56 PM

Hi Michael!

Glad it works for you - will also take the same script on other machines to see if I can replicate it, after the experience with ghost labels I now understand the OS/Hardware itself can also play some unexpected tricks..

Over the next beta I've also corrected the issue that didn't allowed for a single object on the interface to be selected.

I hope this becomes a good stable version and solves most issues experienced about network connectivity which we've been dealing for some time.

Also hope to get some time back into scripting and help in a few other projects which will surely help understand better what needs to be done next.


Our weather around here is also very harsh all year round - rarely get a clean day with bright sun, so I guess we all appreciate these breaks.

Have a nice weekend!! thumbup.gif

Posted by: Nuno Brito Jul 8 2007, 09:15 PM

Solved the bug mentioned by MichaelZ - it was being caused by an empty interface section on the bottom of the script. Should have noticed sooner and was thinking it was related to variables with empty values. Should be compatible with all scripts now.

cheers.gif

Posted by: TheHive Jul 8 2007, 11:31 PM

Suggestion to add to the first launch of Winbuilder a Sample screenshot of how the PE will look when built.



I like the new Available Web Server layout. Yes! the old method made it hidden. This method appears open and better. It needs a way to show the description of each project when you select the different servers. We cant expect people to know what they want untill they read the different descriptions of what each project does or its focus is.

We still run into the problem with the tools folder not being downloaded with the NativeEx Project.

Posted by: Nuno Brito Jul 9 2007, 10:19 AM

Hi TheHive!!

Sounds a good idea - it should definitively be added - how about a youtube clip that also displays where to extract, what to download and how to set up things also showing the final result.

Also agree that an image is truly worth 1000 words. smile.gif


Have no idea on how to add descriptions to these servers - maybe these could come predefined inside winbuilder itself and writen to winbuilder.ini once it would become available.

This was also the reason why I've added the explorer button - so that people can visit the server's page and see what projects can be found inside - this could easily be replaced with custom pages if a developer wishes to use it.

The tools folder is a bit trickier to get working - I'm afraid that current solutions are only making things less simple than prefered, need more time to think on something that works good enough to address this matter..

Thanks for testing!! thumbsup.gif

Posted by: Nuno Brito Jul 9 2007, 11:31 PM

Beta 10 was uploaded and is available for testings on the first post! cheers.gif


Here is a quick log of changes:

QUOTE
- 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.



WebGet is now using the same method as the Download Center - it will also display the direct link location of the file and the overall size expected to be downloaded and a time estimative to be concluded.

The logo that was displayed by default whenever a script didn't used a logo was also updated - hope you like the new graphic.

Filecopy has a new parameter - show - I've been doing some scripts that copied a few hundred mb's from one folder to another and the available commands were not displaying the progress - making it very dificult to tell if the application is running or not, so this new option was added. (at first I had coded a separate app, but then thought it would be better to be included in wb)

The progress bar will be filled to 100% as files get copied and the current copied file is also displayed. This method is not using Win32 API (same as explorer), but it can be changed in the future to allow copying even from media with file errors.


ExtractAndRun was also fixed - it didn't seemed to be working for quite some versions back. It was recoded and is working as expected. One note not mentioned on the help pages: it can run parameters. Look on the ImgBurn.script to see an example on how it can be used.


There was a bug which prevented from selecting single objects on the interface - this bug has been solved. Users should be able to select any object now. There's still a small bug which make the Add/remove object buttons become unresponsive under some situations (very rare), but still need to replicate and debug them out soon. (closing and opening the script again is a good workaround if needed)

Wasn't planning on doing much changes, but also thought that it would be better to do them now that having to wait another month to become included on the next stable..


Hope you like this new binary. Have a good night everyone! smile.gif

Posted by: edborg Jul 10 2007, 01:35 PM

Just tried the new beta after long time (my last working test was with 068!) and got this error right after launching the exe.
May be it has something to do with my somewhat "old" ini or projects?
edborg

 

Posted by: Nuno Brito Jul 10 2007, 01:42 PM

Hi Edborg, welcome back to our beta testings!!! thumbup.gif


Yes, it's likely some conflict with older configurations - please try from an empty folder to ensure you get good scripts and a new configuration file.

smile.gif

Posted by: booty#1 Jul 10 2007, 02:37 PM

QUOTE(edborg @ Jul 10 2007, 03:35 PM) *
Just tried the new beta after long time (my last working test was with 068!) and got this error right after launching the exe.
May be it has something to do with my somewhat "old" ini or projects?
edborg

Looks like a script of version 0.05 has met the Delphi function IntToStr(). happy.gif

A try-catch block around it should solve this problem, or alternativly switching to StrToIntDef().

booty#1


Posted by: Garfield Jul 10 2007, 02:41 PM

I have been very busy lately so I fell behind on recent developments

I downloaded the new WB71-B10, nativeEx_barebone and nativeEx_Core today, added some more apps (which worked fine on WB70, pointed my source Disk and fired away.... thumbdown.gif But No Go..(over 52 errors). I downloaded WB71-B9 and except for 2 minor errors it worked fine

I've attached the log files... [attachment=2469:Logfiles.zip]

The problems with WB71-B10 were
1. 4 - BuildModel.Script would load WB-Default hive but would not Dismount it
2. a windows exception occurred for every shortcut created
3. the log complains about files that can't be renamed, but the rename seems to have been successful confused1.gif


Posted by: Nuno Brito Jul 10 2007, 03:06 PM

QUOTE(booty#1 @ Jul 10 2007, 02:37 PM) *
Looks like a script of version 0.05 has met the Delphi function IntToStr(). happy.gif

A try-catch block around it should solve this problem, or alternativly switching to StrToIntDef().

booty#1


I think this might be related to IniRead itself since this value would be converted to a number too, but this wouldn't likely happen with empty spaces mixed with the value - causing the error message - edborg, would you please post the problematic script and try again with newer projects?


QUOTE(Garfield @ Jul 10 2007, 02:41 PM) *
I have been very busy lately so I fell behind on recent developments

I downloaded the new WB71-B10, nativeEx_barebone and nativeEx_Core today, added some more apps (which worked fine on WB70, pointed my source Disk and fired away.... thumbdown.gif But No Go..(over 52 errors). I downloaded WB71-B9 and except for 2 minor errors it worked fine

I've attached the log files... [attachment=2469:Logfiles.zip]

The problems with WB71-B10 were
1. 4 - BuildModel.Script would load WB-Default hive but would not Dismount it
2. a windows exception occurred for every shortcut created
3. the log complains about files that can't be renamed, but the rename seems to have been successful confused1.gif


Hi Garfield, it's good to see more familiar persons testing wb again!

Please try with the liveXP or nativePE project to ensure this is a winbuilder.exe specific issue and post one of the script that directly output errrors - not the ones that call buildmodel (these are specific buildmodel details that Peter can probably explain better why they occur)

smile.gif

Posted by: Nuno Brito Jul 10 2007, 03:32 PM

Found a reason - look on the interface variables - they are not being converted to variables at all.. frusty.gif

Here is a quick fix for this issue:
 WinBuilder072_Beta10a.zip ( 808.31k ) : 23

Posted by: psc Jul 10 2007, 04:31 PM

QUOTE(Nuno Brito @ Jul 10 2007, 05:06 PM) *
Please try with the liveXP or nativePE project to ensure this is a winbuilder.exe specific issue and post one of the script that directly output errrors - not the ones that call buildmodel (these are specific buildmodel details that Peter can probably explain better why they occur)

It is not a buildModel issue. It depends on the beta version.

Here a log from beta5d
QUOTE
Processing section: [bypass-bug]From file: [%BaseDir%\Projects\nativeEx_core\Basic\Build\4 - BuildModel.Script]

[Success] RegHiveLoad - File: [%BaseDir%\Target\nativeEx\I386\system32\config\default] Section [WB-Default]
[Success] RegRead - read specified key from: [HKLM] Section: [WB-Default\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders] Key: [AppData] into variable: [%Doc%] with value: [R:\Documents and Settings\Default User\Application Data]
[Success] RegHiveUnLoad - Unloaded registry hive: [WB-Default]


Here the log from beta10:
QUOTE
Processing section: [bypass-bug]From file: [%BaseDir%\Projects\nativeEx_core\Basic\Build\4 - BuildModel.Script]

[Success] RegHiveLoad - File: [%BaseDir%\Target\nativeEx\I386\system32\config\default] Section [WB-Default]
[Failed] RegRead - Failed to read specified key from: [HKLM] Section: [WB-Default\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders] Key: [AppData] to variable: [%Doc%]
[Failed] RegHiveUnLoad - Failed to unload registry hive: [WB-Default]


In the second case the hives are really corrupted.

Therefore the reason is inside hivesFactory.
But here the same:

One script makes different results depending on WinBuilder version.

What and why?

I hope, I have some mor information tomorrow.

Peter

Posted by: psc Jul 10 2007, 04:41 PM

QUOTE(psc @ Jul 10 2007, 06:31 PM) *
Therefore the reason is inside hivesFactory.
But here the same:

One script makes different results depending on WinBuilder version.

What and why?

I hope, I have some mor information tomorrow.

Peter

I found the bad boy:
ok:
QUOTE
Processing section: [CopyToTarget]From file: [%BaseDir%\Projects\nativeEx_core\Basic\Build\3 - hivesFactory.Script]

Retrieve - Sucessfully retrieved the file size from: [%BaseDir%\Workbench\nativeEx_barebone\Cache\Prebuild\txtsetup.sif0409W2003] to variable: [] with result: [20372]

FileCopy - Copied [C:\Dokumente#$sund#$sEinstellungen\Peter\Desktop\WB#$sArchiv\Beta8\Workbench\nativeEx_barebone\Cache\Prebuild\txtsetup.sif0409W2003] to: [C:\Dokumente#$sund#$sEinstellungen\Peter\Desktop\WB#$sArchiv\Beta8\Target\nativeEx\I386\]
IF [-0409w2003-] is equal to: [--]
IF - File does not exist: [%BaseDir%\Target\nativeEx\I386\txtsetup.sif] evaluated string: [If,ExistFile,%target%\#1,FileDelete,%target%\#1]
IF [-0409w2003-] is equal to: [--]
FileRename - Successfully renamed file: [%BaseDir%\Target\nativeEx\I386\txtsetup.sif0409W2003] to:[%BaseDir%\Target\nativeEx\I386\txtsetup.sif]

Not ok:
QUOTE
Processing section: [CopyToTarget]From file: [%BaseDir%\Projects\nativeEx_core\Basic\Build\3 - hivesFactory.Script]

Retrieve - Sucessfully retrieved the file size from: [%BaseDir%\Workbench\nativeEx_barebone\Cache\Prebuild\txtsetup.sif0409W2003] to variable: [] with result: [20372]

IF [-0409w2003-] is equal to: [--]
IF - File does not exist: [%BaseDir%\Target\nativeEx\I386\txtsetup.sif] evaluated string: [If,ExistFile,%target%\#1,FileDelete,%target%\#1]
IF [-0409w2003-] is equal to: [--]
<a href="http://" target="_blank"></a> FileRename - Failed to rename file: [%BaseDir%\Target\nativeEx\I386\txtsetup.sif0409W2003] to:[%BaseDir%\Target\nativeEx\I386\txtsetup.sif]


As to be seen, the FileCopy is not performed.

@Nuno: Now it's your time! yahoo.gif

Peter cheers.gif

BTW: The back slash at the end of the copy-to is made by the log. It is not in the command.

Posted by: psc Jul 10 2007, 04:52 PM

QUOTE(Nuno Brito @ Jul 10 2007, 05:32 PM) *
Found a reason - look on the interface variables - they are not being converted to variables at all.. frusty.gif

Here is a quick fix for this issue:
 WinBuilder072_Beta10a.zip ( 808.31k ) : 23


Concerning my two previous posts there is no difference between beta 10 and beta 10a.

Peter

Posted by: edborg Jul 10 2007, 05:10 PM

QUOTE(booty#1 @ Jul 10 2007, 04:37 PM) *
Looks like a script of version 0.05 has met the Delphi function IntToStr(). happy.gif

A try-catch block around it should solve this problem, or alternativly switching to StrToIntDef().

booty#1

Right!
Actually, after finding a script version 0.05 and changing it to 005, I could start the program, but subsequentely found numerous errors during the build, that haven't had the opportunity to examine yet.
Amongst others, I have this error for any shortcut that is created: "shortcutWinExp.exe has encountered a problem and needs to close".
edborg

Posted by: Nuno Brito Jul 10 2007, 07:08 PM

QUOTE(psc @ Jul 10 2007, 04:52 PM) *
Concerning my two previous posts there is no difference between beta 10 and beta 10a.

Peter


Thank you - I assume that it can surely be related to the introduction of the new parameter on the fileCopy command on this last beta.

Will either correct or revert back changes to get it working right! smile.gif

Posted by: Nuno Brito Jul 10 2007, 11:19 PM

I've uploaded a new beta 10 b on the first topic - not many changes were done - only tried to correct the reported issue with filecopy - tested it with nativeEx, LiveXP and picoXP (but no emulation - I'm using a RAM limited machine) - please let me know how it works..

btw: Peter, please add Path rules to nativeEx to ensure it won't start with anything less than a XP/2003 source and also help finding a valid source.

cheers.gif

Posted by: edborg Jul 11 2007, 07:42 AM

I've tested Beta 10b on my previously (WB068) working project (not from scratch, as I assume it has already been tested that way smile.gif ).
I've got several blocks during the build on PENetwork, FBWF and FileDisk, with 72 errors logged.
So, I provisionally excluded those three scripts and got no blocks and a booting build. thumbsup.gif

But still 33 errors in log (attached). sad.gif
Amongst them, %Targetsys32% is not recognized as a variable and files (such as calculator) are not copied to it.
A file named "%Targetsys32%" is created instead in the working directory.
edborg

 log.html ( 760.52k ) : 9
 

Posted by: psc Jul 11 2007, 08:24 AM

QUOTE(edborg @ Jul 11 2007, 09:42 AM) *
I've tested Beta 10b on my previously (WB068) working project (not from scratch, as I assume it has already been tested that way smile.gif ).
I've got several blocks during the build on PENetwork, FBWF and FileDisk, with 72 errors logged.
So, I provisionally excluded those three scripts and got no blocks and a booting build. thumbsup.gif

But still 33 errors in log (attached). sad.gif
Amongst them, %Targetsys32% is not recognized as a variable and files (such as calculator) are not copied to it.
A file named "%Targetsys32%" is created instead in the working directory.
edborg

%TargetSys% is removed simultaneously with %PEDrive%.

Use MiscSettings.Script amd MMC.Script from nativeEx_barebone.

Peter

Posted by: Nuno Brito Jul 11 2007, 08:45 AM

Yes, there have been a lot of changes - better try out with a fresh project from the download center.. smile.gif

Posted by: psc Jul 11 2007, 10:05 AM

QUOTE(Nuno Brito @ Jul 11 2007, 01:19 AM) *
I've uploaded a new beta 10 b on the first topic - not many changes were done - only tried to correct the reported issue with filecopy - tested it with nativeEx, LiveXP and picoXP (but no emulation - I'm using a RAM limited machine) - please let me know how it works..

btw: Peter, please add Path rules to nativeEx to ensure it won't start with anything less than a XP/2003 source and also help finding a valid source.

cheers.gif


Beta 10 b is working fine with nativeEx_barebone.

Additional to path rules I added a source OS check to Verify. So only valid XP or W2003 is possible as source.
(I'll upload this afternoon, after I've made some other changes)

Peter

Posted by: Garfield Jul 11 2007, 11:17 AM

I tested the same project with WB072-Beta10b and the result.... yahoo.gif

Posted by: Nuno Brito Jul 11 2007, 11:50 AM

These are very good news, thanks for testing!! smile.gif

I've also spent all morning moving my work files to a new machine and should be able to properly test everything before upload.

smile.gif

Posted by: edborg Jul 12 2007, 07:37 AM

QUOTE(psc @ Jul 11 2007, 10:24 AM) *
%TargetSys% is removed simultaneously with %PEDrive%.

Use MiscSettings.Script amd MMC.Script from nativeEx_barebone.

Peter

OK, I've downloaded a fresh copy of nativeEx_barebone to get those scripts to allow me to run my project with WB 071 Beta 10b.
I now have an error during build (MMC) and three errors in the log (attached), and the same problem with files (such as calculator, paint, etc) not being copied to the system32.
And I no longer understand the logic of the projects to try and debug those errors. mad.gif

I know I could download a fresh project and run it with the last beta, but I'm not prepared to throw away each time everything I've done with my project/scripts and start from scratch to use a newer beta, so I'll give up and stay with what I have. sad.gif
edborg

By the way, I've tested nativeEx_barebone as it is in WB 071B10b, and confirm that it builds fine.

 

 log.html ( 767.16k ) : 3
 

Posted by: Nuno Brito Jul 12 2007, 07:47 AM

I've already spoted where this issue was occuring - it's the interface section that wasn't properly translating variables as expected. There were also some other issues - mostly because there was a big reorganization over the last 5 betas - bugs are everywhere but I think that the next beta should help you get back to good results.

I will upload a new beta right away! thumbsup.gif

Posted by: Nuno Brito Jul 12 2007, 08:07 AM

A fresh beta is available for download on the first topic!! cheers.gif


Formal log of changes:

QUOTE
- 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


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


Been working to solve as many bugs as possible - since the last beta changes on the script engine the road for a stable binary has been quite bumpy but with the help of people posting their results things have been much easier than trying to find all possible bugs by myself.

Whenever a syntax error is found it will be reported on the log.

The unattended part of wb has also been improved and now it also contains a /debug switch to help people evaluate how paths and variables are handled.

Whenever you close wb - it will try to remember wich was the last used project and reopen it on startup - hope this makes life easier for people who use a specific project often (and this way avoid having to select it on each startup)

Last but not least is the Interface recoding - it was necessay to recode from scratch the way how variables were added from the interface section and this has been completed.

From the previous betas it was very dificult to run the projects on qemu on my (very) old laptop, now I've switched to a more recent machine without any of these limitations and this sure helps to speed up things and see what needs to be done.


Thanks for your pacience with these wb beta - really apreciate all the helpfull feedback so far! thumbup.gif

Posted by: edborg Jul 12 2007, 09:07 AM

Thanks, Nuno for your last upload. smile.gif
I've tested 071 Beta11 and have the same error reported above and same errors in log with the new MMC.
Having lost the logic of the various projects, I can't say whether it's MMC or WB though....
However, as you can see, I've not given up yet wink.gif
edborg

Posted by: Nuno Brito Jul 12 2007, 09:59 AM

Please post a new log - I haven't personally been using MMC, but will try it to see how it goes.. smile.gif

Posted by: edborg Jul 12 2007, 10:08 AM

QUOTE(Nuno Brito @ Jul 12 2007, 11:59 AM) *
Please post a new log - I haven't personally been using MMC, but will try it to see how it goes.. smile.gif

I haven't the log anymore, but it was like the one posted above.
edborg

Posted by: Nuno Brito Jul 12 2007, 07:23 PM

Tried all scripts from the liveXP project available on the download center and they work very well - including MMC.

Your log errors happen because of some fixed variables which were removed, as example for %targetsys32% - you can archive the older wb 068 folder and download a fresh copy from the download center from a brand new folder.

This should solve all these issues. cheers.gif

Posted by: edborg Jul 13 2007, 06:37 AM

QUOTE(Nuno Brito @ Jul 12 2007, 09:23 PM) *
Tried all scripts from the liveXP project available on the download center and they work very well - including MMC.

Your log errors happen because of some fixed variables which were removed, as example for %targetsys32% - you can archive the older wb 068 folder and download a fresh copy from the download center from a brand new folder.

This should solve all these issues. cheers.gif

Thanks again.
You're right. The errors are not due to WB, but to the changed syntax that makes many scripts or ini files obsolete.
To adapt them again to the new releases one should have a clear and complete vision of the syntax used and of the use of the various ProjectInfo.ini, script.project, etc, that perhaps should be uploaded together with the executable to ensure consistency. They could be used at least as a sample to show what is needed, which variables are defined, which ones are obsolete and no longer usable, etc.
Actually, losing everything at any new release of WB (or at change in the basic build, which is even more difficult to trace) is quite frustrating! sad.gif
edborg

Posted by: Nuno Brito Jul 13 2007, 09:13 AM

I guess we're all in a learning process until things start being done in a more effective and long term manner.

Maybe you consider joining our effort to create a script standard to add programs to any project - look here: http://boot-land.net/winbuilder/help/scripts/script_application.html

The concept is that you can write your script to add a program and your favorite project can use it without changing a single line of code inside the script itself.

This should make scripts last much longer since they won't be dependable on individual projects.

At the moment some basics were already defined, but still missing some other good features like the ability to write the registry, start services, associate file extensions and such - more help is needed to ensure good results..

What do you think? smile.gif

Posted by: edborg Jul 16 2007, 05:32 PM

QUOTE
[process]
Add_Shortcut,Desktop
Add_Shortcut,AutoStart
Add_Shortcut,StartMenu,Games and Fun
unpack

Are these new macro commands that only work with selected projects based on nativeEX_Core?
edborg

Posted by: Nuno Brito Jul 16 2007, 05:43 PM

The idea is to actually bring them possible to more projects like vistape and any other project in the future - at the moment I'm testing with liveXP, it's where you can run all the available application scripts at this moment.

smile.gif

Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)