Rick, Re-reading my post, now I wonder if I missed an obvious answer: to simply set ArchitectureInstallIn64BitMode to x64 and let INNO detect 32 or 64 and behave accordingly
Is this what you or others are doing? Bill Hi Rick, In case you haven't already seen it, check out the Inno Setup Help file re the "ArchitectureInstallIn64BitMode" setting in the [Setup] section. It links to the "Install Mode: 32-bit vs. 64-bit" Help page, which also has good info. ------------------- I had seen this reference, but stopped at: "Normally, you should not change this directive from its default value unless your application contains native 64-bit binaries" Which is not the case But then I see in the "Install Mode: 32-bit vs 64-bit" topic, it says: "64-bit mode is selected if the user is running a 64-bit version of Windows and the system's processor architecture is included in the value of the ArchitecturesInstallIn64BitMode [Setup] section directive. Otherwise, 32-bit mode is used." Starts off good by saying "64-bit mode is selected if the user is running a 64-bit version of Window", but then it muddies the waters with "and the system's processor architecture is included in the value of the ArchitecturesInstallIn64BitMode [Setup] section directive. Otherwise, 32-bit mode is used." Then, looking back at the choices for "ArchitectureInstallIn64BitMode", it lists x64 and ia64. http://www.tomshardware.com/forum/68071-28-what-ia64 suggests that we're not likely to be dealing with ia64 soon My sense is that this is leading to 2 SETUP.EXE's being required, 1 for 32 bit, and 1 for 64 bit, with the one for x64 taking into account the limitations discussed in "64-bit Installation Limitations" I really don't want 2 SETUP.EXEs - and I imagine I'm not alone. On the limitations, this one ... I read a few times and not sure I understand it: "The System32 path returned by the {sys} constant does not always map to the 64-bit System directory. When Setup/Uninstall is running in 64-bit mode, it maps to the 64-bit System directory when used in the [Dirs], [Files], [InstallDelete], [Run], [UninstallDelete], and [UninstallRun] sections because Setup temporarily disables WOW64 file system redirection [external link] when files/directories are accessed by those sections. Elsewhere, System32 and {sys} map to the 32-bit System directory, as is normal in a 32-bit process." I think it's saying that it disables WOW64 redirection (which I assume would be performed by Windows) because in these sections it's already targeting the 64 bit folder (sysWOW64), so redirection isn't needed or harmful. Bill _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
