I have an InstallShield program. I ran it with a Setup -R to create the Setup.ISS file. I then place that same .ISS file with the Setup.exe and the rest of the source files.
But, when I run Setup.exe -s for a silent install the program installs to a folder called C:\Lawson and once this C:\Lawson folder is filled up with about 16 files *All the files get deleted and the C:\Lawson folder gets removed*!!!

But, if I run Setup.exe *without* a -S the install works fine and the C:\Lawson folder remains in tact the way it should.

Has anyone ever seen the setup.exe -S delete files/folders when it is done running?

I have run this about 10 times on different machines and each time the result is the same, the C:\Lawson folder gets deleted.

Thanks.
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
mqh7,

Is it an MSI based app? I've seen some vendor MSI's where custom actions detect if the installation is silent and if so, do some straaaange things. If its not an MSI based app, then repackage it as one :)
Answered 03/29/2005 by: plangton
Second Degree Blue Belt

Please log in to comment
0
No, it is not a MSI based app. It is a straight Setup.exe that does not create or launch a MSI.
I did a Setup Capture on it and that seems to work....but I hate doing setup captures and they are the last ditch effort.
Thanks.
Answered 03/30/2005 by: mqh7
Senior Yellow Belt

Please log in to comment
0
Look at the installshield site for error codes. There should be a setup.log file. If it returns other than 0 that means something weird happened.
Answered 03/30/2005 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
This sounds similar to a problem I ran into a few weeks ago. Although, I didn't try running the setup without the -s.

I recorded the setup.iss on W2k. The install worked fine on W2k, but uninstalled itself on XP. Then I recorded the setup.iss on XP. The install worked fine on XP, but uninstalled on W2k.

It turns out that I had to record a setup.iss for XP and one for W2k. The only difference was the last dialog. On XP it was listed as SdFinish-0. On W2k it was listed as SdFinishReboot-0.

Very annoying, but workable.
Answered 03/31/2005 by: jdev
Yellow Belt

Please log in to comment
0
Hi mqh7,

I'd be interested as to why you hate capture based captures ... I've got quite a lot of expiereince doing them and to be honest find them to be very reliable, and in some cases more reliable than vendor based setup installations, not to mention the ability to preconfigure settings in the application, and the benefits of self healing etc.

You should definately do your own thing though, I'm just curious as to why you don't like them.

Rgds

Paul
Answered 04/01/2005 by: plangton
Second Degree Blue Belt

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