setup -s not working
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.
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
Answers (5)
Please log in to answer
Posted by:
plangton
19 years ago
Posted by:
mqh7
19 years ago
Posted by:
aogilmor
19 years ago
Posted by:
jdev
19 years ago
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.
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.
Posted by:
plangton
19 years ago
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
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
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.