DLL reference path

I am currently working on incorporating DLLs into my model. However, I am facing the following issue:

Lets say I have 2 DLLs - DLLA.dll and DLLB.dll. DLLA calls DLLB at runtime. Both DLLs reside in a folder, lets say, C:\DLLFolder. When I call DLLA from FlexSim (by providing the above path), it fails to load as DLLB is not found. It loads correctly only when DLLB is in one of the paths where FlexSim looks. For example, <FlexSim installation folder>/program or folder where the model is saved.

I would like to know if there is a way to add a path that FlexSim can look at when it deals with DLLs?

I am attaching a test solution (VS2010) that will essentially replicate this scenario.

1. Extract attached zip file.

2. Open solution inside DLLMaker folder. This solution creates 2 dlls – DllMaker.dll and DLLB.dll once the solution is built successfully.

3. DllMaker is called from FlexSim with an input as shown in testDLLCall.fsm. DllMaker will in turn call DLLB. However, if DLLB is not in the same folder where testDLLCall.fsm, FlexSim will report DllMaker failed to load.

Thanks in advance.

Unfortunately I don't think there's a way to customize the windows search order dynamically at run-time. I usually refer to this msdn topic to figure out what can be done.
http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx

Originally Posted by Anthony Johnson

Unfortunately I don't think there's a way to customize the windows search order dynamically at run-time. I usually refer to this msdn topic to figure out what can be done.
http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx

Thanks for the response Anthony.

From the article in the link, it says dlls in the windows PATH variable should work. I tried that by copying the DLLB to system32 folder. Still have the same issue. Any idea on what I am doing wrong?

Originally Posted by Ramesh Pinn

Thanks for the response Anthony.

From the article in the link, it says dlls in the windows PATH variable should work. I tried that by copying the DLLB to system32 folder. Still have the same issue. Any idea on what I am doing wrong?

I am able to get this working by placing the DLLs in Windows\SysWOW64 folder. Since I am using a 64-bit OS, apparently Microsoft in all its wisdom decided to that SysWOW64 folder is the place to hold all 32-bit DLLs while system32 will host 64-bit dlls. Read this for more information on Microsoft's amazingly intuitive naming conventions: http://www.forceflow.be/2012/04/04/t...indows-64-bit/