02-26-2007 09:38 AM
02-26-2007 09:36 PM
The following cases are typically thinkable for a DLL that may not work correctly on the target PCs, when you have just copied the DLL:
1)DLL is built as a COM DLL, but not "registered" on the target PC.
2)DLL has some dependency to other DLLs (such as 3rd party components), but they do not exist or not correctly installed on the target PC.
3)DLL has some dependency to specific Windows version, but the target PC OS is different.
4)DLL is build as a legacy non-COM DLL but its location is not specified by PATH environment variable. (This case is not thinkable in your case because you copied the DLL into Windows/System32 directory.)
Is any case matched?
There is a good tool, which checks DLL's dependency. It may help for your problem.
http://www.dependencywalker.com/
02-27-2007 03:30 AM