WinCE failed to load the handwriting library when debugging a handwriting IME

A problem with loading a handwriting library when debugging a handwriting IME fails  WinCE6.0  uses this handwriting input method  SDK  makes a separate handwriting input program a (mfc dialog  framework). Normally, it can be used normally. This  A  program, using the  LIB  method to load this handwriting  sdk. The program  B ,a  program does not run after you run a handwriting entry in a area. This handwritten  sdk is also used in the suspect  B  program, causing loading conflicts. But think about program  B  and program  A  should run in different process space, and finalize program  B  do not use this handwriting. Further testing is found if the program  A  run first, then program  B  program. Although  B  works correctly, it cannot be recognized after handwriting is entered.   Because  A  programs do not run at all after the  B  program runs, you cannot debug to analyze the cause of the problem. Again, I decided to change the way the  A  program calls handwriting  SDK  from static loading to dynamic loading. Analysis  A  program, found only to call the  4  handwriting  SDK  program. Use  loadlibrary ()   load  DLL  and  getprocaddress ()   Load this  4  function (1)   Do not run  B  program,4  function loading is successful, handwriting function can be used normally, (2)   before running  B  program, found that there are three function load is no problem, one of the functions cannot be loaded successfully, GetLastError ()   The error is:  87 (parameter is incorrect).   After modifying to dynamic loading, test run  A  program before running  B  program. And the previous result is the same as the handwriting of the,b  program is not recognized. Re-test, the  A  program in the handwriting  SDK  initialization code deleted, first run  a, then run andnbsp b  program,b  the same way that handwriting recognition is not possible. At this point, the problem has not been resolved.   View this  B  program and discover that it does not use this hand input method. However, the input method used is exactly the same as the name of the  DLL  of the handwriting input method and the function in dll . The  A  program uses this handwriting  SDK  dynamic library  DLL  Renaming, again testing Discovery  A  programs and  B  programs can coexist perfectly. In this step, the problem has been solved, but the root cause (i.e. parsing) of the problem is not yet understood. The key to the problem is why does the function fail to load when the function of the  A  program dynamically loads  DLL  in the run  B  program? Two separate process space, why conflict?

WinCE failed to load the handwriting library when debugging a handwriting IME