Honeywell EBI R310.1
Hi ,
I am working on this application and it has got 76 msi's in it. so we thought of creating a wse script with the silent installation(with the help of .ISS file).
everything is working fine except a screen which pops up asking for click on next. even if we give complete silent install this screenpops up. upon closing this screen application continues to install. hence we are trying to close this screen using vb script in the wse script.
so while we are executing the exe it should execute the vb script also simultaneaously . the pause command is taking more time in the process and doesn't allow the exe to install and hence we are not able to close the pop up screen by the help of vbscript.
item:
Check if File/Dir Exists
Pathname=C:\Temp\HoneyWell.txt
Title=abc
Flags=00000101
end
item: Execute Program
Pathname=C:\Honeywell\R310.1\Sources\Server\SETUP.EXE
Command Line=-s -f1C:\Honeywell\Honeywell.iss
end
remarked item: Custom Script Item
Filename=Pause.wse
Variable Name1=_PAUSE_TIME_
Variable Value1=120000
Variable Name2=HELPFILE
Variable Value2=\\brawisepac001\Wise Package Studio\WiseScript Editor\Wise32.HLP
end
remarked item: Check if File/Dir Exists
Pathname=C:\Temp\Confirmation.txt
Title=abc
Flags=00100111
end
item: Execute VBScript
Pathname=C:\Honeywell\close.vbs
end
remarked item: End Block
end
item: Copy Local File
Source=%INST%\HoneyWell.txt
Destination=%TMP%\HoneyWell.txt
Flags=0000000111000010
end
item: Else Statement
end
item: Remark
end
item: End Block
end
this is the vb script we have used to close the popup window:-
Set shell = createobject("wscript.shell")
Do
success = shell.appactivate("Confirmation")
If success Then
shell.sendkeys "%{F4}" '...maximize
End If
Loop While Not success
I am working on this application and it has got 76 msi's in it. so we thought of creating a wse script with the silent installation(with the help of .ISS file).
everything is working fine except a screen which pops up asking for click on next. even if we give complete silent install this screenpops up. upon closing this screen application continues to install. hence we are trying to close this screen using vb script in the wse script.
so while we are executing the exe it should execute the vb script also simultaneaously . the pause command is taking more time in the process and doesn't allow the exe to install and hence we are not able to close the pop up screen by the help of vbscript.
item:
Check if File/Dir Exists
Pathname=C:\Temp\HoneyWell.txt
Title=abc
Flags=00000101
end
item: Execute Program
Pathname=C:\Honeywell\R310.1\Sources\Server\SETUP.EXE
Command Line=-s -f1C:\Honeywell\Honeywell.iss
end
remarked item: Custom Script Item
Filename=Pause.wse
Variable Name1=_PAUSE_TIME_
Variable Value1=120000
Variable Name2=HELPFILE
Variable Value2=\\brawisepac001\Wise Package Studio\WiseScript Editor\Wise32.HLP
end
remarked item: Check if File/Dir Exists
Pathname=C:\Temp\Confirmation.txt
Title=abc
Flags=00100111
end
item: Execute VBScript
Pathname=C:\Honeywell\close.vbs
end
remarked item: End Block
end
item: Copy Local File
Source=%INST%\HoneyWell.txt
Destination=%TMP%\HoneyWell.txt
Flags=0000000111000010
end
item: Else Statement
end
item: Remark
end
item: End Block
end
this is the vb script we have used to close the popup window:-
Set shell = createobject("wscript.shell")
Do
success = shell.appactivate("Confirmation")
If success Then
shell.sendkeys "%{F4}" '...maximize
End If
Loop While Not success
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
- Please use the CODE tags (accessible using the button marked '<%' when posting lengthy text like this. It makes the thread easier to view in its entirety.
- Much better than trying to press buttions programmatically (using whatever technology, VBS, AutoIt, whatever) would be to stop whatever causes the message to appear. I suspect one of the MSIs is calling an executable. Executing your MSIs with a verbose log should tie that down. As soon as the message box appears, open the log: the last entry should indicate whichever Custom Action is executing.
- Much better than trying to press buttions programmatically (using whatever technology, VBS, AutoIt, whatever) would be to stop whatever causes the message to appear. I suspect one of the MSIs is calling an executable. Executing your MSIs with a verbose log should tie that down. As soon as the message box appears, open the log: the last entry should indicate whichever Custom Action is executing.
Posted by:
Inabus
15 years ago
Alternativly go back to the vendor and tell them to package properly and not use 76 MSI.s :)
P
P
Posted by:
anonymous_9363
15 years ago
Business Objects, anybody? 2,737 CAB files... No wonder WPS chokes on this MSI!
Posted by:
MSIPackager
15 years ago
Business Objects, anybody? 2,737 CAB files... No wonder WPS chokes on this MSI!
Yup this package is a joke.. but it's these that separate the men from the boys [8|]
Posted by:
Inabus
15 years ago
hehe yeh, I would scream at it and snapshot it into a single cool msi that worked :p
P
P
Posted by:
anitha_accen
15 years ago
Hi Everybody,
Did anyone packaged this application successfully?
Did anyone packaged this application successfully?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.