Hi Gianni,
Embedded Wizard itself is a 32-bit application. Mixing of 32 and 64 bit code within one process is as far as I know not possible. So when the intrinsic DLL is working on one PC, then we can disclose the 64/32 bit as the possible reason.
I understood, that the not working system is 32 bit. Thus I deduce that the Windows versions on the three PCs are different. May be the 32 bit Windows is even older? If this is the case, it could be possible, that your intrinsic DLL is linked again other Windows system DLLs which are not available on this 32 bit system. For example, the Visual Studio runtime libraries. In such case the loading of the intrinsic DLL will fail because one of the referenced DLLs fail to load.
How can you proceed in this case? Two ideas:
Idea 1: In your Visual Studio Project, review the C/C++ Compiler setting 'Runtime library'. Select the version without DLL, e.g. in my Visual Studio 2012 I can select Multithreaded (/MT). In this manner, the generated intrinsic DLL will not depend on any extern runtlime library DLLs.
Idea 2: Use the command line tool dumpbin to display dependencies from your intrinsic DLL to other DLLs. The command is used as follows:
dumpbin.exe /dependents ExternBitmapLoader.ewi
The command dumpbin belongs to Microsoft Visual Studio. The command displays a list with DLLs referenced from the Intrinsic DLL. In my case, when I do this, following outputs appear. Please note the both DLL names. These are necessary to exist on the target PC in order to load the intrinsic DLL:
Dump of file ExternBitmapLoader.ewi
File Type: DLL
Image has the following dependencies:
MSVCR110.dll
KERNEL32.dll
Hope it helps you further.
Paul