Re: [WiX-users] Burn failed to initialize COM at EngineRun().

2015-05-26 Thread Uni Gauldoth
Hi, I've found the culprit. I installed a program named Lingoes(a translator), and run the Ligoes.exe in the back. When my installer starts, it loaded the following dll before entering stub.exe's wWinMain. C:\Users\Administrator\AppData\Local\Lingoes\Translator\lingoes-us\OpenText32.dll It looks

Re: [WiX-users] Is there some existing tool I can use when I work with WiX localization?

2014-05-22 Thread Uni Gauldoth
Thank you for the information, Steve. I'm using WiX to author msi package, and there is not a bundle yet. Can ThmViewer.exe be used with WiX's msi project? I've started to write one, hope it will solve my needs. Regards, Uni On Tue, May 20, 2014 at 12:24 AM, Steve-Ogilvie wrote: > Check out th

[WiX-users] Is there some existing tool I can use when I work with WiX localization?

2014-05-19 Thread Uni Gauldoth
Hi all, I'm sending wxl files to translators for translation. When the wxl file of japanese is processed, the translator need to preview the result msi dialog to adjust the text to confirm to some line breaking rules. I wonder if there is already some tools I can achieve this task. For example, th

Re: [WiX-users] [SPAM] Re: Strange behavior about the TempFolder Directory.

2014-05-13 Thread Uni Gauldoth
7;m surprised your MSI passed validation) > > Dave > > > > > - Original Message - > > From: Uni Gauldoth > > To: General discussion about the WiX toolset. < > wix-users@lists.sourceforge.net> > > Cc: > > Sent: Wednesday, May 7, 2014 6:57 AM

Re: [WiX-users] [SPAM] Re: Strange behavior about the TempFolder Directory.

2014-05-07 Thread Uni Gauldoth
t;MyDir" still point to "C:\Users\ADMINI~1\AppData\ Local\Temp\mydir\". Uni On Sat, May 3, 2014 at 12:02 AM, Uni Gauldoth wrote: > Thanks very much. > > I did have a per-machine install. > I uninstalled my package and reinstalled it, and the problem disappeared >

Re: [WiX-users] [SPAM] Re: Strange behavior about the TempFolder Directory.

2014-05-02 Thread Uni Gauldoth
Thanks very much. I did have a per-machine install. I uninstalled my package and reinstalled it, and the problem disappeared magically. I will try to put those files under a Per Machine folder to avoid this kind of pain. On Fri, May 2, 2014 at 4:13 AM, Phill Hogland wrote: > It sounds like you

Re: [WiX-users] Immediate Custom Action could not be run in some computers.

2014-04-29 Thread Uni Gauldoth
ith limited user rights (even > if the user is admin) because the UI sequence isn't elevated by > default. So it might be a security issue on UAC systems. > --- > Phil Wilson > > > On Mon, Apr 28, 2014 at 1:50 AM, Uni Gauldoth > wrote: > > Thanks for reply

Re: [WiX-users] Immediate Custom Action could not be run in some computers.

2014-04-28 Thread Uni Gauldoth
Thanks for replying. I'm sure that there is no dependency problems. If I run the msi installer with elevated privilege on that user's computer, the install will finish successfully. It turns out Windows Installer failed to extract the custom action dll to temp directory during the InstallUISequenc

Re: [WiX-users] How to use \layout to extract all payloads?

2013-11-07 Thread Uni Gauldoth
Thanks,then may be I should try to implement that in my ba. On 11/7/13, Pally Sandher wrote: > You can't. I feature requested this back in June 2012 -> > http://wixtoolset.org/issues/3659/ > > Palbinder Sandher > Software Platform Engineer > T: +44 (0) 141 945 8500 > F: +44 (0) 141 945 8501 > htt