Can "Protect Install with Password" be a Variable?

[NewsArchive]

I've tried specifying a constant $PASSWORD$ and variable %PASSWORD%
for the "Protect Install with Password" setting. The correct password
(the value of the constant/variable) does not work. Instead of using
the value of constant/variable, it uses the name of the token itself
as the password. IOW, if I type "$PASSWORD$" into the password field
during installation, it accepts the entry and proceeds. Weird!!!

Anyway, I'm just about to code my own blocking logic in the wizard
loop.

Mike Hanson
www.boxsoft.net

[NewsArchive]

Mike,

"Protect Install with Password" does not support constants or variables. If
you define "%PASSWORD%" then the password *is* "%PASSWORD%".

BTW, if you use a variable as your password in your own logic, I would
suggest to use set $SB_DISABLEEVENTLOGFLAG$ in the "Set Installer Flag"
function to disable the optional installer event logging.

Does this help?

Friedrich

[NewsArchive]

>Mike,
>
>"Protect Install with Password" does not support constants or variables. If
>you define "%PASSWORD%" then the password *is* "%PASSWORD%".
>
>BTW, if you use a variable as your password in your own logic, I would
>suggest to use set $SB_DISABLEEVENTLOGFLAG$ in the "Set Installer Flag"
>function to disable the optional installer event logging.
>
>Does this help?

I've got it working with manual flow control now, using my own
password variables. (I store the passwords in INI files, which SB
fetches into a constant.)

I'll turn on the $SB_DISABLEEVENTLOGFLAG$ setting, to prevent the
password from become obvious in log files and such. Will that have
any impact on the Uninstallation abililties?

BTW, why won't variables work in the password dialog settings? It
seems a little inconsistent.

Mike Hanson
www.boxsoft.net

[NewsArchive]

Mike,

> I've got it working with manual flow control now, using my own
> password variables. (I store the passwords in INI files, which SB
> fetches into a constant.)
>
> I'll turn on the $SB_DISABLEEVENTLOGFLAG$ setting, to prevent the
> password from become obvious in log files and such. Will that have
> any impact on the Uninstallation abililties?

No, absolutely no problem.

> BTW, why won't variables work in the password dialog settings? It
> seems a little inconsistent.

Quite a few developers use something like:

%%HeyYou%%
%%%HEYYOU%%%
%HEYYOU%ME%%COOL%

The runtime has no chance to detect what a runtime-variable is and what not.

So in this specific case, constants and variables are not supported.

Friedrich

[NewsArchive]

Hi Friedrich,

>%%HeyYou%%
>%%%HEYYOU%%%
>%HEYYOU%ME%%COOL%
>
>The runtime has no chance to detect what a runtime-variable is and what not.
>
>So in this specific case, constants and variables are not supported.

Could you have two options:

Password: [same as it is now]
Password Variable [...] select variable

Would be mutually exclusive. That way those silly developers could
have their %HEYYOU% and regular people could have %HEYYOU%
variable?<g>

This would make automation workflow easier.

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

>Could you have two options:
>
>Password: [same as it is now]
>Password Variable [...] select variable
>
>Would be mutually exclusive. That way those silly developers could
>have their %HEYYOU% and regular people could have %HEYYOU%
>variable?<g>
>
>This would make automation workflow easier.

This would get my vote.

Mike Hanson
www.boxsoft.net