I am using 5.3.6(a) of Inno and version 5.25 of ISTool.
So compiling stops at that line?
Hmmm, looking at the [SETUP] section in ISTOOL,those 2 lines are NOT "keyword recognized" (not in blue) like the other commands. However, all scripts have those 2 lines and all compile.
The following is from....
http://www.jrsoftware.org/files/is5-whatsnew.htm5.1.0-beta (2005-03-01)
Inno Setup now has initial support for the installation of 64-bit applications on 64-bit versions of Windows:
Setup can run in one of two modes: 32-bit or 64-bit. 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
new ArchitecturesInstallIn64BitMode [Setup] section directive. Otherwise, 32-bit mode is used.
How do the two modes of installation differ? Primarily, the differences lie in where things are
installed by default. For example, 64-bit applications have their own Program Files directory, and
their own isolated view of the registry. See the Install Mode: 32-bit vs. 64-bit topic in the help file
for details. Added new [Setup] section directive ArchitecturesAllowed. When set, it specifies
which processor architecture(s) Setup is allowed to run on. Even when running in 32-bit mode,
Setup is capable of installing files and creating registry keys in 64-bit locations, and vice versa.
New options have been added that override the default locations: .................
Short forum post here...
http://www.vbforums.com/showthread.php?t=645176#post3983098>Chris:
>
>Thanks.
>
>My Inno Setup Compiler Ver 5.4.2(a) chokes on:
>
>
>ArchitecturesInstallIn64BitMode=x64 ia64
>
>
>But I'm compling on a 32Bit machine; is that the problem?
>
>dg
>
>
>>Correctly or otherwise, I have that for all builds.
>>
>>
>>>Chris:
>>>
>>>Thank you. Would this be included in all builds or just for the 64Bit version?
>>>
>>>dg
>>>
>>>
>>>>Doyle: do you have "architectures" set in the SETUP area of the INNO/ISTOOL script? Curious if that makes a difference.
>>>>
>>>>ArchitecturesAllowed=x86 x64 ia64
>>>>ArchitecturesInstallIn64BitMode=x64 ia64
>>>>
>>>>
>>>>>Doug, thanks.
>>>>>
>>>>>I'm quite puzzled because that VFP code has worked with Vista in past trials.
>>>>>The Inno script fails to copy/register the ocx with no apparent error at install, then returns "OLE error code 0x90070002: The system cannot find the file specified." when the ocx is called.
>>>>>
>>>>>I distributed the ocx in the application root directory and callled:
>>>>>
>>>>>! /N regsvr32 /s "FTP Wizard3.ocx"
>>>>>
>>>>>which worked on a 32bit Windows7 machine.
>>>>>
>>>>>Haven't yet had a successful install on the 64bit Windows7 platform.
>>>>>
>>>>>Any ideas? Thanks!
>>>>>
>>>>>>Hi Doyle.
>>>>>>
>>>>>>>I have created a Setup.Exe for my application using Inno Setup Compiler
>>>>>>>
>>>>>>>The germane script is:
>>>>>>>
>>>>>>>[Files]
>>>>>>>Source: C:\WINDOWS\system32\FTPWizard3.ocx; DestDir: {sys}; Flags: regserver
>>>>>>>>>>>>>>
>>>>>>>Programmatically in VFP I have used this code
>>>>>>>
>>>>>>> If ! File("C:\WINDOWS\SYSTEM32\FTPWizard3.ocx")
>>>>>>> LOCAL lcFile
>>>>>>> lcFile = ucRootDirectory+'\FTPWizard3.ocx'
>>>>>>> Copy FILE("&lcFile") To C:\Windows\SYSTEM32\FTPWizard3.ocx
>>>>>>>
>>>>>>> ! /N regsvr32 /s FTPWizard3.ocx
>>>>>>> MESSAGEBOX("Done...",32,"Load and Register Ocx")
>>>>>>> ELSE
>>>>>>> MESSAGEBOX("Yes...",32,"Ocx present")
>>>>>>> Endif
>>>>>>>>>>>>>>
>>>>>>>What would the proper method/syntax be to install on Windows 7?
>>>>>>
>>>>>>The Inno line should be all you need. You can remove that VFP code, since it won't work in Windows Vista or 7, and isn't need because the installer took care of it.
>>>>>>
>>>>>>Doug
