In my experience, that message shows up if your exe returns an error and doesn't have an application manifest. Add a manifest to the bootstrapper exe (specifically one that includes the aseemblyidentity and requestedexecutionlevel tags) and you shouldn't see that second message anymore.
-Ari -----Original Message----- From: Rob Mensching [mailto:r...@wixtoolset.org] Sent: Thursday, June 25, 2009 11:08 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Enforcing x86-only and x64-only installs I think that is a Windows Installer message coming up first and then the app compat goo kicking in saying, "Ooo, ooo, your install failed would you like to try again with magic pixie dust and maybe it'll work this time?" even though it won't. <smile/> That's my best guess. Quinton Tormanen wrote: > Our application includes a USB driver in its install through DIFxApp. I > now have two installers, one for x86 and one for x64. I understand this > to be a requirement when using difxap. Since the install will fail if > running the x86 on x64 or vice versa, I thought it would be appropriate > to use the <Condition> element to enforce this up front. Therefore, I > include the following in my WXS file: > > > > <?if $(var.Platform) = x64 ?> > > <Condition Message="This install package only supports 64-bit > operating systems."><![CDATA[VersionNT64]]></Condition> > > <?else ?> > > <Condition Message="This install package only supports 32-bit > operating systems."><![CDATA[NOT VersionNT64]]></Condition> > > <?endif ?> > > > > Notice that the x64 Condition seems unnecessary since the <Package > Platform="x64"> will cause MSIEXEC to reject it before checking my > conditions. > > > > Here is my problem: when I run my 32-bit installer (using the bootstrap) > on 64-bit Windows 7, and I get the expected error saying "This install > package only supports 32-bit operating systems," and click OK, I get the > Program Compatibility Warning saying that the installation may not have > completed properly and offers to set some options to make it work. Does > anyone know what I am doing wrong such that Windows 7 doesn't trust me > when I failed the install intentionally (because it wouldn't have worked > using the x86 difxapp DLLs embedded in that version of the installer? > > > > Notice that I distribute my MSI file embedded in a bootstrap built with > IEXPRESS.EXE, which runs "MSIEXEC /i rmctools.msi /lv RMC_Install.log". > This bootstrap utility also has a manifest embedded using MT.exe that > sets the requested privilege level to "asInvoker". My understanding was > that this turned off Windows' program compatibility engine. > > > > I also welcome any other comments on the way I'm going about this. > > > > Thank you. > > > > Quinton Tormanen > > Software Engineer > > Delta Computer Systems, Inc. > > http://www.deltamotion.com <http://www.deltamotion.com/> > > > > ------------------------------------------------------------------------------ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
