PDA

View Full Version : Self-registering COMDLG32.OCX problems...



NewsArchive
06-12-1997, 12:00 AM
I'm using Installshield Express 2 to build an install for a VB4-32bit
program for a target 32-bit platform. I've built the install already,
and when I do a test run on my development machine from Installshield
Express, it runs fine.
However, if I run the installation on a clean machine (Win95 just
installed), at the point where it says 'Registering installed
componenets' I get 'Failed to self-register COMDLG32.OCX, COMCTL32.OCX'
(used by my VB4-32 app).
The installation then finishes, then when I run the program, I get
'Unexpected Error' and the program closes. From then on, all other
programs that use COMDLG32.OCX or COMCTL32.OCX come up with the same
error on running them, and close.

This effectively cripples the computer until I re-install Windows95.
Does anyone know why this message appears, and is there a solution to my
problem, say registering the OCX's manually somehow during the
installation?

Any help much appreciated.
Andy Bibby.
Programmer, ADG Computer Systems Ltd, Oxford, UK.
Andy.Bibby@adg.co.uk

NewsArchive
06-12-1997, 12:00 AM
The "Unexpected Error" is a result of mixing different versions
of OLE files. The Microsoft Knowledge Base article
http://www.microsoft.com/kb/articles/q162/5/18.htm
has more info on it. I feel that the "Failed to Self Register..."
problem is also related.

--
Rajesh Ramachandran
InstallShield Corporation

Andy Bibby <Andy.Bibby@adg.co.uk> wrote in article
<339FF064.FC6ACB9A@adg.co.uk>...
> I'm using Installshield Express 2 to build an install for a VB4-32bit
> program for a target 32-bit platform. I've built the install already,
> and when I do a test run on my development machine from Installshield
> Express, it runs fine.
> However, if I run the installation on a clean machine (Win95 just
> installed), at the point where it says 'Registering installed
> componenets' I get 'Failed to self-register COMDLG32.OCX, COMCTL32.OCX'
> (used by my VB4-32 app).
> The installation then finishes, then when I run the program, I get
> 'Unexpected Error' and the program closes. From then on, all other
> programs that use COMDLG32.OCX or COMCTL32.OCX come up with the same
> error on running them, and close.
>
> This effectively cripples the computer until I re-install Windows95.
> Does anyone know why this message appears, and is there a solution to my
> problem, say registering the OCX's manually somehow during the
> installation?
>
> Any help much appreciated.
> Andy Bibby.
> Programmer, ADG Computer Systems Ltd, Oxford, UK.
> Andy.Bibby@adg.co.uk
>

NewsArchive
06-12-1997, 12:00 AM
You know, I've been chasing this one myself. My final resolution is to
force the users to download the OLE updates directly from MS first, and
then download my installation.

I would like to suggest InstallShield add a feature to ISX2 that
"smartens" up the install just a little. By this I mean, make the
installer recognize that if an OCX (or any file) that has a dependency
on a shared file that cannot be updated without a reboot, that it also
does not attempt to install / register that OCX BEFORE the dependent
files have been installed and setup -- even if it requires a reboot.

I know that this is not InstallShield's doing, but it sure makes a lot
of sense to support this kind of feature. This type of situation is
going to happen again.



Shawn

Rajesh Ramachandran wrote:
>
> The "Unexpected Error" is a result of mixing different versions
> of OLE files. The Microsoft Knowledge Base article
> http://www.microsoft.com/kb/articles/q162/5/18.htm
> has more info on it. I feel that the "Failed to Self Register..."
> problem is also related.
>
> --
> Rajesh Ramachandran
> InstallShield Corporation
>
> Andy Bibby <Andy.Bibby@adg.co.uk> wrote in article
> <339FF064.FC6ACB9A@adg.co.uk>...
> > I'm using Installshield Express 2 to build an install for a VB4-32bit
> > program for a target 32-bit platform. I've built the install already,
> > and when I do a test run on my development machine from Installshield
> > Express, it runs fine.
> > However, if I run the installation on a clean machine (Win95 just
> > installed), at the point where it says 'Registering installed
> > componenets' I get 'Failed to self-register COMDLG32.OCX, COMCTL32.OCX'
> > (used by my VB4-32 app).
> > The installation then finishes, then when I run the program, I get
> > 'Unexpected Error' and the program closes. From then on, all other
> > programs that use COMDLG32.OCX or COMCTL32.OCX come up with the same
> > error on running them, and close.
> >
> > This effectively cripples the computer until I re-install Windows95.
> > Does anyone know why this message appears, and is there a solution to my
> > problem, say registering the OCX's manually somehow during the
> > installation?
> >
> > Any help much appreciated.
> > Andy Bibby.
> > Programmer, ADG Computer Systems Ltd, Oxford, UK.
> > Andy.Bibby@adg.co.uk
> >