ExecWait + InstallShield v11 and v12 question

o_owd · 31st December 2007, 09:57

Hello,

I have a problem with my installer. Actually the problem is not ExecWait. Let me explain.

I have my installer (NSIS) that must wait for a InstallShield setup and an update for that InstallShield setup. The update is InstallShield. I have three installers like this. Two of them must wait for v11 InstallShield and the third for a v12 InstallShield.
When I run my installer from the HDD everything works as it should. ExecWait works.
If I try the same thing from a CD/DVD it does not work.
Probably InstallShield launches a new process because it cannot write anything on the CD/DVD.?! Anyway, this is my logic.
As I said, I do not believe it is a ExecWait problem.

What can I do ? I searched in TEMP folder after I started the InstallShield setup and I cannot find any .msi file.

Sorry for the long post and sorry for my english.
Thanks in advance,
OJi.

Afrow UK · 31st December 2007, 10:24

What about command line switches?

Stu

o_owd · 31st December 2007, 10:36

What command line switches ?

I do not want to make a unattended install. The user must select options/configs from the IS setup.

I found in NSIS wiki "Check whether your application is running during uninstallation". This can help me. I can check if IS is running or not. But the part where IS is starting and I have only a progressbar - "IS is loading bla bla bla...". This part does not have Name/Class.

Thanks,
OJi.

Afrow UK · 31st December 2007, 11:05

You need to find out if there is a command line switch to stop it running as another process.

If there are none, the next option is to keep checking for a running process using FindProcDLL or Processes (both of which however do not work on Vista apparently).

Stu

kichik · 31st December 2007, 16:58

More in the FAQ about installers fails with ExecWait:

http://nsis.sourceforge.net/When_I_u...esn't_wait

o_owd · 1st January 2008, 16:04

Hello,

I already checked that page. It does not help me.

Thanks anyway,
OJi.

kichik · 1st January 2008, 16:40

Did you try /SMS?

o_owd · 1st January 2008, 17:23

Yes, I did. Nothing happened. The new process was launched.

Thanks,
OJi

kichik · 1st January 2008, 17:29

If it's only from CD, copy to $TEMP prior to execution.

o_owd · 1st January 2008, 17:32

I cannot. I need to do this three times. First installer has 1.4 GB, second 500 MB and the third 1.3 GB. I will search more about InstallShield functionality. If I find something usefull I will post it here.

Thanks again,
OJi.

RaggieSoft · 6th January 2008, 04:52

I am familiar with InstallShield 12 and InstallShield 14 (IS 2008). If the installers are one big EXE, it's extracting the installer to the hard drive. Usually, it is Windows\Downloaded Installations (note that the author of the IS based installers can customize which folder the MSI is "cached" (using IS terminology) to). /SMS is an older InstallShield 5.x switch and wouldn't help out. If the installer launches an MSI, use the /A switch to create an admin image then use the regular MSIEXEC /i (path to MSI). If the IS setup is an EXE that launches an MSI in the same folder, simply directly run the MSI.

Edit: some clarification

If it is an EXE that extracts and launches an MSI, use the /A switch to create the Admin image. Burn that folder (along with everything - there will be a load of files) to your DVD. About the /SMS switch: This was used in InstallShield 5.5 and previous versions to tell IS to not exit the "Preparing InstallShield Wizard" screen until Setup is fully done, thus allowing functions like ExecWait to work properly. Starting with Version 6.0 (this came out back in 2000 or so), the feature provided with /SMS is now the default operation.

o_owd · 6th January 2008, 08:38

Thanks for your reply.

The IS installers are not one big EXE file and I could not find any MSI file. The problem is I cannot/(am not allowed to) modify them. I must use them as they are.
I am still searching...

Thanks again,
OJi.

RaggieSoft · 6th January 2008, 15:13

Oh joy, InstallScript based installations. Here's some command line switches from the InstallShield KB: http://helpnet.macrovision.com/Robo/...ieldLivingHelp|Main&agt=wsm&ctxid=search%2Fgsearch.asp (it's a long and confusing URL)

Try /runfromtemp /clone_wait

If I'm reading the instructions correctly, /clone_wait will only run with /runfromtemp

These instructions are for InstallShield 2008 (AKA InstallShield 14) so hopefully they'll work on IS 11 and IS 12

When you are looking at the Macrovision help site, only the "InstallScript" information applies to you. Ignore "Basic MSI" ans "InstallScript MSI"

