I know dll's need to be assigned a clsid, but I don't know how to do that or how to install the clsid's to the registry.

I've never tried it but here's the instructions that I have. HOW TO REGISTER A DLL/OCX Go to c:\windows\system and look for the file "regsvr32.exe". Find the DLL that you want to register and drag and drop it into the regsvr32 icon. You should get a message saying "Filename.dll registration successful" or something to that effect. Let us know if it works, please.

Mike, This is a good question and I, for one, am very interested in your reply. I would try it myself but unlike you, I do not have a specific .dll that needs to be registered. Please let us know.

Hi! I'm not sure what a "clsid" is, but this is how I register DLLs 1. rightclick the DLL-file 2. Open with Regsvr32 Basically the same as Mr DLL described

To "register" a dll file can be done via Run on the commandline : regsvr32.exe [path:]\filename.dll [CAUTION] This can be found on almost all download site of dll files. The question is why we commonly replace dll files without doing this. The reason is manifold. The main reason is that those particular dll files are already properly registered by the previous installation package of an application, and we simply replace them for whatever reasons. If dll files are currently used, you have to do it via SFC or simply to do it on reboot to Dos. Furthermore, it is not the only way to do it. Inf and ini are also instrumental. Now, the proper way and why to register dll files are complicated issues. Am afraid I may say stupid thing if I venture into it here. There is no necessary relation between CLSID and dll's. You can have a standalone application using its dll's. You can neither register whatever dll files. Regsvr32 will have to verify its DllRegisterServer entry point. So, if you have on hand a dll file you are not familiar with and that you know by whatever method that it is not registered, do you execute the above commandline? I would not do so.