🚀 go-pugleaf

Here is a function that I used that seems to work well for launching IS
setups.

HTH,

Eric
InstallShield Support



unsigned long RunSetupAndWait(LPSTR);

unsigned long RunSetupAndWait(LPSTR szFullCmdLine){
 PROCESS_INFORMATION ProcInfo;
 STARTUPINFO StartupInfo;
 BOOL bRval;
 unsigned long nExitCode;
 long lRetVal;

 GetStartupInfo(&StartupInfo);

 bRval=CreateProcess(NULL,szFullCmdLine,NULL,NULL,
      FALSE, CREATE_NEW_PROCESS_GROUP,
      NULL, NULL, &StartupInfo, &ProcInfo);

 if( bRval == 0

    // return a  error code
    return 999;
 }
 do{
  lRetVal = WaitForSingleObject(ProcInfo.hProcess, 0);
  //setup is complete
  if ( (lRetVal < WAIT_TIMEOUT) || (lRetVal > WAIT_TIMEOUT)  ){
   break;
  }
  //sleep to allow setup.exe to initialize itself and free CPU.
PeekMessage() will work too.
  Sleep(2000);
 }
 while (TRUE);
 GetExitCodeProcess(ProcInfo.hProcess, &nExitCode);
 return nExitCode;
}



kbozek@my-deja.com wrote in message <7s5d8h$eun$1@nnrp1.deja.com>...
>I am using InstallShield to Launch another Installshield app.
>Installshield has its own launch and wait function. However, I noted
>that after it decabs, the function returns even though the installer is
>not finished. It seems that InstallShield launches a process afer
>decabbing and returns on the decabbing function.
>
>I created a Win32 app using CreateProcess.  However, it behaves the
>same as the IS app when using waitforsingleobject.  I know that there
>is a Msgwaitformultiple object function but can't get it to work.
>Checked MSDN without finding a specific.  Help....
>
>
>Sent via Deja.com http://www.deja.com/
>Share what you know. Learn what you don't.
>