Hello -

Package with which I am facing issue doesnt allow hiding dialogues in it,its a vendor MSI.
I have to do little customization which is simple- inserting server name and uncheck one checkbox to "Automatically check updates at program startup.
I am creating MST for this application using Installtailor where as required I am unchecking this checkbox,but still when I run MSI along with customized MST this checkbox is auto-selected.
I hv checked properties ,there are two properties:
RTA_CLIENT_AUTO_UPDATE = N (while creating MST when I check for updates its value in MST shows Y and now when I didnt check that box its N)
UIAutoUpdates=1 (When I go to dialogue box and double click property value this is the property which is always set)

I am not sure what extra i should do so that I can successfully Uncheck this checkbox while installation.
These three lines I am copying from ControlEvent table:
Where dlg_auto_upgrade is dialogue box which contain this checkbox.

"dlg_auto_upgrade","btn_next","[RTA_CLIENT_AUTO_UPDATE]","Y","UIAutoUpdates=1","2"
"dlg_auto_upgrade","btn_next","[RTA_CLIENT_AUTO_UPDATE]","N","Not (UIAutoUpdates=1)","1"
"dlg_auto_upgrade","btn_next","[dlg_ready_to_install_bk]","dlg_auto_upgrade","1","3"

Please suggest how do I do it to uncheck this checkbox.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
are you checking the installation in UI mode ?
try installing MSI with MST in silent mode and check log file ... what does your property hold ?
Answered 04/21/2010 by: mekaywe
Brown Belt

Please log in to comment
0
try setting the property UIAutoUpdates=0 in your MST
Answered 04/21/2010 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
I checked with setting UIAutoUpdates=0 in MST but it didn't work.
Answered 04/21/2010 by: raviray
Orange Belt

Please log in to comment
0
This application can't be installed with /qn switch (Completely silent)
but I will check with /qb (that works) and will tell you.
Answered 04/21/2010 by: raviray
Orange Belt

Please log in to comment
1
How did you set the property, though? Many apps have Custom Actions which set properties to the required default (in effect ignoring the Property table value) so, if you just changed the Property table's value, it might be ignored anyway. Try a Type 51 Custom Action in the UI sequence.

Also, since the values are being set in the UI, they will be completely ignored in any silent - or partially silent - install. So, if your ultimate aim is to install totally silently, you should verbosely log the install and see what the public property RTA_CLIENT_AUTO_UPDATE gets set to. Once you know that, use that property instead.This application can't be installed with /qn switch (Completely silent) Unlikely. I have yet to see an MSI which couldn't be installed silently. It might take some work to force it into cooperating but it's certainly possible. Normally, this means that the package author has a bunch of CAs in the UI sequence which he/she was too stupid or ignorant to copy into the Execute sequence (or force to run at least once).
Answered 04/21/2010 by: VBScab
Red Belt

Please log in to comment
1
This is what I found in logs:

MSI (s) (E0:30) [17:14:40:207]: Doing action: IcaInitSetup
Action ended 17:14:40: CostFinalize. Return value 1.
MSI (s) (E0:30) [17:14:40:207]: Transforming table CustomAction.
MSI (s) (E0:30) [17:14:40:207]: Transforming table Binary.
MSI (s) (E0:0C) [17:14:40:285]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI202.tmp, Entrypoint: IcaInitSetup
Action start 17:14:40: IcaInitSetup.
MSI (s) (E0!90) [17:14:48:834]: PROPERTY CHANGE: Modifying ABC_SRVR_NAME property. Its current value is 'ABCXYZ123'. Its new value: 'ABC123'.
MSI (s) (E0!90) [17:14:48:850]: PROPERTY CHANGE: Modifying ABC_SRVR_IP property. Its current value is '10.XXX.AB.ZZ'. Its new value: '10.LMN.OP.QR'.
IcaInitSetup {
Is new install, maintenance run, or minor upgrade. Installdir resolved internally.
MSI (s) (E0!90) [17:14:48:865]: PROPERTY CHANGE: Adding UIAutoUpdates property. Its value is '1'.
MSI (s) (E0!90) [17:14:48:865]: PROPERTY CHANGE: Modifying ABC_CLIENT_AUTO_UPDATE property. Its current value is 'N'. Its new value: 'Y'.
No ABC server IP was read from the SocketClient2_1 key. The string was null. Server name and IP properties were not set.
}

how should I go about this!!
Answered 04/21/2010 by: raviray
Orange Belt

