how to put a text string in a control using cmdline

[TBBW-II]

Hello,

how do I put a text string in a control using cmdline?
this is the control:

CONTROL "", 1304, EDIT, ES_LEFT | ES_UPPERCASE | WS_CHILD | WS_VISIBLE | WS_BORDER | WS_TABSTOP, 58, 91, 44, 12

regards,

ger

[RobertDickau]

For an InstallScript-based dialog box (pure InstallScript or InstallScript MSI, as this appears to be), you can use CtrlSetText in custom dialog code. For Basic MSI, you can use [PROP_NAME] to expand a property.

Please see the help for CMDLINE for how to read custom data passed to an InstallScript-based setup.exe.

[TBBW-II]

Dear Robert,

thank you for your reply!
I read all the cmdline info. but it does not getting me anywhere...... sorry
what is the exact call
setup.exe /V"control1304="TEST"
or
setup.exe /V"dialogname.control="TEST"
or
setup.exe /V"controlID_1304="TEST"
or
......

hope to hear from you soon.

regards,

ger

[RobertDickau]

For a Basic MSI project, there's setup /V"MYPROP=Something", where MYPROP is the property used by a control.

For an InstallScript dialog, however, there's no similar direct path. For InstallScript MSI (which your question appears to be about), you can use setup /V"MYPROP=Something", and then your script can use MsiGetProperty to read the MYPROP property value, then feed it in to the dialog box.

[TBBW-II]

Hello Robert,

Thanks again for your reply!
I think I was not clear enough about my "problem" my mistake. Sorry about that.
I'm working on third party installer.
(setup.exe in combi with install.msi creating a DLL )
what I what is, to put name/company/serial/etc/etc
in a setup.ini file.
so I can walk away when the program installs.
I'm unable to retrieve property names, so I'd like to shoot the
requested data directly into the appropriate window(s), if this is possible...


regards,

ger

[RobertDickau]

As far as built-in functionality goes: If it's an InstallScript MSI project, please see the "silent install" help information, where you can run the installer in record mode to save a set of answers into a file that you later feed back to an installer.

For MSI dialogs, perhaps create an MSI log file to see the properties you want to populate?

[TBBW-II]

Robert,

I tried the silent/record mode.
It only works half, as soon as user input is required the slient mode stops.
also the rest of the install is not silent any more.

I will have a go with the log option.

apart from the above.
If a property has a value, is the value of the property allways shown?
example property COMPANY_NAME is nill, the input window is blank, the
user has to input the name by keyboard.
when I assign in the setup.ini file the variable/property COMPANY_NAME with
a value like COMPANY_NAME="Wolf Software INC."
is this value allways shown, when the respective windows is called?

regards,

ger

[TBBW-II]

Robert,

logging does not work.

there should be a way to insert a text string directly into the dialog control(s)
in my opinion there is no diff. between the keyboard or a file string.
how about the function SENDMESSAGE() in combination with FINDWINDOWEX()

or other suggestions......

regards,

ger