Software Deployment

Google for 'installshield +response +file'

Even better would be to forget about this unreliable and very old method altogether and repackage it into an MSI.

Oink, flap...

i gets it! :-)

Vbscab,

I know what is command to run setup.exe silently with .iss file and that setup.exe /s f1"c:\test.iss"

I have gone through all way including Google serach, but not able to find desired information.just wanted to know that using above mentioned command I sucessfully created ISS file but now i want to exceute but dont want to use /s command because wanna to see whether whatever Dialog information I had captured using .iss file whether it is getting applied in accurate manner or not.so please advise if you know it...

Aogilmor,

Ii can understand your perception but as we all aware that we can't take capture for Vendor MSI.so i created response file to capture all the dialog changes so i created response file sucessfully but now i want to check whether all the Dialogs captured correctly or not.so i dont want to run silently using /s command please suggest me how to resolve this issue.

Please note that this is a setup.exe which has vendor msi embedded in it.. which itself cannot installed the application...when try to run that msi it gives mesage that you need to run setup.exe...I even tried to put ISSETUPDRIVEN=1 property but even this is not helping..

let me know you kind comments in this...

As far as I know, the only way to achieve (almost) what you want is to pass the argument to have the WI engine create a log file. I'm sure the argument for that is documented somewhere.

As a side benefit, the resulting log will show you the command line which is being passed to MSIExec. That command line will contain the property which indicates that the install is being controlled by the EXE. BTW, a growing number of MSIs I see use a property called SETUPEXE, as in "SETUPEXE=SETUP.EXE" and it is this property which is tested.

Also - no offence - but can you see how you have effectively wasted a day by not explaining in full what it is you want to achieve? If you had stated the exact problem in your first post, you'd be a lot further on by now.

yeah, what vb said.
also, if it is a vendor MSI wrapped in an EXE you were perceptive in using ISSETUPDRIVEN. As Ian alludes to, I've also found MSI's with various conditions in them etc. which could stop it from being installed. verbose logging should help in this case coz it'll tell you exactly where the installation is failing and you can then edit the MSI enough to get it to run. sometimes i'd go with the vendor EXE and command lines (supported) versus hacking the MSI myself, unless there's an overwhelming reason to do so.