Please log in to comment
1
from the log it looks like Ian (vbscab) was correct, it's set by a custom action
disable IcaInitSetup (set its condition in the InstallExecuteSequence to 0 or use the remark feature in the wise UI)
it's good that you caught this....reading the logs is a necessary part of windows installer troubleshooting
Answered 04/21/2010 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
Create Entry in Control Event table of MST for the given properties and assign the Value "{}" and delete those respective properties from Property Manager.

RTA_CLIENT_AUTO_UPDATE ={}
Answered 04/22/2010 by: sushantnarlawar
Yellow Belt

Please log in to comment
0
yeyeyeye..
am so happy..it worked and this time checkbox was unchecked.

Thank you to both of you for quick response.
I was thinking if Ian you could suggest me in direction to make it completely silent..
I would really like to solve this as well.
Answered 04/22/2010 by: raviray
Orange Belt

Please log in to comment
0
As I already mentioned, you'll probably find CAs in the UI sequence which do not appear in the ExecuteImmediate Sequence.
Answered 04/22/2010 by: VBScab
Red Belt

Please log in to comment
0
yup i'm thinkin' the same thing as vb, some kind of Custom action. sometimes you can get a clue by the name, in the checkbox it was IcaInitSetup but even if the names are totally meaningless you can see what it's doing of you do a verbose log like for the checkbox issue.
Grasshopper, you have now ascended to the next level of windows installer, LOL. [:D]
Answered 04/22/2010 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
Me Grasshopper [8|]..ok I will take as compliment..
So here is good news(atleast for me). I found two custom actions which had this condition
(UILevel=2) or (UILevel=3) and (UG_ABC_CLIENT_PATH) and not (UG_ABC_SRVR_PATH)
due to which it was not getting installed completely silent.
I removed it and now I am able to install it completely silent.

Thank you
Answered 04/22/2010 by: raviray
Orange Belt

Please log in to comment
0
What did you remove, the entire condition? Bad idea, if you did. Just remove the 2 'UILevel' elements.
Answered 04/22/2010 by: VBScab
Red Belt

Please log in to comment
0
grasshopper is a ref to the Amreical show kung fu during the 70s...."grasshpper, when you can take the pebble from my hand..."
anyway, look up UILevel as VB suggests and make sure it won't mess up something you need.
Answered 04/22/2010 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
If in these two custom actions I only remove these UILevel element and not entire condition and click on build and then click ok(In condition builder) it gives me following warning
"There were errors detected in the expression.
Are you sure you want to exit the dialog?"

Is there anything wrong in following expression?
(UG_ABC_CLIENT_PATH) and not (UG_ABC_SRVR_PATH)
Please suggest,
Answered 04/23/2010 by: raviray
Orange Belt

Please log in to comment
0
you prolly entered it wrong. i'd say make the condition 0 (don't run) and you don't have to fuck with it.
ah think what VB meant was don't remove all conditions (IE dont' let it run always).
you prolly did the right think removing it
Pace!

peace and good will amongst men.
Answered 04/23/2010 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
I can't recall exactly but I think Condition Builder is somewhat pedantic about syntax. It may be whining because you have no equivalence check for the properties, e.g something like:

(UG_ABC_CLIENT_PATH > "" ) and not (UG_ABC_SRVR_PATH > "")

whereas the engine itself doesn't care. Run it and see what happens.
Answered 04/24/2010 by: VBScab
Red Belt

Please log in to comment
0

(UG_ABC_CLIENT_PATH > "" ) and not (UG_ABC_SRVR_PATH > "")
whereas the engine itself doesn't care. Run it and see what happens.


I tried it and got same error and then I didnt make any change in existing condition (same as vendor msi) and clicked on build ...just to see if this gives error in expression or not and it did.

Why did it give error in existing expression as well?
Answered 04/26/2010 by: raviray
Orange Belt

Please log in to comment
0
(set its condition in the InstallExecuteSequence to 0 or use the remark feature in the wise UI)

Isn't this remark functionality present in Wise Package Studio 7 Standard Edition?
Answered 04/26/2010 by: raviray
Orange Belt

Please log in to comment
0
All that WPS does when you add a remark is to add a condition of '0'. So, for example, your original query would change from:

'(UILevel=2) or (UILevel=3) and (UG_ABC_CLIENT_PATH) and not (UG_ABC_SRVR_PATH)'

to:

'0 AND (UILevel=2) or (UILevel=3) and (UG_ABC_CLIENT_PATH) and not (UG_ABC_SRVR_PATH)
Answered 04/27/2010 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity