Would be interesting to see if the parent PID is really burn starting another
burn instance, or if the CA inside the MSI that is running about that time is
spawning it (process explorer would tell you this). I also think were missing
a log file for the second instance of the bundle that
Process Explorer shows:
1. Parent of second instance was msiexec, which already closed.
2. Second instance don't have sub process with same name like first.
3. The log for second instance is same with first. Second log file really
doesn't exist.
-Original Message-
From: Hoover,
If you run this:
msiexec /quiet /i PKIClient-x32-5.1.msi ARPSYSTEMCOMPONENT=1
MSIFASTINSTALL=7
Do you see the same thing?
-Original Message-
From: Alexey Larsky-RUS [mailto:alexey.lar...@jeppesen.com]
Sent: 14 October 2013 06:37
To: General discussion for Windows Installer XML
Quiet and full mode installations from command line goes normal, without second
gui windows.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Monday, October 14, 2013 11:23 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
That is odd - did you put a
screenshot somewhere?
Neil
On 14 Oct 2013, at 09:06, Alexey Larsky-RUS alexey.lar...@jeppesen.com
wrote:
Quiet and full mode installations from command line goes normal, without
second gui windows.
-Original Message-
From: Neil Sleightholm
Hi,
How to create .wixmsp file.I checked all the methods which present in
Google.but,i cant able to prepare .wixmsp file.
I want to create MSP file which install for Hotfixes and install updates.
--
Thanks Regards,
Chaitanya.
The windows installer property reference is a good resource to know.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370905(v=vs.85).aspx
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: 11 October 2013 17:10
To: General discussion for Windows
AladdinETokenDriverBug.exe /quiet - doesn't show any window.
AladdinETokenDriverBug.exe /passive - opens second windows, ~2sec, first window
closes, ~2sec, second windows closes.
AladdinETokenDriverBug.exe - opens second windows, doesn't close both.
msiexec /quiet /i
What's incredibly strange is that it's MsiExec that is spawning the installer.
As such, I'm wondering what is inside the Wise installers CA that fires right
before the second instance spawns.
-Original Message-
From: Alexey Larsky-RUS [mailto:alexey.lar...@jeppesen.com]
Sent: Monday,
Hi,
You get it by using candle and light on the attached .wxs file (which
containes Patch element).
candle [path to the Patch wxs file] -out [Path where wixobj will be placed]
light [Path of the previously generate wixobj file] -out [Path and name of
the wixmsp file]
Example:
Compile and make
I'm assuming it's around
SI (s) (E0:AC) [16:32:22:539]: Executing op:
CustomActionSchedule(Action=Install.CEB85044_2EEF_484A_8907_2EAF870F92ED,ActionType=3073,Source=BinaryData,Target=f12,CustomActionData=C:\Program
Files\Aladdin\eToken\PKIClient\Install\)
MSI (s) (E0:FC) [16:32:22:554]:
When a bootstrapper v1.0.1 downloads and installs an update (v1.0.2) it
logs Automatically closing the window since update successful and
opens the v1.0.2 bootstrapper with this in the log at the top:
This bundle is being run by a related bundle as type 'Update'.
From what I can tell in the
The engine is going to have burn.related.upgrade passed as a command line
option, but as that is an internal burn parameter it won't get passed to your
BA. The engine does set pCommand-relationType = BOOTSTRAPPER_RELATION_UPGRADE;
Take a look at Command.Relation.
-Original Message-
Hi again,
I have prepared some logs of the exact same behaviour coming up in my installer
on XP:
http://www.tobias-erichsen.de/wp-content/uploads/2013/10/burn_xp_double_startup_logs.zip
I'm pretty sure it has to do with my custom-action (which is implemented in a
dll, but I have also
tried
Thank you for the missing link, I am now able to detect this as I
wanted.
I have a new problem though. When the upgraded/new version of
bootstrapper is invoked through the Update command, I am running into an
issue where the app is trying to see what version it is by using
I apparently made too many changes at once and now when I try to
install an updated version of the bootstrapper I get 'Invalid package
type':
=
[0FB4:0C24][2013-10-14T18:05:31]i199: Detect complete, result: 0x0
[0FB4:0C24][2013-10-14T18:05:31]i200: Plan begin, 7 packages, action:
I'm working on transitioning from Inno Setup to WiX due to corporate
standards.
I have some Inno that are fairly complex, running programs, setting INI
values, registry settings, etc.
If I set the Inno to not make itself uninstallable, I could just move the
files out of it to an MSI, include the
IMO it's crazy. You have to ask yourself WHY Windows Installer is the
corporate standard in the first place. MSI is transactional, declarative,
rich in meta data and transformable with standardized behaviors. You lose
all of that when you choose to use it merely as a glorified ZIP and do
It will also get you (rightfully) ridiculed in blogs:
http://blogs.msdn.com/b/robmen/archive/2006/02/01/521809.aspx
--
Nicolás
2013/10/14 Christopher Painter chr...@iswix.com:
IMO it's crazy. You have to ask yourself WHY Windows Installer is the
corporate standard in the first place. MSI
Rob http://robmensching.com/blog/ reviewed and merged the pull request
https://wix.codeplex.com/SourceControl/network/forks/bobarnso/wixdev/contribution/5484
that integrated Votive 2010 with Visual Studio 2013. The results are
available in build v3.8.1014.0
I totally understand what you're saying. But...
As far as I can tell, I'm going to have to do custom actions to do a bunch
of the stuff that Inno does easily. Like updating an INI file or running a
program.
If I move everything out of Inno to WiX that an MSI can do natively - which
appears to
If all you're going to do is exec a bunch of batch files and vbscripts then
the InnoSetup executable is probably a *far* better idea. Those scripting
platforms are not the way to go to create a robust installation.
However, if you were to integrate fully with the Windows Installer (which
is
Rob-
Thanks for the lengthy reply. I feel like I need to read it about a dozen
times more to have a chance of getting everything in there. Not tonight,
though.
On Tue, Oct 15, 2013 at 12:25 AM, Rob Mensching r...@robmensching.comwrote:
If all you're going to do is exec a bunch of batch files
23 matches
Mail list logo