I ran the ICE validation from ORCA, Examined the output to see if anything related to the custom action and nothing did.
However - the bug is now gone. As of two builds ago I am no longer seeing the installer in an XP environment execute this CA - what changed. Pretty much nothing that should have made a difference. I was working on another CA that managed starting up the client after an install. I got the idea to use the same application to start up the client on a reboot so I moved the CA application from the binary table to the files table. After that this scheduling CA that shouldn't run on XP stopped executing on XP boxes. I still need to do testing back in the W 7 world - but I can no longer reproduce this problem with my current build. (lower case yay) Sorry to trouble y'all - thanks for the input - I now know how to run the ICE validator from Orca - thanks for that. On Mon, Aug 1, 2011 at 3:00 PM, Paul Brook <brook.p...@gmail.com> wrote: > I checked the InstallExecuteSequence table and located the > ScheduleStartRecorder action with this condition, which is correct: > VersionNT<600 AND (NOT REMOVE~="ALL" OR UPGRADINGPRODUCTCODE) > > Here's the property: > Property(S): ScheduleStartRecorder = "C:\WINDOWS\system32\SCHTASKS.EXE" > /CREATE /F /TN "start VIPER" /XML "C:\Program > Files\VayTek\Recorder\StartRecorderSchedule.xml" > Property(N): ScheduleStartRecorder = "C:\WINDOWS\system32\SCHTASKS.EXE" > /CREATE /F /TN "start VIPER" /XML "C:\Program > Files\VayTek\Recorder\StartRecorderSchedule.xml" > > I'm not familiar with standalone ICE validating programs - I will do some > research and get one. I am using Visual Studio 2010 and I am ignoring some > ICE messages that VS2010 / WIX kicks out. > ICE82;ICE03;ICE83;ICE09;ICE25 > > > > > On Fri, Jul 29, 2011 at 6:43 PM, jjbean <jonks2...@yahoo.co.uk> wrote: > >> >> To check for versions of 64-bit Windows use the VersionNT64 property. >> >> This isn't strictly necessary. On 64 platforms, VersionNT64 _and_ >> VersionNT >> properties are created. >> It's ok to just check the VersionNT value. >> You only really need to use the VersionNT64 property to determine if the >> OS >> is 64bit or not. >> >> To the OP: >> >> Do 3 things: >> >> 1) Open the msi in Orca and confirm the condition is what you expect. >> 2) Get the properties values from the log (log with /L*v) and post them. >> 3) Run an ICE validator over the msi. >> >> >> >> -- >> View this message in context: >> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problem-with-CA-executing-when-it-shouldn-t-tp6631071p6635319.html >> Sent from the wix-users mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> Got Input? Slashdot Needs You. >> Take our quick survey online. Come on, we don't ask for help often. >> Plus, you'll get a chance to win $100 to spend on ThinkGeek. >> http://p.sf.net/sfu/slashdot-survey >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > > ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
