Yeah, if on less than Vista (which is XP and Server 2003?), then try using the 
run key instead of runonce key.  I'm curious if that works well.

Note: I don't agree about the elegance of the mutex and all that. It's way 
complicated and challenging to test. Simplicity has significant advantages for 
the long term success of an engine doing stuff as complex as Burn.

Also, XP is going to have to go away. Not desirable to do highly complex stuff 
for something that is *definitely* not the future.

From: Tobias Erichsen [mailto:i...@tobias-erichsen.de]
Sent: Friday, November 8, 2013 7:55 AM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] Issue & possible solution: Burn Startup-Screen is shown 
twice (on Windows XP) if bootstrapper contains driver-installation

...now again with shortened body to not break the size-limit of the 
mailing-list:

Even if the other solution with the named object sounds like the most elegant 
version, I'd
would probably go with the simplest (k.i.s.s), as the room for breakage is the 
least

(and not being totally unselfish, I see hope that this might still slip into 
the 3.8 release,
whereas the other one would probably need more coding & testing ;-)

Concerning the run-key-approach: so that would mean in case the local system 
has on
OS lower than Vista, the Run-key is used instead of the RunOnce - correct?

________________________________
Von: Rob Mensching [mailto:r...@robmensching.com]
Gesendet: Freitag, 8. November 2013 16:13
An: WiX toolset developer mailing list
Betreff: Re: [WiX-devs] Issue & possible solution: Burn Startup-Screen is shown 
twice (on Windows XP) if bootstrapper contains driver-installation
What if on XP Burn writes to the Run key instead? That's actually what we did 
in for all OSes in the early days of Burn. We had to move to the RunOnce key to 
ensure on restart the Bundle launched elevated and the user would not be 
prompted for elevation post-restart. Fortunately, on XP we don't have to worry 
about elevation.

This could also be the most straight forward fix if it works.  I'm hoping the 
"runonce.exe" just runs the runonce key. <smile/>


------------------------------------------------------------------------------
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-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs

Reply via email to