31st December 2007, 09:57	#1
o_owd Senior Member Join Date: Feb 2003 Location: TGM, Romania Posts: 176	ExecWait + InstallShield v11 and v12 question Hello, I have a problem with my installer. Actually the problem is not ExecWait. Let me explain. I have my installer (NSIS) that must wait for a InstallShield setup and an update for that InstallShield setup. The update is InstallShield. I have three installers like this. Two of them must wait for v11 InstallShield and the third for a v12 InstallShield. When I run my installer from the HDD everything works as it should. ExecWait works. If I try the same thing from a CD/DVD it does not work. Probably InstallShield launches a new process because it cannot write anything on the CD/DVD.?! Anyway, this is my logic. As I said, I do not believe it is a ExecWait problem. What can I do ? I searched in TEMP folder after I started the InstallShield setup and I cannot find any .msi file. Sorry for the long post and sorry for my english. Thanks in advance, OJi.

31st December 2007, 16:58	#5
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	More in the FAQ about installers fails with ExecWait: http://nsis.sourceforge.net/When_I_u...esn't_wait NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

1st January 2008, 16:40	#7
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	Did you try /SMS? NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

1st January 2008, 17:29	#9
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	If it's only from CD, copy to $TEMP prior to execution. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

31st December 2007, 10:24	#2
Afrow UK Moderator Join Date: Nov 2002 Location: Surrey, England Posts: 8,434	What about command line switches? Stu

31st December 2007, 10:36	#3
o_owd Senior Member Join Date: Feb 2003 Location: TGM, Romania Posts: 176	What command line switches ? I do not want to make a unattended install. The user must select options/configs from the IS setup. I found in NSIS wiki "Check whether your application is running during uninstallation". This can help me. I can check if IS is running or not. But the part where IS is starting and I have only a progressbar - "IS is loading bla bla bla...". This part does not have Name/Class. Thanks, OJi.

31st December 2007, 11:05	#4
Afrow UK Moderator Join Date: Nov 2002 Location: Surrey, England Posts: 8,434	You need to find out if there is a command line switch to stop it running as another process. If there are none, the next option is to keep checking for a running process using FindProcDLL or Processes (both of which however do not work on Vista apparently). Stu

1st January 2008, 16:04	#6
o_owd Senior Member Join Date: Feb 2003 Location: TGM, Romania Posts: 176	Hello, I already checked that page. It does not help me. Thanks anyway, OJi.

1st January 2008, 17:23	#8
o_owd Senior Member Join Date: Feb 2003 Location: TGM, Romania Posts: 176	Yes, I did. Nothing happened. The new process was launched. Thanks, OJi

1st January 2008, 17:32	#10
o_owd Senior Member Join Date: Feb 2003 Location: TGM, Romania Posts: 176	I cannot. I need to do this three times. First installer has 1.4 GB, second 500 MB and the third 1.3 GB. I will search more about InstallShield functionality. If I find something usefull I will post it here. Thanks again, OJi.

6th January 2008, 04:52	#11
RaggieSoft Junior Member Join Date: May 2004 Location: Virginia Beach, VA, USA Posts: 8	I am familiar with InstallShield 12 and InstallShield 14 (IS 2008). If the installers are one big EXE, it's extracting the installer to the hard drive. Usually, it is Windows\Downloaded Installations (note that the author of the IS based installers can customize which folder the MSI is "cached" (using IS terminology) to). /SMS is an older InstallShield 5.x switch and wouldn't help out. If the installer launches an MSI, use the /A switch to create an admin image then use the regular MSIEXEC /i (path to MSI). If the IS setup is an EXE that launches an MSI in the same folder, simply directly run the MSI. Edit: some clarification If it is an EXE that extracts and launches an MSI, use the /A switch to create the Admin image. Burn that folder (along with everything - there will be a load of files) to your DVD. About the /SMS switch: This was used in InstallShield 5.5 and previous versions to tell IS to not exit the "Preparing InstallShield Wizard" screen until Setup is fully done, thus allowing functions like ExecWait to work properly. Starting with Version 6.0 (this came out back in 2000 or so), the feature provided with /SMS is now the default operation.

6th January 2008, 08:38	#12
o_owd Senior Member Join Date: Feb 2003 Location: TGM, Romania Posts: 176	Thanks for your reply. The IS installers are not one big EXE file and I could not find any MSI file. The problem is I cannot/(am not allowed to) modify them. I must use them as they are. I am still searching... Thanks again, OJi.

6th January 2008, 15:13	#13
RaggieSoft Junior Member Join Date: May 2004 Location: Virginia Beach, VA, USA Posts: 8	Oh joy, InstallScript based installations. Here's some command line switches from the InstallShield KB: http://helpnet.macrovision.com/Robo/...ieldLivingHelp\|Main&agt=wsm&ctxid=search%2Fgsearch.asp (it's a long and confusing URL) Try /runfromtemp /clone_wait If I'm reading the instructions correctly, /clone_wait will only run with /runfromtemp These instructions are for InstallShield 2008 (AKA InstallShield 14) so hopefully they'll work on IS 11 and IS 12 When you are looking at the Macrovision help site, only the "InstallScript" information applies to you. Ignore "Basic MSI" ans "InstallScript MSI"