HELP!
Logitech IO2 software is driving me up the wall...!
It has a setup.exe which then launches an MSI.
Simple enough you would assume.... think again.

The usual Installshield switches do not all work on the setup.exe file. For example the /r to capture the ISS file does not work, nor does the /v to pass switches onto the MSI.
When you try to launch the MSI directly you get the usual "This installation cannot be run by directly launching the MSI package. You must run setup.exe".

I've reached the end of my expertise and have no other alternatives to try. I need this application to install silently for users.
Logitech has not been able to help at all.
My only alternative seems to be to use Wise Package Studio to create a new MSI which would be a pity considering that it already is provided with an MSI!!

The software can be found here:
http://www.logitech.com/index.cfm/downloads/software/US/EN,CRID=1808,contentid=9430
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
look at the custom actions. you may be able to remove/silence the custom action that forces the setup.exe to be used.

if that fails, try adding the property ISSETUPDRIVEN = 1 (or 0).
Answered 04/06/2006 by: dm1
Blue Belt

Please log in to comment
0
by the way...don't use wise to create a new MSI. create a transform to apply your changes.....
Answered 04/06/2006 by: dm1
Blue Belt

Please log in to comment
0
Thanks for the advice dm1. That works great and the MSI runs silently without any Tranform.

I did try to create a Transform but as soon as you use InstallTailor to do this it gives the same problem about having to run setup.exe.
If I edited the MSI directly, when it comes to compiling the package I got loads of Merge Module errors (probably because I didn't have the source files for the required Merge Modules?).

So in the end I just used VBS to clean up where the application shortcuts go.

Thanks again for your help.
Answered 04/06/2006 by: philley
Senior Yellow Belt

Please log in to comment
0
hey no problem, i had the same issue many times previously.

you really shouldn't edit the vendor's MSI directly as you may introduce errors along the way, and it's kind of against best practices. you may also invalidate any vendor support.

You could try generating the MST via Orca, its a very simple process and you'll keep your vendor MSI intact should you want to make changes in the future.

Best of luck,

D.
Answered 04/06/2006 by: dm1
Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity