Re: [WiX-users] Installing DirectX9 Components within a perUser MSI
1) Remove the CA from your MSI. 2) Create a bundle including DX9 and your MSI in the chain. http://wixtoolset.org/documentation/manual/v3/bundle/ http://wixtoolset.org/documentation/manual/v3/bundle/wixstdba/ WixStdBA comes with the toolset, and you can use it for basic installs, but if you need to customize the user experience a lot, you may have to write your own BA. -Original Message- From: Paul Finkiewicz [mailto:p...@mvsengineering.com] Sent: Wednesday, November 05, 2014 4:04 PM To: 'General discussion about the WiX toolset.' Subject: Re: [WiX-users] Installing DirectX9 Components within a perUser MSI Yes, DirectX9 is a prerequisite to my app. I suppose I'm down to 1 option other than having end users installing DirectX9 themselves. How do I go about changing my code to include your burn option? Regards, Paul *** Email Confidentiality Notice *** -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Wednesday, November 05, 2014 1:19 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Installing DirectX9 Components within a perUser MSI You won't be able to force a 3rd party installer to change scope very easily, especially in the case of an EXE based installation (nor would I recommend doing so). What exactly are you trying to do? If DirectX is a prerequisite to your software, use burn to install it in the chain before your MSI. If your simply trying to wrap the DX setup in a MSI (maybe for legacy AD deployment??) then you're on your own as far as MS supporting it. Concurrent installs are bad. Ref: http://msdn.microsoft.com/en-us/library/aa368010(v=vs.85).aspx -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing DirectX9 Components within a perUser MSI
Is the install log showing anything helpful? You say it's a permissions issue. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-DirectX9-Components-within-a-perUser-MSI-tp7597763p7597775.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing DirectX9 Components within a perUser MSI
I'm suggesting it is a permissions issue because it works on my machine with elevated permissions. The problem is on a PC that is limited. I checked the log on the problem PC and get this: Product: MYProduct -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: InstallDirectX, location: C:\Users\LocalUser\AppData\Local\VNet Beta\DirectX9\dxsetup.exe, command: /silent -Original Message- From: Nick Ramirez [mailto:nickra...@hotmail.com] Sent: Wednesday, November 05, 2014 12:53 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installing DirectX9 Components within a perUser MSI Is the install log showing anything helpful? You say it's a permissions issue. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing DirectX9 Components within a perUser MSI
You won't be able to force a 3rd party installer to change scope very easily, especially in the case of an EXE based installation (nor would I recommend doing so). What exactly are you trying to do? If DirectX is a prerequisite to your software, use burn to install it in the chain before your MSI. If your simply trying to wrap the DX setup in a MSI (maybe for legacy AD deployment??) then you're on your own as far as MS supporting it. Concurrent installs are bad. Ref: http://msdn.microsoft.com/en-us/library/aa368010(v=vs.85).aspx -Original Message- From: Paul Finkiewicz [mailto:p...@mvsengineering.com] Sent: Wednesday, November 05, 2014 3:12 PM To: 'General discussion about the WiX toolset.' Subject: Re: [WiX-users] Installing DirectX9 Components within a perUser MSI I'm suggesting it is a permissions issue because it works on my machine with elevated permissions. The problem is on a PC that is limited. I checked the log on the problem PC and get this: Product: MYProduct -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: InstallDirectX, location: C:\Users\LocalUser\AppData\Local\VNet Beta\DirectX9\dxsetup.exe, command: /silent -Original Message- From: Nick Ramirez [mailto:nickra...@hotmail.com] Sent: Wednesday, November 05, 2014 12:53 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installing DirectX9 Components within a perUser MSI Is the install log showing anything helpful? You say it's a permissions issue. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing DirectX9 Components within a perUser MSI
Yes, DirectX9 is a prerequisite to my app. I suppose I'm down to 1 option other than having end users installing DirectX9 themselves. How do I go about changing my code to include your burn option? Regards, Paul *** Email Confidentiality Notice *** -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Wednesday, November 05, 2014 1:19 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Installing DirectX9 Components within a perUser MSI You won't be able to force a 3rd party installer to change scope very easily, especially in the case of an EXE based installation (nor would I recommend doing so). What exactly are you trying to do? If DirectX is a prerequisite to your software, use burn to install it in the chain before your MSI. If your simply trying to wrap the DX setup in a MSI (maybe for legacy AD deployment??) then you're on your own as far as MS supporting it. Concurrent installs are bad. Ref: http://msdn.microsoft.com/en-us/library/aa368010(v=vs.85).aspx -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
