DebbieL wrote: InstallShield adds ISSetupFilesExtract automatically to your project when you add one or more files in the Support Files view. It gets scheduled very early in the UI and Execute sequences. If you don't need to use support files in your installation, you could simply schedule the CheckIfPatchInstalled described in that thread very early in both sequences. Thank you very much, I'll give that a try. ... View more

yossiz wrote: Did you check KB article Q112546 ? Thanks for the info, but that doesn't help with using the Automation framework. That's only running on the command line. ... View more

Do you really need that merge module? MDAC 2.7 was released back in 2003 and is included out of the box in Windows XP and beyond. In fact XP SP2 ( SP3 is latest ) includes MDAC 2.8SP1 out of the box. Are you targeting ancient platforms like Windows NT 4.0 and Windows 2000? I'm guessing if you just removed that module from your installer you'd find your application still works. Check out this link: http://msdn.microsoft.com/en-us/library/ms810805.aspx ... View more

You didn't mention: Did you launch the installation from an elevated command prompt? What command line did you use? Can you provide more details about the environment? Are you trying to debug on your development machine, or on a different machine? About the InstallScript Debugger files that you are using for debugging: Are they from the same version of InstallShield that you used to build the setup? ... View more

I guess your product has still an entry in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall Remove (or rename at first) the subkey of your product, the "strange" number should be the ProductGUID in your setup.ini. HTH, Johannes ... View more

Johannes_T wrote: I do somethig similar, only a setup.rul with declare ... program START: ... endprogram I do everything "manually", show dialogs, copy files and much, much more. You don't really have to use events. You can show the status window with something like this: Enable(STATUS); StatusUpdate (ON, 10); SetStatusWindow (10, "We're doing useful things..."); // Do something useful... SetStatusWindow (20, "..."); Disable(STATUS) Check the SetStatusWindow Example in the manual. HTH, Johannes How are you doing your deploy? Are you using the Ant Tasks that come with OC4J? Do you have any examples you can share? I'm in the process of beating my head into a wall trying to make some sense of this mess. :confused: This is the code I'm scrapping my head against: Deploying ${deploy.ear} to ${targetenv} via ${oc4j.deployer.uri} userId="${oc4j.admin.user}" password="${oc4j.admin.password}" file="${deploy.ear}" deploymentName="${oc4j.deployment.name}" bindAllWebApps="default-web-site" logFile="${log.dir}/deploy.log"/> Undeploying ${oc4j.deployment.name} via ${oc4j.deployer.uri} userId="${oc4j.admin.user}" password="${oc4j.admin.password}" deploymentName="${oc4j.deployment.name}" logFile="${log.dir}/undeploy.log"/> Redeploying ${deploy.ear} to ${targetenv} via ${oc4j.deployer.uri} userId="${oc4j.admin.user}" password="${oc4j.admin.password}" file="${deploy.ear}" deploymentName="${oc4j.deployment.name}" logFile="${log.dir}/redeploy.log"/> Thanks in advance! 🙂 ... View more