Bill, The warnings you cited pertain to COMCTL32.DLL, not COMCTL32.OCX. COMCTL32.OCX contains version 5 of several ActiveX controls like the progress bar and the treeview - if you're curious, you can explore its contents using the VFP Object Browser. Also, if you look inside the COMCTL32.MSM merge module, you'll find it installs only COMCTL32.OCX, no DLLs.
AFAIK, COMCTL32.DLL is a system component unrelated to the OCX. I don't know why you'd ever have to distribute COMCTL32.DLL with a VFP app. -Rick > -----Original Message----- > From: ProfoxTech [mailto:[email protected]] > On Behalf Of Bill Arnold > Sent: Friday, October 05, 2012 8:12 PM > To: [email protected] > Subject: RE: INNO and Windows 7 64 bit problem > > <snip> > The plot has thickened on COMCTL32, unfortunately. See below for the > warning > > Doing some reading, I see this note, which is old, but seemingly relevant. > http://community.flexerasoftware.com/showthread.php?t=43136 which addresses > a question asked about whether it's okay to distribute some DLL's, including > COMCTL32.DLL: > > "Comctl32.dll: Definitely YES. But you must use the Microsoft supplied > 40comupd.exe, 401comupd.exe or 50comupd.exe file (I recommend > 401comupd.exe). You can find these on the Microsoft site" > > So I search for "401comupd.exe" from MS, but can't find it. I do find an MS > library article on Redistributing Common Controls at > http://msdn.microsoft.com/en-us/library/zxw5yfk1%28v=vs.71%29. > aspx but the link it provides specifically for "Redistribution of Comctl32.dll" > is broken. > > Still searching, now decided to search for "inno comctl32", I get to > http://www.jrsoftware.org/isfaq.php#comctl32 Which includes this nugget: > "Don't try to install COMCTL32.DLL directly using the [Files] section; > Microsoft does not allow this, and it's dangerous." > > Wow: "It's dangerous". Can't be good > > This INNO page does point to an MS supplied " 50comupd.exe" file, but the > link to it is broken and a search for this name gets 1 different MS hit, > also with a broken link. Other search results are useless. I'm not about to > download this DLL from some unknown website. > > I think I'll just leave my INNO setup alone for now and deal with this when > it happens again. > > ----------------------- > > > 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. > > --------------------------------------- > That's interesting and very good to know. I'll kept the links > > > 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.
