Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

2013-10-13 Thread Alexey Larsky-RUS
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, Jaco

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

2013-10-13 Thread Hoover, Jacob
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 spawned

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

2013-10-13 Thread Alexey Larsky-RUS
... [0574:0564][2013-10-09T13:56:53]i301: Applying execute package: PKIClient_x32_5.1.msi, action: Install, path: C:\Documents and Settings\All Users\Application Data\Package Cache\{3909BE71-2D8F-42D2-BA46-3831B60CFD0F}v5.1.87.0\PKIClient-x32-5.1.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFAST

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

2013-10-13 Thread Tobias Erichsen
Hi everyone, I do have the same problem with my burn-package which first installs an MSI with a driver (using custom-action DLL) and then the application MSI. This only happens on Windows XP, not on Windows 7 or 8. If I replace the driver-install CA in the first MSI by a special diagnosis "Sl

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

2013-10-13 Thread Neil Sleightholm
Check the burn logs and see what command line is used and try that (still not seeing any screen shots in the link). -Original Message- From: Alexey Larsky-RUS [mailto:alexey.lar...@jeppesen.com] Sent: 13 October 2013 19:01 To: General discussion for Windows Installer XML toolset. Subject

Re: [WiX-users] Sequencing Patches with MBA

2013-10-13 Thread tom
Blair Murri-3 Thanks When you say "...productcode and check the installed state of all of the patches on that product" you mean that is should use MSI api for this? Thanks in advance -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Sequencing-

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

2013-10-13 Thread Alexey Larsky-RUS
With dotNet Installer and our own boostrapper driver Aladdin's driver has been installed without problem. As far I remember, I ran it with same parameters, but only with burn second burns instance has been opened. PS. Attachments are here: http://rghost.ru/49356531 -Original Message- Fr

Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.

2013-10-13 Thread Neil Sleightholm
What happens if you run the Aladdin installs in unattended mode without burn - I suspect it will do the same, if so you will need to take this up with Aladdin and find out what the unattended mode command line options are. (By the way attachments don't come through to the list.) Neil -Orig