Hi again everyone,
I have tried to do a WinDbg session tonight to single-step through the
burn-engine
to find out where the problem is.
But I must confess that I lost track somewhere in the creation of sub-processes
and
communication via pipes :-(
One peculiar thing came up though. I had "shortened" my burn bootstrapper to
only
install the driver (not the application). When I did this, the behaviour was a
little bit
different than before:
When I install the old (large) one with the application msi after the driver,
I do get
the Burn startup screen again. If I only include the driver-MSI, I get the
"Modify Setup"
screen instead (in addition to the normal "Setup Successful") screen.
When I look in WinDbg what kind of processes exist at this moment, I get three:
1.) The inital process which started the installation-process (running as local
admin)
2.) An additional process (also running as local admin)
Command Line being:
"C:\Dokumente und Einstellungen\Administrator\Lokale
Einstellungen\Temp\{b6db9c3d-5a09-47b3-9f87-a01ad7d81fda}\.be\rtpMIDISetup.exe"
-q -burn.elevated BurnPipe.{<GUID>} {<start of guid> (the paths before temp
were "shortened 8.3 compatible names, but I could not copy the line from
windbg, the rest of the line was truncated by windbg)
3.) A third one (running as NT-AUTHORITY\SYSTEM)
Command Line being:
"C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\Package
Cache\{b6db9c3d-5a09-47b3-9f87-a01ad7d81fda}\rtpMIDISetup.exe" /burn.log.append
C:\Dokument.... (here the path did
NOT contain shorted 8.3 path-elements, again the rest of the line was
truncated by windbg)
If I close the "Modify Setup" windows that is created erroneously, the last
process (which is running under SYSTEM-Authority)
vanishes, so only the first two remain...
I don't know if this might be helpful information for someone who is more
intimate with the
code involved but I sure do hope so....
Best regards,
Tobias
________________________________________
Von: uholeschak [ulr...@holeschak.de]
Gesendet: Dienstag, 5. November 2013 15:10
Bis: wix-users@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 burn
window is opening.
It seems the only way to prevent this is a modification in burn ...
Ulrich
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-installation-with-Aladdin-eToken-driver-msi-opens-second-burn-s-window-tp7589681p7590289.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
