PDA

View Full Version : ISX Problem: tdbgs32.ocx not registered...



NewsArchive
12-18-1996, 01:00 AM
Hi,

I recently downloaded the evaluation version of IS Express. In evaluating
ISE, I came across the following problem when attempting to create an
install kit for an VB 4.0 app for WNT 3.51 PCs.

After a "seemingly successful installation", the system is rebooted (at
ISE's request). However, when clicking onto the VB4 app's Icon the
following
message is displayed:

Error: unable to register TDBGS32.OCX

and the app fails to load.

The TDBGS32.OCX is an updated version of the VB 4.0 Pro's Data Bound grid
supplied by Apex Corp. Interestingly, if I were to use VB's setupwiz, VB's
install works fine and this problem does not occur. I've tried this
procedure of various NT3.51 PC's and the results are exactly the same.

After reading the ISE's help file and search through your knowledgebase,
I've tried updating ISE's swdepend.ini with the following lines, but still
without any success.

[TDBGS32.OCX]
Register=$(DLLSelfRegister)
src=<WINSYSDIR>
Uses1=OCX Runtime Support
Uses2=GRDKRN32.DLL

The above is essentially a copy of what's in VB4.0's swdepend.ini, except
for the syntax differences in line: src=<...>.

Your prompt assistance will be much appreciated.

Thanks,
Thomas Siu
Senior Analyst Programmer
MMI Group
Australia

Email: thomas_siu@notes.mmi.com.au
or
tsiu.mmi@s054.aone.net.au

NewsArchive
01-11-1997, 01:00 AM
Thomas Siu wrote:
>
> Hi,
>
> I recently downloaded the evaluation version of IS Express. In evaluating
> ISE, I came across the following problem when attempting to create an
> install kit for an VB 4.0 app for WNT 3.51 PCs.
>
> After a "seemingly successful installation", the system is rebooted (at
> ISE's request). However, when clicking onto the VB4 app's Icon the
> following
> message is displayed:
>
> Error: unable to register TDBGS32.OCX
>
> and the app fails to load.
>
> The TDBGS32.OCX is an updated version of the VB 4.0 Pro's Data Bound grid
> supplied by Apex Corp. Interestingly, if I were to use VB's setupwiz, VB's
> install works fine and this problem does not occur. I've tried this
> procedure of various NT3.51 PC's and the results are exactly the same.
>
> After reading the ISE's help file and search through your knowledgebase,
> I've tried updating ISE's swdepend.ini with the following lines, but still
> without any success.
>
> [TDBGS32.OCX]
> Register=$(DLLSelfRegister)
> src=<WINSYSDIR>
> Uses1=OCX Runtime Support
> Uses2=GRDKRN32.DLL
>
> The above is essentially a copy of what's in VB4.0's swdepend.ini, except
> for the syntax differences in line: src=<...>.
>
> Your prompt assistance will be much appreciated.
>
> Thanks,
> Thomas Siu
> Senior Analyst Programmer
> MMI Group
> Australia
>
> Email: thomas_siu@notes.mmi.com.au
> or
> tsiu.mmi@s054.aone.net.au

My only idea is that this ISX product is very shaky. I cannot get the CRYSTL16.OCX to
register. I can only share what I've done using ISX Pro 1.0 (I presume you are using the
Eval copy of ISX Pro 1.1):

a. The "Begin Automatic Review" button can cause problems. Clicking it the first time is
sort of useful to build an initial list in the system files group. The problem is that
the list is not complete and worse it can undo other things you may have checked. For
example, in chasing down a problem, clicking auto review again removed my check of the
ODBC item and I inadvertently delivered a setup disk without the ODBC drivers I
originally had.
b. The auto review included CRYSTL16.OCX and about 12 related DLLs but this list is
wrong for at least two reasons:
1. We need about 25 DLLs in all to support the Crystal RPT files we deliver so I
created a separate "GROUP" I called "Crystal Extras" and manually added the DLLs
Installshield omitted from the original list in the "SYSTEM GROUP".
2. Installshield violates one of their own rules by listing the CRYSTL16.OCX
before CRPE.DLL and the other Crystal DLLs. The order is apparently important. I've
learned to use QuickView to see the DLLs required by an OCX and make sure these DLLs are
listed in a group before the OCX.
c. Because CRYSTL16.OCX requires CRPE.DLL, I moved the CRYSTL16.OCX to the bottom of the
SYSTEM group under the theory that this would satisfy the "ordering rule". I've had
mixed results with this approach. In one case, this seemed to work but now I've
discovered a case on a "virgin" Win95 machine it does not register the CRYSTL16.OCX.

No error message, no log file exists; so I discover later at runtime when I click on a
command button in my app I get a message: "Can't load (or register) custom control
CRYSTL16.OCX".

I am at the point now where I am debating whether to try to upgrade to Express Pro 1.1
or shop for a install product that works well and is supported better. I've hea

NewsArchive
05-22-1997, 12:00 AM
Greetings,

I had similar problems with CRYSTL16.OCX and Win3.1 machines. Here's
what the SWDEPEND.INI file entry needs to look like:

[CRYSTL16.OCX]
Register=$(DLLSelfRegister)

[CRYSTL16 OCX]
Src=<WINSYS16DIR>
Uses1=CRYSTL16.OCX
Uses2=CRPE.DLL
Uses3=CRXLATE.DLL
Uses4=uxddisk.dll
Uses5=uxfdif.dll
Uses6=uxfrec.dll
Uses7=uxfsepv.dll
Uses8=uxftext.dll
Uses9=pdbdao.dll
Uses10=pdctdao.dll
Uses11=pdirdao.dll
Uses12=pdsodbc.dll
Uses13=PDBBND.DLL
Uses14=MFCOLEUI.DLL

Note that the first entry has a "." between the filename and the
extension, while the second does not. This is Very Important (and was the
source of all my problems)! The first entry tells InstallShield to
register this file, while the second lists all of the files that accompany
the file.

Good luck,

Steve Locke
HBO & Company, Inc

John Adams <john.j.adams@worldnet.att.net> wrote in article
<32D7CC75.39BD@worldnet.att.net>...
> Thomas Siu wrote:
> >
> > Hi,
> >
> > I recently downloaded the evaluation version of IS Express. In
evaluating
> > ISE, I came across the following problem when attempting to create an
> > install kit for an VB 4.0 app for WNT 3.51 PCs.
> >
> > After a "seemingly successful installation", the system is rebooted (at
> > ISE's request). However, when clicking onto the VB4 app's Icon the
> > following
> > message is displayed:
> >
> > Error: unable to register TDBGS32.OCX
> >
> > and the app fails to load.
> >
> > The TDBGS32.OCX is an updated version of the VB 4.0 Pro's Data Bound
grid
> > supplied by Apex Corp. Interestingly, if I were to use VB's setupwiz,
VB's
> > install works fine and this problem does not occur. I've tried this
> > procedure of various NT3.51 PC's and the results are exactly the same.
> >
> > After reading the ISE's help file and search through your
knowledgebase,
> > I've tried updating ISE's swdepend.ini with the following lines, but
still
> > without any success.
> >
> > [TDBGS32.OCX]
> > Register=$(DLLSelfRegister)
> > src=<WINSYSDIR>
> > Uses1=OCX Runtime Support
> > Uses2=GRDKRN32.DLL
> >
> > The above is essentially a copy of what's in VB4.0's swdepend.ini,
except
> > for the syntax differences in line: src=<...>.
> >
> > Your prompt assistance will be much appreciated.
> >
> > Thanks,
> > Thomas Siu
> > Senior Analyst Programmer
> > MMI Group
> > Australia
> >
> > Email: thomas_siu@notes.mmi.com.au
> > or
> > tsiu.mmi@s054.aone.net.au
>
> My only idea is that this ISX product is very shaky. I cannot get the
CRYSTL16.OCX to
> register. I can only share what I've done using ISX Pro 1.0 (I presume
you are using the
> Eval copy of ISX Pro 1.1):
>
> a. The "Begin Automatic Review" button can cause problems. Clicking it
the first time is
> sort of useful to build an initial list in the system files group. The
problem is that
> the list is not complete and worse it can undo other things you may have
checked. For
> example, in chasing down a problem, clicking auto review again removed my
check of the
> ODBC item and I inadvertently delivered a setup disk without the ODBC
drivers I
> originally had.
> b. The auto review included CRYSTL16.OCX and about 12 related DLLs but
this list is
> wrong for at least two reasons:
> 1. We need about 25 DLLs in all to support the Crystal RPT files
we deliver so I
> created a separate "GROUP" I called "Crystal Extras" and manually added
the DLLs
> Installshield omitted from the original list in the "SYSTEM GROUP".
> 2. Installshield violates one of their own rules by listing the
CRYSTL16.OCX
> before CRPE.DLL and the other Crystal DLLs. The order is apparently
important. I've
> learned to use QuickView to see the DLLs required by an OCX and make sure
these DLLs are
> listed in a group before the OCX.
> c. Because CRYSTL16.OCX requires CRPE.DLL, I moved the CRYSTL16.OCX to
the bottom of the
> SYSTEM group under the theory that this would satisfy the "ordering
rule". I've had
> mixed results with this approach. In one case, this seemed to work but
now I've
> discovered a case on a "virgin" Win95 machine it does not register the
CRYSTL16.OCX.
>
> No error message, no log file exists; so I discover later at runtime when
I click on a
> command button in my app I get a message: "Can't load (or register)
custom control
> CRYSTL16.OCX".
>
> I am at the point now where I am debating whether to try to upgrade to
Express Pro 1.1
> or shop for a install product that works well and is supported better.
I've hea
>