Yoda
11-14-2001, 03:08 AM
A while ago someone came up with the following helpful tip :
When you do a lot of registering of DLL's, you can put regsvr32.exe in your Send to folder. That way you can just right click a dll and then send it to regsvr32 to register it
I thought this was a very valuable trick, and started using it right away. Until I noticed something yesterday :
I had a DLL called UniversalInterface.dll which I had to register, so I right clicked it, and sent it to regsvr32. Done. The programs referencing the dll however would not run. Not knowing what was the matter, I decided to unregister and reregister the dll, this time using the command prompt. Now everything worked.
I decided to find out why the error had occured, and found the following : in my registry my UniversalInterface.dll was registered allright, but it was stored as Univer~3.dll - The send to didn't take the full (length > 8 chars) name !!
Now I don't know if it was my Windows NT conflicting or if the send to does this on every windows system, but nevertheless you have been warned. I spent about a whole day looking for the error, and ended my day with a major headache ...
Greetz all,
When you do a lot of registering of DLL's, you can put regsvr32.exe in your Send to folder. That way you can just right click a dll and then send it to regsvr32 to register it
I thought this was a very valuable trick, and started using it right away. Until I noticed something yesterday :
I had a DLL called UniversalInterface.dll which I had to register, so I right clicked it, and sent it to regsvr32. Done. The programs referencing the dll however would not run. Not knowing what was the matter, I decided to unregister and reregister the dll, this time using the command prompt. Now everything worked.
I decided to find out why the error had occured, and found the following : in my registry my UniversalInterface.dll was registered allright, but it was stored as Univer~3.dll - The send to didn't take the full (length > 8 chars) name !!
Now I don't know if it was my Windows NT conflicting or if the send to does this on every windows system, but nevertheless you have been warned. I spent about a whole day looking for the error, and ended my day with a major headache ...
Greetz all,