16 replies to this topic

[pscEx]

Download URL: http://www.boot-land...?...st&p=100442
Really important news here are:

1. Using a variable as a macro is not longer accepted.

Set,%MyMacro%,Run,AnyScript,AnySection

%MyMacro%

will cause an error.

2. System constants cannot be changed PERMANENT

Set,%ISOFile%,MyFile

Set,%ISOFile%,TempFile,GLOBAL

is ok.

Set,%ISOFile%,NewName,PERMANENT

will cause an error.

Changes since WB 081 Beta 1:

fixed - Bug in RegWrite,HKLM,0x1,WB-Setup\Classes\SHCmdFile\shell\open\ddeexec,,"[ShellFile(""%1""#$c""%1"",%S)]"
fixed - Bug in StrFormat,Rtrim
changed - %variables% as macros temporarily tolerated with log warning. In stable version this will be an error.
fixed - Parameter existing only of 2 quotes now becomes empty
fixed - Do not write surrounding quotes into variables when reading the [variables] section
fixed - resolve escapes to character in If command compares
fixed - (Finally) Do not write surrounding quotes into variables when reading the [variables] section
fixed - resolve escapes to character in If,QUESTION
fixed - several 'surrounding quotes' bugs in If command
added - menu entry in magic wand: copy complete command list to clipboard
rewrote - If command
fixed - log output for If commands
fixed - Bug in PackParam
fixed - Bug in RegWriteBin
changed - fine tuning of RegRead and RegReadBin commands
fixed - Incompatibility of GetParam, introduced by the bug fix of PackParam
addded - System,LOG,OFF / System,LOG,ON commands
fixed - Bug in StrFormat when writing result to parameter #n
fixed - Bug in log.html generation causing 'Index out of bounds' when logging a Loop command
fixed - Bug causing 'Access Violation' in interface
changed - Errors supressed by System,ERROROFF are now shown in Debug Log as 'Handled Errors'
added - icons for log.html can be optionally in %BaseDir%\Pictures, bypasses download
fixed - Bug in interface due to values with quotes
fixed - Bug in running section on CheckBox click
fixed - Bug in Interface Click event handling
fixed - Bug in If command, when comparing numerical values
changed - some cosmetics in output of log.html
fixed - Bug in OUT: parameters handling

Peter

[paraglider]

Set,%ISOFile%,TempFile,GLOBAL

is not ok. Gets the same error as:

Set,%ISOFile%,TempFile,PERMANENT


This breaks the win7pe_se project:

[Failed] (00-5_ISO_Name_Dynamic.script) Set - You cannot set WinBuilder system variables GLOBAL or PERMANENT: [%ISOfile%=%BaseDir%\ISO\7PE_SE_x86.ISO]

[Galapo]

Is there now a new certification method? I ask this because every script is reporting this: "Script has an expired certification!". This is even for recently certified scripts.

Thanks,
Galapo.

[pscEx]

Set,%ISOFile%,TempFile,GLOBAL

is not ok. Gets the same error as:

Set,%ISOFile%,TempFile,PERMANENT


This breaks the win7pe_se project:

[Failed] (00-5_ISO_Name_Dynamic.script) Set - You cannot set WinBuilder system variables GLOBAL or PERMANENT: [%ISOfile%=%BaseDir%\ISO\7PE_SE_x86.ISO]

Simpli use a different variable.

E.g. in nativeEx there is already since half a year %BurnISO%.

Peter

[pscEx]

Is there now a new certification method? I ask this because every script is reporting this: "Script has an expired certification!". This is even for recently certified scripts.

Thanks,
Galapo.

There is a new certification program, I'm still working with.

It will be ready with publishing of WB 082.

It checks some important WB 080 rules.

Peter

[Galapo]

There is a new certification program, I'm still working with.

Will that be obtained via Lancelot as before?

Thanks,
Galapo.

[Galapo]

Also, will the new WB upon release be backwards-compatible with the old certification mechanism? Or will every script in a project today have to be re-certified for use with the new WB?

Thanks,
Galapo.

[pscEx]

Also, will the new WB upon release be backwards-compatible with the old certification mechanism? Or will every script in a project today have to be re-certified for use with the new WB?

Thanks,
Galapo.

WB 082 knows 4 different certification status:
certNone
certOK (valid 82 certification)
certExpired (valid pre-82 certification)
certInvalid

Peter

[Galapo]

certExpired which writes into the log as "Script has an expired certification!" is misleading if it is indeed validated as a successful older certification.

Better I think to have something like:

certOldOK (valid pre-82 certification) which writes something like this into the log: "Script validation sucessful under pre-82 certification".

Also, do we obtain the new certification program via Lancelot as before?

Thanks,
Galapo.

[pscEx]

certExpired which writes into the log as "Script has an expired certification!" is misleading if it is indeed validated as a successful older certification.

Better I think to have something like:

certOldOK (valid pre-82 certification) which writes something like this into the log: "Script validation sucessful under pre-82 certification".

Also, do we obtain the new certification program via Lancelot as before?

Thanks,
Galapo.

#1:
I changed the message text to
!#2492=Script has a valid pre-82 certification
It will be in the next publication.

#2:
For me is Lancelot not longer reliable.

Peter

[Galapo]

!#2492=Script has a valid pre-82 certification

That suits me fine.

For me is Lancelot not longer reliable.

That is a truly inaccurate assessment. I guess by "Lancelot not longer reliable" you really mean "I don't like Lancelot anymore".

I say this because Lancelot has demonstrated on these very forums reliability and dependablity time and again. Indeed, it was because of these character traits that I invited him onto LiveXP development. And over the last couple of years, his work in maintaining and developing the project has evidenced much reliability and dependablity. Check the LiveXP changelog for Lancelot's dedicated committment and reliability. I would say Lancelot is one of the most reliable people I know. If he says he'll do something, he'll carry through and do it. He can be relied upon to start and complete a task. He can think ahead and work out solutions to complex project issues (sometime brought about by a new WB stable not being backwards compatibile upon release with previous scripts, no less!). He is a team player and someone any team would value his contribution.

Regards,
Galapo.

[pscEx]

I mean "I do not trust him any more".

And that's my personal feeling, independent from the feeling of different people.

Peter

[Galapo]

Well, that equates to much the same thing. But "feelings" don't always have a correlation with "fact". Because the fact is that Lancelot has consistently demonstrated trustworthiness on these forums.

Regards,
Galapo.

[paraglider]

When you produce the new certify.exe please also produce a new version of pscCert.dll

[pscEx]

When you produce the new certify.exe please also produce a new version of pscCert.dll

Stored in my 'ToDo'

Peter

[pscEx]

Stored in my 'ToDo'

Peter

I saw that it is already in the project build group.

The attached dll should work like previously with new certStatus

type

  certStatus = (certUnknown, certNone, certOK, certInvalid, certExpired);

Peter

 pscCert.zip   52.65KB   434 downloads

[paraglider]

Thanks.