How to "register" a dll, or other file?

[Warren C. E. Austin]

A recent "hotfix" evidently replace the Windows Media dll in both "System32" and "DLLCache" but failed to register the change; consequently I'm getting an error that states something to the effect that WMS is expect version ?? whatever of the dll, but finding only the newer version, and cannot load. It advises I have to let my browser open and download WMS all over again. That's bizarre. I've seen here before the Run" syntax for registering a dll, but a search is not bringing that up, and I want to try that before going through the the other.

Thanks

Warren C. E. Austin
Toronto, Canada

 

[George Hester]

The way you register a self-register(ing) dll is like this. Start | Run | regsvr32 thefile.dll | OK. A few caveats. The thefile.dll must be in your path for this to work. If not you'll need to use %PATH%/thefile.dll. Second the dll must be self-register(able). Many are not those made with Visual Basic such as ActiveX dlls are and all ocx files.

 

[Warren C. E. Austin]

The way you register a self-register(ing) dll is like this. Start | Run | regsvr32 thefile.dll | OK. A few caveats. The thefile.dll must be in your path for this to work. If not you'll need to use %PATH%/thefile.dll. Second the dll must be self-register(able). Many are not those made with Visual Basic such as ActiveX dlls are and all ocx files.

Thanks George, I knew it was something like that but could not be certain that it was "regsrv32" that I needed to use.

Unfortunately that has not solved the problem, so I guess I'm gonna have to bite the bullet and download, and install, WMS all over again; but, not today. The file I needed WMS to view can wait ... being one of those inconsequential little bits of fluff.

Warren C. E. Austin
Toronto, Canada

 

[George Hester]

regsvr32

 

[Guest]

I also have a question:

I tried to register some .dlls and .ocxs on the Microsoft Register Server, but I keep getting and error that the Register Server failed. It only seems to happen to one workstation that is running XP. I tried looking this up on the Knowledge Base, but the only article I found showed that the user that was trying to register did not have admin rights. I am signed in with an admin password that has full control of the hard drive. Besides, I can remove things from the registry with that ID/password, so it must have sufficient rights. Any ideas?

Any assistance you could give me would be greatly appreciated.

 

[George Hester]

First off regsvr32 file.ocx should never fail. The reason is ocx files are
usually made by Visual Basic and ActiveX (dll and ocx) made by Visual Basic
are by default self-registering; ie regsvr32 registers them. If the dll is
not self-registering then either the CLSID info is hard-coded to the
registry or it is not necessary. Yes the issue why regsvr32 may fail is
that the user doesn't have the necessary permissions to write to the
registry other then dlls as I described above. Normally local Admin rights
are sufficient to rule this particular issue out.

If all looks as it should and in that machine the dll cannot be registered
(regsvr32) but transporting that file to another machine and regsvr32 there
succeeds then well, I don't know honestly. All I can guess is that the COM
on that machine is messed up.

--
George Hester
__________________________________

I also have a question:

I tried to register some .dlls and .ocxs on the Microsoft Register Server,

but I keep getting and error that the Register Server failed. It only seems
to happen to one workstation that is running XP. I tried looking this up on
the Knowledge Base, but the only article I found showed that the user that
was trying to register did not have admin rights. I am signed in with an
admin password that has full control of the hard drive. Besides, I can
remove things from the registry with that ID/password, so it must have
sufficient rights. Any ideas?

Any assistance you could give me would be greatly appreciated.

| regsvr32 thefile.dll | OK. A few caveats. The thefile.dll must be in
your path for this to work. If not you'll need to use %PATH%/thefile.dll.
Second the dll must be self-register(able). Many are not those made with
Visual Basic such as ActiveX dlls are and all ocx files."System32" and "DLLCache" but failed to register the change; consequently
I'm getting an error that states something to the effect that WMS is expect
version ?? whatever of the dll, but finding only the newer version, and
cannot load. It advises I have to let my browser open and download WMS all
over again. That's bizarre. I've seen here before the Run" syntax for
registering a dll, but a search is not bringing that up, and I want to try
that before going through the the other.