To automate installation of software on Windows, it's best to make MSIs out of your installers. This way the domain controller can just push out your installs. There are some programs available on the internet to take a snapshot of the machine before and after an install, and can make an MSI for you if the software doesn't come as one.
<blasphemy>It's SOOO much easier than hacking around with Perl.</blasphemy>
(Yes, blasphemy, but IMHO, use the right tool for the right job.) | [reply] |
Blasphemy? Are we going to tell Red Hat users to stop using rpm and Debian users apt-get? Using the preffered packaging tools on a platform is just common sense. Even ActiveState Perl has an MSI installer. Blapshemy would be recommending Python or Ruby! ;-)
| [reply] |
Of course the real question is would recommending Haskel be blasphemy?! ;-)
| [reply] |
Being a proponent of the mantra "the best tool for each job", I'm inclined to agree with archfool. If that's an option, it would be substantially easier.
__________
Systems development is like banging your head against a wall...
It's usually very painful, but if you're persistent, you'll get through it.
| [reply] |
It's obvious English isn't your first language, so your question is a bit hard to understand, but let me give it a try: You're trying to execute an external application "setup.exe", via the perl builtin system function, and you want to interact with it?
If thats the case, then it depends on the interface of the setup application...Is it a command line (CLI) or graphic (GUI) interface? If it's CLI, then you can use IPC::Run (or a similar module) to script interactions with it. If it's a GUI, you may be able to use something like Win32::CtrlGUI, though I have no experience with anything like that, so I can't elaborate any further.
__________
Systems development is like banging your head against a wall...
It's usually very painful, but if you're persistent, you'll get through it.
| [reply]
[d/l] |
For the GUI side of things it may also by worth having a look at Win32::GuiTest.
| [reply] |
Most GUI installers also have a "silent" operation mode. In this mode, they can be run as a simple CLI executable and take user inputs from a pre-populated input file. Use this option if it is available.
C:\setup.exe -i myinputfile
Alternately, if you are planning to use Win32::GuiTest, then using a tool like Winspy-- will reduce the development effort.
Mahesh
| [reply]
[d/l] |
Thank you all.
I will am very glad to see all messages.
All your messages bosted my knowledge level.
Thank you ones again.
I am using a "Win32::Process" module. | [reply] |