|
What
the heck is "dll hell"?
By trying to activate any of
our (or any other for that matter) software you get an error
message, something like, "NCTAudioRecord2.dll" not
registered..." this means that a supporting dll file was not
properly recorded/ registered within the Windows Registry during
the setup/ install process or for some other reason (such as you
have installed then maybe uninstalled similar software that uses
the same supporting files).
Most of you have probably experienced DLL Hell, though you may not
have heard of it described as such. If not, you've probably heard
horror stories from friends or colleagues.
The story goes something like this:
Ring ring, ring ring...
"Good afternoon, Code-it Software, Mike speaking. How can I
help?"
"Uhm, your program doesn't work on my system anymore."
"What seems to be the problem?"
"I don't know - it was working yesterday. There's an error
message that pops up saying a file is not registered - it just
doesn't work and I am a registered user."
Congratulations. You've just become another victim of DLL Hell.
The short of it...
"All it takes is a single DLL, VBX or OCX to be missing, or
present in an older version... for an application to fail."
Most likely, another program installed an older DLL, VBX or
ActiveX file on their system. OR maybe a newer, but incompatible
version. OR a conflict due to an incompatible DLL already loaded
in memory OR the PATH environment setting changed. OR the file was
not properly registered in the registry OR a required file is
missing OR you installed software that uses the same supporting
file(s) then you did an uninstall OR many other reasons!
As you can see, you can literally spend HOURS trying to figure out
what is wrong with your machine, and why the application will no
longer run. Probably, yet another reason to consider running Linux
to get away from the Windows Registry stupidity?
It is not unusual for users to reinstall software - either during
a system upgrade or to change configurations. In many cases users
would install software that included an older version of a dll
(i.e. commdlg.dll) on a system that already contained a newer
version. This would cause the more recently installed version to
replace the newer version. As soon the user attempted to run the
program that required the newer version, problems would occur
ranging from operational difficulties to general protection
faults.
There are hundreds of DLLs, VBXs and OCXs that may be shared by
literally thousands of applications. All it takes is a single DLL,
VBX or OCX to be missing, or present in an older version (or even
an incompatible newer version), for an application to fail.
Now you kind of know what might happen to make this software no
longer run. Here's most likely all you'll have to do to get it
back.
Click START >CONTROL
PANEL>ADD or REMOVE PROGRAMS>THE PROGRAM NAME>CHANGE
When the Repair Wizard
activates (screen shot below) - merely click the REPAIR button.
This will re-register all the supporting dll files, for the
selected software, within the Windows Registry.
If for some reason this
process does not work - do an uninstall then re-install the setup
file. If you need to re-download the most current setup file (you
failed to back it up) then email mb@code-it.com
for support. Please include some "proof of registration"
(i.e. your order number, copy of receipt, etc.).
|
