本文提供了解决在Windows CE应用程序中使用LoadLibrary加载动态链接库时遇到错误代码193的方法。通过分析依赖关系和导入导出函数，可以定位问题并找到解决方案。
Your app is trying to load a DLL either explicitly by calling LoadLibrary or implicitly by linking with the associated static linked library and it fails with error code 193, "The specified module could not be found" or a message that indicates that the app isn't a Windows CE application.
The possible causes of this are:
- The dll isn't a built for Windows CE
This happens when taking a dll from Big Windows (NT, XP, Vista) and trying to use it on a Windows CE device. - The dll isn't built for the processor family
This happens when taking a DLL that was built for a different processor than the target processor - Another dll that the dll needs to load isn't available
This happens when the DLL that you are loading then loads another DLL and there is a failure when that DLL tries to load another DLL that fails. - If a function that is needed isn't in the dll.
This happens if the dll on the system isn't the same as the the one that was being built when the lib that you linked to was created. It is sometimes a symptom of using the wrong SDK for your target.
There are other tools that you can use, but I usually use Dumpbin to view information about the Application or DLL. Dumpbin /DEPENDENTS file.dll will tell you which DLLs the file needs to implicitly load.
Example Dumpbin /DEPENDENTS:
Which tells us that Explorer.exe needs to successfully load ole32.dll, OLEAUT32.dll, commctrl.dll, ceshell.dll, shcore.dll, IECEEXT.dll and COREDLL.dll. But that isn't the whole story, we would need to do the same for each of those dlls to determine if they also have dependents.
You can also use dumpbin to determine which functions are used from the dlls. Dumpbin /IMPORTS file.dll will show the DLL and the functions:
Example Dumpbin /IMPORTS explorer.exe (although I left some out for brevity)
扫一扫
2037
到【灌水乐园】发言
Your Comments.
If you copy your DLL or EXE inside the %FLATRELEASEDIR% of your CE OsDesignand open it inside dependency walker it will report all the DLLs needed by your executable and all its dependencies and the functions liked by each module (useful to understand if you need to add some component that add their APIs to coredll).
Bruce