I developed a MSI Installer using WixV3 and MS2005. It is working fine for
me. Now I have to provide Terminal Services support in my installer. When I
tried to install on Win2003. I am getting error that Terminal Services
version of driver is required. How I can make my installer to terminal
Hello,
I was looking at the weekly build available for download an I noticed the
change log file.
How do you proceed it ? List of the Comments of each checkIn ordered by User ?
something else ?
regards,
-
This
As part of my install I have an unsigned NDIS IM Network driver component:
I am using the following format, with DriverLegacy set to 'yes' because the
driver is unsigned,
DriverForceInstall set to 'yes' because I want to ensure any file left
behind after a previous uninstall
gets overwritten and
Hi Bob - thanks for that help.
I reverted back to using the same Visual Studio MSM for the WiX installers
for this shared COM component (hoping that it would help). Unfortunately it
seems that this behaviour (un-installing the VS MSI breaking the COM
registration of the shared COM component used
You're right.drvutil.dll is from APC SDK.Could you give me any sample or a
link which demonstrate the implementation method you are talking about?
Christopher Painter wrote:
Is drvutil.dll your own DLL or are you using a third party dll? Googling
the name seems to imply that it might be
Anytime I have anything odd going on I always look to a verbose log file
first.
MSIEXEC /L*v name of log file /I name of msi file
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Blankley
Sent: Monday, October 15, 2007 7:04 AM
To:
Hello,
Let's say I have three features - fA, fB, fC. All of these features are
at the same level - Level 1. But only fA and fB are shown to the user.
fB is hidden from the user and should be installed if fA or fB is
installed. If neither of those gets installed, fC should not be
installed.
I had to use XMLPoke to inject a version number into a .wxs file. The
following link helped in getting XMLPoke to work with .wxs files...
http://solepano.blogspot.com/2006/11/problem-with-nants-xmlpoke-task.html
However it seems that NANT also injects the byteorder marks into the file at
the
What is a bootstrap installer how can it be used to install Adobe Reader
other softwares such as .NET 2.0 or .NET 3.0? Is there any example available
where it shows how to add bootstrap installer to your installer install
dependency softwares during your software install?
Please help.
Hina
--
Surely that message is coming from the driver? Your setup is probably
fine for a TS install, but that message seems to be saying that there is
a completely different version of the driver required for TS.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Chad: Thanks for the suggestion.
Unfortunately, the files that fail to be newly incorporated spit out the
exact same info as files that were part of the original msi.
What's also weird is that there seems to be no consistency to this. Other
files are added fine (but not in that directory).
dir
I've never seen a log file be inaccurate as to what happened. And I've
never seen a log file give the same info for files that are installed
versus not installed. Look for the logging of the Component. For the
Components that do not get installed does it say Action: Null? See the
example below of
Robert,
I encountered this same issue when porting our installer from
InstallShield to WiX. InstallShield has the ability to make dependencies
between features - I decompiled the MSI and discovered that it does it
with a custom action and a custom table of dependencies called
ISRequiredFeature.
Below is the output from 2 files. It looks a little different than yours.
The first is successfully installed when I run the msi/msp. The 2nd is
not found on the installed media.
Is there a way I can look inside the cab inside the msi to confirm that
the missing file is indeed in the msi?
The Windows SDK has a utility called 'Orca' that can show you the raw
tables in an MSI. I use it constantly to check Files tables when our
developers claim something is missing from my installers.
You can probably find Orca in other places, but that's one place I know
it resides. It might already
Hello List,
I'm trying to build multiple similar setups (Pro, Standard, Base) of
our product from a single WiX sources. And I'm trying to keep guids
whenever possible.
Bob Arnson wrote earlier in this list that guids are product-global
and it's ok to keep the same guids, but when products are
If two components have the same GUID, they must be the same including
the directory.
-Original Message-
From: [EMAIL PROTECTED] [mailto:wix-users-
[EMAIL PROTECTED] On Behalf Of Ilya Slobodin
Sent: Monday, October 15, 2007 2:29 PM
To: wix-users@lists.sourceforge.net
Subject:
I will be out of the office starting 15/10/2007 and will not return until
17/10/2007.
I will respond to your message when I return
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find
WiX deliberately does not have any mechanism for automatically collecting
files because it's way too easy to break component rules. My initial guess
would be that you've added them to an existing component (which it is
strongly recommend you avoid) but the key file of that component isn't
changed,
Not necessarily true. It is OK to install the same component to different
paths; it is definitely wrong to install two different components to the
same path as then the references get cross-linked.
Windows Installer tracks where every installed product installed every
component that it installed.
Installing the same component to two different folders does not break
component rules - this is allowed. Indeed, if installed to the same
location, the behaviour may be surprising - installing product A with
component version 1 then product B with component version 2, then
uninstalling B will
John Hall wrote:
However, in hindsight, I think just using a ComponentGroupRef instead
of feature fC and including it in both fA and fB might be simpler and
more robust. Not sure what the relative downsides are.
If the feature was used just for grouping (i.e., it's never visible or
user
To whom should the bug be assigned to ?
From: Bob Arnson [EMAIL PROTECTED]
Sent: Monday, October 15, 2007 10:15 PM
To: Harini Gurusamy
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Registry and Permission
Harini Gurusamy wrote:
Registry Id=”Reg”
23 matches
Mail list logo