: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
http://blogs.msdn.com/b/junfeng/archive/2006/09/19/761765.aspx says this:
Be careful about RunOnce registry key: It may run before system restart.
According to KB 281829, RunOnce registry key will run
Thanks for all the useful information.
I have now removed the line:
hr = RegWriteString(hkRun, pRegistration-sczId, sczRunOnceCommandLine);
in registration.cpp, I don't think that I really need this RunOnce feature
at the moment.
Now everything is working fine ...
Ulrich
--
View this
discussion about the WiX toolset.
Betreff: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
That third process has the type of commandline that is placed in the RunOnce
key in case anything goes awry (reboot, BSOD, whatever) to facilitate attempts
http://blogs.msdn.com/b/junfeng/archive/2006/09/19/761765.aspx says this:
Be careful about RunOnce registry key: It may run before system restart.
According to KB 281829, RunOnce registry key will run in the following cases:
1. At the end of installation through InstallFromHinfSection even in
@lists.sourceforge.net
Betreff: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
http://blogs.msdn.com/b/junfeng/archive/2006/09/19/761765.aspx says this:
Be careful about RunOnce registry key: It may run before system restart.
According to KB 281829, RunOnce
Hello,
I have tested now with the DIFxApp.dll and DIFxAppA.dll (that also the
DifxAppExtension is using),
same result!
When the USB device is connect and the driver is installed a second burn
window is opening.
It seems the only way to prevent this is a modification in burn ...
Ulrich
--
View
@lists.sourceforge.net
Betreff: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
Hello,
I have tested now with the DIFxApp.dll and DIFxAppA.dll (that also the
DifxAppExtension is using),
same result!
When the USB device is connect and the driver is installed a second
Hello,
I have the same problem with my driver installation.
When calling DriverPackageInstall() in the custom action of the msi a second
burn window opens.
I am installing an FTDI USB (pnp) driver and the second burn window *only*
opens when the device is connected and the driver is really
: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
Hi everyone,
I was wondering if I should open a ticket for this issue if noone has done that
so far...
Best regards,
Tobias
Von: Tobias Erichsen [i...@tobias
-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
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
toolset.
Subject: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
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
Installer XML toolset.
Betreff: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
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
that spawned.
-Original Message-
From: Alexey Larsky-RUS [mailto:alexey.lar...@jeppesen.com]
Sent: Monday, October 14, 2013 12:37 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window
, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Monday, October 14, 2013 10:10 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
Would be interesting to see if the parent PID is really
toolset.
Subject: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
...
[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
]
Sent: 14 October 2013 06:37
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
...
[0574:0564][2013-10-09T13:56:53]i301: Applying execute package:
PKIClient_x32_5.1.msi, action: Install
[mailto:n...@x2systems.com]
Sent: Monday, October 14, 2013 11:23 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
If you run this:
msiexec /quiet /i PKIClient-x32-5.1.msi
[mailto:n...@x2systems.com]
Sent: Monday, October 14, 2013 11:23 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
If you run this:
msiexec /quiet /i PKIClient-x32-5.1.msi
, October 14, 2013 8:07 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
AladdinETokenDriverBug.exe /quiet - doesn't show any window.
AladdinETokenDriverBug.exe /passive - opens
, October 14, 2013 8:20 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
What's incredibly strange is that it's MsiExec that is spawning the installer.
As such, I'm wondering what
...@greenheck.com]
Sent: Monday, October 14, 2013 8:20 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
What's incredibly strange is that it's MsiExec that is spawning the installer.
As such, I'm
Dear Colleagues,
During setup burn based installer with Aladdin's eToken Pro drivers 3.66(RTE
3.66.msi) or 5.1 (PKIClient-x32-5.1.msi) opens second installer window.
OS: Windows XP SP3 х32
Burn: release 3.7, 3.8.1007.0
MSI:
-Original Message-
From: Alexey Larsky-RUS [mailto:alexey.lar...@jeppesen.com]
Sent: 13 October 2013 07:27
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens
second burn's window.
Dear Colleagues,
During setup burn based installer
-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Sunday, October 13, 2013 11:38 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
What happens if you run the Aladdin installs
.
Subject: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
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
Von: Alexey Larsky-RUS [alexey.lar...@jeppesen.com]
Gesendet: Sonntag, 13. Oktober 2013 08:26
Bis: wix-users@lists.sourceforge.net
Betreff: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens
second burn's window.
Dear Colleagues,
During setup burn based
2:20 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
Check the burn logs and see what command line is used and try that (still not
seeing any screen shots in the link
27 matches
Mail list logo
