Click Right on your prerequisite en go to the properties On the tab behavior you have many option. ... View more

http://kb.flexerasoftware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q107153&sliceId= ... View more

You can use the redistributable Merge Module include in the Installshield Redistributable --> merge Module Visual C++ 9.0 CRT Visual C++ 9.0 MFC Visual C++ 9.0 ATL It OK ?? ... View more

+1 just for UP ... View more

i don't know But i develop my setup on XP, and install on XP and Vista Just some tunning for the setup is ok in both OS ... View more

It's ok Thanks a lot Epoon Closed ... View more

OK I find nothing I rephrase my question differently How can i launch a secondary setup on my main setup on vista. For Xp just create custom action --> New Exe with the filename and working directory But for vista is not ok I think the UAC is the problem. Can you explain how bypass this Spinky ... View more

In general information is just the support language by your setup In release is for actived this language in your User interface. You can do Yes in language dialog, the setup start with a dialog box and porpose the selected language for your UI ... View more

no i will launch a .exe file with my custom action. My main setup launch a custom action include a other setup.exe file. On xp It s ok but on Vista i have the error. I go to see in the admin priviledge I am keeping abreast, but if someone has another idea you are welcome ... View more

one more idea, no solution just direction Use featurelist Stay the name of program on a external file Prog.txt behind your setup.exe For example : Prog1 prog2 prog3 use the a dialog box with include a listbox with property FEATURELIST Create Custom action VB Script and launch "after patchwelcome" with script function PropDisplay The Script is ######Fonction List CallPropDisplay###### Const msiViewModifyInsertTemporary = 7 Const IDOK = 1 Function PropDisplay( ) Set viewlist = Database.OpenView("SELECT * FROM `ListBox` ") viewlist.Execute Set oFSO = CreateObject ("Scripting.FileSystemObject") ProgFile=Me.Property("SETUPEXEDIR") & "\Prog.txt " If oFSO.FileExists(ProgFile) then set f=oFso.OpenTextFile(ProgFile) r=0 while Not f.AtEndOfStream ListSelect = f.Readline If Left(ListSelect, 1) = "#" Then Else r=r+1 Set reclist = Installer.CreateRecord(4) reclist.StringData(1) = "FEATURELIST" reclist.IntegerData(2) = r reclist.StringData(3) = ListSelect reclist.StringData(4) = ListSelect viewlist.Modify msiViewModifyInsertTemporary, reclist End If wend f.Close Else msgbox "Prog.txt missing" End If set fso = nothing PropDisplay = IDOK End Function This Custom action search the text on your file and insert on list box After you can create a button on your dialog box with the condition for launch custom action if FEATURELIST=ProgXX This Launch one after one your setup I hope that it help Spinky ... View more

Up Up Up ... View more

Hi in the Media --> Releases --> Product configuration You can change the setup file name Spinky ... View more

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 ... View more

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 ... View more