22 replies to this topic

[Lancelot]

[process]

Set,%variablefortest%,"32,b0,e8,82,2c,8f,fa,18"

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

RegWrite,HKLM,0x3,WB-Default\Software\ORL\WinVNC3,"Password",e8,82,2c

RegWrite,HKLM,0x3,WB-Default\Software\ORL\WinVNC3,"Password",%variablefortest%

RegHiveUnLoad,WB-Default

This does not work with wb080, I have not find a winbuilder workaround for that.

Found by robinj

Importance Level: +3 depends on development

Edit:
To our scary users. Do not Worry, if such an event happens on build, you get a "Error" on log. As far as I know default selected project build scripts do not contain such lines and mostly application scripts not too. If you find one, post here .

[Lancelot]

....

Well, since i found workaround, I do not care anymore. Further decisions to development.....

edit: in fact i should not even open a topic here, very sorry for opening topic. If development likes, they are free to remove the topic.

[pecd.net]

ouch....this explains a lot here:-(((

[paraglider]

A bug is a bug. Just because you found a work around does not stop it being a bug.

[Lancelot]

I %100 agree paraglider,

as far as you should've notice, I had reported bugs that way so far.

But you should've notice the responds from development even to this topic !!!! don't you ?

Please be my guest, chase bugs to be fixed. Start with convincing development first..... or simply follow what I've done before OR do it your way if you like.

I am exhausted, I hope you can understand.

[pscEx]

A bug is a bug. Just because you found a work around does not stop it being a bug.

Magic wand: (which I always try to hold actual):

RegWrite,HKLM,0x3,Section,Key(Binary),00,01,00

Documentation:

RegWrite,<HKEY>,<KeyType>,<Section>,<Keyname>,<Value>

Where is described that <value> can be an variable?
It is currently not provided.

Maybe a reasonable request, but IMHO no bug!

Peter

[Lancelot]

Where is described that <value> can be an variable?

As seen, Allways is Allways, not sometimes

as written before, I do not care. Have fun.

[paraglider]

If variable substitution is limited to some winbuilder commands and not others then it makes variable use almost impossible. I see no where in the online docs where it says that variables can be used in some function but not others.

How is a developer of scripts supposed to work out which commands can use variable substitution?

As a developer myself I know how easy it is to say that its not a bug its a user error!

[Galapo]

Where is described that <value> can be an variable?
It is currently not provided.

If it's not provided, why does this work?

[process]

Set,%variablefortest%,"test"

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

RegWrite,HKLM,0x1,WB-Default\Software\testkey,"testing",%variablefortest%

RegHiveUnLoad,WB-Default

Like paraglider said, how are we to know which commands support variables and who don't? Trial and error?

Thanks,
Galapo.

[pscEx]

If it's not provided, why does this work?

[process]

Set,%variablefortest%,"test"

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

RegWrite,HKLM,0x1,WB-Default\Software\testkey,"testing",%variablefortest%

RegHiveUnLoad,WB-Default

Like paraglider said, how are we to know which commands support variables and who don't? Trial and error?

Thanks,
Galapo.

You did not understand the issue:

As described in the syntax, the RegWrite 0x3 has as values a list of hex numbers, separated by a comma. ... 03,24,a6, ...
The question was to automagically split ONE variable containing commas, into the paramater list.
But a variable internally is a string, containing no history ...

And when a 0x1 contains a comma? ... Currently it can.

I suggest that you and Paraglider and Lancelot publish a COMPLETE syntax description (addable to the syntax.html) which can be used for ALL cases.

As soon as it is complete and logically w/o any open questions, I'll implement into WB.

Peter

EDIT: Not to be misunderstood: I mean it seriously.

This parameters / variables stuff is so complex, that I did not find a final universal solution yet.

Whenever you make one way posible, you get troubles with another way, which has been open before.

[pscEx]

I found that there is an issue with the command, independent from %variable%

I'm working on that.

(The "Syntax" question is still an issue for me )

Peter

[Lancelot]

And when a 0x1 contains a comma? ... Currently it can.

and can it write a hidden string inside string ?????? (acedemic and no i do not request such thing)

If wb do not support such a feature than no it should not. If comma exists it is between quotes "blabla , blabla" or writtten with escapes blabla#$s#$c#$sblabla

and if wrong 0x1 syntax exists, throw an error saying wrong syntax for transition period.

I suggest that you and Paraglider and Lancelot publish a COMPLETE syntax description (addable to the syntax.html) which can be used for ALL cases.

And this is a tricky question.

syntax html says

RegWrite,<HKEY>,<KeyType>,<Section>,<Keyname>,<Value>

but it should be something like

for single values: RegWrite,<HKEY>,<KeyType>,<Section>,<Keyname>,<Value>
for multi values: RegWrite,<HKEY>,<KeyType>,<Section>,<Keyname>,<Value1>,<Value2>,<Value3>,.....

multi value only supported by REG_MULTI_SZ (0x7)

academically REG_SZ can be a multi value too, reminding I have no request for that since I do not know a reason for that.


every value can be a variable ????? even values inside can contain variable ??? and value may consist of variable inside variable ???

same thing should also apply to HKEY , KeyType , Section , Keyname

These are "natural" rules but If you need to write a rule for these, please write at the bottom of ALLLL syntaxes.

for multistring there are more than 1 value and you agreed with the strick rules.
do not create medusa when fixing
remember post 13


I hope our English origin members can better defination with Good English .

[pscEx]

Fixed.

The real reson was: After resolving the variable, the value has not been written

Peter

[pscEx]

I think cross posting again!

Independent of that, again: I really suggest that you and ??? write the complete syntax for variable use. For me it is too complex and fome features exclude other features.

Peter

[Lancelot]

but IMHO no bug!

Fixed.

The real reson was: After resolving the variable, the value has not been written

Well, it took 13 posts resulting with another success.

@all
As seen from current topic, when more people take part on a specific bug report,
Things turn out from 50 post boxing between psc and me to a 12 post American Gladiator resulting with a successfull fix.
I hope you always remember that

Everybody happy with better wb

[Lancelot]

Crossing a lot tonight psc

Independent of that, again: I really suggest that you and ??? write the complete syntax for variable use. For me it is too complex and fome features exclude other features.

Well, I leave this task to Galapo, paraglider or another member. My english is not sufficient.

[pscEx]

I hope you always remember that

You know that I'm an old man and sometimes have meetings with Mr. Alzheimer ...

Peter

[Lancelot]

sometimes

hihi, allways Peter, allways .

Well I love happy endings which is most important part,
if you remember: when you see Mr. Alzheimer punch him hardly from eye and tell him "This is for Lancelot"

[pscEx]

When I meet him next time I hope that I have not forgotten what you told me now!

Peter

[Galapo]

I really suggest that you and ??? write the complete syntax for variable use. For me it is too complex and fome features exclude other features.

I thought I'd already given a clear statement about this: http://www.boot-land...?...ost&p=89131. Mutatis mutandis, this also applied to 0x3 entries also.

So in the current example, this should throw an error:

[process]

Set,%variablefortest%,"32,b0,e8,82,2c,8f,fa,18"

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

RegWrite,HKLM,0x3,WB-Default\Software\ORL\WinVNC3,"Password","%variablefortest%"

RegHiveUnLoad,WB-Default

This should write correctly to the registry:

[process]

Set,%variablefortest%,"32,b0,e8,82,2c,8f,fa,18"

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

RegWrite,HKLM,0x3,WB-Default\Software\ORL\WinVNC3,"Password",%variablefortest%

RegHiveUnLoad,WB-Default

Regards,
Galapo.

[pscEx]

I thought I'd already given a clear statement about this: http://www.boot-land...?...ost&p=89131. Mutatis mutandis, this also applied to 0x3 entries also.

Unfortunatelly that is not a post which can be copied and pasted into the syntay help file!

Peter

BTW: Your sample in the above post meets my intentions. But do not I feel encouraged enough to implement. That would cause some revolutions about "Back compatibility"

[Galapo]

But do not I feel encouraged enough to implement.

For some reason I suspected that might be said. Which is why I linked to a post rather than drafting "a post which can be copied and pasted into the syntay help file" to save me wasting my time.

Regards,
Galapo.

[Lancelot]

@Galapo,

he does not write syntax page INTENTIONALLY because what ever he hides in his head, this is against it.

For other things he like to FORCE others, he writes to syntax page faster than a Jet Plane.