I wrote a program and created installation disks with Visual Basic 4.0.
My program (Win95
32 bit) has ocx files from other than Crystal Reports.
When the program installs on a computer without VB or Crystal, the
following error shows:
An error occurred while registering c:\windows\system\crystl32.ocx.
Please,Help me !!!!!!!!!
regsvr32 crystl32.ocx
regsvr32 is in the System directory. Look at the error message that
is displays. If it is 0x00000485 then you are probably missing some
dependencies. If this is the case, check out artical Q160018 in
Microsoft knowledge base. It isn't a perfect match, but it has
information that will help you figure it out.
I had a similar probem with an ocx that I wrote. I found that the
following dll's were missing: MFC42.DLL and MSVCRT.DLL. These were
added to my system when I installed VC++ 5.0.
-Scott
On 7 May 1997 10:24:26 GMT, "Francisco Ballesta Camero"
If you built your application under NT4.0, Workstation or Server, you
will need the newer MSVCRT.DLL, MSVCRIT.DLL, and MSVC40.DLL as detailed
in Q160018 (my thanks to Scott for that).
But, what they don't say is, you will also need CO2C40EN.DLL and
IMPLODE.DLL, which are also in the WINNT\SYSTEM32 directory.
I think the CO2C40EN.DLL is the country specific language file for
MSVCRT40.DLL, but don't quote me on it, and don't ask me what
IMPLODE.DLL is for!
Once I copied these files I found that crystl32.ocx registered correctly
with regsvr32.exe and also during installation using the Setup Wizard.
The only problem I found was that SETUP.EXE wouldn't run without the new
MSVCRT.DLL, MSVCRIT.DLL and MSVC40.DLL, which of course doesn't exist
under Windows95, so if anyone knows of a way to get the Wizard to use
these new DLLs as dependencies of the actual SETUP.EXE created, please
let me know.
Oh yes, in case you're wondering, I did try the installation on a
WinNT4.0 workstation, and that also didn't have the 2 additional DLLs,
but at least it told me, so that's how I found them.
Hope this helps out quite a few people...
Regards...Andrew
USESXX=IMPLODE.DLL
USESXX=CO2C40EN.DLL
USESXX=OC30.DLL
USESXX=MFCANS32.DLL
where XX = next available number.
This may be the solution to your problem.
Lee (U.K.)
Francisco Ballesta Camero <fbal...@a2000.es> wrote in article
<01bc5ad2$3a2a1640$4d63...@BALLESTA.a2000.es>...