No replies to this topic

[pscEx]

Like Jaclaz suggested, starting with version 075 beta 5 WinBuilder has a new option which can be set in the 'Options' pane.
 options.gif   22.21KB   80 downloads
If this option is set:
Whenever during build an error occurs, the build is aborted immediatelly.
Two exceptions:

• An error immediatelly following a 'System,ERROROFF' statement, is not treated as error and therefore the build continues
• If there is an open hive, the remainder of the script is scanned (but not executed) until the corresponding RegHiveUnload occurs.
  This RegHiveUnload is executed. Then the build is aborted.

Here a sample:

[variables]

	 

	 [process]

	 RegHiveLoad,"WB-Default","%target_sys%\config\default"

	 StrFormat,INC,%var%,1

	 Set,%x%,a

	 Echo,"No Error Occurred"

	 RegHiveUnLoad,"WB-Default"

	 Echo,"Everything done"

Because %var% is not defined,

StrFormat,INC,%var%,1

will bring an error.

Here the result:

Processing section: [process]
File [%BaseDir%\Projects\nativeEx_barebone\CodeBox.txt] Version [1]
RegHiveLoad - File: [%BaseDir%\Target\nativeEx\I386\System32\config\default] Section [WB-Default]
StrFormat - Failed to convert [%var%] because [%var%] value is not valid:
Halt
RegHiveUnLoad - Unloaded registry hive: [WB-Default]
Finished processing script: CodeBox test
Script time: 265 miliseconds
Script has been sucessfully processed!

In WinBuilder.exe the 'Stop Build on Error' option is intentionally switched on by default.

Usually an error causes that the PE is different from that what you are waiting for.

'Smaller' errors like trying to delete a non-existant directory, must be avoided by the .script developer.

BTW: This new feature is included in the next 'Nightly Build'.

Peter