[Bill Arnold wrote:] > Question on having COMCTL32.OCX included in your INNO build: do you recall > how you got the copy? I found a MS link posted by Matt Slay to get > COMCTLZP.EXE, but it's been removed by MS. Despite my positive experience > of just copying COMCTL32.OCX/DLL from my dev machine to customer's machine > and registering it, it makes me nervous.
I'm deploying the one off my dev machine. I don't recall where it came from, probably VFP 5 or 6. I use the 'onlyifdoesntexist' flag in the Inno Setup script so the installer doesn't overwrite an existing copy on the target machine, although it's such an old control I doubt if a newer one even exists. > I'm sure it's in some MSI/MSM files, but INNO doesn't support using them > (sure would be nice, though) You can launch the Windows Installer executable (msiexec.exe) from the [Run] section of an Inno Setup script and use the /i parameter to install from an MSI file, which you'd also have to distribute. I haven't ever needed to do this so I can't speak from first-hand experience, but there's some discussion on the subject at http://fox.wikis.com/wc.dll?Wiki~InnoScripts~VFP. Merge modules (MSM files) are not stand-alone installers and need to be merged into an MSI file before you can install from them. -Rick > -----Original Message----- > From: ProfoxTech [mailto:[email protected]] > On Behalf Of Bill Arnold > Sent: Thursday, October 04, 2012 8:19 PM > To: [email protected] > Subject: RE: INNO and Windows 7 64 bit problem > > Rick, > > I'm still sorting my problem out. As I just wrote to Tracy, at least part of > this problem stems from a misunderstanding about having to deal with 2 > different OCX files for the same MS Common Controls, which apparently didn't > show up before because all target machines to date already had COMCTL32.OCX > installed. > > The remaining part is that once I do have COMCTL32.OCX in the INNO build, I > wonder if INNO will know to put it in sysWOW64 (or will Windows redirect > it?). Your experience is encouraging, but hard to tell if INNO did the right > thing or files were there all along. > > Question on having COMCTL32.OCX included in your INNO build: do you recall > how you got the copy? I found a MS link posted by Matt Slay to get > COMCTLZP.EXE, but it's been removed by MS. Despite my positive experience > of just copying COMCTL32.OCX/DLL from my dev machine to customer's machine > and registering it, it makes me nervous. I'm sure it's in some MSI/MSM > files, but INNO doesn't support using them (sure would be nice, though) > > > Thanks, > > > Bill > > [excessive quoting removed by server] _______________________________________________ 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.
