Windows Titles
I have 4 patches to apply, each one is a stand alone EXE. The vendor who created these did not provide any command line switches for them. So they can't be run in Silent Mode.
When you run any one of these patches they have a Window Title. This Window Title never changes. So when you click Next, Next, Install etc.... the Window Title is the exact same for each new dialog. Because of this I can't use a tool like RoboScript (within WinBatch) to answer each window.
My question is this: How do you automate EXE's like this? If I knew the very last file copied down I guess I could wait until that exists but that seems a bit crude.
How would many of you solve this?
Thank you.
When you run any one of these patches they have a Window Title. This Window Title never changes. So when you click Next, Next, Install etc.... the Window Title is the exact same for each new dialog. Because of this I can't use a tool like RoboScript (within WinBatch) to answer each window.
My question is this: How do you automate EXE's like this? If I knew the very last file copied down I guess I could wait until that exists but that seems a bit crude.
How would many of you solve this?
Thank you.
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Were the original apps supplied in MSIs? If not, I can't see any problem with capturing these to either a single MSI or, if you prefer, discrete MSIs. If they were, only a brain-dead vendor would NOT supply proper WI patches so ask them for the MSPs.
Posted by:
mhsl808
15 years ago
No, they were not written in MSI or MSP format. And we really don't like using Setup Capture's in our environment. Plus these 4 patches are huge and I have noticed that Wise (which we use) bombs out on massive installs when doing a setup capture.
Posted by:
anonymous_9363
15 years ago
I've not encountered any WPS issues with massive installs but, if I had, I'd use a simple snapshot tool e.g. Ziff-Davis's In Control to get a list of folder and registry key changes/additions, then build a script to do the install. Then use a VBS-EXE converter.
My 2 cents...
My 2 cents...
Posted by:
jmcfadyen
15 years ago
have a look at vb script .sendkeys functions.
also AutoIT is pretty handy for messing with UI driven apps its one of the more powerful UI tools around.
also AutoIT is pretty handy for messing with UI driven apps its one of the more powerful UI tools around.
Posted by:
anonymous_9363
15 years ago
Hmmm...myself, I try to avoid the button/key-pressing tools because, as sure as eggs is eggs, they will encounter a dialog or message box which hasn't been catered for with potentially disasstrous consequences.
Posted by:
mhsl808
15 years ago
Yes, I agree about the button pushing method. But if you use Robo Script withing WinBatch it can answer any dialog without pressing the buttons. This is very handy when you push something to a machine using SMS and no one is actually logged in. Script IT and other tools need to see the Window to get the title but Robo script does not.
And for my issue I talk to the developer and they are seeing if they can make their EXE's silent.
And for my issue I talk to the developer and they are seeing if they can make their EXE's silent.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.