/build/static/layout/Breadcrumb_cap_w.png

Software Deployment Question


setup.ini options

10/10/2016 757 views
Hi All,
I have an application I am packaging, it is a fantastic exe installer that calls on an internal exe file with a number of dll, cabs and one MSI with the prerequisites in it, but nothing in the tables of use.  Because of the MSI inside, I can't repackage the legacy install, the software then doesn't do what it was written for, downloading vehicle firmware.
Awesome!! 
Problem I would like to fix is, it keeps putting a desktop icon on the Public Desktop.  I can't find a list of changes I can make in the setup.ini to remove the shortcut.  
Does anybody have a list, or know where I can find a list of setup.ini properties.  I have tried a few things found on the Google, but nothing works so far.
The installation does not have a desktop shortcut question, so I can't put it in to the ISS file.

The only other option I have is to remove the shortcut last up in the install vbs, but wanted to know more about the ini options for future packages.  I am always trying to find the best way of doing things.

Thanks in advance

Answer Summary:
0 Comments   [ + ] Show comments

Comments


Answer Chosen by the Author

1
>of the MSI inside, I can't repackage the legacy install
Why not? Extract the MSI and then install it before you run your repackaging capture. WI will then see that the product is installed and do nothing.
Answered 10/10/2016 by: anonymous_9363
Red Belt

  • VBScab - sometimes you just need a new head to get you back on track. Thanks
    I had spent so long on the first EXE file, because the app requires a hardware dongle I didn't have until the other day, then working out the first exe was a compressed exe, dll's and another MSI, I was so single minded on not repackaging the MSI and working with the vendors installer.
    I didn't think of it until I got home, about the time I got the email advising I had a response from my question.

All Answers

0
To answer your original question, SETUP.INI - like many similar installer-directive files - is quite crude and doesn't offer that level of granularity. I always re-package legacy installers anyway, since I like to know what nightmares the vendor is attempting to visit on my clients' workstation estates.
Answered 10/11/2016 by: anonymous_9363
Red Belt

  • lol - thanks.
    by the way, the original MSI package didn't work because of the MSI in the compressed exe, but it worked after I took the MSI out. VBS'd the installer and it all works now.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