[WiX-users] Custom Action vs Condition
Hi, I want to know what is the difference between these two (related to launch condition only): Suppose OS Check: if I use: Its working but similar thing is not working in Launch Condition custom action. I have to use this to make it work: Some help required? -- Thanks and Regards, Ravi Raj -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Action vs Condition
And this also is not working: I want to check for OS version Windows 7 SP1 or Windows Server 2008 R2 SP1 in custom action. How can I make it work? On Fri, May 11, 2012 at 12:27 PM, Ravi Raj wrote: > Hi, > I want to know what is the difference between these two (related to launch > condition only): > > Suppose OS Check: > if I use: > > > > > > Its working but similar thing is not working in Launch Condition custom > action. I have to use this to make it work: > > > > > > Some help required? > > -- > Thanks and Regards, > Ravi Raj > > -- Thanks and Regards, Ravi Raj -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Action vs Condition
Hi, we use Install Shield but we want to change to WIX. If we want to go to WIX with an upgrade, we have to use an Major Upgrade, right? Can we after using the Major Upgrade for the next Version come out without Install Shield? I mean if we kann make minor upgrades upon the major upgrade. Is it possible to go back, with uninstallating the updgrade, to the install shield Version. Christoph -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Splash Screen
How to add splash screen at the beginning of installer? -- Thanks and Regards, Ravi Raj -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Update from Install Shield
Sorry Hi, we use Install Shield but we want to change to WIX. If we want to go to WIX with an upgrade, we have to use an Major Upgrade, right? Can we after using the Major Upgrade for the next Version come out without Install Shield? I mean if we kann make minor upgrades upon the major upgrade. Is it possible to go back, with uninstallating the updgrade, to the install shield Version. Christoph -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Votive / WiX not releasing handles on extension dlls after build.
When building a setup project using Votive in Visual Studio, a handle is kept on any extension dlls even after the build has completed. This poses two problems to me: 1. Developing extensions is a slow process, because Visual Studio has to be restarted every time I have to make a change to the extension. In order to release the lock on the extension dll. 2. If an extension loads an assembly from the product itself (the product being released with the setup project) that assembly is loaded into the AppDomain where the extension is running. As a consequence that is not released either, after the build has been completed. This means the product cannot be rebuild if the setup project has been build without restarting Visual Studio. Is there a way around this and release the locks on the assemblies without restarting Visual Studio, or will I have to run WiX manually from the command line? Thanks, Morten -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] light.exe error when merging VC100 merge modules for both x86 and x64
Hi Bob, thanks for your input, but why would it ever be necessary to include 32-bit merge modules in a 64-bit package? You can't install a 64-bit package on a 32-bit operating system, so they'd never be used. The otherway around though - you can install a 32-bit package on a 64-bit operating system, so it's quite reasonable to want to include 32-bit merge modules to execute your own functions and 64-bit merge modules in order to hook into those of the operating system. When you use the system's File Open dialog, for example, you will only get a thumbnail preview on a 64-bit OS if you have the correct 64-bit dipendencies installed. Cheers, G -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/light-exe-error-when-merging-VC100-merge-modules-for-both-x86-and-x64-tp7539587p7549693.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Help in Burn's Condition!!!
I am trying to use launch condition in Burn as for checking windows 7, server 2008, server 2008 r2 and windows 8. But every time it gives me error (on every platform even in XP): "the specific program requires newer version of windows". -- Thanks and Regards, Ravi Raj -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WIX Setup Project says "A reference dll could not be added" in VS2010
Hi, I am creating a WIX installer project. When I am trying to add the reference: Microsoft.ReportViewer.Common.dll and Microsoft.ReportViewer.WinForms.dll, I got the error mentioned on the title. I searched online but can't find any useful info. My DLLs are located in C:\Program Files(x86)\Microsoft Visual Studio 10.0\ReportViewer, so it is not like a question mentioned by somebody when they are referencing to a dll located on network share. I am totally new to WIX and deployment project, so a little bit explanation on what happens will be appreciated! Thanks for any help! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-Setup-Project-says-A-reference-dll-could-not-be-added-in-VS2010-tp7550083.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Action Type 19 in WiX 3.6 RC
Isn't your logic backwards ? The error custom action will run if you are installed or have vista SP2+ or have win7 sp1+. Launch conditions must be true to continue with installation; error custom actions must be true to issue an error. -Original Message- From: Ravi Raj [mailto:raviraj.callin...@gmail.com] Sent: 10 May 2012 09:30 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Custom Action Type 19 in WiX 3.6 RC I am using following but its not working (at-least OS check should work but its not): Not Privileged Installed OR (VersionNT=600 AND ServicePackLevel>=2) OR (VersionNT=601 AND ServicePackLevel>=1) Installed OR NETFRAMEWORK40CLIENT OR NETFRAMEWORK40FULL And in CustomAction.wxs file I defined it as: http://schemas.microsoft.com/wix/2006/wi";> The last custom action is a component search (highly important to have) is defined as: When I am running the setup, its going on executing on my Windows XP machine. OS Validation not working as is only for Win 7 SP1 or Win Server 2008 R2 SP1 also the component which I have a check is not present on this machine. -- Thanks and Regards, Ravi Raj - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX Setup Project says "A reference dll could not be added" in VS2010
> I am creating a WIX installer project. When I am trying to add the > reference: Microsoft.ReportViewer.Common.dll and > Microsoft.ReportViewer.WinForms.dll, I got the error mentioned on the title. > I searched online but can't find any useful info. My DLLs are located in > C:\Program Files(x86)\Microsoft Visual Studio 10.0\ReportViewer, so it is > not like a question mentioned by somebody when they are referencing to a dll > located on network share. I am totally new to WIX and deployment project, so > a little bit explanation on what happens will be appreciated! As I understand it, you basically add references in your installer projects for two reasons: 1. You create a reference to another project - the project you wish to install. By creating a reference, you ensure the project is build, when the installer project is build and you get access to some preprocessor variables. 2. You have WiX extension dlls that somehow add to the functionality of wix. You cannot add a reference to a regular dll. Dlls that should be included in the installation should be included by the use of tags. Have you had a look at this tutorial: http://wix.tramontana.co.hu/tutorial /Regards, Morten -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Action Type 19 in WiX 3.6 RC
Yup I get my mistake.. many thanks
On Fri, May 11, 2012 at 4:50 PM, Peter Shirtcliffe wrote:
> Isn't your logic backwards ? The error custom action will run if you are
> installed or have vista SP2+ or have win7 sp1+. Launch conditions must be
> true to continue with installation; error custom actions must be true to
> issue an error.
>
> -Original Message-
> From: Ravi Raj [mailto:raviraj.callin...@gmail.com]
> Sent: 10 May 2012 09:30
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Custom Action Type 19 in WiX 3.6 RC
>
> I am using following but its not working (at-least OS check should work but
> its not):
>
>
>
>Not Privileged
>
>
>Installed OR (VersionNT=600 AND ServicePackLevel>=2) OR
> (VersionNT=601 AND ServicePackLevel>=1)
>
>
>Installed OR NETFRAMEWORK40CLIENT OR NETFRAMEWORK40FULL
>
>
>
>
> And in CustomAction.wxs file I defined it as:
>
> http://schemas.microsoft.com/wix/2006/wi";>
>
> Error='!(loc.ValidationAdministrator)' />
> />
> Error='!(loc.ValidationDotNetFramework)' />
>
>
>
>
> The last custom action is a component search (highly important to have) is
> defined as:
>
> Guid="{XXX----}" />
>
>
> When I am running the setup, its going on executing on my Windows XP
> machine.
> OS Validation not working as is only for Win 7 SP1 or Win Server
> 2008 R2 SP1 also the component which I have a check is not present on this
> machine.
>
> --
> Thanks and Regards,
> Ravi Raj
>
> -
> -
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and threat
> landscape has changed and how IT managers can respond. Discussions will
> include endpoint security, mobile security and the latest in malware
> threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> SDL PLC confidential, all rights reserved.
> If you are not the intended recipient of this mail SDL requests and
> requires that you delete it without acting upon or copying any of its
> contents, and we further request that you advise us.
> SDL PLC is a public limited company registered in England and Wales.
> Registered number: 02675207.
> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
> 7DY, UK.
>
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Thanks and Regards,
Ravi Raj
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Action Type 19 in WiX 3.6 RC
OK i have used OS_Check Custom Action like this:
Everything is working great :)
But while building the project I am getting this warning.
ICE03: String overflow (greater than length permitted in column); Table:
CustomAction, Column: Target, Key(s): CA_OSCHECK
I don't want to ignore this warning. How can I resolve this?
On Fri, May 11, 2012 at 5:08 PM, Ravi Raj wrote:
> Yup I get my mistake.. many thanks
>
>
> On Fri, May 11, 2012 at 4:50 PM, Peter Shirtcliffe
> wrote:
>
>> Isn't your logic backwards ? The error custom action will run if you are
>> installed or have vista SP2+ or have win7 sp1+. Launch conditions must be
>> true to continue with installation; error custom actions must be true to
>> issue an error.
>>
>> -Original Message-
>> From: Ravi Raj [mailto:raviraj.callin...@gmail.com]
>> Sent: 10 May 2012 09:30
>> To: General discussion for Windows Installer XML toolset.
>> Subject: [WiX-users] Custom Action Type 19 in WiX 3.6 RC
>>
>> I am using following but its not working (at-least OS check should work
>> but
>> its not):
>>
>>
>>
>>Not Privileged
>>
>>
>>Installed OR (VersionNT=600 AND ServicePackLevel>=2) OR
>> (VersionNT=601 AND ServicePackLevel>=1)
>>
>>
>>Installed OR NETFRAMEWORK40CLIENT OR NETFRAMEWORK40FULL
>>
>>
>>
>>
>> And in CustomAction.wxs file I defined it as:
>>
>> http://schemas.microsoft.com/wix/2006/wi";>
>>
>>> Error='!(loc.ValidationAdministrator)' />
>>> />
>>> Error='!(loc.ValidationDotNetFramework)' />
>>
>>
>>
>>
>> The last custom action is a component search (highly important to have) is
>> defined as:
>>
>> > Guid="{XXX----}" />
>>
>>
>> When I am running the setup, its going on executing on my Windows XP
>> machine.
>> OS Validation not working as is only for Win 7 SP1 or Win Server
>> 2008 R2 SP1 also the component which I have a check is not present on this
>> machine.
>>
>> --
>> Thanks and Regards,
>> Ravi Raj
>>
>> -
>> -
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and threat
>> landscape has changed and how IT managers can respond. Discussions will
>> include endpoint security, mobile security and the latest in malware
>> threats.
>> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>> SDL PLC confidential, all rights reserved.
>> If you are not the intended recipient of this mail SDL requests and
>> requires that you delete it without acting upon or copying any of its
>> contents, and we further request that you advise us.
>> SDL PLC is a public limited company registered in England and Wales.
>> Registered number: 02675207.
>> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire
>> SL6 7DY, UK.
>>
>>
>>
>> --
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>
>
>
> --
> Thanks and Regards,
> Ravi Raj
>
>
--
Thanks and Regards,
Ravi Raj
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX Setup Project says "A reference dll could not be added" in VS2010
Thanks Morten, now I think it makes senses that the dependencies are only "to make sure the referenced project is built" and "to get access to some preprocessor variables". I guess I got the wrong impression that the dependencies would be included because when I created a WIX custom action project and referenced to this project, I can call this function from it(of course by using custom tag) just like in a normal project. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-Setup-Project-says-A-reference-dll-could-not-be-added-in-VS2010-tp7550083p7550323.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Action Type 19 in WiX 3.6 RC
A valid fix is to increase the column size in the MSI database schema. You
can do this in Orca or another MSI editor. If you want to do this in an
automated fashion, there might be a way to do it in the MSI COM API.
-Original Message-
From: Ravi Raj [mailto:raviraj.callin...@gmail.com]
Sent: 11 May 2012 12:58
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom Action Type 19 in WiX 3.6 RC
OK i have used OS_Check Custom Action like this:
Everything is working great :)
But while building the project I am getting this warning.
ICE03: String overflow (greater than length permitted in column); Table:
CustomAction, Column: Target, Key(s): CA_OSCHECK
I don't want to ignore this warning. How can I resolve this?
On Fri, May 11, 2012 at 5:08 PM, Ravi Raj wrote:
> Yup I get my mistake.. many thanks
>
>
> On Fri, May 11, 2012 at 4:50 PM, Peter Shirtcliffe
wrote:
>
>> Isn't your logic backwards ? The error custom action will run if you
>> are installed or have vista SP2+ or have win7 sp1+. Launch conditions
>> must be true to continue with installation; error custom actions must
>> be true to issue an error.
>>
>> -Original Message-
>> From: Ravi Raj [mailto:raviraj.callin...@gmail.com]
>> Sent: 10 May 2012 09:30
>> To: General discussion for Windows Installer XML toolset.
>> Subject: [WiX-users] Custom Action Type 19 in WiX 3.6 RC
>>
>> I am using following but its not working (at-least OS check should
>> work but its not):
>>
>>
>>
>>Not Privileged
>>
>>
>>Installed OR (VersionNT=600 AND ServicePackLevel>=2) OR
>> (VersionNT=601 AND ServicePackLevel>=1)
>>
>>
>>Installed OR NETFRAMEWORK40CLIENT OR NETFRAMEWORK40FULL
>>
>>
>>
>>
>> And in CustomAction.wxs file I defined it as:
>> > xmlns="http://schemas.microsoft.com/wix/2006/wi";>
>>
>>> Error='!(loc.ValidationAdministrator)' />
>>> />
>>> Error='!(loc.ValidationDotNetFramework)' />
>>
>>
>>
>> The last custom action is a component search (highly important to
>> have) is defined as:
>>
>> > Guid="{XXX----}" />
>>
>>
>> When I am running the setup, its going on executing on my Windows XP
>> machine.
>> OS Validation not working as is only for Win 7 SP1 or Win Server
>> 2008 R2 SP1 also the component which I have a check is not present on
>> this machine.
>>
>> --
>> Thanks and Regards,
>> Ravi Raj
>>
>> -
>>
>> -
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond.
>> Discussions will include endpoint security, mobile security and the
>> latest in malware threats.
>> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>> SDL PLC confidential, all rights reserved.
>> If you are not the intended recipient of this mail SDL requests and
>> requires that you delete it without acting upon or copying any of its
>> contents, and we further request that you advise us.
>> SDL PLC is a public limited company registered in England and Wales.
>> Registered number: 02675207.
>> Registered address: Globe House, Clivemont Road, Maidenhead,
>> Berkshire
>> SL6 7DY, UK.
>>
>>
>>
>> -
>> -
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond.
>> Discussions will include endpoint security, mobile security and the
>> latest in malware threats.
>> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>
>
>
> --
> Thanks and Regards,
> Ravi Raj
>
>
--
Thanks and Regards,
Ravi Raj
-
-
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will
include endpoint security, mobile security and the latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has chang
Re: [WiX-users] Help in Burn's Condition!!!
The numbers are 3 digit strings. Try: Condition="((VersionNT >= 600) AND (ServicePackLevel >= 2)) OR ((VersionNT >= 610) AND (ServicePackLevel >= 1)) OR (VersionNT >= 620)" -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Help-in-Burn-s-Condition-tp7550014p7550530.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using Torch.exe with Visual Studio (need WIX path)
Also consider the discussion (and my posts) in http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multilanguage-install-tt6161866.html#a6183992 There is described how to directly parametrize the torch task within the wix solution Regards, Tobias -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Managed bootstrap failing to load
Nigel,
Did you get this working past the "Hello World"? I got this far, but
cannot get Burn to install my packages with my custom bootstrapper
application. It appears to get to the Threading.Dispatcher.Run call, but
then just sits there (ie I never get the second message box):
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.Tools.WindowsInstallerXml.Bootstrapper;
using System.Windows.Forms;
using Threading = System.Windows.Threading;
namespace MyBA
{
public class TestBA : BootstrapperApplication
{
static public Threading.Dispatcher Dispatcher { get; private set; }
protected override void Run()
{
this.Engine.Log(LogLevel.Verbose, "Running the TestBA.");
TestBA.Dispatcher = Threading.Dispatcher.CurrentDispatcher;
MessageBox.Show("My Bootstrapper Application is running");
Threading.Dispatcher.Run();
MessageBox.Show("Dispatcher Run has finished.");
this.Engine.Quit(0);
}
}
}
Any little bit of help you could provide would be GREATLY appreciated.
Best regards,
Brian
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-bootstrap-failing-to-load-tp7547420p7550586.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] using wix with powershell
As Edwin could have more tactfully pointed out, his script does have some advantages over mine. Thanks, Edwin. Mine is intended to get you in the right direction, while his is more production ready except for one point: I still suggesting using Start-Process to launch msbuild so that you can get the return code to see if it failed (and conveniently log the output). Things I would use from his script: - His msbuild args are in an array, which is nicer than the literal string in mine. - He reads a registry key to find msbuild which is less appropriate for a quick "how to" email, but better for production code. - Parameter validation, if you want to be pedantic about it. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/using-wix-with-powershell-tp7537541p7550930.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Help in Burn's Condition!!!
Not in burn. Neil -Original Message- From: AlanBrianCovington [mailto:briancoving...@yahoo.com] Sent: 11 May 2012 14:51 To: wix-users@lists.sourceforge.net Subject: -SPAM- Re: [WiX-users] Help in Burn's Condition!!! The numbers are 3 digit strings. Try: Condition="((VersionNT >= 600) AND (ServicePackLevel >= 2)) OR ((VersionNT >= 610) AND (ServicePackLevel >= 1)) OR (VersionNT >= 620)" -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Help-in-Burn-s-Condition-tp7550014p7550530.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Help in Burn's Condition!!!
That looks ok to me, have you checked the logs when it runs? Neil -Original Message- From: Ravi Raj [mailto:raviraj.callin...@gmail.com] Sent: 11 May 2012 11:49 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Help in Burn's Condition!!! I am trying to use launch condition in Burn as for checking windows 7, server 2008, server 2008 r2 and windows 8. But every time it gives me error (on every platform even in XP): "the specific program requires newer version of windows". -- Thanks and Regards, Ravi Raj -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] using wix with powershell
PowerShell gives you lots of options to log the output. For example you could collect the output in a variable and then do something about it like write it in a file or to the event log or whatever. You could also pipe the output to Tee-Object which will automatically write the output to a file and then send the output along the pipeline so that you could do something else with it, like showing it on the console. But, in the case of MSBuild, I find all of the PowerShell options unnecessary as MSBuild has the ability to write to a log file (as well as the console) already built-in. The /fl and /flp arguments control how file logging works. My example lets MSBuild use the default log file name (MSBuild.log in the current working directory) but you could even configure the log file to generate by setting the LogFile property with /flp. The /fl and /flp arguments are actually very powerful as you can define up to 10 different log files to produce with different content in each (while still getting regular output on the console). See MSBuild /? for details on MSBuild's logging features as well as other possible command line arguments. PowerShell automatically puts the exit code in the $LASTEXITCODE variable. This is similar to how %ERRORLEVEL% contains the exit code in batch scripts. I would use $LASTEXITCODE rather than Start-Process. In my opinion, Start-Process, simply adds a layer of indirection that is unnecessary. In fact, I tried to say in my previous email that using a function or script to wrap MSBuild might already be a layer of indirection that is unnecessary depending on what your goal is. I find that a wrapper script is useful for command line usage where I want a specific type of invocation to occur every time. The script allows me to encapsulate MSBuild usage for developers that are less familiar with its capabilities. If I simply needed to call MSBuild as part of an existing build script that does other stuff as well as calling MSBuild, then I might just call MSBuild directly. I think KISS applies here quite a bit. For example, if I have a Solution.sln in the same directory as the automation script that I need to call without a lot of fluff and I know I need to call it with a single Configuration|Platform combo and I don't need anything special else special (because perhaps the CI server that calls my automation script already automatically captures my output) then I would simply use it like this: $ProjectPath = Join-Path -Path (Split-Path -Path $MyInvocation.MyCommand.Path) -ChildPath Solution.sln & $MSBuildCmd $ProjectPath /p:Configuration=Release /p:Platform=x86 /t:Rebuild If you can guarantee that MSBuild.exe will be in your PATH, then you can write it more simply like this: msbuild $ProjectPath /p:Configuration=Release /p:Platform=x86 /t:Rebuild I didn't enclose $ProjectPath in double quotes even though it might have spaces in it. PowerShell will automatically wrap it in double quotes when it passes the argument to MSBuild if necessary. This is another example of how people unnecessarily complicate their PowerShell scripts. In any case, questions about command invocation in PowerShell probably should be posted at http://www.powershellcommunity.com/Forums.aspx There are a lot of active members and they are very friendly. Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail > -Original Message- > From: john.burak [mailto:john.bu...@telvent.com] > Sent: Friday, May 11, 2012 9:09 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] using wix with powershell > > As Edwin could have more tactfully pointed out, his script does have some > advantages over mine. Thanks, Edwin. Mine is intended to get you in the > right > direction, while his is more production ready except for one point: I still > suggesting using Start-Process to launch msbuild so that you can get the > return > code to see if it failed (and conveniently log the output). > > Things I would use from his script: > > - His msbuild args are in an array, which is nicer than the literal string in > mine. > - He reads a registry key to find msbuild which is less appropriate for a > quick > "how to" email, but better for production code. > - Parameter validation, if you want to be pedantic about it. > > -- > View this message in context: http://windows-installer-xml-wix- > toolset.687559.n2.nabble.com/using-wix-with-powershell- > tp7537541p7550930.html > Sent from the wix-users mailing list archive at Nabble.com. > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest
[WiX-users] (no subject)
Hello all, I'm working on a project that communicates with an Arduino Uno. As such, we'd like to install the driver for the Arduino along with our project. The driver is the USB RS-232 Emulation Driver that comes in Windows; Arduino has an INF that references usbser.sys. So, my question is: How do we accomplish this? I've successfully included the INF in the installer. I've tried using a CAQuietExec CustomAction with the command line: rundll32.exe advpack.dll,LaunchINFSectionEx "[INSTALLDIR]\Arduino UNO.inf",DriverInstall.nt,,4,N But that asks me to locate usbser.sys when I run the installer. Do I need to be doing something like: and using DIFxApp? Thanks for reading, I appreciate any insight you can give, Elliott -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using Torch.exe with Visual Studio (need WIX path)
Thanks for the tips. I got it working with the system variable, and I will look into modifying the .wixproj. Mike Schlueter Software Engineer Phoenix Contact USA Ann Arbor, MI (734)205-5410 mschlue...@phoenixcon.com From: Tobias S To: "General discussion for Windows Installer XML toolset." , Date: 05/11/2012 09:53 AM Subject:Re: [WiX-users] Using Torch.exe with Visual Studio (need WIX path) Also consider the discussion (and my posts) in http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multilanguage-install-tt6161866.html#a6183992 There is described how to directly parametrize the torch task within the wix solution Regards, Tobias -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Does wix support calling bcdedit?
Hi, I'm trying to call bcdedit from a deferred custom action to set the machine in test mode. I'm trying to install unsigned drivers at the moment so I want to put the machine in test mode with the command "bcdedit /set testsigning on". I'm calling CAQuietExec byt I'm getting Error 0x80070002 These are snips of my log: MSI (s) (B8:74) [11:25:49:046]: Note: 1: 2205 2: 3: PatchPackage Action ended 11:25:49: InstallFiles. Return value 1. MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd_Cmd Action start 11:25:49: SetInstallCmd_Cmd. MSI (s) (B8:74) [11:25:49:046]: PROPERTY CHANGE: Adding SetInstallCmd property. Its value is '"C:\Windows\system32\\bcdedit.exe" /set "testsigning on"'. Action ended 11:25:49: SetInstallCmd_Cmd. Return value 1. MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd Action start 11:25:49: SetInstallCmd. Action ended 11:25:49: SetInstallCmd. Return value 1. MSI (s) (B8:74) [11:25:49:062]: Doing action: InstallAHCI64 ... MSI (s) (B8:74) [11:25:49:140]: Executing op: ActionStart(Name=SetInstallCmd,,) MSI (s) (B8:74) [11:25:49:140]: Executing op: CustomActionSchedule(Action=SetInstallCmd,ActionType=3137,Source=BinaryData,Target=CAQuietExec,CustomActionData="C:\Windows\system32\\bcdedit.exe" /set "testsigning on") MSI (s) (B8:74) [11:25:49:140]: Creating MSIHANDLE (4) of type 790536 for thread 1908 MSI (s) (B8:D8) [11:25:49:140]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIC31B.tmp, Entrypoint: CAQuietExec MSI (s) (B8:C4) [11:25:49:140]: Generating random cookie. MSI (s) (B8:C4) [11:25:49:140]: Created Custom Action Server with PID 1884 (0x75C). MSI (s) (B8:48) [11:25:49:498]: Running as a service. MSI (s) (B8:48) [11:25:49:498]: Hello, I'm your 32bit Elevated custom action server. MSI (s) (B8!44) [11:25:49:514]: Creating MSIHANDLE (5) of type 790531 for thread 2628 CAQuietExec: Error 0x80070002: Command failed to execute. MSI (s) (B8!44) [11:25:49:514]: Closing MSIHANDLE (5) of type 790531 for thread 2628 MSI (s) (B8!44) [11:25:49:514]: Creating MSIHANDLE (6) of type 790531 for thread 2628 CAQuietExec: Error 0x80070002: CAQuietExec Failed MSI (s) (B8!44) [11:25:49:514]: Closing MSIHANDLE (6) of type 790531 for thread 2628 CustomAction SetInstallCmd returned actual error code 1603 but will be translated to success due to continue marking MSI (s) (B8:D8) [11:25:49:514]: Closing MSIHANDLE (4) of type 790536 for thread 1908 MSI (s) (B8:74) [11:25:49:514]: Executing op: ActionStart(Name=InstallAHCI64,Description="Installing ",) MSI (s) (B8:74) [11:25:49:514]: Executing op: CustomActionSchedule(Action=InstallAHCI64,ActionType=3138,Source=BinaryData,Target=/F /PATH "C:\Program Files\\\",) CustomAction InstallAHCI64 returned actual error code 1073741825 but will be translated to success due to continue marking Any ideas? Thank you -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Does-wix-support-calling-bcdedit-tp7551749.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does wix support calling bcdedit?
Sorry, Here's the CA codes and I'm running elevated as perMachine install --- On Fri, 5/11/12, victorwhiskey wrote: From: victorwhiskey Subject: [WiX-users] Does wix support calling bcdedit? To: wix-users@lists.sourceforge.net Date: Friday, May 11, 2012, 8:07 PM Hi, I'm trying to call bcdedit from a deferred custom action to set the machine in test mode. I'm trying to install unsigned drivers at the moment so I want to put the machine in test mode with the command "bcdedit /set testsigning on". I'm calling CAQuietExec byt I'm getting Error 0x80070002 These are snips of my log: MSI (s) (B8:74) [11:25:49:046]: Note: 1: 2205 2: 3: PatchPackage Action ended 11:25:49: InstallFiles. Return value 1. MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd_Cmd Action start 11:25:49: SetInstallCmd_Cmd. MSI (s) (B8:74) [11:25:49:046]: PROPERTY CHANGE: Adding SetInstallCmd property. Its value is '"C:\Windows\system32\\bcdedit.exe" /set "testsigning on"'. Action ended 11:25:49: SetInstallCmd_Cmd. Return value 1. MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd Action start 11:25:49: SetInstallCmd. Action ended 11:25:49: SetInstallCmd. Return value 1. MSI (s) (B8:74) [11:25:49:062]: Doing action: InstallAHCI64 ... MSI (s) (B8:74) [11:25:49:140]: Executing op: ActionStart(Name=SetInstallCmd,,) MSI (s) (B8:74) [11:25:49:140]: Executing op: CustomActionSchedule(Action=SetInstallCmd,ActionType=3137,Source=BinaryData,Target=CAQuietExec,CustomActionData="C:\Windows\system32\\bcdedit.exe" /set "testsigning on") MSI (s) (B8:74) [11:25:49:140]: Creating MSIHANDLE (4) of type 790536 for thread 1908 MSI (s) (B8:D8) [11:25:49:140]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIC31B.tmp, Entrypoint: CAQuietExec MSI (s) (B8:C4) [11:25:49:140]: Generating random cookie. MSI (s) (B8:C4) [11:25:49:140]: Created Custom Action Server with PID 1884 (0x75C). MSI (s) (B8:48) [11:25:49:498]: Running as a service. MSI (s) (B8:48) [11:25:49:498]: Hello, I'm your 32bit Elevated custom action server. MSI (s) (B8!44) [11:25:49:514]: Creating MSIHANDLE (5) of type 790531 for thread 2628 CAQuietExec: Error 0x80070002: Command failed to execute. MSI (s) (B8!44) [11:25:49:514]: Closing MSIHANDLE (5) of type 790531 for thread 2628 MSI (s) (B8!44) [11:25:49:514]: Creating MSIHANDLE (6) of type 790531 for thread 2628 CAQuietExec: Error 0x80070002: CAQuietExec Failed MSI (s) (B8!44) [11:25:49:514]: Closing MSIHANDLE (6) of type 790531 for thread 2628 CustomAction SetInstallCmd returned actual error code 1603 but will be translated to success due to continue marking MSI (s) (B8:D8) [11:25:49:514]: Closing MSIHANDLE (4) of type 790536 for thread 1908 MSI (s) (B8:74) [11:25:49:514]: Executing op: ActionStart(Name=InstallAHCI64,Description="Installing ",) MSI (s) (B8:74) [11:25:49:514]: Executing op: CustomActionSchedule(Action=InstallAHCI64,ActionType=3138,Source=BinaryData,Target=/F /PATH "C:\Program Files\\\",) CustomAction InstallAHCI64 returned actual error code 1073741825 but will be translated to success due to continue marking Any ideas? Thank you -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Does-wix-support-calling-bcdedit-tp7551749.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does wix support calling bcdedit?
http://msdn.microsoft.com/en-us/library/windows/hardware/ff553484(v=vs.8 5).aspx I see two issues, the first being you are using / instead of -, though I am not sure if it matters. The second being that you didn't read the fine print, " Note After you change the TESTSIGNING boot configuration option, restart the computer for the change to take effect. " Why not just turn the flag on for your test machine and leave it on? This sort of change should not be used in a production environment. -Original Message- From: victorwhiskey [mailto:victorhwhis...@yahoo.com] Sent: Friday, May 11, 2012 3:08 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Does wix support calling bcdedit? Hi, I'm trying to call bcdedit from a deferred custom action to set the machine in test mode. I'm trying to install unsigned drivers at the moment so I want to put the machine in test mode with the command "bcdedit /set testsigning on". I'm calling CAQuietExec byt I'm getting Error 0x80070002 These are snips of my log: MSI (s) (B8:74) [11:25:49:046]: Note: 1: 2205 2: 3: PatchPackage Action ended 11:25:49: InstallFiles. Return value 1. MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd_Cmd Action start 11:25:49: SetInstallCmd_Cmd. MSI (s) (B8:74) [11:25:49:046]: PROPERTY CHANGE: Adding SetInstallCmd property. Its value is '"C:\Windows\system32\\bcdedit.exe" /set "testsigning on"'. Action ended 11:25:49: SetInstallCmd_Cmd. Return value 1. MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd Action start 11:25:49: SetInstallCmd. Action ended 11:25:49: SetInstallCmd. Return value 1. MSI (s) (B8:74) [11:25:49:062]: Doing action: InstallAHCI64 ... MSI (s) (B8:74) [11:25:49:140]: Executing op: ActionStart(Name=SetInstallCmd,,) MSI (s) (B8:74) [11:25:49:140]: Executing op: CustomActionSchedule(Action=SetInstallCmd,ActionType=3137,Source=BinaryD ata,Target=CAQuietExec,CustomActionData="C:\Windows\system32\\bcdedit.ex e" /set "testsigning on") MSI (s) (B8:74) [11:25:49:140]: Creating MSIHANDLE (4) of type 790536 for thread 1908 MSI (s) (B8:D8) [11:25:49:140]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIC31B.tmp, Entrypoint: CAQuietExec MSI (s) (B8:C4) [11:25:49:140]: Generating random cookie. MSI (s) (B8:C4) [11:25:49:140]: Created Custom Action Server with PID 1884 (0x75C). MSI (s) (B8:48) [11:25:49:498]: Running as a service. MSI (s) (B8:48) [11:25:49:498]: Hello, I'm your 32bit Elevated custom action server. MSI (s) (B8!44) [11:25:49:514]: Creating MSIHANDLE (5) of type 790531 for thread 2628 CAQuietExec: Error 0x80070002: Command failed to execute. MSI (s) (B8!44) [11:25:49:514]: Closing MSIHANDLE (5) of type 790531 for thread 2628 MSI (s) (B8!44) [11:25:49:514]: Creating MSIHANDLE (6) of type 790531 for thread 2628 CAQuietExec: Error 0x80070002: CAQuietExec Failed MSI (s) (B8!44) [11:25:49:514]: Closing MSIHANDLE (6) of type 790531 for thread 2628 CustomAction SetInstallCmd returned actual error code 1603 but will be translated to success due to continue marking MSI (s) (B8:D8) [11:25:49:514]: Closing MSIHANDLE (4) of type 790536 for thread 1908 MSI (s) (B8:74) [11:25:49:514]: Executing op: ActionStart(Name=InstallAHCI64,Description="Installing ",) MSI (s) (B8:74) [11:25:49:514]: Executing op: CustomActionSchedule(Action=InstallAHCI64,ActionType=3138,Source=BinaryD ata,Target=/F /PATH "C:\Program Files\\\",) CustomAction InstallAHCI64 returned actual error code 1073741825 but will be translated to success due to continue marking Any ideas? Thank you -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Does-wix-s upport-calling-bcdedit-tp7551749.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does wix support calling bcdedit?
Windows Installer folder properties include a backslash. Try: '"[System64Folder]bcdedit.exe" Phil W -Original Message- From: Vincent Wong [mailto:victorhwhis...@yahoo.com] Sent: Friday, May 11, 2012 1:23 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Does wix support calling bcdedit? Sorry, Here's the CA codes and I'm running elevated as perMachine install --- On Fri, 5/11/12, victorwhiskey wrote: From: victorwhiskey Subject: [WiX-users] Does wix support calling bcdedit? To: wix-users@lists.sourceforge.net Date: Friday, May 11, 2012, 8:07 PM Hi, I'm trying to call bcdedit from a deferred custom action to set the machine in test mode. I'm trying to install unsigned drivers at the moment so I want to put the machine in test mode with the command "bcdedit /set testsigning on". I'm calling CAQuietExec byt I'm getting Error 0x80070002 These are snips of my log: MSI (s) (B8:74) [11:25:49:046]: Note: 1: 2205 2: 3: PatchPackage Action ended 11:25:49: InstallFiles. Return value 1. MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd_Cmd Action start 11:25:49: SetInstallCmd_Cmd. MSI (s) (B8:74) [11:25:49:046]: PROPERTY CHANGE: Adding SetInstallCmd property. Its value is '"C:\Windows\system32\\bcdedit.exe" /set "testsigning on"'. Action ended 11:25:49: SetInstallCmd_Cmd. Return value 1. MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd Action start 11:25:49: SetInstallCmd. Action ended 11:25:49: SetInstallCmd. Return value 1. MSI (s) (B8:74) [11:25:49:062]: Doing action: InstallAHCI64 ... MSI (s) (B8:74) [11:25:49:140]: Executing op: ActionStart(Name=SetInstallCmd,,) MSI (s) (B8:74) [11:25:49:140]: Executing op: CustomActionSchedule(Action=SetInstallCmd,ActionType=3137,Source=BinaryData,Target=CAQuietExec,CustomActionData="C:\Windows\system32\\bcdedit.exe" /set "testsigning on") MSI (s) (B8:74) [11:25:49:140]: Creating MSIHANDLE (4) of type 790536 for thread 1908 MSI (s) (B8:D8) [11:25:49:140]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIC31B.tmp, Entrypoint: CAQuietExec MSI (s) (B8:C4) [11:25:49:140]: Generating random cookie. MSI (s) (B8:C4) [11:25:49:140]: Created Custom Action Server with PID 1884 (0x75C). MSI (s) (B8:48) [11:25:49:498]: Running as a service. MSI (s) (B8:48) [11:25:49:498]: Hello, I'm your 32bit Elevated custom action server. MSI (s) (B8!44) [11:25:49:514]: Creating MSIHANDLE (5) of type 790531 for thread 2628 CAQuietExec: Error 0x80070002: Command failed to execute. MSI (s) (B8!44) [11:25:49:514]: Closing MSIHANDLE (5) of type 790531 for thread 2628 MSI (s) (B8!44) [11:25:49:514]: Creating MSIHANDLE (6) of type 790531 for thread 2628 CAQuietExec: Error 0x80070002: CAQuietExec Failed MSI (s) (B8!44) [11:25:49:514]: Closing MSIHANDLE (6) of type 790531 for thread 2628 CustomAction SetInstallCmd returned actual error code 1603 but will be translated to success due to continue marking MSI (s) (B8:D8) [11:25:49:514]: Closing MSIHANDLE (4) of type 790536 for thread 1908 MSI (s) (B8:74) [11:25:49:514]: Executing op: ActionStart(Name=InstallAHCI64,Description="Installing ",) MSI (s) (B8:74) [11:25:49:514]: Executing op: CustomActionSchedule(Action=InstallAHCI64,ActionType=3138,Source=BinaryData,Target=/F /PATH "C:\Program Files\\\",) CustomAction InstallAHCI64 returned actual error code 1073741825 but will be translated to success due to continue marking Any ideas? Thank you -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Does-wix-support-calling-bcdedit-tp7551749.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well
Re: [WiX-users] Managed bootstrap failing to load
I got tripped up on that and a few other miscellaneous details as well. It
might be worth getting everything just right and exporting a project template
(File > Export Template...) for future use.
David
-Original Message-
From: Nigel Morse [mailto:nigel.mo...@red-gate.com]
Sent: Thursday, May 10, 2012 12:55 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed bootstrap failing to load
*looks sheepish*
Forgot the:
[assembly: BootstrapperApplication(typeof(TestBa.TestBa))]
All good now :)
Cheers,
Nigel
-Original Message-
From: Nigel Morse [mailto:nigel.mo...@red-gate.com]
Sent: 10 May 2012 17:46
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Managed bootstrap failing to load
Hi,
I'm trying to create a managed bootstrap installer but the error log is telling
me it's failing to create it:
[0AFC:15D4][2012-05-10T17:38:07]: Setting string variable
'WixBundleOriginalSource' to value 'C:\temp\testbundle\Bundle.exe'
[0AFC:15D4][2012-05-10T17:38:08]: Setting string variable 'WixBundleName' to
value 'TestBundle'
[0AFC:15D4][2012-05-10T17:38:08]: Loading managed bootstrapper application.
[0AFC:15D4][2012-05-10T17:38:08]: Error 0x80131508: Failed to create the
managed bootstrapper application.
[0AFC:15D4][2012-05-10T17:38:08]: Error 0x80131508: Failed to create UX.
[0AFC:15D4][2012-05-10T17:38:08]: Error 0x80131508: Failed to load UX.
[0AFC:15D4][2012-05-10T17:38:08]: Error 0x80131508: Failed while running
The .wxs file is below (there is the netfx.wxs as well, taken verbatim from the
Wix Toolset installer source. Obviously there are more MSI packages to go in,
but I pulled them out of this example)
http://schemas.microsoft.com/wix/2006/wi";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
The DLL itself is just
namespace TestBa
{
public class TestBa : BootstrapperApplication
{
protected override void Run()
{
MessageBox.Show("Hello World");
Engine.Quit(0);
}
}
}
And the config file:
Any ideas what I've done wrong?
Thanks,
Nigel
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will include
endpoint security, mobile security and the latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will include
endpoint security, mobile security and the latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Managed bootstrap failing to load
Alan,
Dispatcher.Run() starts a message loop. You should setup any UI you want to
display before that, or just call ShowDialog() on your main dialog directly.
Not that you will also need to call a few methods on Engine (Detect(), Plan(),
Apply()...) to actually get things to install. The WixBA used to install WiX
3.6 is a good place to see a working example.
David
-Original Message-
From: AlanBrianCovington [mailto:briancoving...@yahoo.com]
Sent: Friday, May 11, 2012 10:16 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Managed bootstrap failing to load
Nigel,
Did you get this working past the "Hello World"? I got this far, but cannot
get Burn to install my packages with my custom bootstrapper application. It
appears to get to the Threading.Dispatcher.Run call, but then just sits there
(ie I never get the second message box):
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.Tools.WindowsInstallerXml.Bootstrapper;
using System.Windows.Forms;
using Threading = System.Windows.Threading;
namespace MyBA
{
public class TestBA : BootstrapperApplication
{
static public Threading.Dispatcher Dispatcher { get; private set; }
protected override void Run()
{
this.Engine.Log(LogLevel.Verbose, "Running the TestBA.");
TestBA.Dispatcher = Threading.Dispatcher.CurrentDispatcher;
MessageBox.Show("My Bootstrapper Application is running");
Threading.Dispatcher.Run();
MessageBox.Show("Dispatcher Run has finished.");
this.Engine.Quit(0);
}
}
}
Any little bit of help you could provide would be GREATLY appreciated.
Best regards,
Brian
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-bootstrap-failing-to-load-tp7547420p7550586.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will include
endpoint security, mobile security and the latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Does wix support calling bcdedit?
HRESULT 0x80070002 means ERROR_FILE_NOT_FOUND See http://msdn.microsoft.com/en-us/library/windows/desktop/dd319335.aspx Open up a cmd prompt and execute the following command (don't change the quotes or anything else): "C:\Windows\system32\\bcdedit.exe" /set "testsigning on" Verify whether the command above (exactly) succeeds or fails. The command above is the exact command that your custom action is attempting to execute. If it works, then you'll need to continue investigating. If it doesn't then there's something wrong in the way you set the SetInstallCmd property. Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail > -Original Message- > From: Vincent Wong [mailto:victorhwhis...@yahoo.com] > Sent: Friday, May 11, 2012 1:23 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Does wix support calling bcdedit? > > Sorry, > > Here's the CA codes and I'm running elevated as perMachine install > > Property="SetInstallCmd" > Value='"[System64Folder]\bcdedit.exe" /set "testsigning > on"' /> > BinaryKey="WixCA" > DllEntry="CAQuietExec" > Return="ignore" > Execute="deferred" > Impersonate="no"/> > > --- On Fri, 5/11/12, victorwhiskey wrote: > > From: victorwhiskey > Subject: [WiX-users] Does wix support calling bcdedit? > To: wix-users@lists.sourceforge.net > Date: Friday, May 11, 2012, 8:07 PM > > Hi, > > I'm trying to call bcdedit from a deferred custom action to set the machine in > test mode. I'm trying to install unsigned drivers at the moment so I want to > put > the machine in test mode with the command "bcdedit /set testsigning on". > > I'm calling CAQuietExec byt I'm getting Error 0x80070002 > > These are snips of my log: > > MSI (s) (B8:74) [11:25:49:046]: Note: 1: 2205 2: 3: PatchPackage Action ended > 11:25:49: InstallFiles. Return value 1. > MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd_Cmd Action start > 11:25:49: SetInstallCmd_Cmd. > MSI (s) (B8:74) [11:25:49:046]: PROPERTY CHANGE: Adding SetInstallCmd > property. Its value is '"C:\Windows\system32\\bcdedit.exe" /set "testsigning > on"'. > Action ended 11:25:49: SetInstallCmd_Cmd. Return value 1. > MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd Action start > 11:25:49: SetInstallCmd. > Action ended 11:25:49: SetInstallCmd. Return value 1. > MSI (s) (B8:74) [11:25:49:062]: Doing action: InstallAHCI64 > > ... > > MSI (s) (B8:74) [11:25:49:140]: Executing op: > ActionStart(Name=SetInstallCmd,,) > MSI (s) (B8:74) [11:25:49:140]: Executing op: > CustomActionSchedule(Action=SetInstallCmd,ActionType=3137,Source=BinaryD > ata,Target=CAQuietExec,CustomActionData="C:\Windows\system32\\bcdedit.e > xe" > /set "testsigning on") > MSI (s) (B8:74) [11:25:49:140]: Creating MSIHANDLE (4) of type 790536 for > thread 1908 MSI (s) (B8:D8) [11:25:49:140]: Invoking remote custom action. > DLL: > C:\Windows\Installer\MSIC31B.tmp, Entrypoint: CAQuietExec MSI (s) (B8:C4) > [11:25:49:140]: Generating random cookie. > MSI (s) (B8:C4) [11:25:49:140]: Created Custom Action Server with PID 1884 > (0x75C). > MSI (s) (B8:48) [11:25:49:498]: Running as a service. > MSI (s) (B8:48) [11:25:49:498]: Hello, I'm your 32bit Elevated custom action > server. > MSI (s) (B8!44) [11:25:49:514]: Creating MSIHANDLE (5) of type 790531 for > thread 2628 > CAQuietExec: Error 0x80070002: Command failed to execute. > MSI (s) (B8!44) [11:25:49:514]: Closing MSIHANDLE (5) of type 790531 for > thread 2628 MSI (s) (B8!44) [11:25:49:514]: Creating MSIHANDLE (6) of type > 790531 for thread 2628 > CAQuietExec: Error 0x80070002: CAQuietExec Failed MSI (s) (B8!44) > [11:25:49:514]: Closing MSIHANDLE (6) of type 790531 for thread 2628 > CustomAction SetInstallCmd returned actual error code 1603 but will be > translated to success due to continue marking MSI (s) (B8:D8) [11:25:49:514]: > Closing MSIHANDLE (4) of type 790536 for thread 1908 MSI (s) (B8:74) > [11:25:49:514]: Executing op: > ActionStart(Name=InstallAHCI64,Description="Installing ",) MSI (s) (B8:74) > [11:25:49:514]: Executing op: > CustomActionSchedule(Action=InstallAHCI64,ActionType=3138,Source=BinaryD > ata,Target=/F > /PATH "C:\Program Files\\\",) > CustomAction InstallAHCI64 returned actual error code 1073741825 but will be > translated to success due to continue marking > > > Any ideas? > > Thank you > > > -- > View this message in context: http://windows-installer-xml-wix- > toolset.687559.n2.nabble.com/Does-wix-support-calling-bcdedit- > tp7551749.html > Sent from the wix-users mailing list archive at Nabble.com. > > -- > Live Security Virtual Conference > Exclusive live event will cover al
Re: [WiX-users] Does wix support calling bcdedit?
...which is why I suggested deleting that extra "\" as something to try. -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Friday, May 11, 2012 2:37 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Does wix support calling bcdedit? HRESULT 0x80070002 means ERROR_FILE_NOT_FOUND See http://msdn.microsoft.com/en-us/library/windows/desktop/dd319335.aspx Open up a cmd prompt and execute the following command (don't change the quotes or anything else): "C:\Windows\system32\\bcdedit.exe" /set "testsigning on" Verify whether the command above (exactly) succeeds or fails. The command above is the exact command that your custom action is attempting to execute. If it works, then you'll need to continue investigating. If it doesn't then there's something wrong in the way you set the SetInstallCmd property. Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail > -Original Message- > From: Vincent Wong [mailto:victorhwhis...@yahoo.com] > Sent: Friday, May 11, 2012 1:23 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Does wix support calling bcdedit? > > Sorry, > > Here's the CA codes and I'm running elevated as perMachine install > > Property="SetInstallCmd" > Value='"[System64Folder]\bcdedit.exe" /set > "testsigning on"' /> > BinaryKey="WixCA" > DllEntry="CAQuietExec" > Return="ignore" > Execute="deferred" > Impersonate="no"/> > > --- On Fri, 5/11/12, victorwhiskey wrote: > > From: victorwhiskey > Subject: [WiX-users] Does wix support calling bcdedit? > To: wix-users@lists.sourceforge.net > Date: Friday, May 11, 2012, 8:07 PM > > Hi, > > I'm trying to call bcdedit from a deferred custom action to set the > machine in test mode. I'm trying to install unsigned drivers at the > moment so I want to put the machine in test mode with the command "bcdedit > /set testsigning on". > > I'm calling CAQuietExec byt I'm getting Error 0x80070002 > > These are snips of my log: > > MSI (s) (B8:74) [11:25:49:046]: Note: 1: 2205 2: 3: PatchPackage > Action ended > 11:25:49: InstallFiles. Return value 1. > MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd_Cmd Action > start > 11:25:49: SetInstallCmd_Cmd. > MSI (s) (B8:74) [11:25:49:046]: PROPERTY CHANGE: Adding SetInstallCmd > property. Its value is '"C:\Windows\system32\\bcdedit.exe" /set > "testsigning on"'. > Action ended 11:25:49: SetInstallCmd_Cmd. Return value 1. > MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd Action > start > 11:25:49: SetInstallCmd. > Action ended 11:25:49: SetInstallCmd. Return value 1. > MSI (s) (B8:74) [11:25:49:062]: Doing action: InstallAHCI64 > > ... > > MSI (s) (B8:74) [11:25:49:140]: Executing op: > ActionStart(Name=SetInstallCmd,,) > MSI (s) (B8:74) [11:25:49:140]: Executing op: > CustomActionSchedule(Action=SetInstallCmd,ActionType=3137,Source=Binar > yD > ata,Target=CAQuietExec,CustomActionData="C:\Windows\system32\\bcdedit. > e > xe" > /set "testsigning on") > MSI (s) (B8:74) [11:25:49:140]: Creating MSIHANDLE (4) of type 790536 > for thread 1908 MSI (s) (B8:D8) [11:25:49:140]: Invoking remote custom action. > DLL: > C:\Windows\Installer\MSIC31B.tmp, Entrypoint: CAQuietExec MSI (s) > (B8:C4) > [11:25:49:140]: Generating random cookie. > MSI (s) (B8:C4) [11:25:49:140]: Created Custom Action Server with PID > 1884 (0x75C). > MSI (s) (B8:48) [11:25:49:498]: Running as a service. > MSI (s) (B8:48) [11:25:49:498]: Hello, I'm your 32bit Elevated custom > action server. > MSI (s) (B8!44) [11:25:49:514]: Creating MSIHANDLE (5) of type 790531 > for thread 2628 > CAQuietExec: Error 0x80070002: Command failed to execute. > MSI (s) (B8!44) [11:25:49:514]: Closing MSIHANDLE (5) of type 790531 > for thread 2628 MSI (s) (B8!44) [11:25:49:514]: Creating MSIHANDLE (6) > of type > 790531 for thread 2628 > CAQuietExec: Error 0x80070002: CAQuietExec Failed MSI (s) (B8!44) > [11:25:49:514]: Closing MSIHANDLE (6) of type 790531 for thread 2628 > CustomAction SetInstallCmd returned actual error code 1603 but will be > translated to success due to continue marking MSI (s) (B8:D8) [11:25:49:514]: > Closing MSIHANDLE (4) of type 790536 for thread 1908 MSI (s) (B8:74) > [11:25:49:514]: Executing op: > ActionStart(Name=InstallAHCI64,Description="Installing ",) MSI (s) > (B8:74) > [11:25:49:514]: Executing op: > CustomActionSchedule(Action=InstallAHCI64,ActionType=3138,Source=Binar > yD > ata,Target=/F > /PATH "C:\Program Files\\\",) > CustomAction InstallAHCI64 returned actual error code 1073741825 but > will be translated to success due to continue marking > > > Any ideas? > > Thank you > > > --
Re: [WiX-users] Does wix support calling bcdedit?
Thanks Phil and Edwin, I tried out my command and I know it works, but it works when I right click on command prompt and select "run as administrator". I thought with perMachine mode, install privileges="elevated" and deferred custom action would cover, but I'm still getting the same error. --- On Fri, 5/11/12, Wilson, Phil wrote: From: Wilson, Phil Subject: Re: [WiX-users] Does wix support calling bcdedit? To: "General discussion for Windows Installer XML toolset." Date: Friday, May 11, 2012, 9:44 PM ...which is why I suggested deleting that extra "\" as something to try. -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Friday, May 11, 2012 2:37 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Does wix support calling bcdedit? HRESULT 0x80070002 means ERROR_FILE_NOT_FOUND See http://msdn.microsoft.com/en-us/library/windows/desktop/dd319335.aspx Open up a cmd prompt and execute the following command (don't change the quotes or anything else): "C:\Windows\system32\\bcdedit.exe" /set "testsigning on" Verify whether the command above (exactly) succeeds or fails. The command above is the exact command that your custom action is attempting to execute. If it works, then you'll need to continue investigating. If it doesn't then there's something wrong in the way you set the SetInstallCmd property. Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail > -Original Message- > From: Vincent Wong [mailto:victorhwhis...@yahoo.com] > Sent: Friday, May 11, 2012 1:23 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Does wix support calling bcdedit? > > Sorry, > > Here's the CA codes and I'm running elevated as perMachine install > > Property="SetInstallCmd" > Value='"[System64Folder]\bcdedit.exe" /set > "testsigning on"' /> > BinaryKey="WixCA" > DllEntry="CAQuietExec" > Return="ignore" > Execute="deferred" > Impersonate="no"/> > > --- On Fri, 5/11/12, victorwhiskey wrote: > > From: victorwhiskey > Subject: [WiX-users] Does wix support calling bcdedit? > To: wix-users@lists.sourceforge.net > Date: Friday, May 11, 2012, 8:07 PM > > Hi, > > I'm trying to call bcdedit from a deferred custom action to set the > machine in test mode. I'm trying to install unsigned drivers at the > moment so I want to put the machine in test mode with the command "bcdedit > /set testsigning on". > > I'm calling CAQuietExec byt I'm getting Error 0x80070002 > > These are snips of my log: > > MSI (s) (B8:74) [11:25:49:046]: Note: 1: 2205 2: 3: PatchPackage > Action ended > 11:25:49: InstallFiles. Return value 1. > MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd_Cmd Action > start > 11:25:49: SetInstallCmd_Cmd. > MSI (s) (B8:74) [11:25:49:046]: PROPERTY CHANGE: Adding SetInstallCmd > property. Its value is '"C:\Windows\system32\\bcdedit.exe" /set > "testsigning on"'. > Action ended 11:25:49: SetInstallCmd_Cmd. Return value 1. > MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd Action > start > 11:25:49: SetInstallCmd. > Action ended 11:25:49: SetInstallCmd. Return value 1. > MSI (s) (B8:74) [11:25:49:062]: Doing action: InstallAHCI64 > > ... > > MSI (s) (B8:74) [11:25:49:140]: Executing op: > ActionStart(Name=SetInstallCmd,,) > MSI (s) (B8:74) [11:25:49:140]: Executing op: > CustomActionSchedule(Action=SetInstallCmd,ActionType=3137,Source=Binar > yD > ata,Target=CAQuietExec,CustomActionData="C:\Windows\system32\\bcdedit. > e > xe" > /set "testsigning on") > MSI (s) (B8:74) [11:25:49:140]: Creating MSIHANDLE (4) of type 790536 > for thread 1908 MSI (s) (B8:D8) [11:25:49:140]: Invoking remote custom action. > DLL: > C:\Windows\Installer\MSIC31B.tmp, Entrypoint: CAQuietExec MSI (s) > (B8:C4) > [11:25:49:140]: Generating random cookie. > MSI (s) (B8:C4) [11:25:49:140]: Created Custom Action Server with PID > 1884 (0x75C). > MSI (s) (B8:48) [11:25:49:498]: Running as a service. > MSI (s) (B8:48) [11:25:49:498]: Hello, I'm your 32bit Elevated custom > action server. > MSI (s) (B8!44) [11:25:49:514]: Creating MSIHANDLE (5) of type 790531 > for thread 2628 > CAQuietExec: Error 0x80070002: Command failed to execute. > MSI (s) (B8!44) [11:25:49:514]: Closing MSIHANDLE (5) of type 790531 > for thread 2628 MSI (s) (B8!44) [11:25:49:514]: Creating MSIHANDLE (6) > of type > 790531 for thread 2628 > CAQuietExec: Error 0x80070002: CAQuietExec Failed MSI (s) (B8!44) > [11:25:49:514]: Closing MSIHANDLE (6) of type 790531 for thread 2628 > CustomAction SetInstallCmd returned actual error code 1603 but will be > translated to success due to continue marking MSI (s) (B8:D8) [11:25:49:514]:
Re: [WiX-users] Does wix support calling bcdedit?
References on the web suggest that you have too many quotes (and you didn't run the command as I copied it). Did you run the following: "C:\Windows\system32\\bcdedit.exe" /set testsigning on Instead of what I asked you to execute: "C:\Windows\system32\\bcdedit.exe" /set "testsigning on" All the examples I see online suggest that the one without quotes should work. I haven't tried either because this seems like a bad idea but I have a feeling you ran the command without quotes. Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail > -Original Message- > From: Vincent Wong [mailto:victorhwhis...@yahoo.com] > Sent: Friday, May 11, 2012 4:40 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Does wix support calling bcdedit? > > Thanks Phil and Edwin, > > I tried out my command and I know it works, but it works when I right click on > command prompt and select "run as administrator". I thought with > perMachine mode, install privileges="elevated" and deferred custom action > would cover, but I'm still getting the same error. > > > > --- On Fri, 5/11/12, Wilson, Phil wrote: > > From: Wilson, Phil > Subject: Re: [WiX-users] Does wix support calling bcdedit? > To: "General discussion for Windows Installer XML toolset." us...@lists.sourceforge.net> > Date: Friday, May 11, 2012, 9:44 PM > > ...which is why I suggested deleting that extra "\" as something to try. > > -Original Message- > From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] > Sent: Friday, May 11, 2012 2:37 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Does wix support calling bcdedit? > > HRESULT 0x80070002 means ERROR_FILE_NOT_FOUND > > See http://msdn.microsoft.com/en-us/library/windows/desktop/dd319335.aspx > > > Open up a cmd prompt and execute the following command (don't change the > quotes or anything else): > > "C:\Windows\system32\\bcdedit.exe" /set "testsigning on" > > Verify whether the command above (exactly) succeeds or fails. The command > above is the exact command that your custom action is attempting to execute. > If it works, then you'll need to continue investigating. If it doesn't then > there's > something wrong in the way you set the SetInstallCmd property. > > Edwin G. Castro > Software Developer - Staff > Digital Channels > Fiserv > Office: 503-746-0643 > Fax: 503-617-0291 > www.fiserv.com > P Please consider the environment before printing this e-mail > > > > -Original Message- > > From: Vincent Wong [mailto:victorhwhis...@yahoo.com] > > Sent: Friday, May 11, 2012 1:23 PM > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Does wix support calling bcdedit? > > > > Sorry, > > > > Here's the CA codes and I'm running elevated as perMachine install > > > > > Property="SetInstallCmd" > > Value='"[System64Folder]\bcdedit.exe" /set > > "testsigning on"' /> > > > BinaryKey="WixCA" > > DllEntry="CAQuietExec" > > Return="ignore" > > Execute="deferred" > > Impersonate="no"/> > > > > --- On Fri, 5/11/12, victorwhiskey wrote: > > > > From: victorwhiskey > > Subject: [WiX-users] Does wix support calling bcdedit? > > To: wix-users@lists.sourceforge.net > > Date: Friday, May 11, 2012, 8:07 PM > > > > Hi, > > > > I'm trying to call bcdedit from a deferred custom action to set the > > machine in test mode. I'm trying to install unsigned drivers at the > > moment so I want to put the machine in test mode with the command > "bcdedit /set testsigning on". > > > > I'm calling CAQuietExec byt I'm getting Error 0x80070002 > > > > These are snips of my log: > > > > MSI (s) (B8:74) [11:25:49:046]: Note: 1: 2205 2: 3: PatchPackage > > Action ended > > 11:25:49: InstallFiles. Return value 1. > > MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd_Cmd Action > > start > > 11:25:49: SetInstallCmd_Cmd. > > MSI (s) (B8:74) [11:25:49:046]: PROPERTY CHANGE: Adding SetInstallCmd > > property. Its value is '"C:\Windows\system32\\bcdedit.exe" /set > > "testsigning on"'. > > Action ended 11:25:49: SetInstallCmd_Cmd. Return value 1. > > MSI (s) (B8:74) [11:25:49:046]: Doing action: SetInstallCmd Action > > start > > 11:25:49: SetInstallCmd. > > Action ended 11:25:49: SetInstallCmd. Return value 1. > > MSI (s) (B8:74) [11:25:49:062]: Doing action: InstallAHCI64 > > > > ... > > > > MSI (s) (B8:74) [11:25:49:140]: Executing op: > > ActionStart(Name=SetInstallCmd,,) > > MSI (s) (B8:74) [11:25:49:140]: Executing op: > > CustomActionSchedule(Action=SetInstallCmd,ActionType=3137,Source=Binar > > yD > > > ata,Target=CAQuietExec,CustomActionData="C:\Windows\system32\\bcdedit. > > e > > xe" > > /set "testsigning on
