PDA

View Full Version : COMCTL32.OCX Failed to self-register



NewsArchive
11-18-1997, 01:00 AM
I'm using Installshield Express 2 with the service pack to build an install
for a VB4-32bit program for a target 32-bit platform. I have update the
COMCTL32.OCX Update to Version 5.00.3828. But this update need some files to
be updated before (OLEAUT32.DLL, COMCAT.DLL, OLEPRO32.DLL, ASYCFILT.DLL,
STDOLE2.TLB) in the Microsoft Knowledge base the refer it as Q164529 Updated
Automation System Files. Some of these files as to be registered and the
have dependency's. I tried to modify the SWDEPEND.INI but I have some
problem when I install my software

When I run the installation on a clean machine (Win95 just installed), at
the point where it says 'Registering installed components' I get 'Failed to
self-register COMCTL32.OCX'.

The installation then finishes and it asking me to restart. If I don't
restart the program fail to run but if I restart and I start the program it
took a long time and then it work (I am suspecting that the program is
registering some file..).

What could be the SWDEPEND.INI should contain to register correctly the
files?

NewsArchive
11-20-1997, 01:00 AM
You shouldn't be modifying an Express swdepend.ini. This is not supported
by InstallShield. Try to register the file manually on the machine to find
out if it will register that way. It most likely is a dependency issue.
To find the dependencies it is best to run the VC++ tool Dumpbin.exe. Run
this with the /IMPORTS switch to find out the dependencies. Include all
the dependencies, with the exception of the DLL's that are part of the
operating system, in the installation and run it.

Kent
InstallShield Technical Support

Gilles Labelle <Gilles.Labelle@intek.qc.ca> wrote in article
<347204c0.0@news.installshield.com>...
> I'm using Installshield Express 2 with the service pack to build an
install
> for a VB4-32bit program for a target 32-bit platform. I have update the
> COMCTL32.OCX Update to Version 5.00.3828. But this update need some files
to
> be updated before (OLEAUT32.DLL, COMCAT.DLL, OLEPRO32.DLL, ASYCFILT.DLL,
> STDOLE2.TLB) in the Microsoft Knowledge base the refer it as Q164529
Updated
> Automation System Files. Some of these files as to be registered and the
> have dependency's. I tried to modify the SWDEPEND.INI but I have some
> problem when I install my software
>
> When I run the installation on a clean machine (Win95 just installed), at
> the point where it says 'Registering installed components' I get 'Failed
to
> self-register COMCTL32.OCX'.
>
> The installation then finishes and it asking me to restart. If I don't
> restart the program fail to run but if I restart and I start the program
it
> took a long time and then it work (I am suspecting that the program is
> registering some file..).
>
> What could be the SWDEPEND.INI should contain to register correctly the
> files?
>
>
>
>
>
>

NewsArchive
04-25-2000, 12:00 AM
Dear Franco,
Thanks for the 'news'. Sorry, but I have the Express Limited Edition that
came with Delphi 5.
I guess I have to buy from you to actually get a product that will let me
use the features that came with Delphi 5.

This is what I cut out of your website:

Limited Edition Owners

Upon registration of your product a serial number is assigned to you. To
register your product now, use our online product registration form. If you
no longer have your serial number, email register@installshield.com to
request it.
Note: Full product maintenance releases are not available to Limited edition
owners but owners of these products are entitled to technical support.

pl


