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 t
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.
...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
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
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 Wix
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: Thurs
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-us
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
opt
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
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
T
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 too
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 d
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
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
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
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
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;
us
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
---
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-
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]
Se
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
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 war
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 custo
> 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)\M
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.call
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)\Micros
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
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 syst
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 t
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
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 a
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 p
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 o
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 Regard
34 matches
Mail list logo
