05-06-2007 07:53 PM
05-07-2007
09:16 AM
- last edited on
08-11-2026
09:04 AM
by
Content Cleaner
Hi Balaji,
Typically that message means that your DLL probably has dependency DLLs that it can't load into memory. You wouldn't see this during compile time since finding those child DLLs occurs by Windows at run-time.
Usually what I do in this case is to use a 3rd party tool called Dependency Walker (free at www.download.com) which shows DLL dependencies. Any DLL that your "top-level" DLL requires to run will be listed here. You will see references to OS-specific DLLs (kernel32.dll, user32.dll, gdi32.dll, ntdll.dll, etc) but don't focus on them but rather the ones that do not come with the OS that are required.
The thing to remember about finding these child DLLs is what algorithm Windows uses to locate the dependences.
Hope this helps and let me know if you still have trouble.
Best Regards,
05-08-2007 08:34 PM