Richard
I really appreciate your help on this but due to time constraints I have
thrown in the towel and written a custom action that works. It simply gets
the INSTALLDIR property, concatenates the exe name and creates a new
process...works every time.
Again, thanks so much...
John
On 8/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
>
> John,
>
>
>
> The 210 is a little misleading, I admit.
>
>
>
> Expressed in hexadecimal, 210 = 0xD2
>
>
>
> From http://msdn2.microsoft.com/en-us/library/aa368071.aspx we can see
> that this decodes as follows:
>
>
>
> 0x80 = Run operation asynchronously
>
> 0x40 = Ignore exit code
>
>
>
> That leaves us with 0X12 – i.e. 18 decimal which is what we would expect.
>
>
>
> I am seeing the same issue as you – the application launches correctly for
> the default folder, but does not launch for a different folder.
>
>
>
> For some bizarre reason I am unable to run ProcessMonitor against the
> installation, or at least I am unable to do so within Microsoft Virtual PC
> which is where I strongly prefer to test my installations (the virtual PC
> reboots without permission or any obvious reason). I'll let you know what I
> find as I learn more.
>
>
>
> Regards,
>
> Richard
>
>
> ------------------------------
>
> *From:* John Lalande [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, August 09, 2007 2:13 PM
> *To:* Foster, Richard - PAL
> *Cc:* wix-users@lists.sourceforge.net
> *Subject:* Re: [WiX-users] Run program after installation
>
>
>
> Richard
>
> As per the tutorial, my custom action is defined as:
>
> <CustomAction Id='LaunchFile' FileKey='DA_exe' ExeCommand=''
> Return="asyncNoWait" />
>
> This yields a custom action of type 210.
>
> I am very curious how your experiment turns out.
>
> John
>
>
>
> ------------------------------
>
> * C O N F I D E N T I A L I T Y N O T I C E *
> -----------------------------------------------------------
> The content of this e-mail is intended solely for the use of the
> individual or entity to whom it is addressed. If you have received this
> communication in error, be aware that forwarding it, copying it, or in any
> way disclosing its content to any other person, is strictly prohibited.
> Quixote Traffic Corporation is neither liable for the contents, nor for the
> proper, complete and timely transmission of (the information contained in)
> this communication. If you have received this communication in error, please
> notify the author by replying to this e-mail immediately and delete the
> material from any computer.
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
