How do you know which dll's are already registered?

[weigoldk]

Is there a Win XP command (not add on utility) to tell whether a dll or ocx is already registered?

 

[bcastner]

No. Not base install utilites. If you installed the DDK and other tools you can come close.

See this discussion:

http://www.installsite.org/pages/en/tt_app.htm

Consider the underlying problem: many DLLs are self-registering. Many DLLs are not loaded unless needed, so their registration is on-the-fly. And they are unloaded when not needed if programmed properly. (Their registration status is lost).

Finally, there is the issue of where the registration information is kept. It is not in a single database. Consider if you will the following trace of the following command (this is XP SP2 only):

iexplore.exe /rereg

%11%\actxprxy.dll
%11%\asctrls.ocx
%11%\browseui.dll
%11%\browseui.dll,NI
%11%\cdfview.dll
%11%\comcat.dll
%11%\comctl32.dll
%11%\corpol.dll
%11%\cryptdlg.dll
%11%\digest.dll
%11%\dispex.dll
%11%\dxtmsft.dll
%11%\dxtrans.dll
%11%\hlink.dll
%11%\iepeers.dll
%11%\iesetup.dll
%11%\imgutil.dll
%11%\inetcpl.cpl
%11%\inetcpl.cpl,NI
%11%\initpki.dll
%11%\inseng.dll
%11%\jscript.dll
%11%\licmgr10.dll
%11%\mlang.dll
%11%\mobsync.dll
%11%\msapsspc.dll
%11%\mshta.exe
%11%\mshtml.dll
%11%\mshtml.dll,NI
%11%\mshtmled.dll
%11%\msident.dll
%11%\msieftp.dll
%11%\msnsspc.dll
%11%\msr2c.dll
%11%\msrating.dll
%11%\msxml.dll
%11%\occache.dll
%11%\oleaut32.dll
%11%\plugin.ocx
%11%\pngfilt.dll
%11%\proctexe.ocx
%11%\scrobj.dll
%11%\sendmail.dll
%11%\setupwbv.dll
%11%\shdocvw.dll
%11%\shdocvw.dll,NI
%11%\tdc.ocx
%11%\urlmon.dll
%11%\urlmon.dll,NI,HKLM
%11%\vbscript.dll
%11%\webcheck.dll
%11%\wininet.dll,NI,HKLM

Note that when called, most of these DLLs and OCX files self-register. Note as well the NI and HKLM parameters. This indicates that the registration with an I parameter is not user specific to the registry entry involved in special cases, that a specific registry hive is being asked for the registration.

Now I need to ask: what specific issue with DLL registration are you trying to solve? Perhaps DUPS.EXE from Microsoft will resolve the issue:

http://support.microsoft.com/kb/q247957/

 

[weigoldk]

Thanks for all of your help. This is all great information.

We are running a specialized software that is coming up with "filename.ocx" missing error. The software vendor says the error occurs because the ocx is not registered on the PC.

I manually register it and still receive the error. I wanted reassurance that it was indeed registered.

Thanks again.

 

[bcastner]

All OCX files self register.

The OCX needs to be placed in a different folder, or perhaps multiple folders. It literally is not being found when called.

The Microsoft Dependency Walker tool should be able to identify the issue. The quick fix is to place the needed OCX inside the folder of the application as a copy.