Franco-InstallShield <supportnews@installshield.com> wrote in message
news:38da6aee.0@news.installshield.com...
> Hello Paul
>
> Our Express 2.13 Beta which is available to our Express 2.12 users handles
> Delphi 5
> and Express Extensions. One would use the Express Extensions to run an
> external exe
> such as yours.
>
> --
> Regards
> Franco Pagnamenta
> InstallShield Software Corp.
>
> InstallShield® Professional 2000 is now available from InstallShield
> Software Corporation! Take advantage of new event-based scripting
> and enhanced third-party technology support. Target the Windows Installer
> service of Windows 2000. Find out more! Visit www.installshield.com
> and upgrade to InstallShield Professional 2000 today!
> Paul Lagasse' <plagasse@rttinc.com> wrote in message
> news:38cd9426.0@news.installshield.com...
> > Hi all.
> > A couple months ago I ran into some problems trying to distribute
> > comctl32.dll on NT.
> > The problem was that when I installed the comctl32.dll in the Windows
> > system directory, if comctl32.dll was not required, Windows NT would
> > erroneously flag it's current comctl32.dll for deletion and then would
not
> > add in any version of comctl32.dll. This rendered NT unusable and I had
> to
> > reformat the hard drive.
> >
> > I followed this up with Microsoft and sure enough, they had a program
> > (401upd.exe or something like that) that you were supposed to run upon
> > installing you application and it was supposed to update comctl32.dll
> > correctly. Well, you can't run a separate call using IS Express that
comes
> > with Delphi 5 and I didn't want to pay hundreds of dollars to upgrade to
> an
> > IS product that can so I found other datepicker tools (RxTools) that
don't
> > use comctl32.dll. But, the RxTools' datepicker doesn't handle time!
> >
> > What I'd like to know is this. Could I have installed comctl32.dll in
the
> > application's install directory instead of the Windows System directory
> thus
> > by-passing Window trying to add it to the registry on next bootup?
> > Has anyone else had this problem? How did you get around it? Any help
> > would be greatly appreciated.
> > Sincerely
> > Paul Lagasse'
> >
> >
> >
> >
> >
>
>

NewsArchive
03-07-2001, 01:00 AM
Hallo Phil,

may thanks!
That's it, what we looked for.
Johannes


"Phil Wilson" <phil.wilson@unisys.com> schrieb im Newsbeitrag
news:3aa532fd@12.41.20.38...
> See Q186176 in MS KB. In general, you run 50COMUPD.EXE. on 95, 98, NT. You
> have to be careful about locale because it comes in different language
> flavors.
>
> "Johannes John" <jn@rib.de> wrote in message
news:3aa4b251$1@12.41.20.38...
> > Hallo together!
> >
> > Does anybody know, how to handle / install the comctl32.dll?
> >
> > Any answere greatly appreciated!
> > Johannes
> >
> >
>
>

NewsArchive
08-08-2001, 12:00 AM
Windows 95. For the other OSes the comctrl32.dll is new enough to support
the features I use.

I was hoping just adding the merge module would be enough.

Thanks,
Juan Foegen


"Phil Wilson" <phil.wilson@unisys.nospam.com> wrote in message
news:3b706407$1@news.installshield.com...
> What's your operating system? Does it happen to be Windows 2000 or Me?
>
> "Juan Foegen" <jfoegen@agleader.com> wrote in message
> news:3b705bc1@news.installshield.com...
> > I need my users to be using a newer version of the comctl32.dll. I
> thought
> > all I would have to do is include the comctl32.msm, but this did not
seem
> to
> > update the dll. Do I have to use 50comupd.exe or should the merge
module
> > work?
> >
> > Thanks,
> > Juan Foegen
> >
> >
>
>

NewsArchive
08-08-2001, 12:00 AM
The merge module doen't contain the Dll, it contains the OCX, so you need
50comupd.exe.

"Juan Foegen" <jfoegen@agleader.com> wrote in message
news:3b713115$1@news.installshield.com...
> Windows 95. For the other OSes the comctrl32.dll is new enough to support
> the features I use.
>
> I was hoping just adding the merge module would be enough.
>
> Thanks,
> Juan Foegen
>
>
> "Phil Wilson" <phil.wilson@unisys.nospam.com> wrote in message
> news:3b706407$1@news.installshield.com...
> > What's your operating system? Does it happen to be Windows 2000 or Me?
> >
> > "Juan Foegen" <jfoegen@agleader.com> wrote in message
> > news:3b705bc1@news.installshield.com...
> > > I need my users to be using a newer version of the comctl32.dll. I
> > thought
> > > all I would have to do is include the comctl32.msm, but this did not
> seem
> > to
> > > update the dll. Do I have to use 50comupd.exe or should the merge
> module
> > > work?
> > >
> > > Thanks,
> > > Juan Foegen
> > >
> > >
> >
> >
>
>