This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Launch a external .exe no include on my Msi Package
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 10, 2007
07:01 AM
Launch a external .exe no include on my Msi Package
Hello
Sorry for my english, I m a rookie.
I want create a CD with the next tree
CD
setup.exe ( or msi create with install shield )
ïƒ Source (Directory)
_____ïƒ Adobe
________ïƒ Français
____________Adobefrench.exe
________ïƒ English
____________Adobeenglish.exe
I want my setup.exe launch the Adobefrench.exe when i Click on a Button.
I know do a button with the do action. But i dont know how i launch the exe file.
Can you help me please ?
Spinky
Sorry for my english, I m a rookie.
I want create a CD with the next tree
CD
setup.exe ( or msi create with install shield )
ïƒ Source (Directory)
_____ïƒ Adobe
________ïƒ Français
____________Adobefrench.exe
________ïƒ English
____________Adobeenglish.exe
I want my setup.exe launch the Adobefrench.exe when i Click on a Button.
I know do a button with the do action. But i dont know how i launch the exe file.
Can you help me please ?
Spinky
(13) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 10, 2007
08:24 AM
you need to execute a script or batch file
with the following command
$USER_INSTALL_DIR$$/$AdobeFrench.exe
(just check once ) this is how you can call an .exe or .msi
In the pre install or post reply you can call execute script or batch file
with the following command
$USER_INSTALL_DIR$$/$AdobeFrench.exe
(just check once ) this is how you can call an .exe or .msi
In the pre install or post reply you can call execute script or batch file
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 10, 2007
08:34 AM
Create a custom action with the type "launch an executable" and location "stored in the directory table". Set the path to the exe as "[SOURCEDIR]Source\Adobe\Francais\Adobefrench.exe" and the working folder as anything (e.g. TempFolder).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 11, 2007
01:28 AM
ok
thanks james but i don't understand what you want i make.
And sanderson, i understand your propose but i have always the message when i press the button for launch the exe.
The message say the Exe not found
Are you sure of the Syntax.
I think when you do TEMPFOLDER in the Working folder. The [SOURCEDIR] give the TEMPFOLDER. No??
Thanks for the first answer and i wait the second 😉
thanks james but i don't understand what you want i make.
And sanderson, i understand your propose but i have always the message when i press the button for launch the exe.
The message say the Exe not found
Are you sure of the Syntax.
I think when you do TEMPFOLDER in the Working folder. The [SOURCEDIR] give the TEMPFOLDER. No??
Thanks for the first answer and i wait the second 😉
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 11, 2007
03:06 AM
You could try [SETUPEXEDIR] instead of [SOURCEDIR] perhaps. If you run with full logging on you'll see what properties are set up (like these two) and where they point to. Because I call exe's in the Execute sequence I have to call ResolveSource first to set up SOURCEDIR. In your case, in the User Interface sequence, you shouldn't need to, I don't believe.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 11, 2007
04:20 AM
Same problem with SETUPEXEDIR.
Can You tell me how to launch with full login for show the pointing of SOURCEDIR and SETUPEXEDIR.
I think perhaps the probleme come to the Working Directory ? No ??
Can You tell me how to launch with full login for show the pointing of SOURCEDIR and SETUPEXEDIR.
I think perhaps the probleme come to the Working Directory ? No ??
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 11, 2007
08:01 AM
That ok. I have find the solution
It is just the syntax
The good syntax is
[SETUPEXEDIR]\SubDir1\Subdir2\AdbeRdr810_en_US.exe
All Step for other guy search this solution
1.Create Custom action
2. Launch a Exe , Stored in directory table
3. Working Folder is anithing but TempFolder is good
4. Filename [SETUPEXEDIR]\SubDir1\Subdir2\AdbeRdr810_en_US.exe
Thank for you help
Spinky
It is just the syntax
The good syntax is
[SETUPEXEDIR]\SubDir1\Subdir2\AdbeRdr810_en_US.exe
All Step for other guy search this solution
1.Create Custom action
2. Launch a Exe , Stored in directory table
3. Working Folder is anithing but TempFolder is good
4. Filename [SETUPEXEDIR]\SubDir1\Subdir2\AdbeRdr810_en_US.exe
Thank for you help
Spinky
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 11, 2007
08:26 AM
Start a command window and type:
setup.exe /v"/l*v c:\temp\mylogfile.log"
The location and name of the log file can be anything you like.
setup.exe /v"/l*v c:\temp\mylogfile.log"
The location and name of the log file can be anything you like.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 17, 2008
07:37 AM
does not work for me ...
I am putting my custom action right after
InstallInitialize in the Execute installation sequence,
in the logging I see SETUPEXEDIR dir as assigned
but keep geeting errors that SETUPEXEDIR is not in the directory table.
😞
I am putting my custom action right after
InstallInitialize in the Execute installation sequence,
in the logging I see SETUPEXEDIR dir as assigned
but keep geeting errors that SETUPEXEDIR is not in the directory table.
😞
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 17, 2008
07:49 AM
Verify your syntax first
And me i place the custom action after path welcome in the user interface.
Test it perhaps you have no placed in the good place
Spinky
And me i place the custom action after path welcome in the user interface.
Test it perhaps you have no placed in the good place
Spinky
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 17, 2008
08:11 AM
nope, still nothing, also not in the user interface sequence
my syntax:
Filename & CommandLine is [SETUPEXEDIR]\extrakit\setup.exe
Working Directory is TempFolder
my syntax:
Filename & CommandLine is [SETUPEXEDIR]\extrakit\setup.exe
Working Directory is TempFolder
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 17, 2008
08:19 AM
sorry
I have the same example and it s ok.
But i know it s not ok with vista but on XP it s ok
Good luck
I have the same example and it s ok.
But i know it s not ok with vista but on XP it s ok
Good luck
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 19, 2008
08:28 AM
For Vista, you have to add SETUPEXEDIR to the list of properties in the 'SecureCustomProperties' property.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 30, 2008
02:22 AM
Hi Spinky106:
I have similar problem with you and luckily I found your post. Your solution is really helpful to me. But I have additional problem about this topic. First, let me tell you my problem. Please reference this article.
http://community.installshield.com/showthread.php?t=183774
I have some kind of idea handling this problem. The following is my steps:
1. Created a setup.exe (Basic MSI project type).
2. Follow your solutions and insert my new custom action after InstallWelcome action.
http://community.installshield.com/showthread.php?t=174108&page=2
So far, everything is ok. But, I have some special requirements.
1. I hope setup.exe does not show any windows (including Preparing to Install and Welcome windows) and directly enter setup_x86.exe or setup_x64.exe. That is, the task of main installation thread (setup.exe) is: Judge the end user's platform and invoke the suitable child thread (one of setup_x86.exe and setup_x64.exe).
2. When finishing installing setup_x86.exe or setup_x64.exe, the child thread exits and the main thread continues executing. But there is no need for me to let main thread continues executing. Because the whole installation is finished. But my current situation is the setup.exe would run other its original custom actions.
So, how could I solve these problems? Just give me a clue and that will be helpful to me. Thanks
I have similar problem with you and luckily I found your post. Your solution is really helpful to me. But I have additional problem about this topic. First, let me tell you my problem. Please reference this article.
http://community.installshield.com/showthread.php?t=183774
I have some kind of idea handling this problem. The following is my steps:
1. Created a setup.exe (Basic MSI project type).
2. Follow your solutions and insert my new custom action after InstallWelcome action.
http://community.installshield.com/showthread.php?t=174108&page=2
So far, everything is ok. But, I have some special requirements.
1. I hope setup.exe does not show any windows (including Preparing to Install and Welcome windows) and directly enter setup_x86.exe or setup_x64.exe. That is, the task of main installation thread (setup.exe) is: Judge the end user's platform and invoke the suitable child thread (one of setup_x86.exe and setup_x64.exe).
2. When finishing installing setup_x86.exe or setup_x64.exe, the child thread exits and the main thread continues executing. But there is no need for me to let main thread continues executing. Because the whole installation is finished. But my current situation is the setup.exe would run other its original custom actions.
So, how could I solve these problems? Just give me a clue and that will be helpful to me. Thanks