• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 384
  • Last Modified:

3rd party OCX's will not register in Windows XP SP2

I have written and rely upon a few Visual Basic 5.0 programs which use third party OCX's, e.g. Crescent Quikpak and others.  After installing Windows XP SP2 on new machines, those OCX's will not register when I run the installation routines for my programs.  

I have tried to register the OCS's manually (such as REGSVR32 CSCMD32.OCX) with no success.  XP reports failiure to register.  

After I uninstall XP SP2, the problem ends and my installation program registers the OCX's with no problem.  

I assume that there is some sort of "security' feature in XP SP2 that comes into play.  Does anyone know of a workaround that would allow me to use SP2 with this problem?
1 Solution

  You should check this out regarding some files that need to be
  updated so that it will install correctly with Service pack 2.
  It mentions the  CSCMD32.OCX file specifically.

  Good Luck.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now