Install Program From Path
Hi,
I am using Wise Package Studio 7 to create my MSI packages.
Now I want to create a MSI installer which runs a executable from a networklocation. The executable requires some cab files from the same networklocation. My thought is to create a "Install Program From Path" custom action. But it seems the executable can't find the cab files for installing.
This is what I tried.
The setup wants to launch, but is says, it needs to run from disk 1. When I copy the setup.exe to an empty folder without the cab files, I get the same error when I try to run it. I can run the setup.exe from the start>run menu entering the same value as the propery.
Does anyone know what to do?
I am using Wise Package Studio 7 to create my MSI packages.
Now I want to create a MSI installer which runs a executable from a networklocation. The executable requires some cab files from the same networklocation. My thought is to create a "Install Program From Path" custom action. But it seems the executable can't find the cab files for installing.
This is what I tried.
- Created a property with the location of the setup.exe (\\server\share$\SoftwarePackage\setup.exe)
- Opened the Wise Script editor and created a "Install Program From Path" custom action
- For the propery field I used the propery I created.
The setup wants to launch, but is says, it needs to run from disk 1. When I copy the setup.exe to an empty folder without the cab files, I get the same error when I try to run it. I can run the setup.exe from the start>run menu entering the same value as the propery.
Does anyone know what to do?
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
photozz
16 years ago
My initial guess is that the setup is being tripped up by the starting directory (Much the same way a shortcut on your desktop has the path to the exe, and a field listed "Start In"). When you run the setup.exe from the "Run" command, it assumes you are starting the app from the directory that the exe resides in. When you are launching it with the custom action, its probably feeding the setup.exe the starting directory for the MSI. So, the setup fails because its mistakenly looking for the cab files in the same location as the MSI, not the exe. You may need to do something stupid like create a bat file or script to launch the setup.exe. You could also explore the command line options for the setup.exe and see if there is a way to set the "run from" path manually.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
